Articles

E-commerce 9 min read

Headless Shopify with Hydrogen: when it pays off and when it’s a mistake

What headless Shopify is, how it’s built today with Hydrogen and the Storefront API, when it pays off, when it’s a mistake, and the middle path.

André Valle Ortega Founder, Flouvia

Going headless on Shopify means splitting your storefront from the engine that runs it: Shopify keeps the catalog, cart, checkout and payments, and your team builds everything the customer sees. On October 14, 2026, Shopify shipped Hydrogen 2026-10, and the way you build it changed. This guide is for whoever has to decide whether it’s worth it.

What is headless Shopify?

In a traditional Shopify store, the theme renders the store and talks to the commerce engine. Headless pulls those two jobs apart. Shopify’s documentation puts it plainly: headless commerce separates your storefront’s frontend from its backend. You build the frontend on the framework and hosting you choose, and Shopify’s APIs handle the commerce underneath.

  • What stays in Shopify: products, inventory, pricing by market, cart, checkout, payments, orders and customer accounts, all managed from the same admin.
  • What becomes yours: every page, navigation, search, the cart UI, account pages, content, search engine tags and the server it all runs on.

Because the frontend and the engine are separate, you can plug a CMS, your CRM or your ERP into either side. The price is that your frontend stops being a theme Shopify hosts for you and becomes software your company runs.

How it’s built today: Hydrogen, Oxygen and Shopify’s APIs

A headless Shopify storefront has four pieces, and they’re the ones you’ll see in every proposal.

Two sides, joined by Shopify’s APIs

Your frontend Built and run by your team
  • Pages and navigation
  • Search
  • Cart UI
  • Account pages
  • Content and search engine tags
  • Hydrogen, inside your framework
  • On Oxygen, Vercel or other hosting
  • Storefront API Catalog, search and cart, per market
  • Customer Account API Sign-in, orders, addresses and profile
Shopify The engine, from the same admin
  • Products and inventory
  • Pricing by market
  • Cart
  • Orders
  • Customer accounts

At payment, the cart hands off to checkout

Shopify checkout With your extensions and Functions
What your team builds and what stays in Shopify. The APIs join the two sides, and checkout stays with Shopify.

Storefront API and Customer Account API

The Storefront API serves products, collections, search and the cart, and hands customers off to checkout; with the @inContext directive, it returns prices, language and availability for each visitor’s market. Real buyer traffic isn’t capped at a fixed number of requests per minute: what gets limited is automated traffic. The Customer Account API lets customers sign in on a page Shopify hosts, and serves their orders, addresses and profile.

Shopify Hydrogen is now a library, not a framework

Up to version 2026-04, Hydrogen was a full-stack framework built on Remix or React Router: to use its cart, you built your whole store inside it. Since 2026-10, it’s a toolkit you add to the framework you already use. Shopify offers two starters: one on React Router 7, which deploys to Oxygen, and Vercel Shop, a Next.js starter that Vercel maintains. For Nuxt, Astro, SvelteKit and SolidStart, it documents how to wire Hydrogen in.

Hydrogen handles the Shopify-specific parts that are easy to get wrong: cart, variants, collection filters, predictive search, Markets, consent-aware analytics, Shop Pay and customer accounts. It also restores routes a store depends on, like cart permalinks, the handoff to checkout and admin redirects. It doesn’t ship components: design, routing and search engine tags are on your team.

Oxygen

Oxygen is Shopify’s hosting for Hydrogen storefronts, with environments, GitHub deployments with previews and variables managed in the admin, at no extra charge on paid plans. It’s optional: through the Headless channel, you can host your frontend on Vercel or anywhere else.

Checkout stays with Shopify

Headless doesn’t mean building your own checkout. The cart sends customers to Shopify’s checkout, where your checkout extensions and Shopify Functions keep running. Your part is everything that happens before payment.

When headless pays off

Shopify frames it this way: consider headless when your business systems, processes or customer experience don’t fit its sales channels, themes and apps. In practice, that comes down to four situations:

  • Several storefronts on one catalog. A brand site, a mobile app or one site per brand, all sharing products, inventory and orders. Selling in several countries isn’t enough on its own, since Markets already works on a theme; headless pays off when each market or brand needs a different frontend, not just another currency.
  • Complex editorial content. Guides, lookbooks or technical catalogs that live in a CMS and mix with products, with a team publishing every week.
  • An experience a theme can’t handle well. Configurators, kit builders or search with its own logic, where bending Liquid costs more than building the frontend.
  • Other systems on the frontend. Availability from your ERP, pricing or content from another platform, or a site you already run on Next.js or Astro that you want to add commerce to.

The fifth condition isn’t technical: a development team, in-house or external, committed to the frontend after launch. Shopify says it outright: a headless storefront costs more to build and run than a theme.

When headless is a mistake

Headless usually gets pitched as a design or speed upgrade. Often it fixes a problem the store doesn’t have. It’s a mistake when:

  • Nobody will maintain the frontend. Shopify releases a new API version every quarter, each supported for at least 12 months, and every Hydrogen version is tied to a Storefront API version. Add dependencies, hosting and monitoring, and the frontend needs steady work, not a project you hand off and close.
  • Your store relies on apps that only live in the theme. Many App Store apps integrate through app blocks, Liquid files built for Online Store 2.0 themes that don’t show up on a custom frontend. Hydrogen 2026-10 restores the cart routes and the standard events and actions contract that compatible apps use, but reviews, loyalty and any other visual widget have to go through the vendor’s API, if there is one, or be rebuilt. Make the list before you decide.
  • Your marketing team lives in the theme editor. Headless doesn’t have one. Whatever someone rearranges today without help moves to a CMS or to metaobjects that someone has to model.
  • The budget covers the build, not the running. Every design change, every campaign and every new app goes through development.
  • The real problem is conversion. If your store isn’t selling, the architecture is rarely why: checkout friction, a neglected mobile experience or generic product pages get fixed on the theme you already have. Start with the five most common CRO mistakes on Shopify.
Going headless isn’t a redesign: it’s deciding that your company will run a software product of its own.

Theme vs. headless: what you gain and what you give up

The honest comparison isn’t old versus new. It’s two ways of splitting the work between Shopify and your team:

CriteriaOnline Store 2.0 themeHeadless with Hydrogen
Time to launchYou start from a theme and ready-made sections; you ship soonerYou build every page, the cart and accounts; starters shorten setup, but the design is yours
Control over the experienceBroad, within Liquid, sections and blocksFull on the frontend: routes, rendering, interaction and content
App compatibilityApp Store apps drop in as blocks from the editorApps that work with the cart can keep working; visual widgets go through an API or get rebuilt
Content editingTheme editor, no developer neededA CMS or metaobjects someone models; no theme editor
Maintenance costShopify hosts and serves the theme; you maintain its code and appsYour own software: quarterly API versions, dependencies, hosting and monitoring
SEOShopify generates the sitemap and robots.txt, and adds hreflang tags with MarketsCan index just as well, but tags, structured data, the sitemap and hreflang are on your team; Hydrogen honors admin redirects
CheckoutShopify’s, with extensions and FunctionsThe same: Shopify’s, with extensions and Functions

On page speed: a headless frontend isn’t faster by definition. If speed is your main argument, measure the theme you have first.

The middle path: a well-built theme and an extended checkout

Between the theme you bought and a frontend of your own sits a middle path that covers many of the cases that come in asking for headless:

  • A custom Online Store 2.0 theme. Sections and blocks designed for your brand, content pulled from metafields and metaobjects, and your own code where today you load an app for something simple. Your team keeps editing without waiting on developers.
  • An extended checkout. Checkout extensions add fields, messages or offers: on Shopify Plus, in the information, shipping and payment steps too; on every plan except Starter, on the Thank you and Order status pages. Shopify Functions change discount, shipping, payment and validation logic.
  • Headless pieces only where they’re needed. Storefront Web Components or Buy Button JS add products and buy buttons to an editorial site you already run, and Hydrogen 2026-10 drops into an existing project while your store stays on a theme.

Three ways to split the work

Shopify runs more

  1. Online Store 2.0 theme

    Shopify hosts and serves the theme

    • Sections and blocks in the theme editor
    • App Store apps as blocks
    • You maintain its code and apps
  2. The middle path

    A custom theme and an extended checkout

    • Sections built for your brand, on metafields and metaobjects
    • Fields, messages and offers in checkout
    • Headless pieces only where needed
  3. Headless with Hydrogen

    A frontend your company runs

    • Routes, rendering, content and SEO
    • A CMS or metaobjects, no theme editor
    • Quarterly versions, hosting and monitoring

Your team runs more

In all three, checkout is Shopify’s, with extensions and Functions

Between a theme and a frontend of your own, the middle path splits the work without losing the theme editor. Checkout is the same in all three.

Before you decide, answer these in writing:

  1. What specific experience can’t you build with your theme and extensions?
  2. Who will maintain the frontend after launch, and on what monthly budget?
  3. Which apps would disappear, and how will you replace each one?
  4. Who will edit content, and in which tool?
  5. Against what baseline will you measure whether the change worked?

If the answers point to headless, the project stands on solid ground; if not, a well-built theme takes you further for less. At Flouvia we design and build Shopify Plus stores, on a custom theme or headless, depending on what your operation needs. If you’re weighing the move, tell us what you need.

Frequently asked questions

  • Do I need Shopify Plus to run a headless store?
    No. Oxygen is available at no extra charge on Shopify’s paid plans, not just Plus. Plus adds what happens around it: extending the information, shipping and payment steps of checkout, using custom apps with Shopify Functions, and up to 25 public environments on Oxygen, versus one on other paid plans.
  • Is Hydrogen still built on Remix or React Router?
    Not anymore. It was up to version 2026-04; since 2026-10, it’s a library you add to your framework, with starters on React Router 7 and Next.js. Earlier stores keep working, and Shopify publishes a migration guide.
  • Do I lose Shopify’s checkout if I go headless?
    No. Your frontend sends customers to Shopify’s checkout, with the same checkout extensions and Shopify Functions.
  • Does headless improve SEO?
    Not on its own. A server-rendered frontend can index as well as a theme, but your team builds what the theme already gives you. If you migrate, map every URL before launch, even though Hydrogen honors admin redirects.
  • Can I use Next.js instead of Hydrogen?
    You don’t have to choose: Hydrogen 2026-10 runs inside Next.js, and Vercel Shop is the starter to begin with. You can also call the Storefront API and the Customer Account API directly from any stack, with credentials from the Headless channel.

Written by

André Valle Ortega

Founder, Flouvia

André Valle Ortega is the founder of Flouvia, the design and engineering studio that builds made-to-measure websites, stores, portals, apps, platforms and automation.

LinkedIn