FBA reimbursements you are probably missing

Amazon owes most FBA sellers money they've never claimed, and it isn't because Amazon is deliberately withholding it. Lost inventory, damaged units, and processing errors happen constantly at Amazon's scale, and the reimbursement system is opt-in in practice: Amazon doesn't proactively find every discrepancy and pay it out. Sellers have to find it themselves, and most don't check often enough to catch it before the claim window closes.

What actually qualifies for reimbursement

Inventory lost in an Amazon warehouse, whether during receiving, storage, or a warehouse transfer, is reimbursable. So is inventory damaged while in Amazon's custody, as opposed to damage that happened before it arrived at the warehouse.

Customer returns that Amazon processed as a refund but never actually returned to your inventory, or returned in a condition that made it unsellable without Amazon following their own stated return-grading policy, often qualify. Overcharged FBA fees, where Amazon charged a fee based on incorrect weight or dimensions for your product, are reimbursable once corrected. Inventory removed or disposed of without your authorization, or without following the removal process you actually requested, also qualifies.

What generally doesn't qualify: inventory that was correctly sold and delivered, normal wear from the FBA process that doesn't rise to warehouse damage, or discrepancies you can't actually document even if you suspect something went wrong.

Where to actually find these discrepancies

The Inventory Adjustments report and the Reimbursements report in Seller Central are the starting points, but neither one automatically surfaces every discrepancy in a way that's easy to act on. The more useful approach is comparing your own inventory records against Amazon's reported inventory levels over time, looking specifically for units that disappear from Amazon's count without a corresponding sale, return, or customer refund on your end.

The FBA Inventory Reconciliation report, when run over a full quarter rather than a short window, tends to surface patterns that a single month's data hides, since some discrepancies only become visible when you're tracking the full lifecycle of a batch of inventory from receiving through sale or return.

The claim window, and why timing matters more than most sellers realize

Amazon generally allows claims to be filed within 18 months of the date of loss or the transaction in question, though the practical window to catch and act on a discrepancy is often much shorter, since some report data isn't retained or easily accessible past a certain point. Checking quarterly, rather than once a year, catches issues while the underlying data is still easy to pull and while the specific transaction details are fresh enough to build a clear case.

Sellers who only check once a year, or only after noticing a specific problem, tend to find that older discrepancies are harder to document because the relevant shipment or return records have aged out of easy access, even if they're technically still within the claim window.

Building a case Amazon will actually approve

A reimbursement case needs to reference the specific shipment ID, ASIN, and quantity in question, not a general statement that inventory seems low. Amazon's system is comparing your claim against their own internal records, so vague claims without specific reference numbers are easy to deny simply because there's nothing concrete to verify against.

For lost inventory during a warehouse transfer, the shipment ID and the specific units that were part of that shipment matter. For customer returns not properly refunded to inventory, the specific order ID and return tracking information strengthen the claim considerably. For fee overcharges based on incorrect dimensions, your own product measurements, ideally with a photo showing a tape measure against the actual product, help establish the correct figures against Amazon's recorded ones.

What to do when a claim gets denied

A denial isn't always final, and it's common for a first claim to get denied simply because it didn't include enough specific detail, not because the underlying discrepancy is invalid. Re-reading the denial reason and responding to that specific reason, rather than resubmitting the same claim with the same information, moves things forward more often than an identical resubmission does.

If a claim is denied for lack of documentation, adding the specific report data, screenshots, or shipment details that were missing the first time addresses the actual gap. If a claim is denied because Amazon's records show something different from your claim, requesting the specific data Amazon is using, rather than arguing your version is correct without seeing theirs, tends to be more productive.

Doing this manually versus using a service

Running the reconciliation and filing claims manually is entirely possible for sellers with the time to check quarterly and build specific cases. The tradeoff is mostly about consistency: sellers managing this alongside everything else in running a business often let it slip for a quarter or two, and each skipped quarter is a set of discrepancies aging closer to becoming undocumentable.

Reimbursement services, whether software-based or managed, generally work by running the reconciliation process continuously rather than periodically, which catches discrepancies closer to when they happen and before the supporting data becomes harder to access. Whether that's worth the cost depends mostly on inventory volume, since the reimbursement amounts scale with how much inventory is moving through FBA in the first place, and a service fee that's a reasonable percentage of a large reimbursement is a different calculation than the same fee against a small one.

A realistic sense of scale

The amount owed varies enormously by seller size and how long it's been since the account was last checked, so there's no meaningful average figure to point to here. What's more useful than a number is the pattern: sellers running their first-ever reconciliation, especially after a year or more without checking, tend to find more than they expect, simply because discrepancies accumulate quietly and don't show up anywhere unless someone goes looking for them specifically.