E-commerce · 2 min read

· by James Whitaker

Headless stores are faster and more flexible – and more expensive to build. A practical guide to deciding whether your brand needs one.

"Headless" has become one of those words agencies use to sound modern. Underneath the buzz is a simple architectural idea – and a real trade-off. Let's make it concrete.

What headless means

In a classic store, the platform (Shopify, WooCommerce, Shopware) renders the pages your customers see. In a headless setup, the platform only handles products, carts, checkout and orders through APIs – and a separate front-end, usually built with Next.js, renders the experience.

The platform is the "body"; the front-end is the "head" – and you can replace or customise it freely.

What you gain

  • Speed. Server-rendered, edge-cached pages load in under a second on mobile. On our headless builds we see Lighthouse scores of 95+.
  • Design freedom. Editorial layouts, video-first product pages, configurators – nothing is limited by theme structure.
  • Resilience at scale. Traffic spikes hit a CDN, not your platform – a limited drop with tens of thousands of concurrent shoppers stays up instead of taking the store down with it.
  • One front-end for everything. Content, commerce, search and personalisation from different systems, unified in one codebase.

What you pay

  • Higher build cost. A headless store starts at roughly two to three times the price of a well-made theme.
  • You rebuild things the platform gave you for free. Cart drawer, filtering, account pages, discount logic – all of it is your code now.
  • Apps don't just plug in. Many Shopify apps assume a theme. Reviews, upsells and loyalty need API-level integration.
  • You need developers. Content editors keep their CMS, but layout changes go through engineering.

When headless is worth it

  • Mobile conversion is a top-line lever and every 100 ms matters.
  • Your brand experience is a differentiator (fashion, design, premium D2C).
  • You run drops, campaigns or flash sales with extreme traffic.
  • You need to combine commerce with rich content, multiple markets or unusual business logic.
  • Revenue is roughly above €2M/year, so a 10–20% conversion uplift pays for the build quickly.

When it isn't

  • You're launching a new brand and need to test the market. Start with a theme.
  • Your team changes layouts weekly without developers.
  • Most of your growth is still about product-market fit, not site speed.
  • Budget is under ~€30,000 – a great theme with tuned performance will beat a rushed headless build.

A middle path

Shopify's Hydrogen and Storefront API, WooCommerce with a Next.js front-end, or Medusa as a fully open-source backend all let you start pragmatic and go headless later. Good store architecture keeps that door open: clean product data, structured content and no theme-only hacks.

Our rule of thumb

Go headless when you can name the number it needs to move – conversion rate, uptime on drops, time-to-market for new markets – and that number is worth the investment. If you can't, a well-built theme will serve you better today.

E-commerceShopifyNext.jsHeadless

Ready to apply
this?

Let's turn ideas into a plan. Book a free 30-minute discovery call with our team.