Overview

Amazon is revamping the way seller‑fulfilled cancellation requests are presented to sellers. Starting soon, buyer‑initiated cancellations will leave the Buyer‑Seller Messaging inbox and appear in dedicated order‑management locations. Sellers who miss these requests risk unwanted shipments, returns, and extra fees, so the change directly targets a costly pain point.

Key Points

• Banner alert on Manage Orders — A bright banner will appear on the Manage Orders page whenever a buyer submits a cancellation, making the request impossible to overlook.
• New field in bulk order reports — Sellers who download order reports can now enable a “cancellation request” column, ensuring the data shows up during batch processing.
• API enhancements for MWS and SP‑API — Both the legacy Marketplace Web Service and the newer Selling Partner API will return two additional cancellation fields, allowing custom software to capture the request automatically.
• Email alerts remain active — In addition to the on‑screen banner, Amazon will continue sending an email for every cancellation request as a safety net.
• Messaging stays for general chat — Buyer‑Seller Messaging will still host routine conversations, but cancellation messages will be routed exclusively to the new tools.

How the New Cancellation Workflow Works

1. Request appears as a banner — When a buyer clicks “Cancel order” on the Amazon storefront, the system places a red banner at the top of the seller’s Manage Orders view. For example, a seller handling 150 orders a day will see the banner instantly for a buyer who tries to cancel a pending shipment of a Bluetooth speaker.
2. Report column surfaces the request — If the seller uses the “Order Report” download, they can toggle the “Cancellation Request” column in the report settings. In practice, a vendor who processes orders nightly will see a “Yes” flag next to the same Bluetooth speaker order in the CSV file, prompting them to halt fulfillment.
3. API payload includes cancellation flags — Developers pulling order data via MWS or SP‑API will now receive two extra fields— and . A third‑party order‑management system can read these flags and automatically pause the pick‑pack workflow for the affected SKU.