Reported details
What happened
Shopify’s official changelog says Admin GraphQL API version 2026-10 adds a read-only Discount.rollouts connection across Discount types.
Apps must request the read_rollouts scope, while existing resource scopes still apply; existing installations may require merchant reauthorization.
The changelog says discount availability should be read alongside Rollout schedules, effective allocation, treatment splits, and activation or expiry changes. Configured traffic allocation alone does not determine effective reach.
Shopify says partial-traffic Rollout activation applies on the Online Store only, while discounts activated at 100% effective traffic are available across all sales channels subject to normal eligibility rules. Discounts outside Rollouts behave as before.
Business relevance
Why it matters
A discount’s native startsAt and endsAt fields may no longer be sufficient for an app to determine whether the offer is currently available to buyers.
This affects discount dashboards, promotion monitoring, and workflows that use API data to trigger merchant or customer-facing decisions.
For merchants globally, the immediate question is whether an installed app reads discount availability through the Admin GraphQL API and whether it supports version 2026-10.
Editorial perspective
Analysis & judgment
The mechanism is a shift from date-only interpretation to a combined availability model: an app must reconcile the discount’s own fields with Rollout timing, allocation, treatment, and activation state. That changes the merchant decision from trusting a single status field to checking how the integration calculates reach; the supplied evidence is a single official changelog summary and does not show implementation examples or validate behavior in a specific app.
The merchant consequence is most material for stores using automated promotion reporting or operational alerts, because an integration that ignores Rollouts could present an incomplete view of who can receive a discount. Merchants should therefore seek confirmation from the relevant app before relying on discount-status automation; the evidence does not establish that any particular app is currently misreporting availability.
The decision rule is conditional: prioritize an integration review now if the app reads discounts, depends on native dates or status, or supports partial-audience promotions; otherwise monitor its version and scope guidance. The evidence sets out the required data points but provides no migration deadline, incident record, or proof that every discount workflow needs a change.
Applicability
Seller impact
Merchants running partial-traffic discount tests should verify that their reporting or automation distinguishes Online Store reach from broader sales-channel availability.
Existing app installations may need reauthorization when the app requests read_rollouts, so permission changes could become part of an upgrade workflow.
Discounts that are not included in Rollouts are described as behaving as before, limiting the immediate impact for merchants using only standard discount schedules.
Action plan
What to do now
- 1
Inventory discount-reading apps
nowList installed apps, dashboards, and automations that read Shopify discounts or infer availability from startsAt, endsAt, or status. Mark workflows that support experiments or partial buyer reach for priority review.
- 2
Ask vendors about Rollout support
this-weekRequest confirmation that each relevant integration can query Discount.rollouts, use the read_rollouts scope, combine Rollout fields with native discount fields, and handle any required merchant reauthorization.
- 3
Track rollout-aware reporting
monitorWatch app release notes and Shopify’s upgrade guidance for support on the API version used by your store. Recheck promotion reports when a discount is activated for partial traffic or changes treatment.
What not to do yet
- Do not infer buyer reach from configured traffic allocation, native discount dates, or a single discount status field when a discount is part of a Rollout.
Sources & context
Evidence and sources
A source may provide only a headline or summary. Read the evidence scope below. Links and workflow checks are not independent fact verification. Internal confidence values are workflow signals, not probabilities of factual correctness.
- 01Source link
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.
Shopify Developer Changelog · Workflow status: single-source
Retrieved: October 1, 2026 at 04:07 p.m. UTC
Claim is bounded to the ingested title or summary; no source body or quotation is retained.