PrestaShop support is ongoing technical care for a store: updates, backups, uptime monitoring, incident response and an hourly budget for small development work. The difference between "help" and "support" is simple: help is a one-off fix when something breaks (PrestaShop help), while support is a model where the store is watched before anything breaks — and when it does, the response is measured in minutes, not days. For a store generating orders this is not a cost but insurance: standard care costs 300–1,500 PLN net per month, less than one hour of downtime on a good sales day.
Najważniejsze: PrestaShop support (technical care) covers: core and module updates, backups with restore tests, uptime and error monitoring, incident response within an SLA (typically 4–24h), small development tasks and reporting. Cost: 300–1,500 PLN net/month depending on scope; high-traffic stores with integrations: 1,500–4,000 PLN/month. When choosing a vendor, check: SLA scope, response time, hour limits, whether care covers integrations, and who is responsible for security.
What does good PrestaShop support include?
Technical care is a set of processes — not "keeping the server running".
- Updates — PrestaShop core (including security patches), modules, theme; compatibility checks before and tests after.
- Backups — regular file and database backups with periodic restore tests. A backup you cannot restore is not a backup.
- Monitoring — store uptime (24/7), load times, PHP errors, mail queue, payment and shipping webhook statuses.
- Incident response — within the SLA: ticket acknowledgement, diagnosis, repair; priorities based on sales impact.
- Security — vulnerability scanning, panel hardening, brute force and malware protection, incident procedures.
- Small development — an hourly budget for content fixes, minor modifications, promotion configuration.
- Reporting — a monthly report: what was done, what was found, recommendations.
The scope should be written into the contract — "care" without a defined SLA and scope is fiction.
Support models — what to choose for your store?
| Model | Scope | Cost (net/month) | For whom |
|---|---|---|---|
| Basic | Updates, backup, monitoring, response within 24h | 300–600 PLN | Small stores, simple sales |
| Standard | + response within 8h, small tasks (2h), report | 600–1,500 PLN | Stores selling daily |
| Premium | + response within 4h (or 24/7), integrations, development (4–8h) | 1,500–4,000 PLN | Large stores, marketplaces, B2B |
| Hourly | An hourly budget without a fixed fee | 80–200 PLN/h | Stores with occasional work |
Key questions when choosing: what exactly the SLA covers (response vs repair time), how many development hours are included, whether integrations (payments, couriers, marketplaces) are in scope, and what happens to unused hours.
Why care pays off — the simple economics
- Downtime costs more than care. A store doing 100 orders a day loses more during a 4-hour peak-season outage than a year of the standard package.
- Failures happen at the worst moments — pre-Christmas campaigns, Black Friday, payment operator API changes (repeatedly seen).
- Updates prevent more expensive problems — a security patch deployed on schedule is cheaper than malware removal and store rebuild (800–2,500 PLN + lost sales).
- Small tasks without a queue — care gives you "your" team that knows the store; a new vendor pays for onboarding every time.
Stores without care usually come back for help only when something breaks — and then the cost and risk are highest. Most companies switch to ongoing support after their first incident.
What should a support contract include?
- Scope and exclusions — what is covered and what is a separate project (e.g. large implementations, migrations).
- SLA with numbers — response and repair times for priorities (critical: store down; high: checkout/payments; normal: cosmetics).
- Access and security — who holds access, how it is stored, password and key rotation after the collaboration.
- Backup and restore — frequency, retention, location, testing schedule.
- Reporting — a monthly summary of work and store health.
- Termination terms — handover of access, repository, documentation and the customisation register.
The technical side of maintenance (what actually breaks and how to prevent it) is in PrestaShop help, and performance in PrestaShop performance optimisation.
Frequently asked questions
How is PrestaShop support different from technical help?
Help is a one-off fix of a specific problem (200–600 PLN net per ticket). Support is ongoing care: updates, backups, monitoring, SLA and a development budget for a fixed monthly fee. Support prevents failures; help puts them out.
How much does technical care cost?
Basic packages start at 300–600 PLN net per month; standard with faster response and small tasks is 600–1,500 PLN net; premium care with integrations and development: 1,500–4,000 PLN net per month. An alternative is the hourly model: 80–200 PLN/h with no fixed fee.
Is care worth paying for if the store works fine?
That is exactly when it is worth it — because care is mostly prevention: security updates, monitoring, backup tests. Stores that "work fine" and are not updated are the most common victims of attacks and failures after operator API changes.
What does an SLA look like in practice?
Response time (when a specialist acknowledges and starts diagnosing) and repair time (when the problem is solved) for priority classes. A good SLA for a store selling daily: critical within 4h, high within 8h, normal within 24–48h — with a clear ticket channel.
Does care cover content changes and new features?
Small tasks (banners, content, configuration, minor modifications) — usually yes, within the package's hourly budget. Larger implementations (new modules, integrations, rebuilds) are separate projects quoted by scope.
What happens to accesses after the collaboration ends?
An honest contract provides for handing over all access, the code repository, documentation and the customisation register, plus password and API key rotation. If a vendor "holds" access — that is a warning sign already at the negotiation stage.
Sources and tools
- PrestaShop — official support
- PrestaShop Build — updates and security
- PrestaShop DevDocs — documentation
- OWASP — web application security
- Google Search Central — site maintenance
👉 Want to put your store under ongoing care? See e-commerce integrations and PrestaShop store development in my offer — updates, backups, monitoring, SLA and store development in one place. Get in touch via the contact form or at kontakt@informatix.com.pl.
👉 Comparing support models? Check PrestaShop help, PrestaShop performance optimisation and PrestaShop implementation.
📖 See also: PrestaShop developer, PrestaShop modules and customisations and e-commerce store development. Ongoing care: technical care with SLA.