What is headless ecommerce?
Headless ecommerce is an ecommerce model in which the front-end presentation layer is separated from the back-end functionality.
This model splits a digital store into two distinct parts. The presentation layer is the interface customers see and use when they visit your site. This is where your brand identity lives. The back end, or commerce engine, manages the product catalogue, inventory, pricing and orders.
Think of it like a physical retail space. The presentation layer is the shop front where customers browse items and interact with staff. The back end acts as the stockroom behind the scenes. While customers only see the front, the stockroom holds all the essential data and logistics required to process a sale.
For a marketing manager, this separation means the visual design is independent of how orders are processed. You can update the look without touching the core business logic. This structure allows for different tools to handle specific tasks.
Big Rocket builds stores on native Webflow Ecommerce or with a custom ecommerce back end. Rich Oborne calls the LuxuryTrainTickets.com set-up composable commerce rather than headless. Big Rocket has not built a headless Shopify store.
How headless ecommerce works
The front end asks the commerce engine for products, prices and the cart through APIs. This architecture allows you to build a unique front end using your choice of stack, framework and hosting. You can then use these APIs to sell on a website, mobile app, game, livestream, smart device or via a buy button on an existing site. For a marketing manager, this means the presentation layer is entirely under your control. You can decide exactly how the interface looks and behaves across different devices without changing the underlying commerce platform.
Shopify's Storefront API provides a specific way to connect these layers. It uses the following features:
- GraphQL only and versioned: The API is GraphQL-only and has versions like 2026-10.
- Buyer traffic and bots: The API scales with buyer traffic because requests from real buyers are not subject to a fixed request-per-minute limit. However, bots, crawlers and checkout creation are throttled to manage the load.
- Tokenless access: This covers products, collections, search, pages/blogs and the cart. It has a query complexity limit of 1,000.
- Token-based access: This adds features like metafields, metaobjects, menus and customers. An app can have at most 100 active storefront access tokens per shop, but private tokens must never be used client-side.
Tokenless access handles the basic shopping experience for visitors. When you need more specific data like customer details or custom menus, you use token-based access. This separation allows for different levels of data handling depending on the specific needs of your front end application.
Headless vs traditional ecommerce
A traditional platform keeps the shop front and engine in one system with built-in editors, and headless trades that for control and the work of maintaining a custom front end.
- System integration. Traditional commerce integrates the storefront and commerce engine into a single system. You customise this through themes and built-in tools. In contrast, headless separates these layers to give you control over front-end technology.
- Content management and tools. Built-in editors in a traditional setup let merchants update content easily. Prebuilt features generally reduce the initial development work required to launch a store.
- Maintenance and responsibility. Headless architecture requires the team to maintain and test a custom front end. This adds responsibility because front-end bugs can interrupt browsing or purchases.
For a marketing manager, these differences change how you work daily. In a traditional setup like the Ivy's Reserve case study, the team uses native Webflow Ecommerce. This means they manage products and prices in the same place as recipes and stories. This single system handles different versions for the UK, US, Canada and France. The built-in tools allow for updates within one platform.
When you choose a headless approach, the marketing manager gains more control over front-end technology. You are not limited to platform themes. However, the team must take on the work of maintaining that custom interface. If a bug appears in the custom front end, it can affect how customers browse or buy. You must balance the freedom of a unique design with the need to test and maintain the code.
Does headless make a store faster?
It can, but only when developers optimise rendering, caching and page weight. Speed in a headless setup depends on how the custom front end handles data and assets. If the code is heavy or the rendering is slow, performance can suffer. Google uses specific metrics to measure how users experience page speed and stability. These are known as Core Web Vitals and they are measured at the 75th percentile of page loads.
- Largest Contentful Paint: A good LCP is 2.5 seconds or less, while a poor LCP is over 4,000 ms.
- Interaction to Next Paint: A good INP is 200 milliseconds or less, while a poor INP is over 500 ms.
- Cumulative Layout Shift: A good CLS is 0.1 or less, while a poor CLS is over 0.25.
For a marketing manager, these metrics represent how quickly a customer sees the main content or interacts with a button. A low Largest Contentful Paint means the primary visual element loads quickly for the majority of your visitors. This is important because Google uses this metric in ranking. If the front end is not optimised, your site might fail to meet these thresholds at the 75th percentile. This percentage is used so that a majority of visits meet the target without being overly affected by outliers.
Interaction to Next Paint measures how responsive the site feels when a user clicks something. Cumulative Layout Shift tracks whether elements move around while the page is loading.
Headless Shopify: Hydrogen, Oxygen and plan costs
Headless Shopify involves building a custom front end using Shopify's APIs and checkout, often utilising the Hydrogen toolkit. Hydrogen acts as a development toolkit that adds Shopify's cart, product, collection and checkout routes to frameworks like Next.js, React Router, Nuxt, Astro and SvelteKit. For a marketing manager, this means you can use modern web frameworks to build highly specific interfaces while Shopify manages the commerce logic through the Storefront API and Customer Account API.
There are two sales channels available for headless storefronts: the Headless channel and the Hydrogen channel. The Headless channel is used for storefronts you host yourself on any stack, such as hosting Hydrogen on Vercel. The Hydrogen channel allows you to deploy Hydrogen storefronts directly to Oxygen, which is Shopify's hosting solution for Hydrogen. If you prefer not to use Oxygen, Hydrogen can be self-hosted instead.
Oxygen hosting is available at no extra charge on paid Shopify plans, including Starter, Basic, Grow, Advanced, Plus, and Pause and build. It is not available on Agentic plans. Shopify UK plan pricing is structured by monthly or yearly payments. The Basic plan costs £25 a month or £19 when paid yearly. The Grow plan is £65 a month or £49 if paid yearly. The Advanced plan costs £344 a month or £259 when paid yearly. For larger operations, the Plus plan starts at £1,800 a month. Regarding storefront limits, Basic, Grow and Advanced plans each allow 1 headless storefront, while the Plus plan allows up to 25.
Other headless options and front-end running costs
BigCommerce offers its own headless framework called Catalyst, and any custom headless build involves managing front-end hosting and often a headless CMS. Catalyst is a framework built on Next.js and React server components using the BigCommerce GraphQL Storefront API. It is released under the MIT licence and can be deployed to Vercel or any host that supports the necessary Next.js features. BigCommerce also offers its own Storefront Hosting in closed beta.
For a marketing manager, using a framework like Catalyst means the technical foundation is already structured. However, BigCommerce documentation states that custom headless builds require you to manage the application layer and API calls yourself. While BigCommerce handles orders and payment processing, your team is responsible for the front-end application logic. You can use starter apps or pre-built solutions to avoid starting from scratch, which helps manage the development workload.
Choosing a hosting provider or CMS requires understanding different pricing structures. For example, Vercel provides specific limits on its hobby tier, while other platforms use seat-based or credit-based models. This affects how costs scale as your team grows or your traffic increases.
- Vercel: Hobby is $0 a month with usage caps. Pro is $20 a month per developer seat with a $20 included usage credit and pay-as-you-go beyond it. Enterprise is custom.
- Netlify: Free is $0 (300 credits). Personal is $9 a month (1,000 credits). Pro is $20 a month with unlimited members (3,000 credits). Enterprise is custom-priced.
- Sanity: Free is $0 (up to 20 seats, 10k documents, 1M API CDN requests a month). Growth is $15 per seat per month (up to 50 seats, 25k documents, pay-as-you-go overages). Enterprise is custom.
Headless ecommerce examples
Brands Shopify names as using headless storefronts include Sennheiser, Nour Hammour, Denim Tears, Kotn and Boll & Branch. Sennheiser runs headless storefronts alongside Shopify themes for smaller markets. Denim Tears built a Hydrogen storefront with 3D objects and playlists that carry across pages. Boll & Branch moved from a complex custom build to Hydrogen and Oxygen to improve load times. Kotn used the Storefront API to merge two stores into one and add a new CMS.
Nour Hammour rebuilt its store using Hydrogen and Oxygen. It added Sanity for content and Mux for video. A month after launch, the brand reported a 63% year-over-year increase in conversion rate.
LuxuryTrainTickets.com is one of Big Rocket's own businesses, built and still managed by Big Rocket. It is composable commerce rather than headless. The site uses Webflow for pages, CMS and SEO, which is edited by the team. It uses Foxy for cart, checkout, deposits and balances. Stripe handles card payments routed by currency. Cloudflare manages background tasks that monitor supplier pages, and Mailchimp handles emails. The site takes payment in 3 currencies at checkout, each with its own payment account. The business made £1M+ in sales in its second year after launching during the pandemic and now makes £2.5M+ a year, mostly from organic search. You can read the LuxuryTrainTickets.com case study for more details.
Three ways to build, compared
Most small UK brands choose between native Webflow Ecommerce, a Webflow site with a separate cart and checkout, and headless Shopify.
- Native Webflow Ecommerce: This suits small product ranges with rich content. It uses Webflow's native checkout and requires a Webflow plan as the running cost. The Standard plan is $29 a month billed yearly for 500 items with a 2% transaction fee. The Plus plan is $74 a month billed yearly for 5,000 items with 0% transaction fee. The Advanced plan is $212 a month billed yearly for 15,000 items with 0% transaction fee. For a marketing manager, this setup allows you to manage products and content in one place using built-in tools.
- Webflow with a separate cart and checkout: This approach suits bookings, bundles, and complex pricing through custom ecommerce builds. It uses a fully custom checkout, such as Foxy and Stripe, alongside hosting plus ongoing support. Foxy provides a hosted cart and checkout that adds selling to an existing website via links or embedded HTML. A custom checkout from Big Rocket handles dated items with booking options, bundles, gift selections, supplier and seasonal rates, deposits, remaining balances, multiple currencies at checkout, and inventory, order, and email connections. Running costs include hosting, support, and Stripe fees of 1.5% + 20p for standard UK cards or 2.5% + 20p for EU cards, with no setup or monthly fees.
- Headless Shopify: This option is for brands requiring a specific front end using different tools. It involves building a custom interface while Shopify manages the commerce logic through APIs.
When headless isn't worth it
If your current platform already does what you need, stay put, because headless costs more to build and run and needs developers after launch. Moving to a custom front end introduces added complexity that your team must manage. For a marketing manager, this means you are trading the simplicity of built-in tools for a more expensive and technical setup.
Shopify suggests considering a headless approach in specific scenarios:
- Existing tools cannot support the storefront experience you want.
- You want to add commerce to infrastructure you already have.
- You sell on channels not supported out of the box.
- You use a CMS for content integrated with the storefront.
Alternatively, you should keep a themed storefront if:
- Your theme and apps already meet customer and merchandising needs.
- Your team relies on built-in visual editing.
- Your deadline or budget leaves little room for custom development.
- Performance problems come from fixable issues with images, apps or theme code.
Before you commit to a project, Shopify suggests asking a headless partner these questions:
- What the initial quote covers and what would trigger extra fees?
- Which existing apps need custom integration or replacement?
- What recurring costs you will pay after launch?
- Who owns the code and documentation and who fixes problems?
- What performance, accessibility and SEO checks are included before launch?
Sources
Researched and fact-checked with the help of AI tools and Ahrefs data.
- Shopify, Headless commerce: definition, benefits and costs
- commercetools, Headless commerce
- Shopify developer docs, Headless
- Shopify Developers, Storefront API reference
- web.dev (Google), Web Vitals
- web.dev (Google), How the Core Web Vitals metrics thresholds were defined
- Shopify developer docs, Hydrogen
- Shopify Developers, Hydrogen fundamentals
- Shopify UK, Pricing
- BigCommerce Dev Center, Catalyst
- BigCommerce Dev Center, Headless commerce
- Vercel, Pricing (and Vercel Docs, Hobby Plan)
- Netlify, Pricing
- Sanity, Pricing
- Webflow, Pricing
- Stripe UK, Pricing
- Foxy

