Most stores are maintained on a "when it breaks, find someone" basis. That works right up until it breaks on a Friday evening before a sale.
What should be under watch
- Availability. An automated external check: the site responds, returns the expected status code, the certificate has not expired. The cheapest element and the most useful.
- Disk space. The most common cause of sudden failures is neither an attack nor load, but simply running out of space: the database stops writing and orders stop saving.
- Backups with verified restores. A copy you have never restored from is a hope, not a reserve.
- Security updates — applied after testing on a copy, not blindly on the live site.
- Error logs. A slow rise in error counts is visible on a chart long before it becomes an outage.
Why prevention costs less
Not because an hour of work is cheaper, but because most incidents simply do not happen. The disk does not fill up unnoticed, the backup exists and has been tested, the vulnerability is closed before anyone exploits it.
Emergency repair is always more expensive: it happens in firefighting mode, often at night or at the weekend, and comes with lost orders for the duration of the outage.
What to agree on up front
- What the monthly allowance covers and what is quoted separately. New feature development normally sits outside it.
- Response time to an incident — and whether it differs during and outside working hours.
- Who holds access and where credentials are stored.
- Reporting: what was done during the month and what should be done next.
When occasional call-outs are enough
If the store is small, changes rarely and a day of downtime is not critical, a retainer may be unnecessary. The minimum worth having in that case: configured backups and downtime alerts.
If the store is your main sales channel, continuous oversight makes sense: the managed store care service. Platform-specific options: OpenCart, WordPress, server.
