Hydrogen 2026-10 brings Shopify commerce to your stack

Shopify made Hydrogen 2026-10 generally available on 14 October. The main change is architectural: its commerce features can now be added to an existing JavaScript framework as a library, rather than requiring the whole storefront to be built on Hydrogen’s previous framework.

The release follows a developer preview that began in June. Shopify says existing Hydrogen storefronts continue to work, so this is an option to evaluate rather than a compulsory immediate rebuild.

What Hydrogen handles

The current documentation separates responsibilities: your framework retains routing, rendering, data loading and the interface; Hydrogen supplies Shopify-specific commerce logic. That includes cart behaviour, variant selection, collection filtering, predictive search, customer accounts, Markets, Shop Pay and analytics with consent handling.

For complete storefronts, the docs identify frameworks that run server code, including Next.js, React Router, Nuxt, Astro and SvelteKit. React and Vue have dedicated bindings; other frameworks can use the core directly. This is broader framework support, not a claim that an arbitrary static page becomes a complete store without integration work.

Skills for coding agents

The package includes 20 skills matched to its installed version. Shopify says these guide coding agents through storefront work, and provides a way to synchronise them after upgrades. React Router and Next.js starters are available, with hosting choices including Oxygen.

Shopify Developers’ release announcement, 14 October 2026. View the original demonstration on X.

What to test before changing a store

Our suggested agency brief is a small proof of concept around the work the store actually needs: variant selection, market-specific pricing, cart updates, customer login and checkout. Include consent choices and analytics in that test, rather than treating a visually correct product page as completion.

Ask which existing app integrations depend on theme behaviour and how they will be tested in the proposed storefront. Keep a rollback plan and compare implementation and maintenance costs with retaining the current theme. The ability to keep a framework reduces one migration constraint; it does not remove the merchant’s responsibility to validate the finished shopping journey.