Shopify Rollouts vs Headless: What Hydrogen Merchants Need to Know

On October 23, 2026, Shopify added catalog changes to Rollouts. Merchants can now schedule the activation, deactivation, or switching of existing catalogs to control product availability and pricing per market.

Our earlier description of Rollouts as incompatible with Hydrogen was too broad. Catalog scheduling now gives Hydrogen merchants a supported use case, while front-end publishing and experimentation remain separate.

If you run a Hydrogen storefront, a campaign usually involves several changes: a new price list, a landing page, a promotional banner, perhaps a different product-page layout.

Shopify Rollouts can now handle some of that work. A Launch or an Event with 100% traffic allocation can apply catalog changes to Hydrogen through the Storefront API, within the catalog’s assigned markets and sales channels.

The storefront itself remains separate. Rollouts does not publish your React components, schedule your Weaverse pages, or split Hydrogen visitors between design variants. Its reports also exclude headless visitors.

That distinction matters when planning a campaign. You need to know which tool owns the offer, which tool publishes the page, and where you will measure the result.

What Shopify Rollouts Does Today

Rollouts lives under Markets → Rollouts in Shopify admin. You choose a rollout type, add changes, and configure the audience and schedule.

Type	What it does	Shopify plan
Launch	Publishes changes at a scheduled time and merges them into the store permanently	Basic or higher
Event	Publishes changes for a defined period, then rolls them back; changes can also be applied permanently	Basic or higher
Experiment	Compares a treatment with a control	Grow or higher

A rollout can contain one theme change, one checkout-and-accounts configuration change, and changes to catalogs or discounts.

For catalogs, the action is specific: set an existing catalog to Active or Draft. Multiple catalog changes let you switch between prepared offers.

Discount support arrived separately on October 1, 2026. Catalog support followed on October 23. Their scheduling rules should be reviewed separately.

When Catalog Changes Reach Hydrogen

The rollout type and traffic allocation determine where catalog changes apply.

Rollout configuration	Catalog-change reach
Launch	Assigned markets and sales channels, including applicable Storefront API and Hydrogen experiences
Event at 100% traffic allocation	Assigned markets and sales channels, including applicable Storefront API and Hydrogen experiences
Event below 100% traffic allocation	Online store only
Experiment at any allocation	Online store only

Three details matter here.

First, a catalog only affects its assigned markets and channels. Your Hydrogen storefront must request commerce data in the appropriate market context. Scheduling a catalog for one market does not change prices in every market.

Second, this reach applies to eligible catalog changes. Theme and checkout/accounts configuration changes remain online-store only, including when the rollout reaches 100% of visitors.

Third, connected systems refresh on their own schedules. Product feeds, POS, apps, and other channels may pick up the change at different times. Your storefront’s caching can also affect when a shopper sees updated data.

A catalog launch can therefore supply the offer for a Hydrogen campaign. Publishing the accompanying page is still a separate job.

Catalog Rollback Does Not Restore Old Prices

A catalog rollout changes status. It does not save a frozen copy of the catalog.

If you edit prices, price adjustments, or products while the rollout is running, those edits remain saved and apply whenever the catalog is active. When an Event ends, rollback does not recover the catalog contents from the day the campaign started.

Keep these constraints in mind:

A catalog can belong to only one unended rollout at a time.
Archived catalogs cannot be added.
Catalogs assigned directly to a company location cannot be added.
A catalog can be added before it has a market assignment, but customers see no change until it is assigned to a market.

For a promotion, review both the scheduled status changes and the current contents of each catalog. They determine the offer together.

Discounts Have Their Own Rules

Discounts can also be activated or deactivated through Rollouts, but catalog rules should not be used as a shortcut for understanding discount availability.

For a discount-only rollout, check both 100% effective traffic and a 100% split for the activating treatment before treating the offer as available to all buyers. Normal discount eligibility still applies.

Discounts also retain their own active dates independently of the rollout. Review those dates and combination settings alongside the rollout schedule; the rollout is not necessarily the only condition making a discount available.

A discount can belong to one unended rollout, and a rollout can contain up to 250 discounts. In an Experiment, the control follows the store’s standard discount behavior.

What Rollouts Measures

Rollout analytics cover visitors on the online store, cart, and checkout. Visitors on headless storefronts, POS, and other external surfaces are excluded from rollout results.

This is a boundary of the Rollouts report. It does not mean Shopify Analytics is unavailable to Hydrogen.

For a Hydrogen campaign, verify your storefront’s analytics implementation before launch. Decide how campaign exposure, purchases, and revenue will be recorded. A catalog change reaching Hydrogen does not make those visitors appear in the rollout report.

The same applies to design experiments: assigning a visitor to a variant and measuring their behavior are separate parts of the implementation.

Watch for Offer Mismatches Across Channels

An Experiment or a partial-reach catalog Event can show some online-store visitors an offer that differs from the one shown in ads, product feeds, or your Hydrogen storefront.

That can create a confusing journey. A shopper might encounter one price in a listing and another after clicking through.

Shopify warns that mismatched offers can lead to product delisting or account suspension on channels such as Google and Meta. These are possible outcomes, not automatic penalties.

Before testing products promoted elsewhere:

Review the affected feeds, ads, and landing pages.
Consider pausing ads or removing affected products from listing channels during the test.
Monitor channel status while the rollout is active.
If the goal is a consistent offer across eligible channels, consider a Launch or 100% Event and allow for synchronization delays.

Keep this separate from testing a page layout. Changing an offer can affect surfaces beyond the page where the experiment runs.

Where Weaverse Fits

Weaverse gives your team a visual editing and publishing workflow for the Hydrogen storefront.

Developers build the components and expose their settings. Merchants use Studio to update content, arrange sections, and preview pages. That is where the presentation side of a campaign can be prepared.

Schedule Pages and Theme Settings in Studio

Scheduled Publishing lets you publish a saved page or theme-settings snapshot at a chosen date and time.

The schedule targets the prepared snapshot. Later unsaved edits do not change what will publish. You can also select a previous version from Version History and schedule it.

A few details are worth checking before a launch:

Times use your browser’s local time zone.
Each page can have one pending schedule.
Theme settings can have one pending schedule per project.
Creating another schedule for the same resource replaces the pending one.
Publishing replaces the live page or theme-settings version and refreshes the storefront cache.

Plan the campaign’s end explicitly. If the launch is still pending, scheduling its replacement would overwrite that launch schedule. Wait until the campaign version has published before scheduling the follow-up, or arrange a manual publication at the end.

Theme-settings versions restore theme settings only; they do not replace page content.

For a sale, Shopify can schedule the catalog offer while Studio schedules the campaign page. Check both schedules, their time zones, and the actions needed when the sale ends.

New components and application behavior still go through your development and deployment workflow.

Use Multiple Projects for Different Experiences

Multi-Project Architecture lets independent Weaverse projects share a Shopify store and Hydrogen codebase. Each project has its own content, pages, and theme settings.

Your application selects the project to load. Developers can use domains, paths, market context, or other request logic to serve different experiences.

This is useful for:

Use case	Implementation
Market-specific design	Route visitors to the appropriate project while Shopify supplies market-specific commerce data
Multiple brands	Maintain separate content and branding projects on a shared codebase
Design experiments	Create variant projects and implement visitor assignment and measurement
Staged design launches	Route a new experience to a defined market or path before expanding
Staging	Preview a separate project before directing production traffic to it

Projects are independent. Shared content needs an explicit synchronization workflow, such as the Import/Export process described in the documentation.

Build and Measure Experiments Deliberately

The optional @weaverse/experiments package provides variant assignment and an exposure callback. It maps an assigned variant to a Weaverse project.

Developers connect exposure and conversion events to their analytics implementation. The team still chooses the metric, checks event collection, and decides how to evaluate the result.

Creating a second project does not, by itself, create a measured A/B test. You need the routing, tracking, and analysis around it.

Weaverse’s current pricing includes multiple projects and content scheduling on every plan. It describes A/B testing and targeting as developer-built capabilities. Include that implementation work when estimating the cost of an experiment.

Rollouts and Weaverse at a Glance

Capability	Shopify Rollouts	Weaverse on Hydrogen
Scheduled catalog pricing and availability	Eligible changes reach Hydrogen through a Launch or 100% Event	Managed in Shopify
Scheduled discounts	Separate discount reach, date, and eligibility rules apply	Managed in Shopify
Scheduled storefront content	Theme changes apply to the online store	Studio schedules page and theme-settings snapshots
New storefront code	Does not deploy Hydrogen code	Uses your development and deployment workflow
Design experiments	Online-store Experiments on Grow or higher	Developer-built assignment and analytics integration
Results reporting	Excludes headless visitors	Measured through your connected analytics implementation
Market-specific presentation	Supports online-store theme customizations; theme replacement applies to all markets	Developer-configured project routing
Plan requirements	Basic or higher for Rollouts; Grow or higher for Experiments	Scheduling and multiple projects on every plan; experiments require implementation

Check the Stack You Actually Deploy

As checked on November 2, 2026, Pilot’s repository identifies the theme as version 2026.10.4 and declares Hydrogen ~2026.4.7, alongside React 19, React Router 7, Tailwind CSS 4, and TypeScript.

The Weaverse Hydrogen SDK repository, at version 5.24.1, declares a Hydrogen dependency range of >=2025.5 <2026.10.0. Check the package version and release notes before upgrading a storefront to Hydrogen 2026.10.

Review third-party integrations individually as well. A storefront upgrade does not establish compatibility for every connected service. Test the APIs, SDKs, and customer journeys used by your implementation.

Planning a Campaign That Uses Both

Start with a list of changes, then assign each one to its publishing workflow.

Prepare the offer. Check catalog contents, market assignments, rollout reach, and any separate discount rules.
Prepare the storefront. Preview the campaign page and theme settings in Studio. Identify code changes that require a deployment.
Coordinate the schedules. Shopify uses the store’s time zone for rollouts; Studio uses the browser’s local time zone. Confirm the intended moment in both.
Plan the end. Document catalog rollback, discount availability, the follow-up page publication, and any code reversal.
Set up measurement. Verify that Hydrogen visits and conversions reach the analytics tool you will use.
Check the customer journey. Review the offer, landing page, product page, cart, and checkout after launch and after the campaign ends.

For a design experiment, write down the hypothesis and primary metric before building variants. Keep unrelated offer changes out of the test window where possible so the result is easier to interpret.

Shopify’s catalog release gives Hydrogen merchants another useful scheduling tool. Use it for eligible commerce changes, prepare the storefront experience in Weaverse, and make measurement part of the launch work.

Start building with Weaverse →