Discounts can now be included in Rollouts

Update your app to account for discount Rollouts

Summary

Admin GraphQL API version 2026-10 adds a read-only rollouts connection across Discount types. Apps that read discounts should use Discount.rollouts alongside existing discount fields to account for Rollout-driven schedules and buyer reach.

What's changing

Merchants can include discounts in Rollouts to coordinate launches, test discounts with a share of buyers, or run temporary events alongside other store changes. When a discount is part of a Rollout, its native dates alone don't describe its availability.

Update your integration

• Request access. Add read_rollouts to your app's scopes. Existing resource scopes still apply to the underlying resource payloads, and existing installations may need merchant reauthorization.
• Read the discount's Rollouts. Query Discount.rollouts to identify which Rollouts affect the discount.
• Combine schedules and availability data. Read Rollout schedule fields alongside the discount's existing startsAt and endsAt fields. Also read effective allocation, treatment splits, and whether each change activates or expires the discount. Configured traffic allocation alone does not determine effective reach.

Account for sales-channel availability

Discounts activated at 100% effective traffic are available across all sales channels, subject to normal discount eligibility rules. Partial-traffic Rollout activation applies on the Online Store only.

Discounts outside Rollouts behave as before.

Earlier API versions

On Admin GraphQL API versions earlier than 2026-10, discounts are filtered out if they are active but may not reach all buyers, or if their status differs from the status inferred from native dates.

See the Discount Rollouts upgrade guide for integration guidance and examples.

To discover Rollouts independently of a discount or receive notifications when they change, see Rollouts queries and webhooks in the Admin GraphQL API.