Why this money goes missing in the first place
Amazon's fulfillment network moves an enormous volume of inventory every day. Units get scanned onto trucks, cross-docked between fulfillment centers, shuffled during peak season, picked, packed, returned and re-shelved millions of times over. At that scale some units will be lost, damaged, miscounted or mishandled. That's no criticism of Amazon's operations; any warehouse network this large has errors, and the error rate per unit is genuinely small.
What sellers underestimate is how much of the follow-up falls to them. Amazon does not run a background process that finds every one of these errors and pays you automatically. Some cases do get caught and reimbursed without you doing anything, and we'll come to those. A large share of lost, damaged and miscounted inventory, though, just sits as a discrepancy between what you shipped and what Amazon says it received, or between your inventory ledger and what's actually sellable. Nobody on Amazon's side is rewarded for digging up money to hand back to you. The job falls to the seller, and most sellers never do it.
Reimbursement recovery is not about disputing legitimate fees or gaming Amazon's systems. It's about identifying specific, documented instances where Amazon's own records show a unit or a fee doesn't reconcile, and asking them to make it right under their own stated policy. Treat it as an accounting function, not a negotiation.
The main categories of reimbursement-eligible events
Most reimbursement opportunities fall into a handful of recurring buckets. Once you know them by name, they're much easier to spot in a report.
- Units lost inbound. You ship a carton of 48 units to a fulfillment center and the receiving dock checks in only 44. The other 4 went missing somewhere between dock and shelf, and unless someone reconciles the shipment, the gap disappears into the noise.
- Units lost in the warehouse. After receipt, inventory gets moved between storage locations, transferred between fulfillment centers to balance capacity, or pulled for quality checks. Units go missing in these internal transfers more often than people assume.
- Units damaged by Amazon. This means damage that happens inside Amazon's buildings, on Amazon's watch. Damage caused by your own packaging failing in transit, or by the carrier before check-in, doesn't count, and Amazon will push back on claims where the damage is arguably your packaging's fault.
- Customer returns that never come back to you. This is the most underrated category by far. A customer returns an item, Amazon refunds the customer or restocks the unit, and somewhere along the way the seller gets neither the unit back in sellable inventory nor a matching reimbursement. The unit vanishes from both sides of the ledger.
- Overcharged fees, especially from dimensional weight and category errors. FBA fees are calculated from product dimensions, weight and category. If Amazon measures a product wrongly, or a listing is miscategorized in a way that raises the referral fee percentage, you overpay on every unit sold until someone catches it and gets it corrected retroactively.
- Removal and disposal errors. When you request a removal or disposal order and Amazon doesn't account for the units correctly, that's a reimbursement case too, though sellers tend to forget to check once the order is filed.
How sellers actually find these discrepancies
You don't need to guess. Amazon publishes the data you need, but it's spread across several reports that don't talk to each other, which is why most sellers never connect the dots.
- Shipment reconciliation. For every inbound shipment, compare the units you shipped (from your packing list or shipment plan) with the units Amazon logged as received in Seller Central. Any gap is your first lead.
- The FBA Inventory Reconciliation report. It ties receipts, shipments, adjustments and current inventory together in one place, and it's one of the best tools for spotting units that disappeared between reporting periods.
- The Inventory Adjustments report. Amazon logs adjustments here with a reason code. Pull the codes tied to damage, loss or found inventory line by line, because not every adjustment triggers the automatic reimbursement it should.
- The Reimbursements tab in Seller Central. Amazon does process some cases automatically. Check this monthly to see what's already been paid, so you don't waste time chasing a case that's closed.
- Removal order and disposal claim tracking. Keep a running log of removal orders and their outcomes. If a removal order says units were disposed of but the count doesn't match what you sent for removal, that's a case.
Every one of these comes down to comparing two numbers that should match and don't. The work is dull but mechanical, which is why the problem can be solved.
Depending on your Seller Central layout, some of this adjustment and reconciliation data now sits in the Inventory Ledger report under Reports, then Fulfillment. If you can't find a report under the name used here, look there first.
The clock is running: the filing window
Amazon doesn't let reimbursement claims sit open indefinitely, and the windows are now much shorter than many guides still say. For years the figure commonly cited for most FBA claims was around 18 months from the date of the loss or discrepancy. Amazon cut that sharply in late 2024. In its Seller Central announcement, Amazon said that from October 23, 2024, manual claims for items lost or damaged in a fulfillment center must be submitted no later than 60 days after the item was reported lost or damaged. The exact terms live in Amazon's seller policies and can change again, so check the current policy page for your marketplace.
| Claim type | When you can file (per Amazon's October 2024 update) |
|---|---|
| Lost or damaged in a fulfillment center | No later than 60 days after the item was reported lost or damaged |
| FBA customer returns | Between 60 and 120 days after the customer refund or replacement date |
| Removal shipments lost in transit | Between 15 and 75 days from the shipment creation date |
| Other removal issues | Within 60 days of the shipment being delivered back to you |
Amazon also said that from November 1, 2024 it would proactively reimburse items reported lost in its fulfillment centers, and that almost all warehouse lost and damaged claims and customer return cases would be reimbursed automatically. Removal claims stayed manual. If you believe inventory was lost or damaged and no automatic reimbursement appears, you still have to file a manual claim within the window.
In practice this is blunt. Every month a seller goes without checking reconciliation reports, some recoverable money ages out of eligibility for good. There's no retroactive appeal once a window closes. A shipment discrepancy nobody looked at two years ago is a closed case. With windows measured in weeks, this has to be a recurring habit; an occasional cleanup project will miss most of it.
A worked timing example
Say, for illustration, that a fulfillment center reports 6 units of one SKU lost on March 3. If no automatic reimbursement shows up, your manual claim has to go in by early May, 60 days later. Now say a customer was refunded on March 3 for a return that never arrived back. You shouldn't file before early May, because Amazon wants to give the customer time to send it, and you must file before early July, 120 days after the refund. Those two cases from the same day have windows that barely overlap, which is why a monthly review with a dated case log works far better than a once-a-year sweep.
A practical monthly process you can actually run
You don't need a finance degree for this. You need a repeatable checklist and the discipline to run it every month instead of "when I get around to it."
- Pull the reconciliation reports. Download the FBA Inventory Reconciliation report and the Inventory Adjustments report for the prior month, alongside your own shipment records for anything received in that window.
- Line up units shipped against units received. For every inbound shipment closed in the period, check the received quantity against what you sent and flag any shortfall.
- Scan adjustment reason codes. Look for codes showing damage, loss or warehouse-caused events, and check whether a matching reimbursement already appears in the Reimbursements tab.
- Spot-check returns. Pull a sample of customer returns from the period and confirm each one either landed back in sellable (or at least accounted-for) inventory, or the customer refund was matched by a disposition on your side.
- Check fee accuracy on new or recently changed listings. If a product's dimensions, weight or category changed, or a new ASIN launched, confirm the fee charged matches the real product specs.
- Open cases with specifics. When you find a real discrepancy, open a case citing the exact shipment ID, order ID or ASIN, the quantities and the date range. Vague cases get vague responses. Specific cases with a clear paper trail get resolved faster, with fewer follow-ups.
Maintain a simple spreadsheet of every case you open: shipment or order ID, the discrepancy amount, the date filed, and the outcome. Over a year this becomes your own internal audit trail, and it makes it obvious which months you skipped, which is usually where the biggest gaps hide.
Check the amount, not only whether you were paid
A reimbursement that arrives isn't automatically the right one. Compare each payment with what the unit was worth under Amazon's policy and with the quantity that went missing. Amazon's reimbursement policy page says that if you disagree with its valuation of a unit, you can file a claim through Contact Us in Seller Central within 60 days after the reimbursement was issued. Add a column to your case log for the amount paid and the amount you expected, so short payments stand out.
Common mistakes that cost sellers money
- Filing a customer return claim too early. Amazon's own guidance is to wait 60 days so the customer has time to send the item back, and early claims tend to be rejected.
- Counting a unit twice. The same lost unit can appear as an adjustment and later as "found." Net them out before filing.
- Ignoring units marked as carrier-damaged on inbound. If the carrier damaged a partnered shipment, the record you need is different from a warehouse damage case, so read the reason code before you write the claim.
- Letting reports pile up. With 60-day windows, a quarter without review can mean whole categories of claims have expired.
Why you shouldn't file everything you can
Once you see how much money sits in these gaps, it's tempting to file on anything that looks even slightly off. Don't. Amazon tracks reimbursement request patterns at the account level, and sellers who file excessively, or on thin or speculative evidence, can draw account health scrutiny they don't want. A pattern of weak or unsupported claims does more harm than leaving a smaller amount unrecovered.
Evidence is what separates a legitimate audit from a fishing expedition. Every case should rest on a specific number that doesn't reconcile: a shipment quantity, an inventory count, or a fee calculation you can check yourself against the product's real dimensions. If you can't point to the exact discrepancy and the record that proves it, it isn't ready to file. Treat it like a monthly accounting reconciliation.
Manual reconciliation vs. software or an agency
Full reconciliation by hand, every month, across every SKU and shipment, gets tedious once you're past a modest catalog. Pulling several reports, cross-referencing reason codes, spot-checking returns and tracking case outcomes is real operational work, and it's the kind of work that stops the moment a seller gets busy with a product launch or a slow quarter.
Some sellers handle it in-house without trouble, especially at smaller scale, by putting it on a recurring calendar reminder and treating it like closing the books. Others reach a point where SKU count and shipment volume make manual tracking error-prone, and a dedicated tool or a team that does this for a living becomes more reliable. The math is easy; staying consistent is the hard part. A process that runs 8 months out of 12 leaves the other 4 months of discrepancies running toward the filing deadline with nobody watching, and with today's shorter windows, many of those will expire. Whichever route you choose, what matters is that the process runs every month.
This is found profit, not new revenue
Every dollar recovered through reimbursements is money you already earned. You spent nothing to acquire it: no extra ad spend, no inventory risk, no marketing funnel. You don't have to build anything. It's profit that already belongs to you, sitting in Amazon's ledger until someone points at the discrepancy and asks for it back.
That makes it one of the highest-return activities available to an established FBA seller, dollar for dollar. Most growth levers cost money before they make money, and this one doesn't. The only cost is checking every month, before the window closes on money you're already owed.
Frequently asked questions
Some cases get caught and paid without you doing anything, and Amazon said in late 2024 that it would reimburse most warehouse losses automatically. Many discrepancies still never get paid on their own. Lost, damaged and miscounted units often sit as a gap between what you shipped and what Amazon logged as received. Nobody on Amazon's side is looking for money to hand back, so the reconciliation job falls to you.
The window commonly cited for years was around 18 months from the date of the loss or discrepancy, but that is out of date. Under Amazon's October 2024 update, fulfillment center lost or damaged claims must be filed within 60 days of the item being reported lost or damaged, and customer return claims between 60 and 120 days after the refund. The exact terms live inside Amazon's seller policies and can shift, so check the current page. Every month you skip reconciliation, some recoverable money ages out of eligibility.
Start with the FBA Inventory Reconciliation report, which ties receipts, shipments, adjustments and current inventory together, and the Inventory Adjustments report, where Amazon logs adjustments with a reason code. Compare both against your own shipment records, then check the Reimbursements tab monthly so you don't chase cases Amazon already paid.
It can. Amazon tracks reimbursement request patterns at the account level, and sellers who file excessively or build claims on thin, speculative evidence can draw account health scrutiny. Every case should point to a specific number that doesn't reconcile, such as a shipment quantity or a fee you can verify against the product's real dimensions.
It is money Amazon owes you when inventory it holds is lost, damaged, destroyed or disposed of in its network, or when a customer refund was funded but the unit never came back. Amazon issues some automatically, but a meaningful share are only paid if you identify the discrepancy and file within the eligibility window.
The common categories are inbound shipment discrepancies, warehouse lost or damaged inventory, customer returns never restocked, refunds issued without a returned unit, removal order losses, and fee overcharges such as incorrect dimensions or weight. Each has its own report trail and its own filing deadline.
It is the Seller Central message or reimbursement report line confirming Amazon has credited your account for a specific discrepancy. Reconcile these against your own claim log, because an automatic reimbursement is sometimes issued at a lower value than the unit is actually worth, and that gap is disputable.
Amazon's reimbursement policy lets you file a claim through Contact Us in Seller Central within 60 days after the reimbursement was issued if you don't agree with its valuation of a unit. Bring the reimbursement ID, the unit details and your reason for a different value.
Not Sure How Much Amazon Owes You?
SellerVine audits your shipment, inventory, and fee data against Amazon's own records to find reimbursement cases you're currently missing, then files them with the documentation to back each one up.
Get a Free Audit →