Definition
Headless commerce is an ecommerce architecture in which the storefront that shoppers see is built separately from the commerce backend. The frontend, such as a React site or mobile app, gets products, prices and the cart through APIs. On Shopify, it uses the Storefront API and usually sends shoppers to Shopify's own checkout.
How headless commerce works
In a standard Shopify store, the frontend and the backend are one system. The theme, written in Liquid, runs on Shopify's servers and reads products, prices and the cart directly. In a headless store the two are separated: you build the frontend, and Shopify's APIs provide the commerce layer underneath[1]. The "head" is whatever the shopper sees, whether a website, a mobile app or a screen in a shop.
The frontend talks to Shopify through two APIs. The Storefront API serves products, collections, search and the cart and hands the customer off to checkout. The Customer Account API lets customers sign in and returns their orders, addresses and profile[1]. The Storefront API is GraphQL only, with no REST version[2].
Checkout normally stays on Shopify. When the shopper is ready to pay, the frontend asks the cart for its checkoutUrl, which sends the customer through Shopify's web checkout[3]. Orders, payments, inventory, discounts and fulfilment all stay in the Shopify admin. Headless replaces the storefront, not the store.
Ways to build headless on Shopify
| Option | What it is | Hosting |
|---|---|---|
| Hydrogen | Shopify's headless toolkit: React Router apps preconfigured with Shopify features[4] | Oxygen, Shopify's hosting for Hydrogen, or your own |
| Bring your own stack | Any language or framework, such as Next.js, calling the Storefront and Customer Account APIs directly[1] | Your own (Vercel, Cloudflare and so on) |
| Mobile app | A native app using the same APIs as its backend[1] | App stores |
| Lighter options | Storefront Web Components, Buy Button JS or the WordPress plugin to sell on a site that is not built on Shopify[1] | The existing site |
In the Shopify admin, a self-hosted storefront connects through the Headless channel, which issues the API access, and a Hydrogen app deployed to Oxygen uses the Hydrogen channel[1]. Oxygen is included at no extra charge on paid Shopify plans, from Starter and Basic up to Plus[4]. We cover Hydrogen and Oxygen in detail in What Is Shopify Hydrogen?.
Example: one order through a headless store
Take a hypothetical Serbian store with 1,200 products, selling in Serbian and English, that went headless because it wanted a product configurator its theme could not handle. Here is one order:
- A shopper opens a product page. The Hydrogen server sends one GraphQL query to the Storefront API for the product, its variants and prices, renders the HTML and returns it.
- Editorial content, such as the lookbook and size guides, comes from a separate CMS, because there is no theme editor in a headless build.
- The shopper adds two items. The frontend creates a cart through the Storefront API, and the cart lives on Shopify, not in the browser.
- At "Checkout", the frontend requests the cart's
checkoutUrland redirects the shopper to Shopify's checkout[3]. - Payment works exactly as on a theme store: in Serbia, card payments through a local processor such as CorvusPay, cash on delivery or bank transfer. The order lands in the Shopify admin and goes through the same fiscalisation and fulfilment.
Steps 4 and 5 are identical to a theme store. Everything before them is code the store owns and maintains. That is the trade: total control over the shopping experience, and a codebase that needs a developer for every change.
Pros and cons
| Pros | Cons |
|---|---|
| Any design or interaction, without theme limits | Higher build cost and a longer build |
| One backend serving a website, an app and other channels | No theme editor: content changes need a CMS or a developer |
| Content can come from any CMS | Apps that add features through the theme don't appear on their own and need custom integration |
| Full control over rendering and performance | You own hosting, monitoring and upgrades |
| Checkout, payments and orders stay on Shopify | Speed depends on your code; headless is not fast by default |
For the full decision framework, costs and the 2026 changes, read our comparison of Shopify themes vs headless commerce.
Headless commerce vs composable commerce
| Headless commerce | Composable commerce | |
|---|---|---|
| What is separated | The frontend from the commerce backend | Every capability: search, CMS, payments, reviews, OMS |
| Backend | Usually one platform, such as Shopify | Several specialised services joined by APIs |
| Scope | An architecture for the storefront | An approach to the whole stack |
| Relationship | A step towards composable | Always headless, plus more |
FAQ
Is Shopify a headless platform?
Shopify can be used either way. Most stores use a Liquid theme, where Shopify runs the frontend. For headless, Shopify provides the Storefront and Customer Account APIs, the Hydrogen toolkit and Oxygen hosting[1].
Do I need Shopify Plus to go headless?
No. Hydrogen storefronts can be deployed to Oxygen at no extra charge on paid plans from Starter and Basic up to Plus[4]. Plus adds features many large headless builds want, but it is not a requirement.
Does headless change the checkout?
Usually not. The headless frontend hands the cart to Shopify's web checkout through the cart's checkoutUrl[3], so payment methods, discounts and order processing work the same way as on a theme store.
Is a headless store faster?
Not automatically. A well-built headless frontend can be very fast, but speed depends on the code, the hosting and how data is fetched. A poorly built one is slower than a good Liquid theme. Measure before and after, not in theory.
What is the difference between headless and Hydrogen?
Headless is the architecture: a frontend separated from the commerce backend. Hydrogen is Shopify's framework for building that frontend in React, based on React Router[4]. You can go headless without Hydrogen, for example with Next.js.
The bottom line
Headless commerce separates what shoppers see from the system that runs products, orders and payments. On Shopify, a custom frontend reads data through the Storefront API and hands shoppers to Shopify's checkout. It gives you full control at the cost of building and maintaining the frontend yourself. If that trade makes sense for your store, our Shopify headless development team can plan it with you.
Article sources
We use primary sources only: official documentation, product pages and laws. Each link was checked on the date shown.
- Shopify. Headless commerce (Shopify developer documentation). Accessed 17th Nov 2026.
- Shopify. Storefront API reference. Accessed 17th Nov 2026.
- Shopify. Manage a cart with the Storefront API. Accessed 17th Nov 2026.
- Shopify. Hydrogen fundamentals. Accessed 17th Nov 2026.
Need this on your store?
See the serviceThe checklist we run before touching a client's code
Get it by email, plus a few short notes over the next two weeks: what we see most often on Shopify stores and what actually fixes it.