Requirements and considerations for using rollouts

Before you create or manage a rollout, review the following requirements and considerations, including which plans support rollouts, the permissions that your staff need, and the limitations that apply to rollouts.

Requirements for using rollouts

To use rollouts, your store needs to meet the following requirements:

  • Rollouts are available on the Basic plan or higher.
  • Experiments are available to stores on the Grow plan or higher.

User permission requirements

The following users can edit, create, or manage rollouts:

  • The store owner and organization owner.
  • Users with the Administrator or Organization administrator roles.
  • Users with a Store role with the Markets > Rollouts store permissions, and the following additional store permissions for the type of changes that can be added to a rollout:
    • The View and edit checkout and customer accounts permission to replace a checkout and accounts configuration.
    • The Discounts permission to add a discount change.
    • The Online store > Themes permission to add a replacement theme. To edit your current theme in a rollout, change a replacement theme that's already in a rollout, or save theme editor changes to a rollout, users also need the Online store > Edit code permission.
    • The Manage and install apps and channels or Translate & Adapt permission for App and sales channel permissions to manage translations and theme and content edits to themes and checkout and account configurations.
    • The Catalogs > View permission to review a catalog change. To add or edit a catalog change, users need both the View and Create and edit catalogs permissions, which also require the View products permission.

Considerations for using rollouts

Before you create a rollout, review the following considerations:

  • A rollout that publishes catalog changes to 100% of visitors updates your prices and product availability in your online store. Depending on the catalog's markets and sales channels, the rollout can also update the following places:
  • When you pause a rollout, or when an Event ends and rolls back, those places return to your catalogs' current prices and product availability. A rollout changes only whether a catalog is active or draft, so it doesn't restore a copy of your catalog from when the rollout started. Any edits that you make to a catalog while the rollout is running stay in place. Shopify POS and your product feeds return on their next sync. Until that happens, they can still display the published prices.
  • A Launch merges its changes into your store permanently. To keep the changes from an Event, apply the rollout permanently.
  • Theme changes, and checkout and accounts configuration changes, apply only to your online store. Headless and custom storefront checkouts aren't supported for those changes, and can't be tested with rollouts.
  • Experiments, and rollouts that publish to less than 100% of visitors, apply only to your online store.
  • Your online store can display different prices or products than Google or other sales channels. This happens when a catalog change is in an Experiment, or in a rollout that publishes to less than 100% of visitors. Product ads, listings, feeds, and third-party apps might not display the same offer.
  • Rollout analytics measure visitors on your online store, cart, and checkout. Visitors on the other places that a rollout applies to, such as headless storefronts and Shopify POS, aren't included in your rollout's results.
  • You can't apply rollouts to vintage themes.
  • You can't change Liquid templates as part of a rollout.

Considerations for catalog changes

If you add a catalog change to a rollout, then review the following considerations:

  • You can add a catalog before you assign it to a market, but the rollout's catalog change isn't displayed to any customers until the catalog is assigned to at least one market. A catalog that's assigned directly to a company location can't be added to a rollout.
  • You can't add an archived catalog to a rollout.
  • A catalog can be part of only one unended rollout at a time.
  • A rollout changes a catalog's status only. You can still change the status manually, and a warning is displayed when your change affects an active rollout. Edits to the catalog's prices, price adjustments, and products are saved right away, and they apply whenever the catalog is active.
  • If a catalog is removed from all of its markets, then the rollout's catalog change isn't displayed to any customers, but the change isn't cancelled. If you assign the catalog to a market while the rollout is running, then the change applies to that market, and a rollout that applies permanently still sets the catalog's status.
  • You can set a catalog to the status that it already has. In an Experiment, the control and the treatment then display the same status, and the comparison measures no change.
  • Your plan determines how many catalogs can be active across your B2B markets, and that limit counts each catalog's market assignments. You can't set a catalog to Active when the activation takes you over the total limit. Setting another catalog to Draft in the same rollout offsets the activation only when it frees up at least as many market assignments as the activation uses. Learn more about the limits for each market type.
  • If you remove or reassign a market's catalogs while an unended rollout includes one of those catalogs, then the rollout's audience changes.

Considerations for discount changes

If you add a discount change to a rollout, then review the following considerations:

  • A discount can be part of only one unended rollout at a time.
  • You can add up to 250 discounts to a rollout.
  • In an Experiment, the control follows your store's standard discount behavior. No discount is included in the control.
  • A discount that's part of a rollout keeps its own active dates, and those dates continue to apply independently of the rollout.
  • A discount is active for a visitor when the discount's own active dates apply, or when an active rollout that activates the discount applies to that visitor. A rollout that deactivates the discount makes it inactive for the visitors in the rollout, even when the discount's own active dates apply.
  • A discount that's part of a rollout can still be edited. A warning is displayed when an edit can affect the rollout's schedule or an Experiment's results.
  • Combination settings still apply to a discount that's part of a rollout. During an Experiment, the visitors in the treatment and the visitors in the control can be eligible for different sets of discounts, so a combination that applies for one group might not apply for the other. Learn more about discount combinations.