Shopify is making the storefront optional

Shopify is expanding its developer ecosystem so that storefronts can be built with whichever framework fits the job.

For years the platform was centred on its own theme ecosystem and Liquid. As storefronts grew more complex, brands started reaching for headless architectures to get real control over the frontend. Shopify's answer was to partner with Remix, then acquire the team behind it and bring that technology deeper into its ecosystem. Today Hydrogen is built on React Router, following the convergence of Remix's framework work with React Router.

Read the whole sequence together and it does not say what most people take it to say.

Shopify is not pushing everyone toward headless. It is decoupling its commerce backend from the storefront. That is a different, and larger, claim.

Headless is not a capability unlock

It is worth being blunt about this, because it is where most headless projects go wrong before they start: headless does not hand you powers that a theme can never have. Shopify's modern theme architecture is genuinely capable, and many stores that go headless could have achieved their goals without it.

The difference shows up somewhere more specific — at the point where a storefront needs logic the platform will not run for you.

There are ordinary requirements that need Shopify Admin API access, or a piece of server-side logic of your own, and you cannot execute that inside a theme. The usual answer is to build a custom app, or find one on the App Store that is close enough.

Which means another subscription, another dependency, another set of scripts on the page, and often another compromise in the experience — because the app was built for someone else's store, not yours.

Do that three or four times and you are maintaining a system you do not own, assembled from parts you did not choose.

Where headless starts to earn it

Past a certain amount of customisation, owning the solution costs less than stitching one together. That is the real threshold, and it is a commercial one as much as a technical one.

Cross it and the frontend becomes a genuine choice — React Router, Next.js, Astro, SvelteKit, whatever suits the requirements rather than whatever the platform mandates.

The infrastructure around that has quietly become accessible too. Oxygen, Shopify's edge hosting for custom storefronts, is available at no extra charge on paid Shopify plans — Starter through Plus, with Agentic plans the exception. That is not a footnote. Hosting used to be one of the first real costs of going headless, and for a lot of stores it now is not.

You can also introduce your own server-side layer and securely work with Shopify's Admin API alongside the Storefront API, which is where much of the flexibility actually comes from. The distinction matters: the Admin API is not something a frontend calls, it is something your own server does — which is precisely the layer a theme does not give you.

Oxygen does not replace something like Vercel for every workload. It is purpose-built for Shopify storefronts rather than a general-purpose backend platform, and it is worth choosing it for what it is.

The piece that is still missing

A first-party, standalone content layer.

Headless Shopify projects still reach for Sanity, Contentful or similar when content management gets serious. Shopify has the commerce infrastructure, the storefront framework, the hosting and the APIs. Content is the obvious gap, and it would not be surprising if Shopify eventually expanded further into this layer — though that is our reading of the direction, not something the platform has signalled.

Themes are not going anywhere

None of this is an argument against themes, and the industry's habit of treating headless as an upgrade path does real damage.

Themes remain the right answer for most of the market and for any brand that does not want to fund custom development. Pick one, customise it, add the apps you need, and you have a capable storefront without the cost or the complexity.

Headless is a different proposition entirely. Established premium and luxury brands generally do not want their digital presence to read as a variation on a template someone else is also running. They want control over how the brand is presented, how customers move through it, and how the whole thing feels from discovery to checkout.

Themes optimise for accessibility and speed of implementation. Headless optimises for control, differentiation and flexibility. Neither is better. They answer different questions, and the only one that matters is what the brand actually needs.

This distinction matters particularly for premium and luxury brands, where the storefront is not just a sales channel but part of the brand itself.

The shift underneath

So the headline is not "Shopify is moving to headless."

It is that Shopify is making the storefront increasingly optional — and for anyone building on the platform, that is the more consequential change.

Sources

• Hydrogen and Oxygen fundamentals, Shopify's own documentation — Oxygen "available at no extra charge on paid Shopify plans," the Agentic exclusion, and the confirmation that Hydrogen is built on React Router.