Headless commerce on Shopify decouples the storefront from the Shopify admin — using Shopify as a backend for products, cart, and checkout while the frontend runs on Hydrogen, Next.js, Nuxt, Remix, Astro, or a custom framework. It unlocks design freedom, faster performance, and custom UX beyond theme limits, but it also removes Shopify's biggest advantage: the theme editor and app ecosystem work differently or not at all. Post-Brexit, UK merchants selling into the EU also increasingly consider headless as a way to run country-specific storefronts under one codebase. Work through these five steps before you request quotes from UK-based headless developers.
Confirm you actually need headless before scoping the project. Most Shopify stores do not need headless — a well-optimised premium theme with custom sections covers 90% of what merchants think they need headless for. Real reasons to go headless: you're on Shopify Plus and need UX beyond theme limits, you're integrating multiple content sources (blog CMS, learning content, product data) into one storefront, you're building a PWA or mobile app sharing a codebase with the storefront, you're running UK plus EU country-specific storefronts under one codebase, or you have specific performance requirements (sub-1.5s LCP on complex pages) themes cannot meet.
Match the framework to the project. Hydrogen (Shopify's official React framework) plus Oxygen (Shopify's hosting) fits stores that want Shopify-native tooling, deepest platform integration, and Shopify's app ecosystem support where possible. Next.js Commerce fits stores that want Vercel's ecosystem, broader React talent pool, and integration with multiple headless CMSs. Nuxt (Vue) fits stores with Vue-preferring teams. Remix and Astro fit specific technical use cases. A good UK headless expert will recommend the framework that fits your team and stack, not the one they're best paid for.
Verify Shopify Storefront API and headless-specific experience. Many React and Next.js developers can build headless sites but do not know Shopify's Storefront API rate limits, cart persistence quirks, checkout redirect handling, or how apps behave (or don't) in a headless context. Ask for three live headless Shopify stores they've shipped in the last 18 months, ideally on the same framework you're planning to use.
Review real headless case studies with performance and conversion numbers. "We built a headless store" is not a case study. "We migrated an £8M Shopify Plus brand from Dawn to Hydrogen, improved LCP from 3.8s to 1.1s, and lifted mobile conversion rate 18% in the first 60 days" is. Ask for before-and-after Lighthouse scores and Google Search Console data.
Compare quotes with framework decisions locked in and app migration plans documented. Good headless quotes name the framework, the CMS (if applicable), the hosting (Oxygen, Vercel, Netlify, AWS), and how each existing Shopify app will be replaced, replicated, or removed. If the quote is a lump sum without those decisions, the developer is either senior enough to be worth it (rare for headless) or vague enough to be avoidable (common).