Executive summary
- What changed: Rollouts now covers catalog changes, so per-market availability and pricing can be scheduled, activated, deactivated, or swapped at a set time.
- Why it matters: Seasonal pricing can be staged in advance and released alongside theme and checkout changes in one rollout, instead of someone toggling catalogs by hand at midnight.
- Who should act: Merchants running multiple markets or catalogs, and teams whose peak-season launches depend on a manual sequence of admin changes.
What changed
Rollouts already scheduled theme, checkout, accounts, and discount changes. Catalogs are now in scope: prepare a catalog ahead of a launch and schedule when it activates, deactivate one on a fixed date, or switch between existing catalogs.
Three rollout types apply. A Launch merges changes permanently. An Event publishes changes for a defined window then rolls them back automatically, which maps onto a sale that must end. An Experiment runs a treatment against a control so you can measure the effect before committing.
Scheduling is composable: a catalog change can ride in the same rollout as the theme and checkout updates that depend on it, so storefront, checkout, and prices change together.
Why it matters
For enterprise teams the gain is less the feature than the removal of a class of operational risk. Seasonal launches have required a human in the admin at a set time, making a precise series of changes outside business hours across several markets. Every manual step is a chance to publish a price early, or leave a sale price active after it ends.
Scheduling also shortens the gap between merchandising intent and execution: a pricing decision made two weeks ahead is configured once, reviewed by someone else, and left to fire. For brands already running per-market catalogs through Shopify Markets for global expansion, this closes a real gap: the catalogs were market-aware, but their activation was not time-aware.
The Experiment type deserves attention. Pricing and assortment tests previously meant app overrides or theme logic, both of which drift from the source of truth. Testing between catalogs keeps the comparison in the platform's own pricing model.
Role-specific impact
- Marketers: Campaign calendars can be mirrored in the admin rather than tracked in a spreadsheet and executed by hand. Use Event rollouts for sales with a firm end date, and Experiments to settle pricing questions with data.
- Developers: Expect catalog state to change on a schedule you did not trigger. Audit anything that caches prices or availability, including headless storefronts, feed exports, and middleware syncs, and confirm cache invalidation tolerates a timed switch.
- Store admins: Build and review catalogs ahead of the date, not on it. Confirm who can schedule and cancel a rollout, and keep one owner per rollout so two people do not stage conflicting changes into the same window.
Use-case example
Real-world scenario
An outdoor equipment brand sells into the United States, Canada, and the EU with a catalog per market, running an end-of-season clearance from Friday midnight to Monday 23:59. That meant two people, six admin changes per market, and one incident where EU clearance pricing stayed live 31 extra hours at roughly $18,000 in margin. With an Event rollout the three catalog switches and the theme change are staged Wednesday, reviewed once, and left to activate and revert alone. Manual steps drop from eighteen to zero.
Implementation checklist
- Open Markets, then Rollouts, and confirm your store meets the documented requirements.
- Map your next 90 days of promotions, noting which markets, catalogs, themes, and discounts each involves.
- Pick the rollout type per promotion: Launch for permanent changes, Event for a fixed window, Experiment to measure first.
- Build target catalogs in advance with pricing and availability set, and have someone else review them.
- Group dependent changes into one rollout so catalog, theme, and checkout updates activate together.
- Verify downstream systems: product feeds, headless caching, ERP price sync, and any app reading catalog pricing.
- Schedule one low-risk Event rollout first, confirm activation and rollback behave as expected, and define who owns cancelling or amending a rollout.
FAQ
Q: Can we schedule a catalog that does not exist yet, or does it have to be built first?
A: Scheduling applies to existing catalogs. You activate, deactivate, or switch between catalogs you have already created, so the real work is building and reviewing the target catalog ahead of time. Treat preparation as the task and scheduling as the last step.
Q: How does an Experiment rollout differ from running a discount or an app-based price test?
A: An Experiment compares a treatment catalog against a control and reports the difference, so pricing stays in Shopify's catalog model rather than a discount layer or app override. That keeps your source of truth intact and makes the result easier to act on.
Resources
Need guidance? Talk to Makro.