Headless on Shopify Just Got Easier. Here’s How to Tell If It’s Right for You.
Shopify, Vercel, and JIBE on what going headless changes for merchants, what stays the same, and why the first question is still “why?”
In June, Vercel and Shopify announced that they were rebuilding Hydrogen, Shopify’s framework for headless storefronts, from the ground up. By the end of that same month, Shopify’s developer changelog confirmed that the Hydrogen developer preview could be deployed to Vercel in a few clicks. The new version is open source and runtime agnostic, so it can run anywhere JavaScript does, and Vercel’s write-up of the project notes that developers can build with Svelte, Nuxt, Next.js, or a custom framework of their own.
This upgrade brings up a recurring question in the age of composability: If the tooling barrier to headless is falling, does that make headless the right move for more brands?
JIBE founder Steve Krueger put that question to Matt Hickey, a partner solutions engineer at Shopify, and Patrick Williams, a partner solutions engineer at Vercel, in a recent webinar.Both made the case for what the new Hydrogen makes possible, and the most useful parts of the discussion were about when a merchant shouldn’t go headless at all.
Start with why
When a merchant tells Williams they want to go headless, he said, “My first question’s always, why?” It’s not that he’s not a proponent of headless, far from it. But decoupling the storefront from Shopify’s back end adds complexity, so it’s not something that should be done just because— just because your competitor did it, just because your board heard it was the right thing to do, just because you have reached the next GMV tier.
The reasons he sees that justify it are actually fairly specific: a buying experience too complex for standard variant pickers, third-party data such as customer-scoped ERP pricing in B2B that needs to surface in the storefront, or performance at a scale where speed materially affects conversion. Each of these is a reason a theme might genuinely limit a brand, and that’s the bar Williams sets with clients before recommending a headless build.
What stays with Shopify, and what you take on
Going headless on Shopify leaves most of what merchants rely on in place. Products, discounts, customer accounts, order processing, and checkout all stay in Shopify, so merchandisers and customer service keep working in the same admin.
What a brand does take on is everything between the customer and Shopify’s APIs. Hosting, CDN configuration, and security settings that came with a Liquid storefront become decisions someone has to make. New Shopify features no longer arrive automatically, since a decoupled front end needs code changes to pick them up. The catch Hickey flagged as most often overlooked is apps: many Shopify apps were built for the Liquid storefront and won’t carry over to a headless front end, so merchants need to check whether the partners they depend on offer open APIs before committing.
The recording goes further into how Vercel’s template handles caching and Shopify’s rate limits, and into the agent skills Vercel is building that Williams said can turn a 20-hour upgrade into a one-hour job.
A choice of front end on the same commerce engine
What the partnership gives Shopify merchants is a wider range of options without changing platforms. A brand can run a theme, move to a headless storefront when its experience outgrows one, and keep the same commerce engine, checkout, and operational workflows either way. That makes the decision less about replatforming and more about which layer a brand’s problem actually lives in. If the constraint is the customer experience, headless is worth evaluating; if it’s somewhere else in the operation, a new storefront won’t be the fix.
The runtime-agnostic rebuild extends that flexibility. Opening Hydrogen to any framework and any host means teams can build with the tools they already know, and a brand that goes headless isn’t tied to a single way of building or hosting its front end, which addresses one of the long-standing hesitations about headless builds.
Deciding whether headless is right for your brand
Both speakers agreed that the question of who should go headless has changed since the early days, when brands often made the move because they were told to or because they’d crossed what Hickey called “some imaginary GMV threshold.” With the barriers to entry lower, size matters less than whether a brand has a specific problem a theme can’t solve. Williams has seen plenty of brands correctly decide against headless, usually after a discovery process showed that the pain they were feeling had a different cause or a simpler fix. In the full recording, Krueger, Hickey, and Williams talk through what that discovery looks like, along with how teams are using AI to build on Shopify faster and where headless commerce is headed next.
Leigh Bryant
Editorial Director, Composable.com
Leigh Bryant is a seasoned content and brand strategist with over a decade of experience in digital storytelling. Starting in retail before shifting to the technology space, she has spent the past ten years crafting compelling narratives as a writer, editor, and strategist.