Headless commerce is an e-commerce architecture in which the front-end (the visible layer, what the customer sees and interacts with) is decoupled from the back-end (the engine that manages products, cart, payment and orders). The two communicate through APIs. This separation offers near-total creative freedom, at the cost of significantly more complexity and expense than a classic theme.
It is a powerful architecture, but rarely a necessary one. At Stellar Projects, after more than 100 Shopify projects, we advise the vast majority of our clients against headless, and this page explains honestly why, who it is really for, what it costs, and what we do instead.
Table of contents
What is headless commerce?
By definition, headless commerce separates the storefront from the engine. In a classic Shopify store, the front and back are tied together: the theme displays the pages and Shopify handles the commerce logic, all within a single system. In a headless architecture, you remove the "head" (the front) and rebuild it on an independent technology (React, Vue, Next.js), connected to Shopify's back-end through the Storefront API.
In practice, the split looks like this:
| Layer | Role | In headless |
|---|---|---|
| Front-end | Design, pages, customer journeys, interactions | Custom application (React, Next.js), hosted separately (Vercel, Netlify) |
| API | Bridge between the two layers | Shopify Storefront API |
| Back-end | Catalog, cart, payment, orders, admin | Shopify, kept as is |
The theoretical gain: a 100% custom experience and cutting-edge performance. The downside: you leave the comfort of native Shopify (theme editor, some apps, checkout extensions) and take on a second tech stack to build and maintain.
As this table shows, in a decoupled architecture everything relies on data exchanges between the front and Shopify. Before you dive in, get up to speed on the Shopify APIs you need to master to understand exactly what flows between the two layers.
Headless or theme: what really changes
The difference with a classic theme is not just about performance. Here is the honest comparison, pros and cons included:
| Criterion | Shopify theme (customized) | Headless |
|---|---|---|
| Design freedom | High, within the theme's framework | Total, no constraints |
| Performance | Very good if the theme is clean | Potentially excellent |
| Time to launch | Weeks | Months |
| Marketing team autonomy | Strong (theme editor, sections) | Low, everything goes through developers |
| App ecosystem | Complete | Partial, many apps no longer work |
| Maintenance | One stack | Two stacks, front and back |
| Cost of ownership | Under control | High and recurring |
The classic trap: choosing headless "for performance" when the slowness actually came from a poorly built theme or one overloaded with apps. In that case, an optimized theme solves the problem for a fraction of the budget.
How much does a headless project cost?
This is the point headless advocates rarely bring up first. Two types of costs add up: the initial build, then the run, meaning the recurring operating cost.
| Item | Customized theme | Headless |
|---|---|---|
| Initial build | €5,000 to €30,000 | €40,000 to €150,000 and beyond |
| Annual run | Shopify subscription and apps | Front-end hosting, maintenance of both stacks, ongoing development team |
| Changes and improvements | Fast, often done in-house | Every change requires a developer |
These ranges are the ones we see on the French market. The gap is not only in the upfront price: headless commits you to a lasting maintenance burden, whereas a well-built theme can be run by the marketing team itself. To understand the budget of a standard Shopify project, our page on how much a Shopify site costs details each line item.
Who is headless actually right for?
Headless has real use cases: very high volumes, extreme performance constraints, a radically distinctive brand experience, a tech ecosystem already oriented toward composable. Before saying yes to a client, we run through five questions:
- Is your current theme really holding you back, or is it an integration and optimization problem that a good theme would fix?
- Do you have an in-house team of front-end developers, or the budget for ongoing technical maintenance? Headless is not a project, it is a permanent commitment.
- Do your traffic and revenue justify a six-figure investment, build and run included?
- Do you have a real need that the native Shopify ecosystem, its apps and its metaobjects do not cover?
- Are you ready to give up part of native Shopify: the theme editor, checkout extensions, some apps?
If the answer to most of these questions is no, headless will cost a lot for a benefit you will not use. That is what we find in the vast majority of cases.
Our approach: semi-custom
Let's be clear about it: Stellar does not do headless. Not for lack of technical ability, but because our clients' e-commerce maturity and their expectations in terms of experience and design do not call for it. Poorly exploited headless means a high cost for value that is never recouped.
Our specialty is what we call semi-custom: advanced theme customization. We start from an existing theme, keep its proven set of features (cart drawer, mega menu, filters, native checkout), and fully adapt it to aesthetic mockups that we design from scratch. You get the best of both worlds:
- A design that is entirely yours, drawn by our teams, without the visual straitjacket of a standard theme.
- The robustness and features of native Shopify, maintained and compatible with the app ecosystem and the theme editor.
- A site you manage on your own, without depending on a developer for every change.
- A controlled budget and cost of ownership, without the double stack of headless.
This is the approach we apply to every one of our Shopify builds and redesigns: a custom-level result, without the technical debt of headless.
The native alternatives that are enough
In the vast majority of projects, what brands expect from headless is already achievable natively, since the arrival of Online Store 2.0 themes. Three building blocks are usually enough:
- Sections everywhere: 2.0 themes let you add modular sections to every page, product and collection pages included, to build rich layouts without code.
- Metaobjects: true structured databases inside Shopify for your reusable content, with no external app. The details are in our guide to Shopify metaobjects.
- Advanced theme customization: targeted Liquid development where the theme reaches its limits, without ever breaking native features.
This combination covers nearly all the needs of a growing brand, for a budget and a level of agility that simply cannot be compared with a headless project.
Composable commerce and Hydrogen
Two terms often come up around headless. Composable commerce is the broader concept: building your entire e-commerce stack from interchangeable best-of-breed components, of which the decoupled front is just one element. Hydrogen is Shopify's official front-end framework, designed to build headless storefronts on Shopify faster, hosted on Oxygen.
If your context truly justifies a decoupled architecture, it is better to build it with the ecosystem's native tools. We cover the "how" in our page dedicated to Shopify Hydrogen. And if you are still unsure, a 30-minute conversation with an expert will save you a six-figure investment you did not need.