Amazon FBA Removal Order + Expiration Dates

Short version

An Amazon FBA Removal Order is the seller's instruction to Amazon to dispose of or return units inside FBA. For expiration-dated inventory the right play is usually a Disposal Request scheduled to submit on the Unsellable by Date, so Amazon acts on a date the seller chose rather than Amazon's automatic disposal cycle. Removal Orders submit through the Selling Partner API; Amazon controls acceptance, processing time, per-unit fees, and the physical disposal or return.

What a Removal Order is

Amazon's Removal Order is the only seller-controlled way to clear inventory from FBA short of letting the units sell. Two types exist:

• Disposal Request. Amazon physically destroys the units. The seller does not receive the stock back.
• Return Order. Amazon ships the units to a seller-supplied address. The seller pays a per-unit return fee plus shipping.

For expiration-dated categories (food, supplements, cosmetics, OTC), Disposal Requests are the operator default because the units have no resale value outside Amazon. For non-expiration categories (overstock electronics, returned-but-unopened goods), Return Orders dominate.

Disposal Request vs. Return Order — pick the right one

The right call depends on the residual value of the units net of fees.

• Disposal Request is right when: the units are already past Unsellable by Date, the category does not permit re-sale outside Amazon, or the residual margin is lower than the return fee plus inbound shipping cost to the alternative channel.
• Return Order is right when: the units have residual sellable shelf life, an alternative channel exists at a positive net margin, and the per-unit return fee is lower than the residual sales price.

For supplement and food categories the math almost always favors Disposal. For consumer-electronics overstock the math almost always favors Return. The grey zone is cosmetics and OTC where some operators run an outlet channel.

The Removal Order lifecycle

1. Created. Seller (or Shelfdoc on the seller's behalf) builds the request — type, MSKU, quantity, address (for Return Orders).
2. Submitted. The request POSTs to SP-API. Amazon assigns an internal order ID and surfaces it in Seller Central.
3. Processing. Amazon picks the units from the warehouse. Cancellation is no longer guaranteed past this point.
4. Completed. Amazon has physically disposed the units (Disposal Request) or shipped them to the return address (Return Order).
5. Cancelled. The order was cancelled before processing. The units remain in FBA.
6. Failed. Amazon rejected the order — usually a status code with a reason (insufficient inventory, address invalid, MSKU mismatch).

Scheduled submission vs. ad-hoc

Two ways to file a Removal Order:

• Ad-hoc. Seller opens Seller Central or Shelfdoc, picks an MSKU, files immediately. Useful for one-off cleanup of a specific batch.
• Scheduled. Seller sets a future date on the MSKU. When the calendar reaches that date, the software submits the order automatically. The right pattern for expiration-dated inventory because the trigger (the Unsellable by Date) is known months in advance.

Scheduled submission is the only way to guarantee the units are filed on the day they FEFO-block. Manual filing relies on the operator remembering, on a day where many other operational tasks compete for attention.

A real-shaped example

A cosmetics seller has 624 units of MSKU CC-25SU-LOT09with an Unsellable by Date of March 15, 2026. On November 4 the seller projects: weekly velocity for this MSKU has been running at 18.4 units, and a small FEFO discount on the soonest-expiring offer brings it to about 22. Over 18 weeks until Unsellable by Date, that's roughly 400 units sold through, leaving about 220 units residual at the cutoff.

The seller schedules a Disposal Request in Shelfdoc for the residual to fire on March 15. The schedule re-reads the FBA quantity at submission time — so when March 15 arrives and the actual quantity is 211 units (slightly above the projection), the Removal Order is built and submitted for 211, not 220. Amazon accepts the order; status moves to Processing within about 36 hours and to Completed nine business days later.

Without the schedule, the same 211 units sit FEFO-blocked through Amazon's automatic disposal cycle. The seller pays storage on the case-pack volume for the additional 30 to 60 days the cycle takes to reach them. The per-unit removal fee is the same in both paths; the carrying cost is what differs.

Common mistakes

• Filing a single Removal Order for the whole ASIN. Bulk Removal Orders dispose units that may still have months of shelf life. Per-MSKU filing preserves the still-sellable batches.
• Scheduling against the printed expiration instead of Unsellable by Date. The Unsellable by Date is usually 30–60 days earlier. A Disposal Request filed on the printed expiration submits weeks after the units already FEFO-blocked.
• Filing a Return Order for residual expired stock. Per-unit return fees plus inbound shipping back to the seller often exceed the residual value of expired units. Disposal is usually cheaper.
• Not reconciling the quantity at submission time. Sales between the scheduling date and the submission date change the quantity. The scheduled order should submit against the actual current quantity, not the quantity at the time the schedule was created.

How Shelfdoc helps with Removal Order scheduling

• A scheduled Removal Order sits on each mapped MSKU. The seller picks the trigger date and chooses Disposal Request or Return Order.
• At submission time the script re-reads the current FBA quantity, so the Removal Order matches the quantity Amazon actually holds — not the quantity the seller projected weeks earlier.
• The Removal Orders page shows status updates synced back from SP-API — Submitted, Processing, Completed, Cancelled, Failed — with the timestamp on each transition.
• The full lifecycle of each Removal Order exports as a PDF or Excel row, which is the format Seller Support cases and downstream accounting reconciliation both ask for.

What Shelfdoc does not do

• Shelfdoc does not change Amazon's acceptance decision, processing time, or per-unit removal fee. The submission is ours; the rest is Amazon's.
• Shelfdoc does not negotiate Removal Order fees or cancellation windows with Amazon Seller Support.
• Shelfdoc does not coordinate the physical shipment when a Return Order ships to an address other than the seller's default warehouse.

Related topics

• Amazon FBA expiration date management — the four-stage lifecycle.
• Amazon FBA expired inventory — what happens when the seller does not file a Removal Order.
• Amazon FBA Unsellable by Date — the date that should drive the Removal Order schedule.
• FNSKU and MSKU expiration date tracking — the per-MSKU unit-of-work model.
• Resources hub — every guide, glossary entry, calculator, and decision framework, organized by topic.