“Headless” is one of those words that gets used as if it were automatically better. It isn't. It's a trade-off that suits some stores very well and others not at all. Here's what it actually means, what you gain, what it costs, and how to tell which side of the line you're on.

What headless means

A traditional online store uses the platform's own theme system for everything customers see. The platform stores the products and handles checkout, and it also renders the pages. A headless store splits those jobs. The platform keeps doing what it's good at — products, inventory, carts, checkout, orders — while the storefront is built as a separate, custom application that talks to the platform through its APIs.

The “head” is the part customers see. Headless means the commerce engine doesn't come with one; you build your own.

What you gain

  • Speed — a custom front end can be much leaner than a theme carrying many plugins and scripts.
  • Design freedom — layouts and interactions aren't limited by what the theme system supports.
  • Content flexibility — combine products with rich editorial content from a dedicated CMS.
  • Multiple storefronts — a website, an app and in-store screens can share one commerce engine.
  • Independence — you can change the front end without migrating your orders and customers.

What it costs

  • More engineering, both to build and to maintain — you now own a whole application.
  • Some platform apps and plugins that inject features into the theme won't work without extra integration.
  • Your team needs a workflow for previewing and publishing content across systems.
  • Hosting, monitoring and security for the front end become your responsibility.

Signs headless might suit you

  • Your brand depends on a distinctive, highly designed experience a theme can't deliver.
  • Content — guides, stories, lookbooks — is central to how you sell.
  • You sell through several channels and want one source of products and orders.
  • Performance problems persist even after a well-optimised theme.
  • You have, or can afford, ongoing engineering support.

When to stay on a theme

If your catalogue is modest, your marketing team relies on platform apps for reviews, upsells and promotions, and your theme performs well after proper optimisation, a carefully built theme is often the smarter choice. Modern commerce platforms' themes are far more capable than they used to be, and the money saved can go into photography, content and marketing — which may matter more.

Go headless to solve a problem you actually have, not to own an architecture diagram.