How Amazon Seller Reimbursement Actually Works

What actually qualifies as a reimbursement

Reimbursement covers Amazon's mistakes, not yours. The main categories: units lost or damaged in an FBA warehouse, units lost or damaged in transit between warehouses, customer returns that Amazon marks as received but never credits back to your inventory, fee overcharges from incorrect weight or dimension data, and removal orders that go missing before they reach you.

It does not cover units you shipped short, inventory that's simply unsellable due to your own packaging, or normal shrinkage within Amazon's stated tolerance. Sellers who file for everything, including the stuff that's genuinely on them, tend to get flagged for review faster and get less benefit of the doubt on the cases that are actually valid.

How Amazon calculates what it owes you

Amazon reimburses at your manufacturing cost per unit, landed, not your retail price and not your average selling price. This is the single most common source of disputes — sellers expect to be made whole at what they would have sold the unit for and get a fraction of that instead. That's the rule as written, and it's worth knowing before you file so the number doesn't feel like an insult when it lands.

Deadlines vary by category and change occasionally, so treat any specific day-count as something to verify in Seller Central at the time you file rather than something to memorize. What doesn't change: the clock starts running the moment the discrepancy is created, not the moment you notice it. Sellers who audit monthly catch cases inside the window. Sellers who audit twice a year lose a real share of valid claims to the deadline alone.

A worked example: the math behind one case

Say a shipment of 500 units arrives at an Amazon warehouse and the system confirms receipt of 480. Twenty units are gone — not damaged, not returned, just unaccounted for in the inventory ledger. Your landed manufacturing cost is $4.50 per unit. Amazon reimburses at that $4.50, so the case is worth $90, not the $400 you'd have made at a $19.99 retail price.

Now scale that up. Across the more than $500M in managed revenue Full Circle has managed across 100+ brands, warehouse-count discrepancies like this one are one of the most consistent reimbursement categories we find, and they're almost always caught by matching the shipment reconciliation report against the warehouse receiving report, not by waiting for Amazon to flag it. Amazon does not proactively tell you about most of these. You find them or you don't get the $90.

Filing the case: what Amazon actually wants

A reimbursement case needs the FNSKU, the shipment or removal order ID, the exact quantity in dispute, and the date range. Vague cases — "some units seem to be missing from this shipment" — get closed fast, often with a boilerplate denial. Specific cases with the shipment reconciliation report attached get resolved.

The reports that matter: the Shipment Reconciliation report shows what you sent versus what Amazon confirmed received. The Reimbursements report shows what's already been paid, so you don't refile something Amazon already settled. The Fee Preview report shows what Amazon calculated for weight and dimensions, which is where a lot of the fee-overcharge cases start.

Common mistakes — including the one everyone makes at least once

The biggest mistake is treating reimbursement as a once-a-quarter cleanup task instead of a standing check against every shipment and removal order. By the time a seller notices a pattern, several individual cases are already past deadline.

The second is assuming a denial is final. Amazon's first-line reimbursement decisions are automated and wrong often enough that a documented appeal with the reconciliation report attached succeeds a meaningful share of the time. We've had cases where the first denial cited the wrong SKU entirely — a data-matching error on Amazon's side, not a judgment call — and the fix was simply resubmitting with the correct identifier called out explicitly.

The third, and one we've made ourselves: reconciling reimbursement cases against gross units shipped instead of net units after known returns and cancellations, which overstates the discrepancy and gets a case rejected for inflated numbers when the underlying claim was actually valid at a smaller amount.

When the number is wrong or the claim gets denied

If the reimbursed amount looks low, check whether Amazon used your correct manufacturing cost — sellers who haven't updated their cost basis in Seller Central sometimes get reimbursed against an old, lower figure. If a claim is denied outright, request the specific reason code and respond to that reason directly rather than resubmitting the same case. If a case sits open past 30 days with no movement, escalate through Seller Support with the case ID rather than opening a duplicate, which resets the queue.

If the leak you're chasing turns out to be in ad spend — wasted spend on the wrong search terms, not lost units in a warehouse — that's a different problem with a different owner. That's Dr. PPC's territory, not this one.