New APIs for buyer-requested order edits
Shopify developer change
MerchantDiff detected this entry in Shopify's official developer changelog on October 01, 2026.
This Shopify update is categorized as API, New, GraphQL Admin API, Events & webhooks, 2026-10.
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, RequestedOrderEdit, across Shopify's APIs. On the GraphQL Admin API: A new RequestedOrderEdit 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: requestedOrderEditCreate creates a request, requestedOrderEditResolve marks a request as manually resolved, and requestedOrderEditDecline rejects a request. A new requestedOrderEditCalculate query returns the calculated financial outcome of a request before it's created. The Order object has a new requestedOrderEdits connection and a new displayRequestedEditStatus field that aggregates the order's request state for display.
Who is 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 read_orders scope for queries and write_orders for mutations.
What action may be needed
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.
Use the official Shopify entry below as the source of truth for technical implementation details, affected APIs, migration instructions and deadlines.
Want the actionable version?
MerchantDiff monitors Shopify API changes, deprecations, deadlines and ecosystem updates, then turns them into developer-focused release intelligence: what changed, who is affected and what action may be needed.
Get MerchantDiff →