Shopify Rollouts for catalogs, reviewed through one holiday sale
Shopify's Rollouts can now schedule catalog changes, so a Black Friday price list can switch on at midnight and switch off on Monday by itself. It's a real improvement. Just know what it rolls back, what it doesn't, and where your sale prices can linger.

Shopify added catalog changes to Rollouts on October 23, 2026, so merchants on Basic or higher can schedule per-market prices and product availability and pair them with theme, checkout and discount changes. Experiments need Grow or higher. It's a strong upgrade over setting alarms to flip catalogs by hand. The cautions: an Event rollback changes catalog status, not a saved copy, so edits made mid-sale stay; POS and Google feeds can show sale prices until their next sync; and experiments or partial rollouts only affect the online store.
The short answer
Shopify announced on October 23, 2026 that Rollouts now handles catalog changes. Catalogs are where Shopify Markets keeps per-market price lists and product availability. Now you can schedule them to switch on and off at a set time, test one against another, and launch them together with a theme and checkout change.
For any merchant who has ever set a 12:01 a.m. alarm to start a sale, that's a genuine improvement. It's available on the Basic plan and up, with experiments on Grow and up.
Our verdict: use it for your holiday sales this year, but understand one thing first. Rollouts flips which price list is switched on. It doesn't remember what the price list said when you started. Most of the surprises come from that one fact.
The clearest way to see it is to walk through a single sale.
The setup: a weekend sale for one market
Picture a home-goods store selling into the US and Canada. For Black Friday weekend, it wants lower prices on 40 products for Canadian shoppers only, a new homepage banner and a sitewide discount code, all going live Friday at midnight and ending Monday night.
With Rollouts, the store prepares a sale catalog for the Canada market ahead of time, leaving it in draft. Then it creates an Event, one of three rollout types Shopify offers. An Event publishes changes for a set period and rolls them back when it ends. It requires an end date.
Into that one Event go a theme change for the banner, a catalog change that sets the sale catalog to Active, and a discount change that switches on the code. Shopify's help center lists exactly those as allowed change types, along with checkout and accounts configuration.
That's the good part. One plan, one start time, one end time, and nobody awake at midnight.
Sequence of work
One sale, start to finish
- Before the sale
Prepare the Canada sale catalog in draft; build one Event.
- Friday 12:00 a.m.
Catalog, banner and discount go live together.
- Saturday
Edits to any catalog are saved and stay after the sale.
- Monday night
Event ends; online store returns to current catalog prices.
- Next sync
POS and product feeds catch up; until then they can show sale prices.
Rollouts flips which price list is switched on. It doesn't remember what the price list said when you started.
Friday at midnight: what goes live, and where
When a rollout goes to 100% of visitors, Shopify says it updates prices and availability in the online store, and depending on the catalog's markets and sales channels, it can also update checkout and cart, headless or custom storefronts, Shopify POS, and Google and YouTube product feeds.
That reach is a strength. Your sale doesn't just appear on product pages while checkout charges the old price.
Two details to plan around:
Partial rollouts stay on the website. If you send a rollout to less than 100% of visitors, or run it as an experiment, Shopify says it applies only to the online store. Your ads, listings, feeds and third-party apps might show a different offer than what a shopper sees on your site. If you advertise the sale price on Google, only do it with a full rollout.
Analytics have a boundary. Rollout analytics measure online store, cart and checkout visitors. Headless storefronts and POS aren't included.
Decision guide
Full rollout or partial rollout
| Consideration | 100% of visitors | Under 100%, or an Experiment |
|---|---|---|
| Online store | Updated. | Updated for the visitors in the rollout. |
| Checkout, POS, headless, Google feeds | Can be updated, depending on markets and channels. | Not updated. |
| Ads and listings | Can match the site after feeds sync. | May show a different offer. |
Saturday afternoon: someone edits the sale catalog
Here's where the important fact bites. Say that on Saturday the merchandising lead notices a typo in one sale price and fixes it in the catalog, and adds two more products to the sale.
Shopify's help center is explicit. A rollout changes only whether a catalog is active or draft. It doesn't restore a copy of the catalog from when the rollout started, and any edits you make to a catalog during the rollout stay in place.
In our sale, that's fine, since the edits were to the sale catalog, which goes back to draft. But if someone edits the regular Canada catalog during the sale, those edits are permanent and live the moment the Event ends. And if the next sale reuses this catalog, it'll carry Saturday's changes.
The practical rule: during a scheduled sale, edit only the sale catalog, and write down what you changed.
Monday night: the rollback, and what lingers
At the end date, the Event rolls back. The sale catalog goes back to draft, the discount switches off and the old banner returns.
Shopify notes that the online store and other connected places return to your catalogs' current prices and availability. But POS and product feeds return on their next sync. Until then, they can still display the published sale prices.
So for a short window after the sale, a Google listing or a register in your shop might still show the Black Friday price. Plan for it. Know when your feeds next sync, and tell store staff what to honor if a customer points to a sale price shown after the end time.
If the sale goes so well you want to keep the prices, Shopify lets you apply an Event permanently instead of rolling it back.
Green flags, red flags and who should use it
Green flags
- Scheduling replaces midnight manual switches and the mistakes that come with them.
- One rollout can bundle theme, checkout, catalog and discount changes, so they start and end together.
- Full rollouts reach checkout, POS and Google feeds, not just product pages.
- Experiments between catalogs, on Grow and up, let you test a price list against another on the online store, with a 50/50 split and a 90-day end by default.
Red flags and limits
- Rollback isn't a snapshot. Edits during the rollout stay.
- POS and feeds can show sale prices until their next sync.
- Experiments and partial rollouts only touch the online store.
- A catalog can belong to only one unended rollout at a time, which means active, draft, scheduled or paused rollouts all count. Archived catalogs, and catalogs assigned directly to a B2B company location, can't be added.
- Vintage themes aren't supported, and you can't change Liquid templates as part of a rollout.
- A rollout holds up to 250 discounts, and each discount keeps its own active dates alongside the rollout's.
Who should use it now: stores already using Markets with separate catalogs per market, planning a holiday sale or a seasonal launch. Start with one Event in one market before trying several at once.
Who should wait: stores on vintage themes, B2B setups where catalogs are tied directly to company locations, and anyone whose sales depend on ads or marketplace feeds staying in lockstep with the site minute by minute.
If you want help planning holiday pricing across markets, or connecting Rollouts with your feeds and POS so nothing lingers, our ecommerce team works on exactly that. Talk to us.
Related work: Spin Market.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.