What headless means in practice
In a standard store, the platform renders every page through its theme system. In a headless store, the platform still runs products, carts, customers and orders, but the pages people see are built in a separate application that talks to the platform through APIs. The front end can be hosted anywhere and can pull content from a content management system as well as from the store.
The main platform-backed options are well documented. Shopify describes Hydrogen as a set of components, utilities and design patterns for working with Shopify APIs, built on the React Router framework, and Oxygen as its global serverless hosting platform for deploying Hydrogen storefronts[1]. BigCommerce describes Catalyst as its composable, fully customisable headless storefront framework, built on Next.js[2]. A fully custom front end on another framework is also possible.
Good reasons to go headless
| Reason | Why a theme struggles |
|---|---|
| Content and commerce are equally important | Editorial layouts, long-form guides and shoppable stories are awkward inside most themes |
| Several storefronts share one catalogue | Different brands, regions or channels need different front ends on the same back end |
| Unusual product experiences | Configurators, bundles or calculators that need full control of the interface |
| A team that will keep developing | Headless pays off when developers keep improving the front end after launch |
Weak reasons to go headless
Speed alone is rarely a good enough reason. A well-built theme on a hosted platform can reach Google's "good" Core Web Vitals thresholds, and a badly built headless site can miss them. "Future-proofing" is also vague: a headless build replaces theme limits with application maintenance, dependency updates and hosting bills. If the business does not have, or does not want to pay for, ongoing development, a theme is usually the safer choice.
What changes when you go headless
- Apps that inject scripts into a theme often do not work on a custom front end, so features may need rebuilding
- Previewing content, running sales and editing pages need a content workflow designed for your team
- Checkout usually stays on the platform's hosted checkout, which keeps card handling with the platform
- Search, filtering and redirects become your application's responsibility
- Hosting, monitoring and dependency updates become ongoing costs
Our headless build process
- A written case for headless. We list what the theme route cannot do for you and what headless will cost to build and run. If the case is weak, we say so before any build money is spent.
- Architecture plan. Commerce platform, front-end framework, content management system, hosting and search, with who owns each system.
- Design system in code. The design becomes a component library, so new pages are assembled rather than built from scratch.
- Commerce integration. Products, cart, customer accounts and a hand-off to the platform's hosted checkout.
- Content workflow. Editors can preview and publish pages, schedule campaigns and manage redirects.
- Launch and monitoring. Performance and error monitoring set up, redirects tested, and a review two weeks after launch.
Search and structured data still matter
A headless front end has to do the SEO basics a theme would have handled: server-rendered pages, clean URLs, sitemaps, canonical tags and product structured data. Google recommends providing both structured data on product pages and a Merchant Center feed, since doing both maximises eligibility for shopping features[3]. We build those in from the start, and the structured data guide explains the markup.
Cost and timeline
Headless builds take longer and cost more than theme builds because the front end is a software project. Australian price guides place custom and enterprise builds at the top of their ranges; one lists Shopify Plus or enterprise builds from $30,000 to $100,000 or more[4]. We quote headless work in stages, starting with the architecture plan, so you can stop after the plan if the numbers do not suit.
Questions
Is a headless store faster?
It can be, but it is not automatic. A careful theme build is often fast enough, and a headless build needs its own performance work.
Can I still use Shopify or BigCommerce apps?
Back-end apps that work through the platform usually still work. Apps that change the storefront through theme scripts often do not, and their features may need custom work.
Who hosts a headless store?
The commerce platform still hosts products and checkout. The front end is hosted separately, for example on Shopify's Oxygen for Hydrogen storefronts or on another hosting platform.
Can we start with a theme and go headless later?
Yes, and it is often the sensible order. A theme build teaches you what the store really needs before you invest in a custom front end.
Sources
Opened and checked on 3 November 2026. Each entry says what kind of source it is.
- Hydrogen and Oxygen fundamentals. Shopify developer documentation, undated page. Platform documentation
- Catalyst. BigCommerce Docs, undated page. Platform documentation
- Intro to Product Structured Data on Google. Google Search Central, updated 10 December 2025. Platform documentation
- Shopify Website Cost Australia 2026: $2,000-$30,000 Verified Pricing. What's The Damage, updated November 2026. Commercial publisher, referral site