Headless commerce: when it makes sense (and when it doesn't)

Vela Commerce·May 14, 2025·8 min read

Headless gets a lot of hype. But it adds real complexity and cost. Here's a clear-eyed framework for deciding whether it's right for your business.

When clients ask us about headless commerce, they usually expect one of two answers: "yes, you should definitely do it" or "no, it's overhyped." The honest answer is neither. Headless is a genuinely powerful architecture for the right context — and a significant liability for the wrong one.

After building headless storefronts for brands from €1M to €100M in revenue, here's the framework we actually use.

What headless actually means

A traditional eCommerce setup couples the frontend (what users see) with the backend (commerce logic, product data, checkout). Change one, you're working within the constraints of the other.

Headless decouples them. Your commerce engine (Shopify, CommerceLayer, BigCommerce, Commercetools) handles products, pricing, inventory, and checkout. Your frontend is a completely independent application — usually built in React or Next.js — that talks to the commerce engine via APIs.

The result: total creative freedom on the frontend, no theme constraints, and the ability to use the best commerce tool for each job rather than one monolith that does everything adequately.

The real benefits

Performance you can actually control

Theme-based storefronts are constrained by the platform's rendering pipeline. Headless lets you own every byte that loads — static generation, edge caching, image optimisation, critical CSS inlining. We regularly achieve sub-0.5s LCP on headless builds that would be 2–3 seconds on a comparable theme.

True omnichannel

One commerce API, multiple frontends: web, mobile app, in-store kiosk, voice. You build the commerce logic once and serve it everywhere. For brands with genuine multi-channel ambitions, this is transformative.

No platform ceilings

Theme limitations disappear. Complex UI patterns, custom checkout flows, real-time personalisation — these are engineering problems, not platform permission problems.

The real costs (that get undersold)

The honest number: A well-executed headless build typically costs 2–4× more than an equivalent theme-based build, and takes 30–50% longer to launch. Ongoing maintenance requires frontend engineering capability that many brands don't have in-house.

Build complexity

You're building a custom application, not configuring a product. Cart logic, search, filtering, wishlist, product recommendations — all of these need to be built or integrated. With a platform theme, they're included.

Checkout is still constrained

Shopify's headless checkout is better than it used to be with Shopify Functions and Checkout Extensibility, but you're still working within their checkout UI. True custom checkouts require custom solutions — which adds scope.

Ongoing engineering dependency

Theme-based stores can often be managed by non-engineers. Headless builds cannot. You need frontend engineers for ongoing development. If you don't have them in-house, you need an agency partner permanently.

When headless makes sense

Traffic above ~500k monthly sessions where performance gains have meaningful commercial impact
Complex UX requirements that no theme can deliver (highly interactive configurators, real-time inventory, custom search)
Genuine omnichannel — web, mobile app, and in-store all needing the same commerce data
You have engineering capability in-house or a committed agency relationship
Your content and commerce are deeply intertwined and need to be managed together

When it doesn't

You're early stage and need to launch fast — a great Shopify theme will outperform a mediocre headless build
Your current platform is performing well commercially — if conversion is strong, headless won't help it
You don't have or can't afford ongoing engineering support
Your team needs to make frequent content and product changes without developer involvement
Budget is constrained — that money is usually better spent on CRO and marketing on a well-configured theme

The middle path

Most brands don't need fully headless — they need specific parts of their experience to be custom. Shopify's Storefront API lets you build custom sections, sub-pages, or experiences while keeping the rest of the platform intact. This hybrid approach gives you 80% of the flexibility at 30% of the cost.

Our default recommendation: start with the best available theme, instrument everything, and only go headless when you have specific, measurable problems that headless will solve — not because it sounds impressive in a board deck.

Want to put this into practice?

We help brands apply exactly this kind of thinking to their actual business.