Rollouts / Improvement (Admin)

Rollouts setup redesigned
Plan launches, limited-time events, and tests with more granular control

Choose a schedule and traffic percentage, and the setup adapts to your goal (launch, limited-time event, or experiment). Bundle theme, checkout, and customer account page changes into a single Rollout, and check reach and setting conflicts right in the setup screen.

On this page
  1. What's changing? (30-second overview)
  2. 4 key improvements
  3. How it works: setup adapts to your intent
  4. Changes you can bundle into one Rollout
  5. What the post says / what it doesn't
  6. Previous vs. new setup screen
  7. 5 things developers should know
  8. 3 practical use cases
  9. One-line summary for proposals

1What's changing?

The Rolloutssetup experience has been redesigned.
You can now plan launches (shipping something new), limited-time events (running something temporarily), and tests (trying and comparing) more clearly and with finer control.

Your goal shapes the setup

Choose a schedule and traffic percentage, and the setup adjusts based on whether the Rollout is a launch, a limited-time event, or an experiment.

Manage changes together and catch issues early

Bundle theme, checkout, and customer account changes into one Rollout, and see reach, per-variant traffic split, and setting conflicts as you set it up.

24 key improvements

Your goal shapes the setup
Choose timing and percentage → setup adjusts for a launch, event, or experiment
Bundle multiple changes
Theme, checkout, and customer accounts in one Rollout
Understand your audience
See the percentage of traffic reached and the split per variant
Check for conflicts
Spot conflicting settings within the setup flow and resolve them early

3How it works: settings adapt to your "intent"

Merchant chooses ① Timing ② Traffic percentage Settings adjust to match your intent Rollouts determines the type Launch Publish changes Limited-time event Run temporary changes Experiment (test) Test store changes (split traffic between test versions)
The article lists two inputs: "timing" and "traffic percentage" . The specific conditions that determine whether a combination is treated as a launch, event, or experiment arenot stated. See the help documentation for details.

4Changes you can combine into one Rollout

Theme Checkout Customer account pages One Rollout Delivered at the same time and traffic percentage Check reach Allocation per test version A B
From the storefront (theme) to checkout and post-purchase customer accounts,you can manage purchase experience changes together as a single Rollout.

5What the article says / doesn't say

Stated

What we know

The setup screen (setup experience) has been redesigned
Timing and traffic percentage switch the settings to match your intent (launch / limited-time event / experiment)
Changes to themes, checkout, and customer account pages can be combined into one Rollout
You can check reach and allocation per test version
Conflicting settings can be reviewed within the setup flow
Type: "Improvement"; area: "Admin"

Not stated

What the article doesn't tell us

• Eligible plans / requirements
• Details of the intent detection logic
• Concrete examples of what counts as a "conflicting" setting
• Whether test result measurement or reporting has changed
• Whether it can be managed via API or apps
• Pricing

Step-by-step setup instructions arenot providedin the article. It says to "refer to the help documentation for the new Rollouts settings," so check the help docs and the actual admin before using it in production.

6Previous vs. new settings screen

ItemPreviousNew settings screen
Handling of goals Not stated Reflects intent Adjusts settings for a launch, event, or experiment based on timing and percentage
Scope of changes Not stated Handled together Theme, checkout, and customer accounts in a single rollout
Audience visibility Not stated Visualized Shows reach and the allocation for each test variant
Setting conflicts Not stated Detected early Shown within the setup flow

* The article only describes the new screen and doesn't explicitly state how it differs from the previous behavior.

75 key points for developers

Intent

1. Inputs are "timing" and "percentage"

Rather than picking a launch, event, or experiment type directly, the article says settings are adjusted to match your intent based on the timing and traffic percentage you choose. Decide which type your initiative is before you start to keep the setup consistent.

2. Ship three surfaces as one unit

Changes to the theme, checkout, and customer account pages can go in the same Rollout. This reduces the risk of shipping changes that span the buying experience separately.

3. Check allocation during setup

Reach and per-variant allocation appear on the settings screen. When designing a test, you can check here that your estimated sample size matches the actual allocation.

4. Check for conflicts before publishing

Conflicting settings now appear within the setup flow. The article doesn't say what counts as a conflict. In stores running many initiatives in parallel, always review what's shown.

API ?

5. An Admin improvement, with no mention of APIs

This article covers the "Admin" area. Changes to APIs, webhooks, and app integrations arenot mentioned. If you operate or automate Rollouts from external tools, verify the help documentation against actual behavior separately.

83 use cases you can put to work

LAUNCH
USE CASE 1

Launch a redesign across "theme + checkout + customer accounts" at once

Challenge
During a site redesign, changes to the storefront, checkout, and customer accounts go live at different times, leaving the look and flow inconsistent.
Approach
Bundle changes across all three surfaces into a single Rollout and schedule its publish timing as a launch.
Impact
The entire buying experience switches over at the same time, reducing missed steps during publishing.
Technical note
Check the conflict indicators in the setup flow before publishing. The detection criteria are not documented, so pair this with testing in staging.
SALE Limited time
USE CASE 2

Plan sale and campaign experiences as "limited-time events"

Challenge
You want to change the look and checkout display only during a sale, but switching it on and off manually invites mistakes and adds workload.
Approach
Set up a Rollout as a limited-time event with a specified schedule, bundling the related changes into one.
Impact
Event planning is consolidated in the settings screen, making it easier to share with the operations team.
Technical note
Details on how event types behave, such as how changes revert automatically when the event ends, are not documented. Confirm in the help documentation before running in production.
A B 50% / 50%
USE CASE 3

Design A/B tests while checking the traffic split

Challenge
You want to try improvements to your theme or checkout, but it's hard to tell how much traffic actually reaches each version.
Approach
Set it up as an experiment with a specified traffic percentage, and check the reach and per-variant split in the settings screen before starting.
Impact
Prevents tests from starting with an unintended split and makes it easier to align on how to interpret results.
Technical note
Changes to result measurement and reporting are not mentioned. Estimate the test duration and required sample size in advance, and cross-check them against the split display.

9One-line summary for proposals

"The Rollouts settings screen has been redesigned.Just pick the timing and percentage, and the setup matches your intent, whether a launch, a limited-time event, or a test.
Bundle changes to your theme, checkout, and customer accounts into a single Rollout, and check reach and conflicts before publishing."