Headless Shopify Development for UK Brands

Headless Shopify means the shop front customers see is a separate website, while Shopify still runs products, stock, orders and checkout behind it. The front end reads data through Shopify’s Storefront API. When a shopper pays, Shopify’s documentation says the cart returns a URL that redirects them through Shopify’s web checkout. Your Liquid theme goes. Your Shopify admin, order flow and back-office connections stay.

Hydrogen is Shopify’s own framework for headless shops. Shopify’s documentation calls Hydrogen projects React Router apps preconfigured with Shopify features (React Router is a common open-source toolkit for building web apps), and says it provides ready-made components wired to Shopify data. The design is still custom: Hydrogen gives the building blocks, and we build your pages on them. Most Hydrogen shops run on Oxygen, Shopify’s edge hosting, which Shopify says is available at no extra charge on paid plans.

Both are sound choices for an established brand. Hydrogen is maintained by Shopify, hosts on Oxygen and suits a team that wants one supplier for platform and hosting. Next.js suits a brand that already runs a Next.js marketing site, wants a CMS-led content site with a shop inside it, or hosts on its own cloud account. We recommend one after reading your catalogue, content plan and in-house skills.

No. Shopify’s Hydrogen documentation lists Oxygen hosting on the Starter, Basic, Grow, Advanced and Plus plans, and on development stores. Moving to Plus is a separate decision about your store’s size and needs. Shopify’s UK pricing page shows Plus starting at £1,800 a month on a monthly plan, read on 29 October 2026. That page does not say whether VAT is added, so check your Shopify bill.

Merchandisers keep working in the Shopify admin for products, prices, discounts and orders. What changes is page building. Theme editor sections are gone, so landing pages and content are edited in a headless CMS or in fields we set up for you. Developers work in a code repository instead of the theme editor. We train the team before launch and write down who edits what.

When a good Online Store 2.0 theme already does the job. If your pages are standard product and collection templates, your apps depend on theme blocks and nobody on your side owns code, headless adds cost without a return you can measure. We say so on the first call and point you to theme work on our UK Shopify development page instead.

Pick the CMS by who edits and how much content you publish. Shopify’s own content entries, called metaobjects, can feed a Hydrogen site, and Shopify publishes a recipe for building section-based pages with them, so a small content team may need no extra system. A brand publishing buying guides every week often wants a separate headless CMS with a visual editor. We recommend one after seeing your content plan.

One UK agency publishes figures. Imaginaire, based in Nottingham, says its headless Shopify projects start from £60k, with most between £80k and £160k, and complex catalogues over 1,000 products at £120k to £250k. Its page does not say whether VAT is included. These are market figures, read on 29 October 2026. FactoryJet quotes a fixed price per phase in writing after a short scoping call.

Four things: the number of distinct page templates, the size and messiness of the catalogue, how much content lives in a CMS, and how many storefront features your current apps provide that must be rebuilt, such as reviews, wishlists or bundle builders. Back-office links to Xero, Sage or Linnworks rarely change, because orders still complete in Shopify checkout.

It depends on templates, catalogue size and the storefront features to rebuild, so we do not publish one number. Every project is split into phases, and each phase is scoped, priced and signed on its own, with its timeline in writing. Phase one usually covers the home, collection, product and cart pages, so you see your real catalogue running early.

Back-office apps that read orders and products from the Shopify admin carry on. Storefront widgets are different. Shopify describes theme app extensions, the blocks behind many reviews and ratings apps, as integrating with Online Store 2.0 themes. A headless front end is not a theme, so each widget is rebuilt through the app’s own API or replaced. We list every app in the audit before quoting.

No. Buyers still pay in Shopify’s checkout. Shopify’s documentation says the cart returns a checkout URL that redirects customers through Shopify’s web checkout, and that a cart carrying a customer token (a code that proves which customer is signed in) opens a logged-in checkout. Payment methods you already offer at Shopify checkout stay where they are, and orders land in your Shopify admin exactly as today.

Usually not. Those systems read orders, stock and products from the Shopify admin, and a headless front end does not change the admin. Orders still complete in Shopify checkout, so Xero or Sage still receive the same sales, and Linnworks or Mintsoft still see the same orders for Royal Mail, DPD or Evri labels. We test each link on staging before launch to prove it.

Shopify’s Storefront API reference says requests from real buyers are not subject to a fixed request-per-minute limit, and that checkout creation and automated traffic are throttled, which means slowed down once they pass a set rate. So the data layer scales with shoppers. What we test is your own front end and hosting: page caching, image sizes, search and filter calls, and the third-party scripts that slow a busy sale day.

It can, but it is not automatic. Google’s web.dev guidance sets good thresholds at 2.5 seconds for Largest Contentful Paint, 200 milliseconds for Interaction to Next Paint and 0.1 for Cumulative Layout Shift, measured at the 75th percentile of page loads, so three in four visits must hit the mark. A headless build gives you control of every script on the page. Heavy tracking tags can still undo that, so we budget them.

Your marketing team, without a developer. We set up a headless CMS, or structured content fields, so landing pages, banners and buying guides are edited in a visual editor and published on a schedule. Product data stays in Shopify. We agree which system owns each kind of content in writing before the build, so nobody edits the same thing in two places.

Yes, through Shopify Markets. Shopify’s documentation says merchants can set product prices per country in the Shopify admin, and that the Storefront API can query international prices and set the country and language of a cart and checkout. So a UK shopper sees pounds and a French shopper sees euros from one catalogue. We build the country picker and test prices in each market.

It can if old URLs break or pages load blank for search engines. We map every old product, collection and blog URL to its new address with a permanent 301 redirect, render pages on the server so the HTML carries the words, and copy titles, descriptions and product structured data across. After launch we watch Search Console for crawl errors through the first weeks.

The CMA’s price transparency guidance says the invitation to purchase must give the total price, normally including unavoidable charges, and that mandatory delivery charges must be shown there too. It says hiding additional fees, taxes or other charges is illegal, with fines of up to 10% of turnover or £300,000, whichever is greater. A custom front end has to build those rules in.

Often yes, with a narrower exception. The ICO’s guidance on cookies and similar technologies, updated for the Data (Use and Access) Act and finalised in April 2026, describes a statistical purposes exception, which needs clear information about the purpose and a simple, free way to object. Marketing tags still need consent. Shopify’s Hydrogen analytics guide says to meet consent rules before tracking starts, and points to its Customer Privacy API and banner.

No. GOV.UK says VAT-registered businesses must use compatible software to keep VAT records and file VAT Returns. Your sales records still come from Shopify orders, because checkout does not move. The route from Shopify into Xero, Sage or QuickBooks stays the same. Your accountant confirms the set-up, and our UK Shopify Xero integration page covers that link.

Yes. Before a contract, we show working software on your own data. For a headless project that means a draft of your home, collection and product pages running on your real Shopify catalogue, so your team can click through it on a phone and compare it with the live theme before committing to a phase.

You own the code and the repository from day one. Hosting can run in your own Shopify Oxygen setup or your own cloud account, at cost with no markup. Defects are fixed inside the build price for a cover period agreed before work starts. Support afterwards is optional, each change is quoted and approved, and there is no monthly minimum.

Yes. We agree the split at scoping and write it into the phase one scope: who owns the storefront code and who runs paid media tags. Your developers get access to the repository and review rights from the start, so there is no separate handover project at the end.

Your Shopify plan, monthly order volume and catalogue size; every app on the store today; the systems around it, such as Xero, Sage, NetSuite, Linnworks or Mintsoft; the countries and currencies you sell in; your content plan; and any launch date that cannot move. Send it with the form on this page, and we reply with questions or a fixed quote per phase.