Shopify Rollouts vs Headless: What Hydrogen Merchants Need to Know

Author: Paul Phan, Founder @ Weaverse Published: April 2026 Category: Shopify Hydrogen / Headless Commerce Target: weaverse.io/blogs

Shopify's Winter '26 Edition shipped 150+ updates in January. Two stand out: Rollouts — native A/B testing and scheduled deployments — and SimGym — AI-powered simulation for pre-validating store changes before real customers see them.

Together they form a two-stage validation pipeline: simulate first, then test with real traffic. No third-party apps. No scripts. No monthly cost. Built into the admin.

It's a big deal. The CRO industry has been waiting for this. Only 20% of Shopify stores run any kind of testing, and Shopify just removed every barrier to entry.

But here's the part nobody's talking about: if you're running a Hydrogen storefront, none of this works for you.

This isn't a hot take. It's architecture. Let me explain why, and what Hydrogen merchants should do instead.

What Shopify Rollouts Actually Does

Rollouts lives under Markets > Rollouts in the Shopify admin. Three core capabilities:

1. Scheduled Deployments

Set a go-live date and time for theme changes. Your store reverts automatically when the promotion ends. No more midnight deploys for Black Friday. No scrambling to undo seasonal changes. Set it, forget it, wake up to a changed store.

This works on all Shopify plans — Basic and up.

2. A/B Testing with Real Traffic

Split a percentage of visitors between your current theme and a variant. Track conversion rate, AOV, and revenue with confidence intervals. The split happens server-side — zero flickering, no performance penalty, no client-side JavaScript injecting changes.

Requires Advanced plan or higher.

3. Market-Level Targeting

Run different versions for different regions. Test a homepage redesign in the US while keeping the UK store unchanged. This is particularly valuable for international brands with regional preferences.

Requires Advanced plan or higher.

The SimGym Connection

Rollouts pairs with SimGym, Shopify's AI simulation tool. Before running a real A/B test, you can simulate how AI shoppers would interact with your changes. SimGym uses AI trained on billions of real commerce sessions to predict conversion impact.

The intended workflow: simulate first with AI → catch obvious problems → refine → then test with real traffic via Rollouts. It's a smart two-stage pipeline that reduces risk.

How Rollouts Works Under the Hood

Understanding the technical mechanism is key to understanding why it's Liquid-only.

Rollouts works by duplicating your entire Liquid theme. When you create a rollout, Shopify clones your published theme into a variant. You edit the variant in the standard theme editor. Shopify's infrastructure then routes a percentage of traffic to the variant theme while keeping the rest on the original.

The routing happens at Shopify's server level — before the page renders. That's why there's no performance impact. The visitor's request hits Shopify's servers, the server checks which group they're in, and serves the appropriate theme. The visitor never sees a flash of the wrong version.

This is elegant for Liquid themes. But here's the problem: Hydrogen doesn't use Liquid themes.

A Hydrogen storefront is a React application. It runs on Oxygen (Shopify's edge runtime) or your own infrastructure. It fetches data via the Storefront API. It renders pages with React Router. There's no Liquid theme to duplicate. No Shopify-hosted theme editor to modify variants in. No Shopify server-level routing that applies to your custom React app.

Rollouts is architecturally incompatible with Hydrogen. This isn't a bug or a missing feature — it's a fundamental difference in how Liquid and headless storefronts work.

What Rollouts Can't Do (Yet)

Even for Liquid merchants, Rollouts has real limitations in its v1 release. Understanding these is useful context, because some of them are problems Weaverse already solves for Hydrogen.

To be fair — this is version one. Shopify has signalled plans to expand Rollouts to products, discounts, and other areas over time. The initial release is deliberately scoped to theme-level visual changes, which handles roughly 80% of what most stores need to test regularly.

Why This Matters for Hydrogen Merchants

Headless commerce was supposed to give you more control, not less. You chose Hydrogen for performance, flexibility, and custom UX. But in practice, Hydrogen merchants have been waiting for Shopify to bring feature parity to the headless world.

Rollouts is the latest — and most glaring — example of this pattern.

Without a split testing solution, Hydrogen merchants face three concrete problems:

1. No data-driven design decisions. You're guessing what converts better instead of measuring it. Every theme change, every layout restructure, every new section is a leap of faith.

2. No scheduled campaigns. Flash sales, seasonal themes, and holiday merchandising require manual deployment. Want to launch a Black Friday redesign at midnight? Someone has to push the code. Want to revert it Monday morning? Same thing.

3. No market-specific experiences. Showing the same storefront to every visitor regardless of location is a missed conversion opportunity. Different markets respond to different design languages, different hero images, different calls to action.

These aren't nice-to-haves. They're table stakes for modern e-commerce. And every Liquid merchant now gets them for free.

What Weaverse Already Has

Here's the thing: Weaverse shipped the headless answer to Rollouts months before Shopify launched Rollouts itself.

Multi-Project Architecture (November 2025)

Weaverse's Multi-Project Architecture was designed specifically for Hydrogen storefronts. Instead of duplicating a Liquid theme, it uses project variants — separate Weaverse projects with their own content, theme settings, and pages, all sharing the same Shopify data source and Hydrogen codebase.

Traffic routing is handled in your Hydrogen app, giving you complete control:

// Route traffic to different Weaverse projects
const weaverse = new WeaverseClient({
  projectId: () => {
    const origin = new URL(request.url).origin;

    const projectMap = {
      "https://mystore.se": process.env.WEAVERSE_PROJECT_SWEDEN,
      "https://mystore.fr": process.env.WEAVERSE_PROJECT_FRANCE,
    };

    return projectMap[origin] || process.env.WEAVERSE_PROJECT_ID;
  },
});

This isn't a hack or a workaround. It's the architecture. You can route by:

• Domain — mystore.se vs mystore.fr
• Path — /collections/summer shows a different project
• Cookie — returning visitors see a different variant
• Query parameter — ?variant=b for quick testing
• Any custom logic — device type, referrer, UTM parameters, geographic data

Content Inheritance

Variant projects inherit from a parent project automatically. You don't rebuild from scratch — you change one section, one page, or one color, and everything else flows from the parent.

This is a meaningful advantage over Rollouts, which duplicates the entire theme. With Weaverse, your variant only contains the differences. Less to manage, less to break, easier to reason about.

Use Cases

No Plan Restrictions

Rollouts gates A/B testing behind Shopify's Advanced plan ($399/month). Weaverse's Multi-Project Architecture works on any Weaverse plan. No tier gate, no artificial restriction.

If you're weighing the total bill before committing to either path, our headless Shopify pricing breakdown walks through what a Hydrogen stack actually costs in 2026 — plans, infra, and the hidden line items most teams miss.

What Else Weaverse Gives Hydrogen Merchants

Multi-Project Architecture is one piece. Weaverse is a full platform for Hydrogen storefronts:

Visual Page Builder (Weaverse Studio)

Drag-and-drop page editing for Hydrogen. It works like the Shopify theme editor — but for your React application. Merchants update content, images, and layouts without developer help.

Before Weaverse, every content change on a Hydrogen storefront required a developer. That's the #1 reason teams hesitate to go headless. Weaverse Studio removes that bottleneck.

Data Connectors (October 2025)

Visual data binding without code. Click a database icon, select data from products, collections, or pages, and see your data bindings render in real time. Third-party API integration too.

Before Data Connectors, binding dynamic data required writing code. Now merchants can build dynamic content themselves — product grids, collection pages, blog feeds — all from Studio.

AI-Ready by Default

Hydrogen storefronts built with Weaverse themes are optimized for AI discovery. Complete schema.org Product markup, structured data for Google AI Mode and ChatGPT Shopping, semantic HTML hierarchy, and crawlable content. Eight AI platforms are already recommending products to shoppers. Your store should show up.

Production-Ready Themes

Pilot — our flagship Hydrogen theme — is built on React 19, TailwindCSS v4, TypeScript, and React Router v7. Complete cart features (discounts, gift cards, notes), Judge.me reviews integration, combined listings support, and Core Web Vitals optimization out of the box.

Clone it and launch in minutes:

npx @weaverse/cli@latest create --template=pilot --project-id=YOUR_PROJECT_ID

Full Stack Alignment

Weaverse tracks Shopify Hydrogen's evolution precisely:

• Hydrogen 2025.1.x: Single fetch, B2B methods stabilization
• Hydrogen 2025.5.0–7.0: React Router v7 migration
• Hydrogen 2026.1.4+: Storefront MCP proxy, AI agent endpoints
• React 19 + TailwindCSS v4: Current, not catching up

The Comparison: Rollouts vs Weaverse Multi-Project

Where Weaverse Is Going

Shopify validated the demand. Rollouts proves that merchants want native split testing, scheduled deployments, and market-specific experiences. The market is educated now.

Here's what Weaverse is building next for Hydrogen:

AI-Powered Experimentation

Building on the SimGym concept — but for headless. AI-driven simulation of storefront changes before deploying to real traffic. Except Weaverse can go deeper: simulate changes at the component level, not just the theme level. Test a single section change without duplicating anything.

Advanced Personalization

Dynamic content based on customer behavior, not just random traffic splits. Show different hero sections to first-time visitors vs loyal customers. Different product recommendations based on browsing history. This is where headless has a structural advantage over Liquid — you control every render decision.

Component-Level Testing

Rollouts duplicates entire themes. Weaverse can test at the component level. Want to test two different product card designs? Two different hero sections? Two different checkout funnels? Duplicate just that component, not the whole store. Faster to set up, less risk, cleaner data.

Built-In Analytics

Native performance tracking and insights for every variant. Conversion rate, AOV, revenue, add-to-cart rate — without wiring up Google Analytics yourself. The data lives in Weaverse, alongside your content.

Integration Ecosystem

Pre-built connectors for popular services. Email marketing, reviews, analytics, search — all connected through Weaverse Data Connectors. Less custom code, more clicks.

The Bigger Picture: Shopify Builds Liquid-First

Rollouts isn't an isolated case. It's a pattern.

Shopify consistently ships new merchant features for Liquid themes first. Headless support comes later — if it comes at all. SimGym, Heatmaps, native analytics enhancements — all Liquid-first.

This makes business sense. Liquid serves the majority of Shopify's merchants. But it leaves Hydrogen merchants in a structural gap: you chose headless for performance and flexibility, but you're waiting for basic e-commerce features that Liquid merchants get for free.

The good news: this gap is exactly where the ecosystem thrives. Shopify builds the platform. Partners build the headless layer. Weaverse is that layer.

Every feature Weaverse ships is Hydrogen-first:

• Visual page builder — because Hydrogen has no native theme editor
• Data Connectors — because binding dynamic data in React shouldn't require a developer
• Multi-Project Architecture — because Hydrogen merchants need split testing too
• AI-ready structured data — because your Hydrogen store should be visible to AI agents from day one
• Production-ready themes — because Hydrogen shouldn't take months to launch

Getting Started

If you're running a Hydrogen storefront and want split testing, scheduled deployments, or market-specific experiences:

1. Create a Weaverse project — scaffold with our CLI in 5 minutes
2. Set up project variants — in Weaverse Studio, create variants for your tests or campaigns
3. Configure traffic routing — add the projectId function to your Hydrogen app
4. Publish and measure — push variants live, track performance, pick the winner

npx @weaverse/cli@latest create --template=pilot --project-id=YOUR_PROJECT_ID

Shopify Rollouts is a great feature — for Liquid merchants. It validates that split testing and scheduled deployments are table stakes for modern e-commerce. Hydrogen merchants deserve the same capability, built for their architecture.

We built it. Months ago.

Start building with Weaverse → weaverse.io