Headless commerce
E-commerce with a separate frontend
Headless commerce is an approach to building an online store that separates the visible storefront (frontend) from its core handling products, the cart, and orders (backend). The two layers talk to each other over an API. As a result you can change the design and add sales channels without touching the store’s logic.
How the headless approach works
In a classic store, the storefront and the business logic form one tightly bound whole. In a headless architecture these layers are split apart. The backend, which handles products, prices, the cart, and orders, sends data over an API, and a separate frontend displays it. The word headless means exactly this: separating the body of the store from its visible head.
The same core can then serve several storefronts at once: a website, a mobile app, sales through social networks, or an in-store kiosk. Each channel looks and behaves as needed, while products, stock, and orders are run from one shared place.
What benefits it brings
Splitting the layers mainly delivers freedom and speed. That shows up in the store’s everyday operation.
- A custom frontend allows markedly faster loading and a smoother experience for the customer.
- You change the design and user experience without the limits of a commerce platform’s template.
- One core serves several channels at once, which simplifies omnichannel selling.
- Individual parts of the solution can be developed and deployed independently of each other.
When headless pays off
Headless is a strong choice for stores with higher demands on speed, look, or the number of sales channels, or for projects where a standard template stops being enough and a custom e-shop makes sense. It does, however, require more development and care across several separate parts.
For a smaller store with standard needs, a classic solution is usually simpler and cheaper. The decision therefore depends on your goals: whether you need maximum flexibility, or rather a fast, low-effort launch.
Need a fast, flexible online store?
See our e-commerce buildsFrequently asked questions
Is headless commerce suitable for every store?
No. It pays off most for larger, more ambitious stores that need high speed, an unusual design, or several sales channels. For a smaller store with standard needs, a simpler and cheaper classic solution is usually the better fit.
What is the difference between headless and a classic store?
In a classic store the storefront and business logic form one whole. In a headless approach they are separated and talk over an API, so you can change the frontend and add channels independently of the core that runs products and orders.
Does headless commerce need custom development?
Usually yes. Because you build the frontend separately and connect it to the core over an API, a headless solution involves more development than deploying a ready-made template. In return you gain full control over both look and performance.