The Money Amazon Owes You and Never Mentions

FBA is a physical operation running at enormous scale. Units get miscounted at receiving, dropped in a warehouse, scanned into the wrong bin, refunded to a customer who never posts anything back, measured wrong and billed at the wrong size tier. None of this is unusual and most of it is nobody's fault in particular. It's just what happens when hundreds of millions of items move through buildings.

Amazon has processes for correcting a good deal of it. What Amazon does not have is a habit of telling you when it's happened. There's no alert, no monthly statement line that reads "we lost eleven of your units." The information is sitting in reports you have to know to open, and the corrections that don't happen automatically only happen if you ask.

The money involved is rarely dramatic in any single instance. That's precisely why it accumulates. A handful of units here, a fee tier there, and nobody notices because no individual line is big enough to notice.

Here's each category, where it hides, and what to do about it.

1. Inventory lost or damaged in the warehouse

The most common one. A unit was received into a fulfilment centre, and at some later point it is no longer there and was not sold. Or it's there but has been damaged in handling and moved to unsellable.

Where it lives: the Inventory Ledger, under Reports → Fulfilment. Use the detail view rather than the summary. Every movement of your stock is recorded as an event with a reason code, and the ones you care about are the adjustments — lost, damaged, found, disposed, and the various flavours of each. The Inventory Adjustments report covers similar ground.

How to read it: work by reason code, not by product. Filter to loss and damage events over a period, group them, and compare against what has already been reimbursed. Amazon does credit a portion of this automatically, and it has expanded the categories it handles without being asked, so the first thing to establish for any loss is whether it's already been settled. The Reimbursements report, under Reports → Fulfilment → Payments, is where credits appear.

The gap you're looking for is losses in the ledger with no matching entry in the reimbursements report. That's the claimable set.

A trap worth knowing: "found" events. Amazon loses a unit, reimburses you, then locates the unit later and adds it back to your inventory, reversing the reimbursement. That's correct behaviour and not something to fight. But it means a naive count of loss events overstates what you're owed, and filing on losses that were later resolved creates duplicate claims you don't want on your record.

2. Inventory lost inbound

Different problem, different report. You sent 500 units, Amazon received and checked in 480. The other 20 exist somewhere between your freight forwarder and the receiving dock.

Where it lives: shipment reconciliation inside your shipping queue. Each shipment has a reconcile view showing units shipped against units received. Discrepancies are flagged there.

Why this one gets missed: the shipment closes. Sellers check the queue while a shipment is in transit and stop looking once it flips to received, but the received count and the shipped count are different numbers and only one of them is on screen by default. Discrepancies also resolve themselves fairly often, because units from one shipment get checked in over a period, sometimes across multiple buildings.

What you need: proof. This is the category where a claim lives or dies on documentation, because the loss might have happened before Amazon ever touched the boxes. You want the shipment ID, your packing list, the carrier's proof of delivery, and invoices from your supplier showing the quantity actually existed. Sellers who don't keep these systematically cannot claim, regardless of whether they're right.

Give a shipment discrepancy some time to settle before filing. Then check it again, because a discrepancy that hasn't resolved after a reasonable wait usually isn't going to.

3. Customer returns that never came back

A customer requests a refund. Amazon refunds them, often immediately, and the money comes out of your account. The customer is then supposed to post the item back. Sometimes they don't. Sometimes they post back a different item, or an empty box.

You've paid for a return that never returned.

Where it lives: the FBA Customer Returns report shows return events and the disposition each unit was given. Cross-referencing this against your refunds is the exercise. A refund with no corresponding return receipt after a sensible interval is the pattern.

There's a second version of this that's easier to miss: the unit did come back, was graded unsellable, and then neither reimbursed nor returned to you. Unsellable is a legitimate outcome, but the unit still exists and belongs to someone. Check what happened to it.

Why it compounds: return rates are usually reported as a percentage, and a percentage feels bounded. But this failure mode scales with volume, and it's invisible in aggregate because your return rate looks normal whether or not the units actually arrive back.

4. Fee overcharges from wrong measurements

Your fulfilment fee is set by size tier, and size tier is set by the dimensions and weight Amazon recorded for your unit. Amazon measures units in its own facilities using automated equipment. That measurement can be wrong.

The usual causes are dull and mechanical. A unit measured while packaging was slightly inflated. A soft-sided product measured at its thickest point. A dimension recorded before you changed the packaging. Once a wrong measurement is on file, every single unit you sell is billed at the wrong tier, silently, for as long as it stands.

Where it lives: the FBA fee preview report shows the dimensions and weight Amazon holds for each of your products, alongside the fees it will charge. This is the report to check.

What to do: measure and weigh your own units, in their shipping-ready state, and compare against what the report says. If there's a real discrepancy, request a remeasurement through support. Amazon will re-cube the item, and if its own figure was wrong, the tier corrects going forward. Overcharges already billed can be raised as a separate claim.

This is the category most worth checking proactively, because unlike a lost unit, it doesn't happen once. It's a small error multiplied by every sale of that product until someone catches it. It's also the one to check whenever you change packaging, since your dimensions changed and Amazon's record didn't.

5. Disposals and removals you didn't authorise

Units can be disposed of or returned to you under a removal order. That's normal when you asked for it. Occasionally it happens when you didn't, or in a quantity you didn't request, or a removal you did request arrives short.

Where it lives: the Removal Order Detail report and the Removal Shipment Detail report, plus disposal reason codes in the Inventory Ledger.

The check: reconcile removals requested against removals completed, and disposals against your own instruction. Anything disposed of that you never asked to dispose of is inventory that left your business without a sale. Same for a removal order where fewer units arrived than were shipped out.

Check your automated removal settings while you're in there. Long-term storage automation can be configured to remove or dispose of aged stock without a per-instance prompt, which is a setting sellers switch on once and then forget. Units disposed of under a setting you enabled are not a claim, they're a decision. Worth knowing which of the two you're looking at before you file.

About claim windows

Be careful here, and don't trust anything you half-remember.

Amazon applies time limits to reimbursement claims, they differ by claim type, and Amazon has revised them. Several of the windows have been shortened in recent years, and some categories moved to automatic reimbursement in a way that changed what sellers are expected to file at all. Any specific number of days you read in a forum post or an older article may simply not be current.

So rather than working to a number: check the current policy in Seller Central before you build any process around a deadline, and operate on a cadence tight enough that the exact window stops mattering. Monthly reconciliation, or fortnightly if your volume is high, keeps you comfortably inside any window Amazon is likely to set. Sellers who get caught out are almost never the ones who missed by a few days. They're the ones who looked once a year.

Two other operational points. Reimbursement is generally made at Amazon's own assessed value for the unit, which is derived from its own data and may not match what you paid or what you'd have sold it for. And filing duplicate claims for the same event is a real problem rather than a harmless one, so reconcile against the reimbursements report before you file anything.

Why this compounds silently

Every category here shares a structure. The loss is small per instance. It's recorded in a report that isn't part of anyone's routine. It never appears as a line item labelled as a loss. And nothing in the system prompts you.

So it doesn't show up as a problem. It shows up as a margin that's slightly worse than your spreadsheet says, month after month, with no identifiable cause. If you've ever reconciled your calculated profit against your actual deposits and found a persistent unexplained gap in the same direction, this is one of the places to look.

The fix isn't complicated, it's just unglamorous: a recurring reconciliation, each report checked against the one that should corroborate it, claims filed while the evidence is fresh. Plenty of sellers outsource this to a reimbursement service that takes a percentage of what it recovers. That's a reasonable trade if you're not going to do it, though it's worth reading how any such service accesses your account and whether its filing practices are ones you'd be comfortable defending.

If you'd rather see it yourself, that's the sort of gap Seller Sphere is built to surface: the ledger, the fees and the reimbursements reconciled against each other, so a loss that was never credited back shows up as a number rather than as a vague sense that the maths is off.