What is headless commerce?

Headless commerce is an ecommerce architecture that separates the storefront customers see from the backend that runs products, carts, checkout and orders. The two connect through APIs, so one backend can power a website, a mobile app or any other internet-enabled device.

Updated November 2026

Illustration of two storefront windows showing products, surrounded by separate building blocks
Contents

How headless commerce works

A traditional ecommerce platform ships the storefront and the backend as one system. Headless commerce separates them into a frontend application that shoppers use and a commerce backend that holds the data and business rules. Every exchange between the two goes through an API, so neither side depends on how the other is built.

  1. A shopper opens a product page. The frontend, built in a framework such as Next.js or Nuxt, requests the product, price and stock from the commerce API.
  2. The backend returns the data and the frontend decides how to display it. The same response can feed a website, a mobile app or an in-store screen.
  3. Cart and checkout actions go back through the API, where the backend applies pricing, discounts, tax and shipping rules. Checkout can be hosted by the platform or built as a custom flow.
  4. When the order is placed, the backend records it and sends events or webhooks to connected systems, such as an ERP, an email tool or a fulfillment provider.

Because the layers are separate, a frontend team can redesign the storefront or add a channel without touching the backend, as long as the API stays the same.

Headless vs. traditional commerce

In software architecture, a monolith is an application that keeps data storage, business logic and user interfaces in one tightly coupled system. Traditional commerce platforms work this way. Shopify and WordPress, released in 2006 and 2003, helped a generation of merchants and publishers get online by combining a back office, a theme editor and a template engine in one product.

Monoliths gain features over time, and those features build up dependencies between parts of the system. Themes have to work inside the platform’s templating system, while frontend developers have moved to libraries like React, Vue and Svelte that assemble data from several sources by API. Headless commerce lets those teams work in their own tools while the commerce system stays in place, and Shopify and WordPress both offer APIs for headless builds today.

  • Headless
    Traditional
  • One backend can power multiple frontends and sales channelsvsOne backend powers one frontend, and the two sides are tightly coupled together
  • Provides a single source of truth for products, customers, orders, content, and promotionsvsProvides store administration, product management, and an editor in one system
  • No technology lock-in for frontends, allowing for any capability the backend supportsvsGood for simple use cases, struggles to meet complex requirements
  • Storefront changes ship on your own release schedulevsStorefront changes happen inside the theme system
  • Needs developers to build and maintain the storefrontvsA merchant can launch and edit a theme without code

Benefits of headless commerce

Headless commerce gives teams more control over the storefront and lets one backend serve several channels.

  • Control the customer experience

    Design every page and interaction without the limits of a theme, using the frameworks your team already knows.

  • Sell on more channels

    Power a website, mobile app or in-store screen from one catalog and one set of orders.

  • Tune performance

    Build a frontend that loads only what each page needs, with rendering and caching under your control.

  • Unite B2B and B2C

    Run your wholesale and retail operations from a single catalog and dashboard. Use separate storefronts made for each audience, or provide a unified experience for both.

  • Sell internationally

    Localize your stores with multiple content languages and currencies, and give a market its own storefront when it needs one.

  • Change one part at a time

    Replace a frontend, CMS or search tool without replatforming the commerce system behind it.

Drawbacks of headless commerce

Headless commerce adds work that a theme-based store doesn’t have, so the benefits need to justify the extra cost.

  • You need developers

    Someone has to build the storefront, connect it to the APIs and maintain it after launch.

  • Higher upfront cost

    A custom frontend takes longer and costs more to build than a theme, and hosting, monitoring and testing join the budget.

  • Editing tools can shrink

    Theme editors and page builders may not work on a custom frontend, so teams often add a CMS to keep content out of code.

  • Apps may not carry over

    Apps that add features by injecting code into a theme may need an API integration or a rebuild on a custom storefront.

  • Checkout needs a decision

    A hosted checkout limits what you can change. A custom checkout gives you full control and makes payments and testing yours to handle.

  • SEO is yours to manage

    Server rendering, metadata, structured data, redirects and sitemaps become your team’s responsibility.

When to use headless commerce

Headless commerce suits businesses whose storefront needs have outgrown a theme and that have developers to maintain a custom frontend.

Headless is a good fit when

  • A theme can’t deliver the experience you need, such as a product configurator, a member portal or a custom subscription flow
  • You sell across several channels or need multiple storefronts on one backend
  • Commerce has to fit into an existing site, app or proprietary stack
  • You have developers or an agency to maintain the storefront after launch

A theme is a better fit when

  • You’re launching a new store and speed matters most
  • A standard storefront covers what you sell
  • Your team needs to edit the store without developers
  • Your budget doesn’t cover ongoing frontend work

Swell’s storefront docs take the same view: themes and storefront apps are the recommended starting point for new stores, and headless storefronts suit integrations with an existing site or a proprietary stack.

Headless vs. API-first vs. composable

These terms are sometimes used interchangeably, but they describe different things.

  • Headless means the storefront is separate from the backend. It says nothing about how the backend is built.
  • API-first means the API was designed as the main way to use the platform, so system data and functionality are available through one unified API or a suite of APIs with the same behavior and design patterns.
  • Composable means the stack is assembled from separate services, such as search, CMS and payments, that can each be replaced. It’s often linked with MACH: microservices, API-first, cloud-native and headless.

A number of monolithic CMS and ecommerce vendors have added APIs to their products and now market themselves as headless. When APIs are added to an existing product later, some common pitfalls appear:

  • Not all platform functionality is available via API, limiting the scope of what developers can do.
  • Functionality provided by third-party apps may not be available via API unless the app vendor offers its own, in which case there may be synchronization issues.
  • To fit with existing architecture, multiple APIs are needed to interact with different parts of the platform, sometimes with inconsistent behavior.

The impact of these shortcomings often isn’t clear until later, when considerable resources have already been spent integrating the platform.

What a headless stack includes

A headless store is a set of connected services. A typical stack includes:

Commerce backend
Products, pricing, carts, checkout, orders, customers and subscriptions.
Frontend framework
Next.js, Nuxt or another framework that renders the storefront.
Frontend hosting
A platform such as Vercel or Netlify that builds and serves the storefront.
Content management
A CMS for pages and editorial content, if the commerce platform doesn’t cover them.
Search
Product search and filtering, from the platform or a dedicated provider.
Payments, tax and shipping
Gateways and services connected through the commerce backend.
Email and analytics
Transactional and marketing email, plus tracking that you set up on the new frontend.

How to evaluate a headless platform

When evaluating headless solutions, it’s critical to assess the scope of the API (what it can do) and the developer experience (how easy it is to work with), preferably by building a small prototype of the desired solution.

API coverage
Can every feature you need be reached through the API, including discounts, subscriptions and data added by apps?
Checkout
Is there a hosted checkout, can you build a custom flow, and which payment gateways work with each?
Data model
Can you add custom fields and models without workarounds, and do they appear in the same API?
Extensibility
Are there events, webhooks and functions for custom logic, and where does that code run?
Developer experience
Are the docs, SDKs and starter kits current, and can you build against a test environment?
Operations
Who runs hosting, upgrades, security and uptime?
Pricing
Are prices published, and what triggers overage or usage charges as you grow?

Platforms sold as headless include hosted suites that added storefront APIs, hosted API-first platforms, enterprise platforms, and open-source platforms you can run yourself. Each splits hosting, upgrades and checkout work differently. For prices and fit by platform, see our guide to the 10 best headless commerce platforms.

Headless commerce with Swell

Swell is a modern SaaS ecommerce platform making sophisticated customer experiences more accessible to smaller businesses, with capabilities like subscriptions, content management, and localization baked into the core. Swell hosts the backend, admin dashboard and checkout, and you choose how much of the storefront to build.

Backend and Frontend APIs
The Backend API handles server-side work with secret keys. The Frontend API covers carts, checkout, customer accounts and subscriptions from the browser, and the Swell.js SDK works with any JavaScript framework.
Hosted or custom checkout
Use Swell’s hosted checkout or build your own flow with the APIs.
Subscriptions in the core
Sell subscription and one-time items in the same cart, on every plan.
B2B and wholesale
Sell to retail and wholesale customers from one catalog, with customer groups and volume price rules.
Custom data
Add models and fields in the dashboard model editor or through the Backend API.
Themes or headless
Start on a theme or storefront app hosted by Swell, or build a headless storefront hosted wherever you choose.
Smashing MagazineTax rules, invoicing, memberships and bundles that mix physical and digital products.Infinitas LearningA headless store for an educational publisher operating across Europe.SpinnA coffee marketplace linked to a mobile app and a connected brewer.

Read the Frontend API docs, see Swell for developers, or compare plans and pricing.

Frequently asked questions

What does headless mean in ecommerce?

Headless means the frontend, or “head”, is separated from the commerce backend. The storefront is its own application and talks to the backend through APIs.

Does a headless store still have a storefront?

Yes. Going headless doesn’t mean that you don’t have a storefront for customers to shop, only that you aren’t tied to a particular frontend technology and can adapt to new market trends.

What is an example of headless commerce?

A brand that runs a Next.js website and a mobile app on one commerce backend is using headless commerce. Both frontends read the same products and write to the same carts and orders.

Is headless commerce the same as composable commerce?

No. Headless separates the storefront from the backend. Composable commerce builds the whole stack from separate services that can each be replaced. A headless store doesn’t have to be composable.

What is the difference between headless commerce and a headless CMS?

A headless CMS manages content and delivers it through APIs. Headless commerce does the same for products, carts, checkout and orders. Many headless stores use both.

Is headless commerce good for SEO?

It can be, but the results aren’t automatic. A custom storefront can be fast and flexible, and your team becomes responsible for server rendering, metadata, structured data, redirects and sitemaps.

Is headless commerce worth it for small businesses?

Usually only when a theme can’t do what the business needs and a developer or agency can maintain the storefront. Otherwise a theme costs less to build and run.

Can a store move from a theme to headless later?

Yes, on a platform that supports both. Products, customers and orders stay in the backend while you replace the storefront, and any theme-dependent apps or redirects need a plan.

How much does headless commerce cost?

The total depends on the platform fee, the storefront build, hosting, third-party tools and ongoing engineering time. Swell’s plans start at $29 per month billed yearly, each with an included sales ceiling and a published overage rate. See Swell pricing.

What are the best headless commerce platforms?

Swell is our top pick for most custom builds: a hosted, API-first platform with subscriptions on every plan, custom data models and published prices. Shopify with Hydrogen fits brands already on Shopify, and enterprise and open-source platforms suit other teams. Compare the 10 best headless commerce platforms.

Take your brand to the next level with Swell

Create your storeDeveloper docs
3d logo