startsAt, endsAt or status says one thing while buyers experience another, check whether the discount belongs to a Shopify Rollout. Admin GraphQL 2026-10 adds a read-only rollouts connection on discount types. Read rollout treatment, schedule and effective traffic allocation before reporting the discount as universally active or inactive.On this page
Why dates no longer tell the whole story
On October 1, 2026, Shopify added discount participation in Rollouts. Merchants can schedule an offer alongside theme and checkout changes, or serve it to only a portion of Online Store visitors. The discount’s own dates and configuration do not change when a rollout treatment adds or removes it. A monitoring app that only reads native dates can therefore mislabel buyer-facing availability.
Read the rollout context
Upgrade the relevant Admin GraphQL calls to 2026-10, request read_rollouts and preserve existing resource scopes. Some installed merchants may need to reauthorize the new scope. Query the discount’s rollouts connection, inspect each rollout’s schedule and treatment changes, and read effectiveTrafficAllocation rather than assuming configured traffic percentage is the live percentage. Check for pauses, early conclusions and competing rollouts.
Full effective traffic activation can reach supported sales channels subject to normal discount eligibility. Partial-traffic rollout activation applies to the Online Store only. A discount may still be restricted by its customer, product or other normal eligibility rules, so rollout participation is one diagnostic dimension, not the entire checkout decision.
Make status reporting honest
Separate discount configured status from buyer-facing rollout availability in dashboards. For example, show “scheduled by discount dates; currently served to a subset through Rollout” rather than forcing one green Active label. Cache carefully and invalidate on rollout lifecycle and update webhooks. A paused rollout or changed effective allocation can make a previously accurate snapshot stale.
Don’t treat a missing read as a deletion
On Admin API versions earlier than 2026-10, Shopify may filter rollout-affected discounts out of reads when status and actual buyer reach disagree. If a discount disappears from a query, do not automatically delete its local record or turn off an external promotion. Upgrade and re-read, or flag the record for reconciliation. This is especially important for promotion sync jobs that treat a missing discount as an instruction to deactivate product-level price displays.
status and date range do not always describe what every buyer sees. Rollouts can override reach without editing those native fields, and a partial rollout is not a global activation.How to test this
- Create a discount in a development store and read its dates and status on API 2026-10.
- Add it to a Rollout serving only part of Online Store traffic. Read the
rolloutsconnection and effective allocation. - Test qualifying and non-qualifying buyer sessions, and compare Online Store behavior with another channel where appropriate.
- Pause and conclude the Rollout; verify dashboard status and cache refresh after webhook or re-read.
- Simulate a discount missing from an older-version read; confirm the sync does not delete the record or disable an unrelated promotion.

