Glossary · H

Headless Commerce.

Headless commerce is a shop architecture in which the visible interface (the front end) is separated from the shop system in the background (products, cart, payment, orders). The two communicate via an API, so the interface can be designed freely and built with any technology.

Headless Commerce — Explained in Detail

A classic online shop is a package: the shop system manages products and orders and also delivers the pages customers see, usually via a theme. With headless commerce this 'head' is cut off. The shop system remains responsible for catalogue, prices, stock, cart, checkout and order processing; the interface is a separate application that fetches its data through an API. The principle is the same as in headless architecture and the headless CMS, applied to selling.

Well-known shop systems offer their own interfaces for this; Shopify, for example, has the Storefront API and the Hydrogen framework. The front end is often built with a modern framework such as Next.js and delivered pre-rendered. Content such as guides, lookbooks or landing pages often comes from a headless CMS, products and prices from the shop system. The interface combines both.

The benefits lie in design freedom, loading speed and multichannel capability. Product presentations, configurators or animations are not bound by the limits of a theme. Well-built headless front ends load very quickly, which benefits the user experience and the conversion rate. And the same product data can be provided to the website, an app, a kiosk screen or AI agents, which is gaining importance with agentic commerce.

The drawbacks are just as real. A headless shop is a software project, not a theme swap: it needs development, hosting for the front end and ongoing maintenance. Many apps and extensions of the shop system that plug into a theme do not simply work in a custom front end and have to be rebuilt or connected via their API. Marketing staff can no longer change pages in the familiar theme editor unless a CMS is planned in. For many smaller shops a well-implemented theme is therefore the better choice.

When headless commerce pays off

Headless pays off when presentation is a central selling point and a theme is not enough for it, when content and products are to be closely intertwined, when several channels are served from the same data, or when loading time and design remain insufficient despite optimising the theme. Shops with very specific processes, such as made-to-measure configuration, also benefit.

Headless does not pay off when the range is conventional, the budget is tight, no team is available for ongoing maintenance or the shop relies heavily on apps from the ecosystem. Then a cleanly built theme with good image optimisation usually achieves more for less effort. A middle way is to keep the checkout in the shop system and build only individual pages such as the home page and campaigns freely.

Example: a furniture shop with a configurator

An example: a Swiss furniture maker sells tables in many sizes, wood types and finishes. In the standard theme this can only be shown as a long list of variants, and there is no preview of the configured table. With headless commerce the shop system remains responsible for prices, stock, payment and orders, while a custom front end shows the configurator with a live preview and price calculation and hands the result to the shop system as a cart.

Guide content on wood care and dimensions comes from a CMS and links directly to matching configurations. The effort is considerably higher than with a theme, but the result is a shopping experience that could not be built with standard means. How we plan shops is described on the pages Shopify agency Switzerland and e-commerce agency.

Headless Architecture

Frequently Asked Questions About Headless Commerce

It can be considerably faster because the front end is freely optimised and pre-rendered. That is not automatic, though: a poorly built headless front end can be slower than a good theme. The implementation is decisive, not the architecture alone.

Yes. With the Storefront API and the Hydrogen framework, Shopify offers official ways to build a custom front end. Catalogue, checkout, payments and order management stay with Shopify. It is worth checking which installed apps continue to work in the custom front end.

It can be very good for SEO if pages are rendered on the server or statically and deliver clean HTML, structured data and fast loading times. A front end that loads content only in the browser via JavaScript, by contrast, does harm. SEO requirements therefore belong in the concept from the start.

Ready for Your Project?

Apply this knowledge to your website — DLM Digital will help you.

Calculate Costs All Terms