New APIs for buyer-requested order edits
Source: Shopify Dev Changelog
What Changed
Shopify has introduced new APIs for managing buyer-requested order edits, available starting in API version 2026-10. The update adds support across the GraphQL Admin API and Customer Account API, along with three new webhook topics.
Buyers can now request the removal of unfulfilled line items from an order directly through their customer account. These requests are modeled as a new first-class resource called RequestedOrderEdit. Merchants, or apps acting on a merchant’s behalf, can review each request and choose to resolve or decline it through the Admin API.
The three new webhook topics notify apps when a buyer submits a request, and when that request is resolved or declined, allowing systems to stay in sync without polling.
Why This Matters for Shopify App Developers
Order editing has traditionally been a merchant-initiated workflow, with buyers needing to contact support to request changes after checkout. This update formalizes buyer-side edit requests as a structured API object rather than an unstructured support ticket, making it possible to build automated or semi-automated approval flows.
For apps that handle customer service, order management, or post-purchase experience, this opens up new functionality: surfacing edit requests in a merchant dashboard, auto-approving requests based on configurable rules, or syncing request status with external help desk or OMS platforms.
What to Watch For
Developers working with order management, fulfillment, or customer service apps should review the RequestedOrderEdit object schema and the new webhook topics in the 2026-10 API reference. Since the feature currently covers removal of unfulfilled line items only, apps planning broader order edit workflows (such as quantity changes or additions) should confirm current scope limitations before building dependent features. Testing webhook delivery and idempotency will be important for apps that automate request resolution.