Why This Audit Pays for Itself Every Quarter
Every unit Amazon loses in a fulfillment center, damages in transit, or overcharges a fee on is money that already left your P&L once, as landed cost or as a fee, without a matching sale to show for it. Amazon's systems catch a meaningful share of these events on their own, but a large share of the remainder simply sits unclaimed in reports most sellers never open, because the discrepancy does not get flagged, it gets recorded.
Recoverable claims typically run 1 to 3 percent of annual FBA revenue once a full audit is run. On a seven-figure catalog, that range lands squarely in five figures a year, recovered from money that is already technically owed rather than from new sales. Few other activities on the operations side of an Amazon business return that much for the time invested.
The Four Reimbursement Categories That Matter Most
Of these four, refund-without-return and fee overcharges tend to be the quietest leaks. A refund-without-return case is easy to miss because it looks like a normal customer refund in the reports. A fee overcharge is easy to miss because it is small on any single unit and only becomes visible once it is totaled across months of fulfillment activity on the same ASIN.
| Category | What It Covers |
|---|---|
| Lost or damaged inventory | Units lost in a fulfillment center, damaged by Amazon or a carrier, or destroyed and disposed of without an authorized removal order |
| Customer return discrepancies | Refunds issued where the item was never actually returned, or units restocked in unsellable condition without a corresponding inventory adjustment |
| Removal order errors | Units lost or damaged during a removal or disposal shipment initiated by the seller |
| FBA fee overcharges | Fulfillment fees charged against an incorrect measured weight or dimension, often persisting on every unit sold until someone catches it |
Claim Windows You Cannot Afford to Miss
Amazon extended its general reimbursement eligibility window from 9 months to 18 months for most claim types, which sounds generous until the fine print on specific categories is factored in. Several claim types carry much shorter deadlines measured from the date the discrepancy first appears in a report, not from the original inventory event itself.
| Claim Type | Typical Filing Window |
|---|---|
| General reimbursement eligibility lookback | Up to 18 months from the inventory event |
| Lost or damaged inventory, once discrepancy is recorded | Around 60 days |
| Customer return, refund-without-return | Roughly 45 to 120 days after the refund |
| FBA fee overcharge dispute | Roughly 90 days once the mismatch is identified |
| Removal order discrepancy | 90 days, not extended under the 18-month rule |
What Amazon Already Reimburses Automatically
Amazon's automated reimbursement engine has gotten better at resolving straightforward warehouse-lost and damaged-inventory cases without a seller ever filing a claim. That is real progress, but it is a floor, not the full picture. Automatic reimbursements are also increasingly calculated against manufacturing or landed cost rather than retail price, which means even the cases Amazon does catch on its own may be underpaying relative to what the unit was actually worth.
Entire categories still require a seller-initiated claim in most cases: unreturned customer refunds, unsellable returns restocked without an adjustment, most FBA fee overcharges, and virtually anything involving a removal or disposal order. Treating Amazon's automatic reimbursements as sufficient coverage is the single biggest reason sellers underestimate how much they are actually owed.
The Quarterly Audit Process, Step by Step
- Pull the core reports. Export the Inventory Adjustment report, FBA Customer Returns report, Removal Order report, and a fee-charge history covering the full quarter from Seller Central.
- Reconcile inbound versus received units. Any gap that is not explained by a normal receiving delay is a candidate for a lost-inventory claim.
- Cross-check customer returns against refunds. A refund with no matching returned unit inside the expected window is a refund-without-return case.
- Audit fee charges against expected dimensions. A persistent mismatch usually means every unit sold in the period was overcharged by the same delta.
- Cross-reference against reimbursements already paid, so claims are not duplicated and rejected on review.
- File with evidence attached: ASIN, FNSKU, shipment or order ID, the date range of the discrepancy, and supporting documentation such as the inventory adjustment report or a supplier invoice for cost substantiation.
- Track outcomes back into your P&L against the quarter they were claimed for, not the quarter they were paid, so the true recovery rate is visible next time.
Manual Audit vs. Automated Tools: When Each Makes Sense
For catalogs under roughly 10 active SKUs, a manual quarterly reconciliation across the four core reports is usually manageable without additional tooling. Beyond that, the volume of transactions makes manual review genuinely difficult to do thoroughly, and automation starts paying for itself quickly.
Two paths tend to work well at scale. Analytics platforms with automated reconciliation flag discrepancies daily and let the internal team file claims directly, which keeps more of the recovered amount in-house. Dedicated reimbursement services handle sourcing and filing end to end, typically for a percentage of what is actually recovered. Either approach beats a spreadsheet once revenue passes roughly the half-million-dollar mark, mainly because manual review at that scale reliably misses cases.
Mistakes That Cost Sellers Legitimate Claims
- Running this audit annually instead of quarterly, which guarantees some claims expire before anyone looks for them.
- Assuming Amazon's automatic reimbursements are complete coverage, leaving refund-without-return and fee overcharges unaudited indefinitely.
- Filing claims without matching evidence such as the specific shipment ID or a supplier invoice, a common reason legitimate cases get denied on first submission.
- Not tracking cost-of-goods accurately on every active SKU, since claims are often paid against manufacturing cost and an inaccurate COGS record means even a successful claim settles for less than it should.
