Headless Shopify commerce UK
Headless Shopify keeps Shopify for catalogue, cart, checkout and orders, and replaces the theme with a custom frontend — usually Hydrogen or another React storefront on the Storefront API. It typically costs 30–50% more than the equivalent custom theme, and On The Road will recommend a theme instead when headless is not earning that premium.
Headless commerce gives you full creative and technical freedom on the frontend — with Shopify powering checkout, inventory and operations behind the scenes.
Headless is not for everyone, but when you need a fully custom frontend experience, multi-channel content delivery, or performance that exceeds what Liquid themes can deliver, it is the right architecture. We build headless storefronts on Shopify's Storefront API and Hydrogen framework.
Our headless work includes custom React frontends, progressive web apps, content-driven experiences with CMS integration, and composable architectures that connect Shopify to your existing design system. RVinyl's headless setup achieved 98/100 page-speed scores and more than doubled mobile conversions.
We help you decide whether headless is justified for your business — because a well-built custom theme is often the better investment. When headless is the answer, we deliver it without unnecessary complexity.
When a theme is the better buy
A custom theme is the right architecture for most brands we meet. Shopify’s theme stack is fast when it is built carefully, merchants can edit it, and checkout stays on Shopify without a second frontend to host. Headless adds a hosting environment, a deployment pipeline, and a frontend team that has to keep up with cart and account behaviour Shopify would otherwise give you.
Choose headless when the storefront cannot be a theme: a design system you already ship on the web, a content model that does not fit sections, more than one frontend on the same catalogue, or a performance bar a Liquid theme has already failed after a serious attempt. The RVinyl case study reports a 98/100 page-speed score and a large lift in mobile conversion after a Shopify Plus migration with custom checkout logic. That case study does not describe a headless storefront, so we do not cite it as one.
What we build
The commerce engine stays Shopify. Products, inventory, discounts, checkout and orders remain there, which is the point of not replatforming the backend. The frontend talks to the Storefront API. We use Hydrogen where it shortens the work, and a custom React frontend where an existing design system or a non-Oxygen host is a real constraint rather than a preference.
Content often sits in a CMS next to Shopify, with a clear rule for which system owns which field. Cart and checkout need an explicit design: Shopify’s hosted checkout is still the right end of the funnel for almost everyone, and we will argue for it unless there is a compliance reason not to. Account, search and filtering are where headless projects quietly double in size, so they are in the scope, not discovered in week eight.
Performance is a requirement in the build, not a phase at the end. A headless store that ships a megabyte of JavaScript has bought complexity and lost the reason for doing it. The same Core Web Vitals bar we use on themes applies here, with the CDN and caching strategy written down.
How the decision is made
The first conversation is whether headless is justified. Bring the constraint: the design system, the content team, the speed problem, the second channel. If the constraint is “we want it to look custom”, that is a theme project, quoted at £10k–£40k, and we will point you at that service instead.
If headless is the answer, discovery fixes the hosting, the CMS, the checkout boundary and the launch scope. You still get a fixed quote. You also get an honest note on who has to maintain the frontend after we leave, because a headless store without an owner becomes a theme you can no longer edit.
Plan for the month after launch as well as launch week. Someone has to deploy the frontend, read the error logs, and update it when Shopify changes a cart or account API. If that is us, it sits on the retainer from £2,500 a month. If it is your team, handover includes the repository, the host, and a normal release — not a zip file.
Timeline and cost
Headless projects run longer than a theme of similar visual scope because of the extra system: plan on the upper end of a complex build, and often beyond a 12-week theme timeline once CMS, search and account are included. The proposal breaks that into a first release and a follow-on, so launch is not waiting on every future channel.
Expect roughly 30–50% more than the equivalent custom theme. Themes are £10k–£40k; headless therefore sits with complex builds, commonly inside £15k–£50k+ depending on CMS, search and integrations. Hosting is a separate running cost. We quote it as a fixed project after discovery.
How we deliver headless shopify.
- Headless architecture consulting
- Hydrogen and React storefront development
- Storefront API integration
- CMS and content platform connection
- Performance optimisation and CDN strategy
- Checkout and cart customisation
Case studies.
Common questions.
What is headless Shopify?
Headless Shopify decouples the storefront (what customers see) from Shopify's backend (products, cart, checkout, orders). You build a custom frontend that talks to Shopify via the Storefront API.
Is headless more expensive than a custom theme?
Generally yes — headless projects typically cost 30–50% more than equivalent custom theme builds due to additional infrastructure, API development and ongoing maintenance.
When should we go headless?
Consider headless when you need a fully bespoke frontend experience, want to integrate deeply with a CMS or design system, or have performance requirements that exceed theme capabilities. We will tell you honestly if a custom theme is the better fit.
Ready to get started?
Book a free consultation and we'll scope your headless shopify project — no obligation.
Book a consultation →