You can now manage buyer-requested order edits through the GraphQL Admin API, Customer Account API, and three new webhook topics in API version 2026-10. Buyers can request the removal of unfulfilled line items from an order, and merchants (or apps acting on their behalf) can review, resolve, or decline those requests.
What changed
Buyers can now request edits to the unfulfilled line items on an order, and those requests are exposed as a first-class resource, , across Shopify's APIs.
On the GraphQL Admin API:
- A new
object represents a buyer's request, including its status, the requested changes, and timestamps for when the request was made, resolved, or declined. - New mutations let apps act on requests on behalf of merchants and buyers:
creates a request,marks a request as manually resolved, andrejects a request. - A new
query returns the calculated financial outcome of a request before it's created. - The Order object has a new
connection and a newfield that aggregates the order's request state for display. You can use the newsearch filter on the orders query to find orders with requests waiting for merchant action.
On the Customer Account API, a new mutation lets buyers submit an edit request, and a new query previews the financial outcome. supports an optional idempotency key through the @idempotent directive. A retried request returns the originally created object instead of a duplicate.
Three new webhook topics notify apps as requests move through their lifecycle: , , and . The payload includes the request's status, the , and the requested line item changes with their resolved quantities.
Who's affected
Apps that read or manage orders, such as order management, ERP, fulfillment, and 3PL integrations, and apps that build customer account experiences. To use the new GraphQL Admin API surface, apps need the scope for queries and for mutations.
Why this matters
In the 2026-07 API version, there is no API-visible record when a buyer wants an order changed after purchase. Buyers contact the merchant out-of-band, and merchants edit the order manually. Order edits made through requests flow through the existing order editing model, but apps can't see the request, act on it, or keep external systems (ERP, WMS) in sync with pending changes before fulfillment. With these APIs, apps can now surface pending requests in their own workflows, hold fulfillment on orders with a REQUESTED status, and automate resolution or decline decisions.
What to do
No action is required. If you want to support buyer-requested order edits you can update your app to use the latest version of GraphQL Admin API, Customer Account API, and webhooks.