Headless Commerce: When It Makes Sense and When It Doesn't
Headless commerce is the right architecture for some e-commerce businesses and completely wrong for others. After 30+ headless implementations, we have a framework we run every prospective client through before recommending it — because the business and technical requirements that justify going headless are specific, and the cost of choosing it without meeting those requirements is real.
What headless actually means
Headless commerce decouples the customer-facing frontend from the commerce backend. Your storefront is built independently (typically in Next.js or similar) and pulls product, inventory, and cart data from the commerce engine (Shopify, Medusa, Commercetools) via API. The benefit is total frontend control. The cost is increased complexity and a higher engineering requirement.
The cases where headless wins clearly
- You need a deeply custom shopping experience that a theme simply cannot deliver
- Your brand invests heavily in editorial content and needs seamless content-commerce integration
- You operate across multiple storefronts, geographies, or brands from a single backend
- Performance is a core business metric — you need sub-1s page loads at scale
- You need to sell across multiple channels: web, mobile app, in-store kiosks, from one system
When to stick with a traditional storefront
If you're launching your first online store, your team has no frontend engineering resource, your product catalog is straightforward, and you need to move quickly — a well-built Shopify theme will outperform a poorly-built headless implementation every time. Headless requires ongoing engineering investment. If that resource isn't there, the architecture works against you.
Headless commerce is not a performance upgrade. It's an architecture that enables performance — if your team has the capability to realise it.
The right question isn't 'should we go headless?' — it's 'what do we need to be able to do that we cannot do with our current setup?' If the answer involves custom experience, scale, or multi-channel complexity, headless is likely the right call. If the answer is 'sell more,' the problem is usually not the architecture.
