Store Sheriff → Who looks after your store
Who actually looks after a small online store?
Every WooCommerce and PrestaShop store needs the same unglamorous list done repeatedly: updates applied, backups taken and tested, security patches followed, a test purchase made now and then, and somebody to look when something breaks. There are only four realistic ways that happens. Here is what each one actually covers, how each one fails, and which size of shop it suits.
Who wrote this, and why that matters
This page is published by SwiftForge Web, who sell two of the four options below. So read it with that in mind — and notice that we recommend against our own agency retainer for most small shops, because at that size the maths genuinely does not work. The comparison is only useful if it is honest about where each option stops making sense.
The four models at a glance
| Model | What it really covers | How it fails | Suits |
|---|---|---|---|
| Do it yourself | Whatever you personally remember to do, when you have time. | Not through laziness — through the busy season. It stops exactly when the shop is doing well, which is when breaking it is most expensive. | Very small shops with a genuinely technical owner. |
| Freelancer on call | Fixing things once they have broken. Nothing preventative is scheduled. | You only ever buy emergency work, which is the most expensive kind, at the least convenient time. And one day they stop replying. | Shops with a reliable, available person and a tolerance for downtime. |
| Agency retainer | A team who know your code, planned maintenance, and someone accountable when it breaks. | Nothing — it works. It is simply priced for stores where downtime costs serious money, so below a certain size it is not rational spending. | Stores where a day offline is a genuine financial event. |
| Hosting with care included | The routine list — updates, backups, monitoring, SSL, plugin maintenance — bundled into the hosting itself. | It is routine care, not bespoke engineering. It will not rewrite your checkout or rescue a store that is already broken. | Small stores that need the basics done reliably, cheaply. |
Do it yourself
Perfectly viable for a small shop if the owner is technical and disciplined. The work is not difficult: apply updates on a copy first, check the copy still takes an order, then apply them live. Take a backup off the server. Restore one occasionally to prove it works. Buy something on your own store once a month, on a phone.
The reason it fails is not capability. It is that maintenance is never the most urgent thing on a Tuesday. It gets deferred during the quarter when sales are good, and the deferral compounds: skip updates for long enough and applying them stops being routine and becomes risky, at which point the rational move is to skip them again. That spiral is how almost every neglected store we see got there.
If you do choose this, the single highest-value habit is testing a restore. It is free, it takes an afternoon, and it converts your biggest unknown into a known.
A freelancer you call when it breaks
The most common arrangement, and the one that quietly costs the most. Break-fix means you only ever pay for emergencies — the most expensive work there is, bought under time pressure, usually at a weekend. Nothing preventative is ever scheduled, because nothing preventative is ever urgent.
It also has a specific failure mode that has its own page on this site: the freelancer moves on, and takes with them the only knowledge of how your store is put together. If that has already happened to you, start here instead: your developer stopped replying.
Even a few hours of planned time a month changes the economics completely, because it is the planned time that prevents the emergencies.
An agency on a retainer
This is the model that unambiguously works. A team that knows your code, maintenance on a schedule rather than on panic, staging to test on, someone accountable, and the ability to do real engineering when you need it.
The only question is whether it is proportionate. Retainers are priced for stores where an hour of downtime is measured in lost orders — SwiftForge Store Care, for instance, starts at $395 a month. For a store turning over a few thousand a month, that is a large share of margin spent on insurance against a risk that is real but modest. We would rather tell you that than sell it to you.
The honest rule of thumb: if a full day offline would be an inconvenience, you probably do not need a retainer. If it would be a bad month, you do.
Hosting with the care built in
The newest of the four, and the one most small shops have never heard of. The idea is simple: the routine list is not hard, it is just relentless, and relentless is exactly what you can bundle into a hosting plan. Monitoring, updates, backups, SSL renewals, plugin maintenance — done for every store on the platform, as a matter of course, rather than quoted per incident.
It is cheaper than a retainer for the obvious reason: it is standard care, not bespoke attention. Nobody is learning the specifics of your custom checkout. If your store needs real engineering, this is not that, and anyone telling you otherwise is overselling.
But for a small store whose actual problem is that nobody is doing the basics, it closes the gap that matters, at a price a small shop can carry indefinitely. That is the gap GrannyHost was built for — six months free, then $290 a year, run on the same servers and by the same people as SwiftForge, as a separate low-cost brand for small shops.
Which one, by size of shop
Size is the main variable, and being honest about it saves everybody time.
| If your store is… | The sensible answer |
|---|---|
| Small, and a day offline is survivable | Hosting with care included, or disciplined DIY if you are technical. An agency retainer would be money badly spent. |
| Growing, and downtime is starting to hurt | Care-included hosting is still usually right, plus a one-off piece of work if the store is already behind. Move up when the maths changes, not before. |
| Large enough that a bad day is a bad month | A retainer with people who know your code. At this size the retainer is cheaper than the incidents. |
| Already broken, slow or badly out of date | Repair first, then maintain. Maintenance plans assume a working starting point — none of the four models above fixes a store that is already in trouble. |
Not sure which category you are in?
The free Store Sheriff check answers that in two minutes. Eighteen questions about software age, backups, plugin hygiene, speed and oversight, and it tells you whether your store needs maintaining or repairing — which is the question that decides everything above. No login, no email, nothing leaves your browser.
Related
- What managed hosting actually does for a small store — and the things it genuinely will not do.
- Your developer stopped replying — how to get control of your own store back.
- Is your store platform still supported?
- The maintenance checklist SwiftForge actually use — worth copying whether you hire anyone or not.