Costs and pricing
Part of What is headless commerce and is it worth it for UK retailers?
What is headless commerce and is it worth it for UK retailers?
Headless commerce separates the storefront from the commerce engine. We explain UK build costs, developer constraints and when mid-market retailers see a return.
What to take away
- Headless commerce splits the storefront from the commerce engine, so a retailer can change the front end without replatforming the back end.
- It costs more to build and run than a themed store on the same engine, once hosting, monitoring and two support contracts are counted.
- The return comes from speed, several sales channels or separate content workflows, not from a smaller licence fee.
- Developer availability, not the platform, is the usual constraint on a UK mid-market build.
- Write the requirements and a 24-month total cost model before commissioning any proof of concept.
Headless commerce in plain English
Headless means the customer-facing storefront is separated from the engine that holds products, prices, stock and orders. The engine is the back end, and the storefront talks to it through an API. In practice the storefront might be a JavaScript framework, a mobile app or a kiosk.
Headless storefront to commerce engine
- Storefront: JavaScript, app or kiosk
- API: sends and receives requests
- Commerce engine: products, prices, stock
- Orders: held in the back end
The trade-off is control against cost. You gain freedom over page speed, layout and channel logic. You take on hosting, caching, security updates and the people who keep the front end running.
The commerce engines UK retailers most often pair with a custom front end are Shopify Plus, BigCommerce and Adobe Commerce, all of which expose product, price and checkout APIs. Commercetools and Centra go further and are API-first by design: they host the commerce engine itself, and the retailer owns the storefront that sits in front of it.
On the storefront side, Next.js and React cover most UK builds, with Vue Storefront for Vue and React teams and Hydrogen, Shopify's React storefront framework, for Shopify stores that have Storefront API access. Front ends are usually deployed to something like Vercel, Netlify or Cloudflare Pages, with errors and performance tracked in something like Sentry or Datadog.
What a headless build costs and how to price it
Two cost lines separate a headless build from a themed store: the front end, and the ongoing operation of it.
Five steps before committing
- Write selling journey as customer events
- Price front end, hosting, support
- Get two fixed discovery quotes
- Pilot one category behind old storefront
- Compare pilot cost per order
- Write the selling journey as a sequence of customer events, with a blank threshold for each one.
- Price the front-end build, hosting, monitoring and two support contracts over 24 months.
- Ask at least two UK developers for a fixed discovery quote before any design work starts.
- Pilot one product category behind the existing storefront and keep the old front end live.
- Compare cost per order in the pilot with cost per order in the current store before committing.
Developer time, not the engine licence, dominates the first year. The storefront is built, hosted and released separately from the engine, so every change runs through the front-end contract.
As an illustrative figure, a £60,000 build plus £3,000 a month for hosting, monitoring and support comes to £132,000 over two years, before any uplift is booked.
Set the recurring lines into the 24-month model too: licence or API-call fees, CDN and hosting charges, observability tooling, security patching, and payment fees kept after refunds. Our guide to hidden platform costs covers the ones buyers most often leave out.
A decision table for mid-market retailers
Run a decision table before spending anything on discovery. The gates below are about fit, not fashion.
Headless fits
- More than two front ends (web, app, partner)
- Yes
- The problem is checkout or page speed on a heavy theme
- Sometimes
- Separate teams for content and commerce data
- Yes
- Fewer than five developers or one agency partner
- No
- A new sales channel needed within six months
- Unlikely
Themed store usually fits
- More than two front ends (web, app, partner)
- No
- The problem is checkout or page speed on a heavy theme
- Yes, a lighter theme may fix it
- Separate teams for content and commerce data
- Rarely
- Fewer than five developers or one agency partner
- Yes
- A new sales channel needed within six months
- Yes
If most of your answers sit in the right-hand column, a themed store on a better engine is the cheaper route. Headless earns its place when the front end is the constraint, not the product data.
The ONS Retail Sales Index, the monthly release that covers online's share of UK retail spending, is a firmer guide than a vendor case study.
Where the return actually comes from
Returns on a headless build are narrow and specific. A retailer that ships to three front ends from one catalogue avoids rebuilding product data three times.
A retailer with heavy editorial can ship content changes without a platform release, which shortens the queue between marketing and the live page.
Splitting the stack spreads personal data across more services, so read the ICO's guidance on encryption and check lawful bases, processor contracts and retention under UK GDPR before the build is signed.
Recovery also matters. A headless front end can be replaced while the engine and its order history stay in place, which lowers exit risk compared with a full replatform.
Budget the migration of content and redirects inside the first phase. Those tasks sit outside the front-end build and are easy to underestimate.
For retailers whose problem is platform choice rather than architecture, the discipline of turning the selling journey into requirements applies before any headless decision.
Common questions
The questions UK retailers ask most often about a headless build.
Is headless commerce worth it for a UK retailer?
Rarely for a mid-market retailer with one storefront and a standard theme. It can pay for one running three channels from a single catalogue.
Do I need headless to sell on more than one channel?
No. Most hosted engines offer APIs and marketplace connectors, so adding a channel is a separate decision from rebuilding the front end.
What does headless commerce cost in the UK?
Build and running costs dominate, not the licence. A 24-month model is the minimum test before you commit.
Can a small UK retailer run headless?
It is possible but hard to justify without a retained front-end developer. A themed store remains the cheaper route below mid-market scale.
