GuidesE-commerce

Headless commerce: separating the store from its storefront

By the Banzai Labs teamUpdated on 2 min read

APICommerceFree storefrontsOne engine
In headless, one commerce engine serves several storefronts through an API.

The principle

All-in-one, or separated
Classic store
  • Engine and display tied together
  • One theme, some settings
  • Quick to launch
Headless
  • The engine exposes an API
  • Website, app, kiosk: each has its own display
  • Complete design freedom

When it is a good idea

Situation Headless?
One store, one website, a theme that fits No
Website and mobile app on the same catalogue Yes
Rich editorial content mixed with products Often
Small team with no developer No

What it takes

  • Storefront development: cart, account and search to rebuild.
  • Careful caching of product pages.
  • A team to maintain the code over time.

To compare engines: Shopify or WooCommerce. To launch simply: Launching a Shopify store.

Frequently asked questions

Is headless faster?
It can be, because the storefront is built freely, often as static pages. But a well-optimised Shopify theme is already fast: speed alone does not justify the switch.
Can Shopify be headless?
Yes, through its Storefront API, with its Hydrogen framework or any other. Management and checkout stay with Shopify.
How much does a headless store cost?
More than a theme: the storefront is custom development that must be maintained. It pays off with several channels or an experience themes cannot deliver.

Read next

All guides