Glossary · E-commerce

Headless commerce

Headless commerce is an e-commerce architecture that decouples the back office (product catalog, orders, inventory) from the front-end display, with the two communicating through APIs instead of being bundled into one system. A single catalog can then feed a website, a mobile app, and an in-store kiosk without duplicating business logic. It stands apart from all-in-one platforms like standard Shopify, where back end and front end ship together.

Updated on July 10, 2026 · Bertrand Dumast

When headless commerce makes sense

Headless commerce earns its complexity when the same product catalog needs to feed multiple touchpoints with different constraints: a fast website, a native mobile app, an in-store kiosk, a feed to marketplaces. In that situation, duplicating business logic in every interface costs more over time than centralizing it behind APIs and letting each front-end team own its own Core Web Vitals instead of depending on the rest of the platform.

  • Real multi-channel traffic: website, mobile app, kiosks, IoT, all sharing the same catalog.
  • Front-end customization requirements (a highly specific interface, advanced animation) that a standard platform cannot handle natively.
  • An in-house team or agency able to maintain a dedicated front end and the API integration over time.

When it is over-engineering

For a catalog that lives on a single channel, with a small or outsourced team, headless adds complexity that pays nothing back: more components to maintain, more failure points between back end and front end, a higher development and hosting budget for an experience gain that is often marginal. A platform like Shopify or WooCommerce, properly configured, covers most needs of a standard online store.

  • A single sales channel, with no concrete diversification plan in the near term.
  • No dedicated team to maintain a custom front end past launch.
  • The real need is visual customization of the theme, not a different architecture.

How to scope a headless project

Before choosing a headless architecture, clarify what actually justifies it: list the channels to serve today and over the next two years, identify the APIs the front end will depend on (catalog, cart, payment, inventory), and confirm the team taking on the project can maintain it. This is the kind of scoping work we do as part of our Custom E-commerce and B2B offer.

  • Map out the real channels (site, app, marketplace) and their volume before adding architectural complexity.
  • Choose the back office (Shopify, a custom system) independently from the front end, based on product and order management needs.
  • Budget for dedicated front-end maintenance, separate from the back-office platform subscription.
Questions
Does headless commerce cost more than a standard platform?

Usually, yes: you need to build and maintain a dedicated front end on top of the back office, which an all-in-one platform does not require. The extra cost pays off when several channels share the same catalog; it does not pay off for a single-channel store.

Do we have to start from scratch to go headless?

Not necessarily. You can keep the existing back office (Shopify, an ERP) and rebuild only the front end, connected through APIs. That is usually less risky than a full platform migration, as long as the back end exposes the APIs you need.

What is the main risk of a poorly scoped headless project?

Ending up with a custom front end and no team to maintain it long term: every back-end security update or new feature becomes a development project instead of a simple configuration change. The risk is not technical at launch, it shows up after the site goes live.

In practice

View the service Custom E-commerce and B2B

Also worth reading

Related terms.

Shopify Plus

Shopify Plus is Shopify's enterprise tier, built for high-volume merchants and companies running multiple stores.

Learn more

E-commerce replatforming

E-commerce replatforming is the process of migrating an online store from one technical platform to another, for example from Magento to Shopify or from PrestaShop to a custom build.

Learn more

Core Web Vitals

Core Web Vitals are a set of three metrics defined by Google to measure the real loading and interaction experience of a web page: LCP (how fast the main content renders), INP (how responsive the page is to user interactions), and CLS (how visually stable the page stays while it loads).

Learn more
Full glossary

A project where Headless commerce comes into play?

Send us your context. We tell you where to start, with a concrete first opinion and no commitment.

Get advice on my project