PrestaShop Store Care & Maintenance Plan combines shop monitoring, repairs and monthly work by the same technical caretaker. You provide access and initial priorities; monitoring and backups are configured within 3 to 5 working days.
An alert leaves someone needing to investigate. Here failures in availability, scheduled work or error records become repair tasks, with critical checkout and payment problems prioritised even outside normal working hours.
The monthly plan has no fixed term and includes two expert hours, flexing to six in busy months; unused hours expire. Work beyond six hours needs prior approval and separate billing. Redesigns, migrations, new features and third-party costs are excluded. Daily encrypted off-site backups and restore tests support recovery.
A monthly report records repairs and time against named tasks, giving you a maintenance history with accountable work.
Summary of what the Store Care & Maintenance Plan covers
PrestaShop Store Care & Maintenance Plan combines continuous store supervision with people who repair what the supervision finds, billed monthly with no fixed term. The same technical caretaker learns the shop, and every included minute of expert time is assigned to a named task.
- Continuous monitoring of availability, scheduled work and error records, with deviations repaired rather than reported
- Two expert hours each month, flexing up to six when the month demands it
- Security checks, urgent fixes, daily encrypted off-site recovery copies and restore tests
- Speed work measured before and after on the pages that earn money
- Critical sales faults at the front of the queue, including outside normal working hours
- A one-page monthly report and a clean handover whenever the plan ends

What is watched before it reaches customers?
The plan continuously checks whether the shop answers, whether scheduled work completes and whether the store begins recording unusual failures. A deviation becomes an owned task: it is investigated, its effect is established and the repair is carried through, rather than leaving the merchant with another alert to chase.
This catches the quiet failures that later become visible ones. An order message that stopped leaving, a catalogue task that no longer runs or a growing stream of warnings is handled while the storefront still looks normal.

What fits into the monthly expert hours?
Two expert hours per month cover configuration changes, safe clearing of the shop’s internal working files, repair of scheduled tasks, module installation and settings, routine module and platform updates, compatibility checks, deeper conflict diagnosis, visible errors and small storefront corrections. The same technical caretaker learns the store, so recurring work begins with context rather than another introduction.
You choose the order of this work, the monitored store paths and the maintenance window. Every included minute is recorded against a named task, which turns the monthly pool into visible output and keeps a larger project from quietly consuming maintenance time.

How are security, recovery and speed kept under control?
Regular security checks look for known weaknesses, unsafe exposure and signs of malicious changes. Urgent security fixes are applied through a controlled process, and daily encrypted recovery copies are stored away from the shop. Restore tests prove that the copy works before an incident makes that question urgent.
Speed work begins with measurements on the pages that earn money. Slow database work, oversized images and heavy storefront resources are corrected with before and after evidence, so improvement means a faster customer path rather than a vague maintenance label.

What happens when the month gets busy?
The normal allowance is two expert hours and unused time does not roll over. A busy month flexes to a total of six hours, while anything beyond that is approved first and billed in fifteen-minute increments or quoted as a separate project. Critical unavailability, checkout and payment failures move to the front of the queue, including outside normal working hours, so a cosmetic correction never delays a broken sales path.
The boundaries are equally plain. Redesigns, migrations and new feature development are scoped and quoted as their own projects, hosting fees, domain and certificate costs and third-party module licences remain the merchant’s, and marketing, SEO and advertising data work belongs to PrestaShop Marketing Data & Growth Plan.

How does the plan begin, and what do you keep?
Onboarding needs your access details and a first priority list; monitoring and backups are configured within the first 3 to 5 working days, and the listed price is a monthly price from the first month onwards. The monthly one-page report shows what was watched, what changed, what was repaired and where every included minute went, with cause, corrective action and preventive step recorded for incidents.
The plan runs month to month and cancellation takes effect at the end of the paid period. On exit you keep the report history, the most recent recovery copy is handed over on request, and open recommendations remain listed with their priority, so the next caretaker starts from a map. The plan suits an established store with real orders and no in-house technical caretaker; a merchant who only wants to be told when something breaks is served by PrestaShop Uptime Monitoring & Alerts Plan, and monthly hours are not the funding route for a large one-off project.

-
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)
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 neededWe aim to provide a human response to P1 incidents within 3 business hours, then fix or escalate them.
-
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.
Related services
Is there an uptime guarantee?
There is a 99.5% monitored uptime target, excluding hosting and upstream provider outages.
How many hours do I get, and what if I need more?
Store Care Plan includes 2 expert hours per month. Hours don't roll over, and additional work is billed in 15-minute increments, with total monthly hours capped at 6.
How the hours are structured
- 2 hours included each month, your standing allowance for routine maintenance.
- No rollover. Each month starts fresh; unused time isn't banked. The hours are designed to keep your store current, not to accumulate a balance.
- Overage in 15-minute increments, if a month needs more than the included 2 hours, additional work is billed precisely, in quarter-hour blocks rather than rounded up to the hour.
- Capped at 6 hours. Total monthly hours are capped at 6, so even an unusually demanding month has a predictable ceiling.
What the hours are for, and what they're not
The hours cover the small, recurring work that keeps a PrestaShop store healthy: configuration, cache, cron, module settings and obvious PHP errors. They're deliberately scoped to the steady maintenance that otherwise piles up.
A larger piece of work, a new feature, a custom module, a data migration, a redesign, falls outside the monthly hours and is scoped and quoted on its own. That keeps the monthly allowance focused and your bill predictable: routine upkeep inside the plan, projects priced transparently and approved before they start.
Tracking it all
Every action and the hours it consumed are recorded on your live dashboard and summarised in the monthly report, so you can see exactly how the 2 hours were used and whether any overage applied. If you consistently need more than the cap allows, that's a clear signal it's worth scoping a dedicated engagement rather than stretching a maintenance plan.
We tell you before undertaking work beyond your hours and either use agreed overage or quote it as a project.
What's included in Store Care Plan?
Store Care Plan keeps your PrestaShop store healthy and gives you a real person to handle the small things that otherwise pile up. It's the practical middle of our Care Plans: monitoring plus a monthly pool of expert hours, so problems are both spotted and dealt with.
What's included
- Everything in Monitoring Plan, continuous uptime, cron and core-health monitoring with immediate alerts, so you always know when something is wrong.
- Security & performance checks, module and configuration warnings plus regression watch, so a change that quietly degrades your store gets flagged.
- 2 hours of expert work per month (cap 6h), the config, cache, cron and module fixes, and obvious PHP errors, that otherwise accumulate into a backlog.
- Live dashboard + monthly report, health scores, incidents, actions taken and hours used, so you can see exactly where your time went.
How the hours work
Store Care Plan includes 2 expert hours per month. Hours don't roll over, and anything beyond them is billed in 15-minute increments up to a monthly cap of 6 hours, so a busy month never runs away from you. The hours are aimed at the small, recurring maintenance that keeps a store running; a larger project (a new feature, a custom module, a migration) is scoped and quoted on its own.
Service targets and reporting
Store Care Plan carries a 99.5% monitored-uptime target and targets a response within 3 business hours for a P1 incident, storefront or checkout down, during the business window (every day, 08:00–20:00 Polish time). The monthly report ties it together: it shows your health scores and their trend, the incidents that occurred, the specific actions taken on your store, and how the monthly hours were used, a transparent record rather than a vague “all good”.
Store Care Plan suits owners who want their store watched and the routine work quietly handled, without raising a separate quote every time something small needs attention. If your priority is search visibility instead, pair it with SEO Care Plan, which focuses on technical SEO hygiene.
What's the response time if my store breaks?
For a P1 incident, your storefront or checkout down, Store Care Plan targets a response within 3 business hours (every day, 08:00–20:00 Polish time). The plan also carries a 99.5% monitored-uptime target, so problems are caught and acted on quickly rather than left to linger.
What P1 means
P1 is reserved for the issues that directly stop you trading: your storefront not loading, or checkout failing so customers can't complete an order. These are the highest-priority events because every minute matters for a PrestaShop store, and they're what the response target is built around.
How response works alongside monitoring
Store Care Plan includes everything in Monitoring Plan, with alerts when monitoring checks detect a P1 event. The 3-business-hour response target then governs how quickly a person on our team responds to the incident during the business window. It is a target for a human response, not for the start of hands-on work; there is no guaranteed start or fix time.
An honest word on uptime
The 99.5% monitored-uptime target is exactly that, a target we monitor against and report on, not a promise of zero downtime. No honest provider can guarantee a store will never go down. What Store Care Plan does commit to is fast detection and a defined response window, plus a transparent record of incidents and how they were handled in your monthly report.
Remember that the monthly resolution work draws on your 2 expert hours (cap 6h, no rollover); a genuinely large recovery or project beyond routine fixes is scoped and quoted separately. The combination of continuous monitoring, a 3-business-hour P1 response target and a 99.5% monitored-uptime target means issues are surfaced and responded to quickly rather than discovered late and left to fester.
What kind of work do the monthly Store Care Plan hours cover?
The Store Care Plan monthly hours cover the small things that keep a store healthy: configuration, cache, cron, module settings and obvious PHP errors. It's the steady, unglamorous maintenance that quietly piles up otherwise and, left alone, turns into a much bigger problem.
Typical work the hours cover
- Configuration. Adjusting PrestaShop and module settings, correcting options that have drifted, tidying shop parameters.
- Cache, clearing and rebuilding cache when it's causing stale pages or odd behaviour, and resolving cache-related glitches.
- Cron, getting stalled or broken scheduled tasks running again so background jobs do their work.
- Module settings, correcting misconfigured modules and the small conflicts that surface after updates.
- Obvious PHP errors, resolving the clear-cut fatals and warnings that degrade a store.
What falls outside the monthly hours
Anything bigger, a new feature, a custom module, a theme change, a data migration, is scoped and quoted separately. That's intentional: it keeps the monthly hours focused on keeping you running smoothly, and it keeps your bill predictable, with larger work priced transparently and approved before it begins.
How the time is managed
You have 2 expert hours per month. Hours don't roll over, overage is billed in 15-minute increments, and the total is capped at 6 hours in a month, so even a heavy month stays predictable. Every task and the hours it used are logged on your live dashboard and summarised in the monthly report, so you can see precisely what was done and where the time went. If you find you're regularly hitting the cap on routine work, that's usually a sign it's worth scoping a dedicated engagement rather than stretching a maintenance plan, and we'll tell you so honestly.
Easy return - no questions asked
Install, set up and take profit
Priority Help & Satisfaction Over Sales
Who builds and maintains this module
Built and maintained by David Miller and mypresta.rocks. David Miller has worked with PrestaShop since 2013, and the company behind this shop has been registered since 3 December 2018. Every module in this catalogue is our own work, so your questions to support reach the people who wrote the code. The changelog on this page lists every update with its date.
More modules
Compliance & Legal
PHP2Shell: what PrestaShop shops should do about CVE-2026-109618 and CVE-2026-109619, even when they cannot upgrade
News & Updates
What's new at mypresta.rocks: September 2026
News & Updates
What's new at mypresta.rocks: August 2026
News & Updates
PrestaShop 9.2 native One Page Checkout: what it does and when you need more
News & Updates
Introducing Expert Services: PrestaShop audits before you buy another module
News & Updates

















