Everything in Monitoring Plan, plus a monthly pool of expert hours to actually handle the small things that keep a PrestaShop store healthy — config, cache, cron, module settings and obvious PHP errors — with a 3 business-hour response when the storefront or checkout goes down.
Includes 2 hours of expert work per month (cap 6h), a live dashboard and a monthly report showing exactly where the time went. €490/month, billed monthly, cancel any time.
Your PrestaShop store, monitored and handled
\nStore Care Plan is the plan most healthy stores actually want: continuous monitoring plus a real person who fixes the small things before they pile up. It keeps everything in Monitoring Plan — uptime, cron and core-health watching with alerts — and adds a monthly pool of 2 expert hours for the configuration, cache, cron and module work that otherwise sits in a backlog until it becomes an outage. It is the difference between knowing your cron broke and having it quietly repaired the same day. €490/month, billed monthly.
\nWho it is for
\nAny owner who wants peace of mind and a safe pair of hands without hiring a developer on retainer. It is the right fit when you do not have a steady stream of large projects, but you do have a constant trickle of small jobs — a module setting to change, a cache to clear properly, a cron to repair, a PHP notice flooding the log. Works on PrestaShop 1.6, 1.7, 8 and 9, single or multistore, on any host.
\nThe watch and fix distinction
\nThis is the line between Core and Monitor, and it is the whole point of the upgrade. Monitor tells you the cron broke; Core repairs it within the included hours. We do not just escalate an alert back to you — we triage it, fix what falls inside the monthly pool, and tell you honestly when a job is bigger than the hours allow so you can decide on overage or a separate quote. You get a person, not just a dashboard.
\nWhat the 2 hours actually cover
\nThe hours are for genuine maintenance, not open-ended development. Typical work: configuration changes, safe cache and OPcache clears, cron repair, module settings and minor module conflicts, fixing obvious PHP errors and warnings, small template tweaks, and applying low-risk updates. The pool is 2 hours/month with no rollover, and we can flex up to a 6-hour cap in a heavy month; anything beyond is billed in 15-minute increments or quoted as a project. We log every minute so you always see where it went.
\nPrestaShop-native fixes, across every version you might run
\nThe value of a maintenance pool is only as good as the hands using it, and PrestaShop maintenance has its own traps. A “clear the cache” request is not the same on PrestaShop 1.6 as on a Symfony-based 9.x back office, where raw-deleting the admin container can take the back office down. A module conflict throwing a 500 on one controller often traces to an autoloader skew or a hook that another module hijacked. We fix these the right way for your exact version — 1.6, 1.7, 8 or 9, single or multistore — because we build and maintain modules across all of them and run a PrestaShop store ourselves. You are not paying for someone learning the platform on your time.
\nWhat we deliberately do NOT do here
\nStore Care Plan is maintenance, not a disguised dev shop. Building a new feature, a custom module, a theme migration, a full performance or security remediation, or incident cleanup after a compromise are scoped separately — we will tell you the moment a request crosses that line rather than quietly burning your hours on something that needs a real project. That honesty is what keeps the relationship working: you always know whether you are getting maintenance or a build, and your monthly hours are never silently consumed by something that should have been a quote.
\nWhere it fits
\nCore is the operational backbone of the range, and the right floor for most stores that want things actually handled rather than just watched. Bolt on SEO Care Plan for monthly organic-health accountability or Growth Care Plan for tracking, feed and ads hygiene — both are specialist plans that layer on top of Core rather than replace it. Or get all three under one accountable team, with a single priority list and a quarterly strategic review, in Complete Care Plan. A one-off audit (SEO, performance, security) is a sensible first step if there is a backlog to clear before monthly care begins. See the full range under Expert Services.
-
ReferenceCARE-CORE
-
Service typeCare plan (monitoring + fixes)
-
DeliverableLive dashboard + monthly report (with hours ledger)
-
Access neededScoped back-office account; host read where needed
-
PrestaShop versions1.6 / 1.7 / 8 / 9
-
NDA / DPAAvailable on request
-
Included hours2 hours / month (cap 6h, no rollover)
-
Monthly cap6 h / month
-
Response SLA3 business hours, P1
-
Live dashboardIncluded
-
Monthly reportIncluded
-
BillingMonthly, no minimum term, cancel any time
-
Emergency coverBusiness hours
-
Price€490 / month
-
ResponseP1 within 3 business hours (Mon–Fri 09:00–18:00 CET)
-
Uptime target99.5% monitored (hosting outages excluded)
What customers say about us
Be the first to share your experience with this module.
Write a Review
Monitoring plus a monthly pool of expert PrestaShop fixes for cron, cache, config, minor module issues and incidents.
Store Care Plan includes everything in the Monitoring Plan, then adds hands-on maintenance hours and a human P1 response. It is the operational floor for stores that want small problems handled instead of merely reported.
Monitoring inherited from Monitoring Plan
The live health layer stays active while fixes are handled.
- Storefront and checkout uptime with alerts
- Cron, core-health, fatal-error and HTTP 500 detection
- SSL/TLS and performance-regression alerts with live dashboard
2 hours/month of expert work
Small operational fixes that keep the store healthy.
- PrestaShop configuration, SEO/URL settings, email, shipping and tax toggles
- Cache, OPcache, CCC hygiene, cron repair and safe clears
- Module settings, minor conflicts, obvious PHP warnings and small template/text tweaks
Incident and reporting discipline
A human response, clear boundaries and a record of the work.
- P1 triage and in-scope repair within the hours pool
- Out-of-scope work quoted before it burns maintenance time
- Monthly actions taken, incident log, hours ledger and watch list
How it works
-
Onboarding Setup weekWe set access, monitored paths, cron inventory, alert recipients and change-approval rules.
-
Monitoring ContinuousMonitoring checks run continuously for uptime, checkout, SSL, cron, fatal errors and regressions.
-
Monthly work MonthlyWe use the hours pool for approved fixes, config, cron, cache and minor module work.
-
Incident response As neededP1 incidents get a human engaged within 3 business hours, then fixed or escalated.
-
Report MonthlyYou receive actions taken, hours used, incidents, watch list and next steps.
Plan boundaries
The Store Care Plan handles real maintenance, but it is not unlimited development or incident cleanup.
A maintenance month with an hours ledger
A Store Care Plan report might show: cron stopped and feeds stale - diagnosed and repaired in 35 minutes; module conflict caused 500 on one page - settings corrected in 50 minutes; OPcache/CCC hygiene performed in 20 minutes. Larger work such as a new loyalty feature, Core Web Vitals remediation or Magecart cleanup is flagged for separate scope.
FAQ
What do the 2 hours cover?
Do unused hours roll over?
What does P1 response promise?
What if work is bigger than my hours?
Is there an uptime guarantee?
Related services
Loading feature requests...
Easy return - no questions asked
Install, set up and take profit
Priority Help & Satisfaction Over Sales