Headless commerce: complete guide

Headless commerce is an ecommerce architecture where the frontend (the store the user sees) is completely separated from the backend (catalogue, cart, checkout, payments, inventory). Both layers communicate through REST or GraphQL APIs.

Unlike a monolithic platform where the interface is predefined by the system, in headless the development team has full freedom to build the shopping experience with their preferred technology: React, Next.js, Astro, a native app or even a physical point of sale.

A typical headless commerce architecture consists of a transactional backend that exposes APIs for products, pricing, cart, checkout and order management. The frontend consumes these APIs and handles only the visual and interactive experience.

In mature implementations, a middle layer (BFF — Backend for Frontend) is added to orchestrate calls to multiple services: CMS for editorial content, search engine (Algolia, Typesense), payment gateway (Stripe, Adyen), CRM and recommendation engine. This composable architecture lets you pick the best service for each function.

The most tangible benefit is performance. A decoupled frontend served from a CDN with static or SSR rendering loads significantly faster than a monolithic store. Every 100ms improvement in load time can increase conversion by 1% to 3%.

Additionally, headless allows iteration on the shopping experience without risk to the transactional engine. The marketing team can launch landing pages, campaigns and interactive experiences without depending on the backend team or risking checkout stability.

Shopify Plus with its Storefront API and Hydrogen (React framework) is the most popular option for brands already on Shopify. commercetools is the enterprise reference with a MACH approach (Microservices, API-first, Cloud-native, Headless). Medusa and Saleor are open-source alternatives with growing communities.

BigCommerce also offers solid headless capabilities. The choice depends on transaction volume, catalogue complexity, target markets and budget. For projects with fewer than 10,000 SKUs and one primary market, Shopify Plus or Medusa are usually sufficient. For multi-country operations with complex catalogues, commercetools provides greater flexibility.

Headless commerce is not free in terms of complexity. It requires a development team capable of building and maintaining the frontend, managing integrations with multiple APIs and solving problems like session management, persistent cart and real-time inventory synchronisation.

Total cost of ownership (TCO) can be higher than a monolithic platform, especially in the first months. It is essential to evaluate whether your team has the technical capability and whether the benefits in performance and experience justify the additional investment.

Headless commerce makes sense when the shopping experience is a competitive differentiator, when you need a presence across multiple channels, or when your current platform limits the speed of innovation. If your store works well with a standard template and you have no advanced personalisation needs, an optimised monolith remains a valid and more affordable option.

The recommended approach is progressive: start with a headless frontend for your primary web channel, validate the results in performance and conversion, and expand to other channels gradually.