Headless Commerce

Headless commerce decouples the customer-facing storefront (the “head”) from the backend commerce engine (inventory management, checkout, order processing, payment handling). In a traditional “monolithic” setup, the storefront and backend are one system — what you see in a Shopify store is what Shopify builds and controls. In a headless setup, the backend is a Shopify or BigCommerce API, and the frontend is a custom-built React or Vue application.

The short version: headless = custom frontend, commerce API on the back. Traditional = platform provides both.

Why merchants go headless

Frontend performance: A React/Next.js frontend can be faster than a platform’s default storefront, especially for page transitions and progressive loading. This matters for Core Web Vitals.
Brand control: The frontend is yours. You’re not constrained by Shopify’s theme system or BigCommerce’s Cornerstone template.
Omnichannel: The same commerce API can power a web store, a mobile app, a kiosk, and a social commerce integration simultaneously.
Checkout customisation: Headless bypasses the checkout constraints that non-Plus Shopify plans enforce.

Why most merchants shouldn’t go headless

Headless adds 3–6 months of initial engineering time, breaks the visual editor for non-technical marketers (they can no longer drag-and-drop in the Shopify admin — they need a developer for every content change), and the performance gains only pay back at meaningful scale ($5M+ GMV where site speed is a proven revenue lever).

The honest calculation: an engineering team that can build and maintain a headless storefront costs £80,000–£250,000/yr in salaries. The performance benefit is real but rarely worth that cost until organic traffic is generating millions of pounds in revenue.

Headless options by platform

Shopify Hydrogen: Shopify’s official React-based headless framework. Well-documented, Shopify-supported, best-in-class for Shopify merchants going headless.
BigCommerce headless via Storefront API: Mature, well-documented. BigCommerce’s API-first approach makes it easier to headless than Shopify was pre-Hydrogen.
Commercetools: Pure API, no built-in frontend. Requires full custom development. Enterprise only.
Saleor / Medusa: Open-source headless options. Require significant developer investment.

The skip-headless-until rule

Skip headless until:

Your GMV exceeds $5M/yr
Your frontend engineering team has at least 2 full-time engineers
Your marketing team is comfortable requesting content changes via pull request or a CMS like Contentful or Sanity

Below these thresholds, the cost of maintaining headless infrastructure exceeds the performance benefit.

Why merchants go headless

Why most merchants shouldn’t go headless

Headless options by platform

The skip-headless-until rule

Go Deeper