Prepare catalogs ahead of promotions and seasonal sales, then choose when they go live. You can also run comparison tests between catalogs, or publish them alongside theme and checkout updates.
The article doesn't describe how catalogs were switched before. It only states that this update lets Rollouts handle catalog changes.
Prepare catalogs ahead of promotions and seasonal launches, then choose when they go live. You can also bundle them into the same rollout as theme and checkout updates.
At a set date and time, you can activate, deactivate, or switch existing catalogs.
You can run catalog-vs-catalog experiments on the Online Store.
You can publish catalog changes in a single rollout alongside theme and checkout updates .
| Item | Before | Rollouts (with catalog support) |
|---|---|---|
| Rollouts scope | Theme and checkout updates | New Catalog changes now included |
| Catalog publish timing | Not specified | Scheduled Activate / deactivate / switch at a set date and time |
| Granularity | Not specified | Per market Availability and pricing |
| Offer validation | Not specified | Experiments Cross-catalog testing on the Online Store |
| Coordination with themes and checkout | Not specified | Simultaneous Published in a single rollout |
Applies to existing catalogs. Experiments run on the Online Store. Category: Feature / Admin. The article points to the help documentation for details.
Eligible plans, supported regions, experiment traffic allocation and metrics, API support, and rollback methods are not covered in this article.
Set up per-market availability and pricing ahead of a promotion or seasonal launch.
Choose activate, deactivate, or switch, and set the publish date and time. If needed, include theme and checkout updates in the same rollout.
Changes go live at the time you choose. The actual admin steps are described in the help documentation.
Changes target per-market availability and pricing. Organizing your Markets and catalog structure first makes them easier to add to a rollout.
Existing catalogs can be activated, deactivated, or switched. Rather than creating new catalogs, think of it as a feature that controls"when an existing catalog becomes active".
Helps you avoid a half-finished state where landing page visuals, checkout, and pricing change at different times. You can consolidate your release plan into a single rollout.
You can run experiments between catalogs on the Online Store, but the article doesn't cover traffic allocation, how a winner is determined, or which metrics are measured. Check the Help Center before designing a test.
The article only presents this as an Admin feature. Whether rollouts can be managed through Admin GraphQL, whether a Webhook fires on publish, and whether changes can be reverted after publishing arenot stated. If you combine this with an external PIM or inventory integration, verify it beforehand.