Shopify Rollouts: choose a launch, event or experiment before scheduling

Shopify’s 22 September 2026 Rollouts update makes it easier to distinguish a permanent launch, a temporary promotion and an experiment while setting up store changes. The revised flow brings timing, audience allocation and conflicting settings into clearer view, and supports coordinating theme, checkout and customer account changes. Read the announcement.

For merchants preparing holiday campaigns, the useful decision comes before the schedule: should this change stay live, expire automatically, or be tested against the current experience?

Choose the outcome before choosing the date

These behaviours come from Shopify’s Rollouts overview; the examples are editorial suggestions. You manage the feature under Markets → Rollouts.

Shopify’s current requirements say Rollouts is available on Basic and higher, while experiments require Grow or higher. Staff also need Rollouts permissions and the relevant permissions for the changes they manage. Vintage themes and Liquid template edits are not supported. Check requirements and limitations.

Two details to check before scheduling

Shopify’s setup guide says schedules use the store’s timezone from Settings → General. A launch applies changes permanently; adding an end date changes the setup into an event. Read the final configuration after editing dates rather than assuming the original selection still describes it.

Also check what “rollback” means for your changes. Shopify warns that catalog rollbacks change active/draft status rather than restoring a historical copy of the catalog. Edits made while it runs remain. POS and product feeds can take until their next sync to reflect the return. Experiments and partial-traffic catalog changes can also show different offers from external feeds. These details matter if your campaign includes prices or product availability, not just a banner.

Keep a test interpretable

Our recommendation: write one sentence explaining what you expect the change to improve, then choose the available metric that would support that conclusion. Combining several unrelated changes may be convenient for a launch, but it makes an experiment harder to interpret.

Shopify’s analytics documentation says available metrics depend on the rollout type and changes included, and cannot be customised. Results cover online-store, cart and checkout visitors, rather than every channel a catalog change might affect.

Check traffic allocation separately from the experiment split. For example, if 50% of eligible visitors enter an experiment and half of that group receives the treatment, the treatment reaches 25% of eligible visitors. Record both figures in your test brief.

Before approving a campaign, review its mobile appearance, audience, start and end times, and the expected state after it finishes. For wider reporting context, see our guide to September’s Shopify session-measurement change. Keep that reporting change separate from conclusions about a storefront experiment.

Discounts join Rollouts

Updated 4 October 2026. Shopify’s 2 October release adds discounts to Rollouts. You can test an offer with part of your online-store audience, compare it with existing offers, or coordinate its launch with theme and checkout changes.

The current requirements also specify Discounts permission for staff adding a discount change. Experiments and rollouts reaching less than 100% of visitors apply only to the online store.

Our recommendation: record the offer, eligible customers and intended audience before starting. If the aim is to understand the discount’s effect, avoid changing the theme at the same time. A coordinated campaign can change several things together, but that makes it harder to identify which change affected the result.

Check how your discount apps read Rollouts

Added 5 October 2026. Shopify’s app upgrade guide identifies an integration risk: API versions before 2026-10 can omit discounts affected by certain serving rollouts. A missing result must not be treated as proof that the merchant deleted the discount.

Version 2026-10 keeps those discounts readable and adds rollout information. Apps need the read_rollouts scope alongside read_discounts to read that information; existing installations may need renewed authorisation. A discount’s status and dates alone do not establish what buyers receive during a rollout.

For merchants, ask the provider of any app that displays, syncs or promotes your discounts how it handles rollout traffic and refreshes cached data. Shopify’s guidance also calls for periodic reconciliation alongside webhook notifications. Before a promotion, test the app’s displayed offer while a rollout starts, pauses and ends.