Term
Headless commerce
An online shop architecture in which the customer-facing front end is separated from the commerce system handling products, basket and orders, and connected via API. It allows a fast, flexible site but is more demanding to build.
Updated
What it means
Headless commerce is an online store architecture in which the customer-facing front end, the website or app, is separated from the commerce system that handles products, basket, orders and payments. The two communicate through an API, so each can be developed and changed independently.
In a traditional shop, the look is tightly bound to the platform and its templates. A headless approach makes it possible to build a fast, flexible site on modern technologies and connect the same commerce system to a mobile app, an in-store kiosk or a marketplace.
It is often combined with a headless CMS for content, a PIM for product data and other services in a microservices style. The whole is sometimes called a composable architecture, in which the company assembles its solution from best-of-breed components.
How it works in practice
The main benefit is site speed and performance, which improve Core Web Vitals, conversions and SEO. The company can change the look and customer experience without touching business logic and test new features faster.
The downside is higher development and maintenance costs. Instead of one platform there are several systems and integrations to manage, and the company needs in-house developers or a reliable partner. For a small shop with ordinary needs, a traditional platform is often better.
When moving to headless, SEO needs care: preserving URLs, redirects, structured data and server-side rendering so search engines see the content. A badly handled migration can cause a sharp drop in organic traffic.
What to watch out for
More systems mean more points of failure and more suppliers. Monitoring, clear ownership of each part and contracts covering availability and support are essential, or nobody knows whom to call during an outage.
A headless setup can increase dependence on specific vendors and their APIs. When choosing components, check data export options, standard interfaces and the cost of replacement, so the company does not get stuck with an expensive solution.
Need the term explained on your own situation? Consulting from €55 / hour excl. VAT, depending on topic and complexity.