Digital Transformation

Headless Commerce: Who Needs It and Who Doesn’t

What headless commerce is, what it really costs and which stores benefit. A plain-English decision guide for Shopify, WooCommerce and Magento brands.

TL;DR
  • Headless commerce separates the storefront customers see from the commerce engine that runs products, carts and orders, connected by APIs. It buys design and content freedom at the cost of a permanent engineering team.
  • Most $1M to $25M stores don't need it. A well-built theme on Shopify, with fewer apps and better images, usually solves the speed and flexibility problems that prompt the headless conversation.
  • Headless makes sense when you have a concrete requirement a theme can't meet, and the budget and people to own a custom front end for years, not just to launch it.

What is headless commerce?

In a traditional setup, your platform does two jobs. It runs the commerce back end (products, inventory, pricing, carts, checkout, orders) and it renders the storefront through a theme. On Shopify that’s a Liquid theme; on WooCommerce, a WordPress theme; on Magento, its own theme layer.

Headless commerce splits those jobs. The platform keeps the back end. A separate front end, usually a JavaScript application built with a framework like React, pulls data from the platform through APIs and renders the pages. On Shopify, that front end talks to the Storefront API, and Shopify offers its own framework, Hydrogen, and hosting, Oxygen, for building and running it. Many headless builds also add a content management system, such as Contentful or Sanity, for editorial pages.

The checkout usually stays with the platform. On Shopify, headless storefronts hand shoppers to Shopify’s checkout, so payments and order processing work as before.

Headless vs. composable

You’ll also hear “composable commerce.” Headless is about separating the front end. Composable goes further: every part of the stack (search, CMS, promotions, OMS, PIM) is a separate service you choose and connect. Composable is headless plus many more contracts and integrations. For most brands in this article’s range, it’s a bigger step again.

Why do brands consider going headless?

The reasons usually sound like these:

  • “Our site is slow.”
  • “Our designers want layouts the theme can’t do.”
  • “We want to publish rich content and shoppable editorial.”
  • “We sell in several regions or brands and want one front end for all of them.”
  • “We want the same product data in an app, in-store screens and on the website.”

Some of these are good reasons. Others are problems a theme can solve for far less money.

What does headless actually solve, and what doesn’t it?

Reason given Does headless solve it? Cheaper alternative to try first
Slow site Sometimes. A well-built headless front end can be fast, but a poorly built one can be slower Remove unused apps and scripts, fix image sizing, avoid lazy-loading the main image, audit the theme
Design limits Yes, if the limits are real Custom sections and blocks in a modern Shopify theme cover most layouts
Rich content Yes, especially with a dedicated CMS Shopify metaobjects, blog templates and custom sections
Multiple brands or regions on one front end Often yes Shopify Markets, or separate stores with a shared theme
Same data across web, app and in-store Yes, this is a strong fit Few alternatives at real scale
Better SEO No, not by itself Technical SEO on the current theme
Higher conversion rate Not by itself Conversion research and testing

Speed deserves a closer look because it’s the most common reason. Core Web Vitals problems on Shopify stores usually come from apps injecting scripts, oversized hero images, heavy sliders and third-party widgets. A headless rebuild removes those only if the team chooses not to rebuild them. If you add the same reviews widget, chat tool, personalization script and tracking pixels to the new front end, you rebuild the same problems at a higher cost. Our guide to Core Web Vitals for Shopify shows what usually moves LCP on a theme.

The same goes for SEO. A JavaScript front end can rank well, but only if it renders content for crawlers, outputs correct canonicals and structured data, and handles redirects and sitemaps. Those were mostly handled for you on a theme. In headless, your team builds and maintains every one of them.

What does headless cost?

The build is the visible cost. The ongoing cost is the one that catches brands out.

Cost area Theme-based store Headless store
Front-end build Theme purchase or custom theme Custom application, often several months of development
Hosting Included with the platform Separate hosting, or the platform’s own (such as Oxygen on Shopify)
Apps Install and configure Many theme-based apps won’t work on a custom front end; you integrate their APIs or replace them
Content editing Theme editor, available to marketers A CMS that needs setup, or developer help for page changes
Tracking Platform pixels and app integrations Analytics, ad pixels, consent and the data layer built by hand
Maintenance Platform updates the theme layer Your team owns dependencies, upgrades, bugs and security for the front end
People Agency or freelancer as needed Developers on staff or on retainer, permanently

Here’s an illustrative way to frame the decision. Suppose a headless build costs $150,000 and ongoing development another $120,000 a year, compared with $30,000 for a custom theme and $30,000 a year in upkeep. The extra cost in year one is $210,000. At a 40 percent contribution margin, the store needs about $525,000 in additional revenue in year one just to break even on the move, and about $225,000 in additional revenue every year after that. These numbers are for illustration only; get real quotes. The calculation is the point: divide the extra cost by your contribution margin to see the revenue headless has to produce.

Who should go headless?

Headless tends to make sense when several of these are true at the same time:

  • You have a specific requirement a theme genuinely can’t meet, written down and tested against what modern themes can do.
  • You serve the same catalog to several front ends: website, mobile app, in-store kiosks, partner sites.
  • Content and storytelling are central to how you sell, and editors need a richer CMS than the platform provides.
  • You have, or will fund, an in-house or retained engineering team for the long term.
  • Your revenue is large enough that the extra cost is a small share of contribution margin.
  • You’ve already fixed the basics (apps, images, tracking) and still hit the limits.

Who doesn’t need it?

Headless is usually the wrong move when:

  • The main goal is speed, and you haven’t yet removed unused apps or fixed images on your current theme.
  • Marketers need to launch landing pages and promotions without developer help.
  • Your growth depends on installing and testing apps quickly.
  • You don’t have engineering staff and don’t plan to hire them.
  • The problem is really conversion, retention or acquisition. A new front end doesn’t fix offers, flows or ad efficiency.

For most stores between $1M and $25M, the better investment is a well-built theme on Shopify or Shopify Plus, with spend going into retention, conversion testing and measurement. If you’re weighing a platform move first, our Shopify Plus migration checklist covers what to plan.

Is there a middle ground?

Yes. Some brands keep the theme for product, collection, cart and account pages and use a headless CMS or a separate front end only for editorial content. Others build a custom app on the Storefront API while keeping the theme-based website. These hybrids give you flexibility where it matters and keep the cost of headless away from your revenue-critical templates.

How do you decide? A practical checklist

Answer these before talking to a headless agency:

  • [ ] We have listed the specific features or experiences the current theme can’t deliver, and confirmed with a theme developer that they really can’t.
  • [ ] We have fixed known speed problems on the current site (unused apps, images, scripts) and measured the result with field data.
  • [ ] We have priced every app we rely on and confirmed whether it works headless, has an API or needs replacing.
  • [ ] We have a plan for tracking, consent and the data layer on the new front end.
  • [ ] We have a plan for SEO: rendering, canonicals, structured data, redirects and sitemaps.
  • [ ] We know who will maintain the front end in year two and year three, and what it costs.
  • [ ] We have calculated the extra revenue needed to cover the extra cost, using contribution margin.
  • [ ] Marketing, merchandising and customer service have reviewed how their daily work changes.

If you can’t check most of these, you’re not ready, and that’s a useful finding. Treat a headless move as a change management project, not just a build.

What should you do next?

Start with the problem, not the architecture. Measure what’s slow, what’s limiting and what it costs you. Then compare the cheapest fix that solves it with the headless option, over three years, in contribution margin. If headless still wins, plan it properly, with tracking, SEO and app replacements in scope from the first day.

FAQ

Is headless commerce faster than a Shopify theme?

It can be, but it isn’t automatically. A carefully built headless front end can load quickly, and a poorly built one can be slower than a well-tuned theme. Most speed problems on Shopify come from apps, scripts and images, which you can fix without going headless.

Does headless commerce help SEO?

Not by itself. Search engines can index well-built JavaScript storefronts, but your team must handle rendering, canonical tags, structured data, redirects and sitemaps that a theme manages for you. Done badly, a headless launch can lose rankings.

Can I go headless on Shopify without Shopify Plus?

Shopify’s Storefront API and Hydrogen are available beyond Plus, but plan features and limits change, so check Shopify’s current documentation for your plan. The bigger question for most brands is whether they have the engineering budget to maintain a custom front end, not which plan they’re on.

Turn this into a plan for your store

The Free Profit Audit scans your store, sizes your biggest profit leaks and builds a 90-day plan.

Free Profit Audit