Why headless Shopify is usually the wrong first move

Headless commerce has become the default recommendation for many agencies pitching "scalability". But for 90% of brands doing under £20m turnover, it is often an over-engineered distraction that adds cost, complexity and dependency on specialist developers.

The Operational Overhead

Moving to a headless React or Hydrogen stack disconnects you from the native Shopify ecosystem. Apps that used to "just work" now require custom API middleware. Your marketing team loses the ability to drag-and-drop sections in the Theme Editor unless you invest heavily in a visual CMS like Sanity or Contentful.

The result: higher monthly costs, slower content updates and a dependency on developers for every small change.

The Real Cost

Most agencies quoting headless builds understate the true cost. The initial build might be £40k-£80k, but ongoing maintenance, hosting and the CDN layer add £1k-£3k per month on top of your existing Shopify subscription.

For brands doing £2m-£5m, that is a significant overhead with questionable return.

When Headless Actually Makes Sense

There are legitimate use cases, but they are narrower than most agencies suggest:

• You have a multi-market setup with radically different content needs per region
• You are selling complex configurable products that defy standard product models
• You have an in-house engineering team to maintain the stack long-term
• Your checkout requires deep customisation beyond Shopify Functions

The Better Path for Most Brands

Shopify 2.0 with Online Store 2.0 themes, combined with good metafield architecture, handles most requirements. Pair it with Shopify Functions for checkout logic and the Storefront API for specific headless features (like a custom product configurator) while keeping the rest on the standard stack.

This hybrid approach gives you the flexibility where you need it without the blanket complexity of going fully headless.