In short: A headless online shop separates the engine that handles products and orders from the site the customer sees. It gives you design freedom and more channels from the same data. But it costs more in development, maintenance and skills. It makes sense when you have needs a theme cannot meet, revenue that justifies the work and a stable team or supplier.
In a traditional online shop, the engine that manages products and orders and the part you see on screen sit together. In a headless shop they are separate: the engine (the ‘body’) works in one place, and the site the customer sees (the ‘head’) is a separate application that talks to it through interfaces.
What you gain
- Design freedom. The look of the site is no longer tied to the limits of a theme.
- More channels from the same engine. Website, app, in-store screens and kiosks can all use the same data.
- Performance you control. With the right choices you can get very fast pages.
- Parts that are easier to swap. You can replace the search system or the content system without rebuilding everything. That is the idea behind composable commerce: a shop made of components chosen one by one.
What you pay
- A longer, more expensive build. Much of what comes ready-made in a theme has to be built: basket, search, accounts, content pages.
- More pieces to keep running. The engine, the site, the connected services. Each piece has its own updates and costs.
- Compatibility with apps and plugins. Many extensions designed for themes don't work in headless mode. Features have to be redesigned.
- People with different skills. You need someone to develop and someone to manage the infrastructure. Someone who updates the products is no longer enough.
When it makes sense
- You need very specific experiences that a theme cannot provide.
- You sell on several channels from the same catalogue and want consistency.
- Your traffic and revenue are high enough to justify the development and maintenance work.
- You already have a technical team or a stable supplier.
When it is better avoided
- The shop is young and you don't yet know what works.
- The problem to solve is speed or a heavy theme: that can often be fixed with less work.
- The team is small and has to handle everything on its own.
- The only goal is ‘being modern’.
A middle way
Before going fully headless, consider customising a theme in depth on an established platform. Shopify, for example, lets you build proprietary themes far removed from the standard templates. On WooCommerce you can get to a custom-built site while keeping the WordPress environment. Many shops find all the freedom they need here, with a fraction of the complexity.
How to decide
Write down three things: what experience you can't offer today, what it is worth to your revenue, and who will maintain the system two years from now. If the first two are clear and the third has a concrete answer, headless may be the right path. Otherwise you are buying complexity.
Further reading: Shopify or WooCommerce · a slow site sells less · e-commerce and websites
Frequently asked questions
What is headless e-commerce?
A shop in which the engine (catalogue, basket, orders) is separate from the site the customer sees, which talks to the engine through interfaces.
What is composable commerce?
A shop built from components chosen one by one (search, content, payments) that can be replaced without rebuilding everything.
When is headless best avoided?
If the shop is young, if the only problem is a slow, heavy theme, if the team is small, or if the only goal is to be modern.