You requested 500 units back. Seller Central says the removal order is "Completed." Your warehouse counted 462. That 38-unit gap is the classic Amazon removal order missing items problem — and if you don't catch it fast, Amazon will never pay you for it. "Completed" means Amazon finished processing the order. It does not mean you received everything.
- "Completed" ≠ complete. The status means Amazon processed the removal order — not that every unit arrived at your door in sellable condition.
- Reconcile three numbers: requested (Removal Order Detail report), shipped (Removal Shipment Detail report), and received (your own receiving counts). Any gap is a potential claim.
- Lost-in-transit removal claims have a hard corridor: you must wait 15 days from the removal shipment creation date to file, and after day 75 the claim is gone forever.
- All other removal claims (delivered short, damaged in transit) must be filed within 60 days of the shipment being delivered back to you.
- Log every removal box the day it arrives. Removals trickle in over weeks; if you wait to count them "all at once," the window closes before you finish.
The removal lifecycle — and where units vanish
A removal order looks like one transaction in Seller Central. In reality it's a multi-week, multi-box logistics chain, and units can fall out at every link.
Here's what actually happens after you click "Create removal order":
- Requested. You specify SKUs and quantities. Amazon queues the order — removals are low priority in the fulfillment center, so this stage alone can take days or weeks.
- Picked. Warehouse workers pull your units from bins across one or more FCs. Units that can't be located are quietly cancelled off the order — they were lost before the removal even shipped.
- Shipped — in multiple boxes, over weeks. Amazon doesn't consolidate. A 500-unit removal might leave as nine boxes from three different FCs, spread across four or five weeks. Each box is its own shipment with its own tracking number.
- Delivered. Boxes land at your warehouse, your 3PL, or your garage — rarely on the same day, rarely in order.
Units disappear in four distinct ways, and each failure mode points to a different claim:
- Never picked. Amazon couldn't find the units in the FC. These often show up as cancelled quantity on the removal order — but the underlying units may be lost or misplaced inventory that belongs in a warehouse lost & damaged claim instead.
- Lost in transit. The Removal Shipment Detail report says a box shipped; the tracking dies somewhere between the FC and your door. This is the claim type with the strict 15–75 day corridor (more below).
- Delivered short. The box arrives, but the count inside doesn't match the shipped quantity on the report. Nine units on paper, seven in the box.
- Damaged in transit. The units arrive, but crushed, leaking, or otherwise unsellable — damage that wasn't noted when Amazon shipped them.
The status field never distinguishes any of this. Once every unit on the order has been either shipped or cancelled, the order flips to "Completed" — even if half the boxes are still on trucks, and even if some of them never arrive at all. That's why sellers searching for answers about Amazon removal order missing items usually find the problem weeks after it happened: nothing in Seller Central flags it for you.
How to find Amazon removal order missing items: reconcile requested vs. shipped vs. received
Removal order reimbursement starts with three numbers that should match and often don't. Two come from Amazon reports; the third comes from you. Here's the exact workflow.
Pull the Removal Order Detail report
In Seller Central, go to Reports → Fulfillment → Removals → Removal Order Detail. For each order and SKU it shows requested quantity, shipped quantity, in-process quantity, and cancelled quantity. This is your "what should have come back" baseline: requested − cancelled = expected units.
Pull the Removal Shipment Detail report
Same menu: Removal Shipment Detail. This lists every physical shipment Amazon created for the order — carrier, tracking number, ship date, and shipped quantity per box. This is where you see that your one removal order became nine separate shipments. Note the shipment creation date for each one; the lost-in-transit clock runs from this date, not from delivery.
Count what actually arrived — box by box
Match each delivered box to a tracking number from step 2 and record the date, the count per SKU, and the condition. This receiving log is the one piece of evidence Amazon can't generate for you — and no claim survives without it.
Run the discrepancy math
Three comparisons: requested vs. shipped (gap = units Amazon never sent — investigate as lost or misplaced in the FC), shipped vs. tracking delivered (gap = lost in transit), and shipped vs. your received count (gap = delivered short or damaged). Illustrative example: 500 requested, 12 cancelled, 488 shipped, 480 delivered per tracking, 462 counted sellable — that's 8 lost in transit, 18 short or damaged, and 12 cancelled units worth investigating separately.
Classify each gap and file the right claim
Lost in transit goes in one bucket with one deadline; short and damaged deliveries go in another with a different deadline (table below). Cancelled units that Amazon "couldn't find" may belong in a warehouse-lost claim, and if units were destroyed instead of returned, check whether you're owed a disposed-without-consent reimbursement. File each via Seller Support with the removal order ID, tracking numbers, and your counts attached.
Do this for every removal order — including the automated ones Amazon creates for stranded or aged inventory if you have auto-removals enabled. Those are the easiest to lose track of, because you never manually requested them in the first place.
The timing rules: removal claim windows you cannot miss
Since October 23, 2024, Amazon's claim windows are short and unforgiving — the current FBA reimbursement policy cut most eligibility periods by roughly 90% from the old 18-month standard. Removal claims got the strangest rule of all: a window that doesn't just close, but also doesn't open right away.
| Claim scenario | Window opens | Window closes | Clock starts from |
|---|---|---|---|
| Removal units lost in transit (box shipped, never delivered) | Day 15 — you must wait; earlier claims are rejected | Day 75 — hard cutoff, no exceptions | Removal shipment creation date (per box, not per order) |
| All other removal claims (delivered short, damaged in transit, wrong items) | On delivery | 60 days after delivery back to you | Date the shipment was delivered to you |
| For comparison: lost/damaged in an Amazon FC | When reported lost or damaged | 60 days after the item was reported lost or damaged | Ledger event date |
For lost-in-transit removal claims, you get a 60-day corridor that starts on day 15 after the removal shipment was created. File on day 10 and Amazon rejects it as premature. File on day 76 and it's permanently ineligible — no appeal, no exception. And because each box is its own shipment with its own creation date, a single removal order can have nine different deadlines running at once. If a box shipped six weeks ago and the tracking is dead, you have roughly a month left. Check today.
Note the asymmetry: the lost-in-transit clock runs from when Amazon created the shipment, not from anything you can see at your receiving dock. A box that quietly never arrives triggers no alert, no email, no dashboard flag. If you're not diffing the shipment report against your receiving log, day 75 passes in silence. This is the same trap we cover in our breakdown of the 60-day deadline era — Amazon's automation won't catch what its own reports don't reconcile.
The documentation checklist that gets removal claims paid
Removal order reimbursement claims live or die on evidence. Seller Support's first move is almost always to quote the shipped quantity back at you; your job is to make the discrepancy undeniable. Before you open a case, have all of this ready:
- Removal order ID — from the Removal Order Detail report, plus the requested/shipped/cancelled quantities per SKU.
- Per-box tracking numbers — from the Removal Shipment Detail report, with each box's carrier, ship date, shipment creation date, and shipped quantity. For lost-in-transit claims, include the tracking history showing the box never delivered.
- Your receiving log — dated entries for every box that arrived, matched to tracking numbers, with per-SKU counts. Photos of each opened box and its contents on arrival are the strongest evidence you can attach, especially for short or damaged deliveries.
- The discrepancy math, spelled out — one or two lines: "Shipment X (tracking …) shows 60 units shipped on July 2; delivered July 9; box contained 52 units of SKU ABC. Claiming 8 units." Don't make the agent do arithmetic.
- Your product cost data — since March 10, 2025 (US), pre-order inventory losses are reimbursed at manufacturing cost, and Amazon uses its own estimate unless you've uploaded actual costs. If Amazon's estimate is low, you're underpaid on every approved claim. Upload real costs first.
One case per issue works better than one mega-case per removal order. A lost-in-transit box and a short delivery are different claim types with different windows — bundling them invites a partial denial that stalls everything.
The habit that saves these claims: log every box the day it lands
Here's the practical reality that kills most removal claims: the boxes trickle in. Week one, two boxes. Week three, four more. Week six, one straggler. The natural instinct is to wait until "the removal is done" and count everything at once.
That instinct costs you money. By the time the last box arrives, the first box's lost-in-transit window may be half gone — remember, the 75-day ceiling runs from each shipment's creation date, and Amazon often creates shipments days or weeks before they move. A removal that stretches over six weeks of deliveries can leave you with only two or three weeks to notice a missing box, gather evidence, and file.
Every removal box gets logged the day it arrives: date, tracking number, per-SKU count, condition, photos. Five minutes per box. Then, once a week, diff the Removal Shipment Detail report against the log and ask one question: which shipped boxes have I not received, and how old is each shipment? Anything past day 15 with dead tracking gets filed that week — don't wait for the order to "finish."
If that weekly diff sounds like exactly the kind of chore that slips during Q4 — it is. This category is one of the eight we built ClawbackPro to watch automatically: it reconciles every removal shipment against what Amazon's reports say arrived, flags the gaps at unit level, and files inside the corridor, alongside categories like lost inbound shipments where the same requested-vs-received logic applies in the other direction. Pricing is 15% of what's actually recovered, charged only after Amazon pays — $0 otherwise.
Removal order reimbursement FAQ
Why does my removal order say "Completed" when items are missing?
"Completed" only means Amazon finished processing the order on its side — every unit was either handed to a carrier or cancelled. It says nothing about whether the boxes survived transit or whether the counts inside match the reports. Amazon will never flag the gap for you; you have to reconcile requested vs. shipped vs. received counts yourself.
How long do I have to file a claim for a removal lost in transit?
Between 15 and 75 days from the removal shipment creation date. You must wait until day 15 (claims filed earlier are rejected as premature), and after day 75 the claim is permanently ineligible. Each box on a removal order is its own shipment with its own clock.
Which reports show how many units Amazon actually shipped back?
Two reports under Seller Central → Reports → Fulfillment → Removals: the Removal Order Detail report (requested, shipped, in-process, and cancelled quantities per SKU) and the Removal Shipment Detail report (every shipment with carrier, tracking, and shipped quantity per box). Compare both against your own receiving counts.
How much will Amazon reimburse for removal order missing items?
Since March 10, 2025 (US), inventory lost or damaged before a customer order — which covers most removal losses — is reimbursed at manufacturing cost (product cost excluding shipping, duties, and handling), not sale price. Amazon uses its own estimated cost unless you upload actual cost data, so upload real numbers if Amazon's estimate runs low.
Removal orders are where inventory goes to disappear quietly. The reports exist, the claim paths exist, and the money is recoverable — but only for sellers who count every box and respect two deadlines that arrive faster than the boxes do.
