What a Shopify retainershould cost.
Almost nobody publishes a price, so working out whether a quote is fair means asking three agencies and guessing. Here is the whole market, in numbers, including the cases where the honest answer is that you don't need a retainer at all.
The short answer
£500 to £3,000 a month, and the hours tell you where in that.
- A stable store shouldn't be on a retainer. Buy a block of five hours for £500–£1,000 and draw it down.
- A store that changes monthly sits at 5–8 hours, £500–£1,000 a month.
- A store that changes constantly sits at 10–20 hours, £1,500–£3,000 a month.
- Anything charging a monthly fee with no hours attached is selling you a place on a list, not a developer.
The rest of this page is how those numbers are arrived at, so you can check a quote against them rather than take the ranges on faith.
Start with the hour · everything else is arithmetic
Every retainer is an hourly rate wearing a hat.
A monthly figure only means something once you know how many hours it buys. Divide any quote by its hours and compare the result against what an hour actually costs in the UK.
| Who | Rate | What that buys |
|---|---|---|
| Solo senior developer (UK) | £100–£150 / hour | The person who writes the code is the person you speak to. Highest rate, lowest overhead, and no handover cost. |
| Agency (UK) | £85–£100 / hour | Cheaper per hour because the hours are spread across juniors and seniors. You buy a team and an account manager, not a specific developer. |
| Offshore “cover” plans | £40–£200 / month | Priced as a subscription with no meaningful hours attached. Fine for uptime dashboards, not for someone fixing your cart on a Tuesday. |
The agency line surprises people. An agency is usually the cheaper hour, not the dearer one, because it amortises your work across juniors and seniors and sells the blend. That's a real saving if the work is routine and a real cost the first time something subtle breaks and the person who picks it up has never seen your theme. Don't price a solo developer against an agency's hourly rate and conclude you're being overcharged; you're buying different things.
The monthly bands · what's actually published
Three shapes, and most stores want the third.
£500–£1,000
A store that changes a few times a month and wants a fast answer when it breaks.
£1,500–£3,000
A store shipping campaigns, sections and fixes continuously, where downtime costs real money.
£500–£1,000 per 5 hours
A stable store. The honest answer for most merchants, and the one nobody selling a subscription wants to give.
Notice what isn't on that list: a cheap monthly plan with no hours. It exists — £40 to £200 a month, usually offshore — but what it buys is monitoring and a mailbox, and the moment you need eight hours of Liquid work it turns into an hourly quote anyway. If the price looks too good for a developer's time, it's because it isn't a developer's time.
The question the seller won't ask
Do you need a retainer at all?
Shopify is not WordPress. There's no core to update, no plugin vulnerabilities to patch and no server to keep alive — that's all Shopify's, and it's the single biggest reason a "maintenance plan" argument transplanted from WordPress doesn't survive contact with a merchant who knows the platform. A Shopify store left alone does not rot. It just stops improving.
So the question isn't whether your store needs maintaining. It's these two:
- Is the store changing? Campaigns, new sections, a theme version, a new app every quarter. Change is what generates support work, not age.
- What does an hour of breakage cost? If a broken cart on a Tuesday costs less than the monthly fee, you're insuring against something cheaper than the premium.
As a rough line, a retainer starts paying for itself somewhere north of £10,000 a month in revenue. Below that, hours bought as you need them are almost always the better deal, and any developer who tells you otherwise before asking what you turn over is selling rather than advising.
Reading the quote
Five things worth arguing about.
Red flags in a Shopify retainer quote
None of these are dealbreakers on their own. All of them are worth a straight answer before you sign.
Borrowed wholesale from WordPress. Shopify hosts your store, patches it and keeps it up — there is no core to update and no server to harden. If a quote leans on this, it was written for a different platform.
“Cover” with no stated time is a fee for being on a list. Ask how many hours it buys and what happens in the month you need twelve.
A retainer should survive on being worth it each month. A lock-in is a bet that at some point it won't be.
It sounds generous and it isn't. A year of rollover is a debt your developer owes you, and it gets settled by rushing work or by the arrangement quietly ending.
Reserved time costs more to sell, not less, because other work has to be turned away to keep it free. A retainer hour priced below a booked hour is a discount that comes out of your response time.
A price that only exists after a discovery call is a price set by what you seem able to pay. It isn't always cynical — plenty of good developers just never got round to publishing — but it does mean you have no way to check the quote against anything, which is why this page exists.
What the money should cover
Support is bounded. A redesign isn't.
A retainer works because support work is unpredictable in timing but small in size: a bug on Tuesday, an app conflict a fortnight later, a section before a campaign. Reserved time is the right instrument for that. It is the wrong instrument for a redesign, a migration or a custom app, all of which are large, plannable and quotable — and all of which will eat a support retainer alive if they're allowed inside it.
So a good quote has two lists, not one. Fixes, Liquid and CSS changes, theme updates applied without losing your customisations, app conflicts and Core Web Vitals work belong in the monthly fee. New builds, migrations, product entry and brand work belong in a separate quote. A retainer with only the first list published is one where the boundary gets decided later, when one of you is annoyed.
Both halves of that list are published on the theme support page, along with what happens to unused time and what out-of-hours work costs.
Asked most often
The practical questions.
Is a Shopify retainer worth it for a small store?
Usually not. Shopify hosts and patches the platform, so a quiet store genuinely can sit untouched for months without rotting. A retainer starts earning its money at the point where your store changes regularly, or where an hour of breakage costs more than the monthly fee — in practice somewhere north of about £10,000 a month in revenue. Below that, buy a block of hours and draw it down.
How many hours should a Shopify retainer include?
Nobody credible sells fewer than about five hours a month, because below that the overhead of holding the time costs more than the time is worth. The published UK bands cluster at 5–8 hours for a store that changes occasionally and 10–20 hours for one that changes constantly. If a plan doesn't state its hours anywhere, that's the answer to how many it includes.
Why is a retainer hour more expensive than a project hour?
Because you're buying availability as well as work. A project day is booked in advance, scoped before it starts and slotted in where it fits. A retainer day is held open for you, which means turning other work down to keep it free and being able to say yes to “can you look at this today?”. The general rule holds across the market: the more notice you give, the cheaper the hour.
Should a retainer cover a redesign or a new theme build?
No, and you should be wary of one that claims to. Support work is bounded and unpredictable in timing; a redesign is large and predictable. Bundling them means either the redesign never quite happens or the support quietly stops. Expect fixes, changes, sections, app conflicts and speed work in scope, and a separate quote for anything that amounts to a new build.
What should notice and cancellation look like?
One month, either way, no minimum term and no exit fee. Your theme, your code and your repository access stay yours throughout. Anything longer is protecting the supplier's forecast rather than your store.
Is an agency or a solo developer better value?
They're different purchases. An agency bills a lower hourly rate but spreads your work across whoever is free, and part of what you pay for is the account management that makes that work. A solo developer costs more per hour and gives you one person who already knows your store, which is why the same fix tends to take fewer hours the second time. For a single storefront on a support arrangement, the second usually wins on total cost; for round-the-clock cover, the first genuinely does.
Our own numbers
Here's what we charge, on a page.
Everything above is the market. Harbour Labs publishes its own ladder against it — a £650 block of hours for a stable store, £1,150 a month for one day, £2,000 for two — with the scope, the overage rate and the notice period written down rather than quoted on request.