BigCommerce

Headless commerce or a theme? How to decide

Is headless worth it? What headless Shopify and headless BigCommerce really cost, the SEO risks, why speed needs tuning, and when a modern theme is the better choice.

For most growing brands, a modern theme is the better choice: it is cheaper to build, cheaper to run and works with the full app ecosystem. Headless commerce is worth it when you have needs a theme cannot meet, such as several regions or brands on one custom front end, very complex content, or a specialist experience, and when you have the budget and team to run it. Headless is not automatically faster, and it adds SEO and maintenance risks you have to manage.

This guide explains what headless means, what it really costs and how to decide.

What headless commerce means in plain English

A normal Shopify or BigCommerce store has two parts joined together: the "back end" that runs products, stock, orders and checkout, and the "front end" that shoppers see. The front end is a theme, built and hosted by the platform.

Headless means separating the two. The platform still runs products, cart and checkout, but the shop front is a separate website your team builds, usually in a JavaScript framework such as React or Next.js. It talks to the platform through APIs and is hosted separately.

Both platforms have an official headless route:

  • Headless Shopify usually means Hydrogen, Shopify's framework built on React Router, hosted on Shopify's Oxygen platform, which Shopify includes at no extra charge on paid plans.
  • Headless BigCommerce usually means Catalyst, BigCommerce's official storefront built on Next.js, which can be deployed to Vercel. BigCommerce is also trialling its own native hosting for Catalyst in closed beta.

You can also build a fully custom front end on either platform's APIs, as many brands did before these frameworks existed.

The real benefits of headless

  • Design and experience freedom. You are not limited by how a theme structures pages, so unusual layouts, configurators or app-like experiences are easier.
  • One front end, many back ends. You can combine commerce data with a separate content system, search tool or several storefronts in one site.
  • Control over URLs and routing. On Shopify, the standard online store uses fixed subdirectories such as /products/ and /collections/, which Shopify says cannot be edited. A headless front end can use any structure you choose.
  • Performance potential. A well-built headless site can be very fast, because you control exactly what loads and when.

The real costs of headless

Build cost

A headless build is a software project, not a theme customisation. Everything a theme gives you for free (navigation, filtering, account pages, search, cart behaviour, translations) has to be built or configured and tested. Expect a larger build budget and a longer timeline than a theme.

Hosting and running costs

Hosting may be included (Oxygen for Hydrogen) or a separate bill (Vercel or your own cloud). On top of that you pay for a content system, monitoring, and the developer time to keep frameworks and dependencies up to date. A theme store has almost none of this overhead.

Team skills

Your team, or your agency, needs JavaScript developers who understand caching, rendering and APIs. Marketing teams also lose some independence: changes that take minutes in a theme editor may need a developer or a content system set up specifically for them.

App compatibility

This is often underestimated. On Shopify, many apps add features to your store through theme app extensions, which integrate with Online Store 2.0 themes. On a headless site, reviews widgets, upsells, loyalty and similar tools usually need custom integration through their APIs, if they offer one. Check every app you depend on before you commit.

SEO risks

Search engines need to see complete pages, correct status codes and stable URLs. Headless sites commonly go wrong in a few places:

  • Pages rendered only in the browser, so content and links are not in the initial HTML.
  • Missing or wrong canonical tags, hreflang tags and structured data.
  • Sitemaps that include the wrong URLs or miss new ones.
  • Error pages that return a "200 OK" status instead of 404.
  • Old URLs left without redirects during the switch.

How to avoid them: render pages on the server, create a full URL map and redirect list before launch, test status codes and canonicals on every page type, and monitor rankings and crawl errors for at least 90 days after go-live.

Speed is not automatic

Headless is often sold as the fast option. In reality, a headless site is only as fast as it is built and tuned. Heavy JavaScript, uncached data requests and large images can make it slower than a good theme.

L'azurde, a jewellery brand selling in Saudi Arabia, the UAE and Egypt in Arabic and English, runs a headless BigCommerce store with a Next.js front end. Before our speed work, its homepage scored 42 for mobile and 48 for desktop on Google PageSpeed, and the main content took 8.1 seconds to appear. After tuning, mobile reached 93, desktop reached 100 and the main content time fell to 3.1 seconds. The architecture was the same before and after. The difference was the work on how the site loaded and cached. You can read more in the L'azurde case study.

If you go headless, budget for performance work from the start, and keep budgeting for it as the site changes. Our site speed optimisation page explains how we approach it.

When a modern theme is the better choice

Modern themes are far more capable than they were a few years ago.

On Shopify, Online Store 2.0 themes use JSON templates so your team can add, remove and rearrange sections on most pages from the theme editor. Apps plug in through theme app extensions without code edits, and Shopify's checkout and hosting are handled for you.

On BigCommerce, Stencil is the theme engine, with Cornerstone as the default theme to build from. Stencil themes give you a fully hosted storefront with page building tools, and you keep BigCommerce's native checkout and app integrations.

A theme is usually the right call if:

  • Your catalogue and content fit standard product, collection and content pages.
  • Your marketing team wants to launch pages and campaigns without developers.
  • You rely on several apps for reviews, subscriptions, loyalty or search.
  • Your budget is better spent on conversion, content and marketing than on running a custom front end.

A good theme can still move the numbers. Perky Pear moved to a new Shopify theme and saw conversion rise from 7% to 8.5% and average order value from £25 to £31, without going headless. See the Perky Pear case study.

Is headless worth it? A decision checklist

Question Points to a theme Points to headless
Can a theme deliver the experience you need? Yes, with sections and some custom code No, you need custom layouts or app-like features
How many storefronts or regions? One store, or a few handled by Markets or Multi-Storefront Many regions or brands on one shared front end
Who edits the site day to day? Marketing team in the theme editor Developers, or a content system set up for marketers
Do you have in-house or retained developers? No, or only a few hours a month Yes, with JavaScript and performance skills
How dependent are you on apps? Heavily Lightly, or your key tools have good APIs
Budget for build and ongoing running costs? Limited, or better used on marketing Yes, including ongoing performance and SEO work
Do you need full URL control? Platform URLs are acceptable Yes, for example to keep a legacy structure

If most of your answers sit in the theme column, start with a theme. Going headless later is a front end rebuild, not a replatform, so you lose nothing by waiting.

FAQs

Is headless Shopify faster than a Shopify theme?

Not automatically. A well-built headless site can be very fast, but so can a well-built theme. Speed depends on how much code loads, how data is cached and how images are handled.

Does headless commerce hurt SEO?

It does not have to, but it adds risk. Render pages on the server, keep canonicals, hreflang, sitemaps and status codes correct, and redirect every old URL at launch.

Is headless BigCommerce different from headless Shopify?

The idea is the same. Shopify's official route is Hydrogen hosted on Oxygen, and BigCommerce's is Catalyst, built on Next.js. The best fit depends on your catalogue, markets and team skills more than the framework.

Can we start with a theme and go headless later?

Yes. Your products, customers and orders stay on the platform, so you can replace the front end later without migrating your store data.

How Superior can help

We build and tune both theme and headless stores on Shopify Plus and BigCommerce. If you are deciding between the two, our technical consulting team can review your requirements and give you a straight answer.

All insights

Start a project

Want help with this?

Tell us about your store. We reply within one working day with next steps.

Prefer email? hello@superiorecom.com