Headless means separating the storefront your customers see from the commerce engine handling products, carts and payments. The two talk over an API. It is presented as the modern default, and for most stores it is the wrong choice.
What it genuinely buys
- Speed ceiling. You control every byte on the page, with none of the platform's theme layer or app scripts.
- Design freedom. No theme constraints, no fighting a template to build something unusual.
- One engine, many front-ends. A website, a mobile app and an in-store kiosk sharing a catalogue.
- Independence. Swapping the storefront framework later does not mean re-platforming commerce.
What it costs, beyond the build
| Cost | Detail |
|---|---|
| Rebuilt features | Search, filtering, reviews, wishlists, promotions. All shipped in a theme, all now yours |
| Checkout limits | Some platforms only allow their own checkout. You go headless up to payment, then hand back |
| Preview and editing | Merchandisers lose the visual editor. You build a preview, or they work blind |
| Two systems to maintain | A storefront deploy pipeline plus the commerce platform, forever |
| Ongoing hosting | Modest, but real, and it never appeared on the quote for a themed build |
When it is the right call
- 01Page speed is a genuine competitive advantage, not a score you want to feel good about. High-traffic stores where a tenth of a second is measurable revenue.
- 02The storefront needs to do something a theme structurally cannot. A configurator, an interactive tool, a hybrid of application and shop.
- 03You are serving several front-ends from one catalogue and duplicating merchandising work across them.
If none of those describes you, a well-built theme on a mid-range platform will get you most of the performance at a fraction of the cost and complexity.
The failure pattern
A team chooses headless for the architecture, then spends the following year rebuilding admin features their previous platform included for free. The site is fast and nobody can merchandise it without a developer.
Before committing, list every feature your team touches weekly and ask which of them you are about to rebuild. That list is the real quote.
Working on something like this?
We build websites, stores and custom applications, and we will tell you honestly if the thing you are describing does not need one.