Amazon FBA Refunds and Reimbursements, Explained With the Actual Math

What 'FBA refund' actually means

Most people typing this phrase aren't asking about giving a customer their money back. They're asking about the money Amazon owes them for something that went wrong inside Amazon's own warehouses or fee system. The correct term for that is a reimbursement, and it's a separate process from a customer-facing refund, even though Seller Central blends the language in ways that confuse both.

There are four buckets that generate this kind of reimbursement, and they behave differently:

• Lost or damaged inbound inventory — a carrier or Amazon receiving crew loses count between your dock and the fulfillment center.
• Lost or damaged inventory once it's inside the FC — units vanish or get destroyed during storage, picking, or a warehouse transfer.
• Customer returns that go wrong — a customer sends an item back, Amazon refunds them, but the unit never gets scanned back into sellable inventory, or comes back damaged and isn't reimbursed automatically.
• FBA fee overcharges — the wrong dimensional weight, size tier, or category gets applied and you're billed more than the published rate card says you should be.

Each one has its own report, its own evidence trail, and its own deadline. Treating them as one undifferentiated pile is the first mistake, and it's the one that causes people to miss money they were owed.

The math Amazon runs — a worked example

Say you ship 500 units of a product with a landed cost of $9.20 per unit that sells for $34.99. Amazon's receiving report at the fulfillment center shows only 480 units checked in. That's a 20-unit shortage — nothing dramatic, easy to miss if you're not reconciling shipment reports against sales floor inventory counts every month.

For inventory lost or damaged inside a fulfillment center, Amazon reimburses at your manufacturing cost — what you paid to source or produce the unit. That is the basis Amazon moved to under the updated FBA inventory reimbursement policy, announced in its Seller Forums News channel and effective 31 March 2025, and it explicitly excludes shipping, handling and customs duties. So the 20 missing units are settled against the factory price, not against the $34.99 they sell for and not against the $9.20 landed figure that includes freight. Sellers who still budget recovery at sale price are the ones who get surprised. If you have not entered your own cost on the Manage Your Manufacturing Cost page in the Inventory Defect and Reimbursement portal, Amazon estimates it from comparable products — and an estimate against the wrong comparable is the most common reason a payout looks too low.

Inbound shipment shortages work differently again — Amazon compares what the carrier's bill of lading says you sent against what its dock scanned in, and the reimbursement calculation runs off a separate report than the in-FC loss does. If you're only checking one report, you're only catching one kind of leak.

The claim window, and what evidence you need

Amazon's reimbursement windows aren't unlimited, and the company has changed them before, so treat any specific day count as something to confirm on the current policy page rather than take on faith from a blog post — including this one. The direction of travel is the thing to know: the windows have been shortened, not lengthened. Claims that older guides describe as running to 18 months now run in weeks and months depending on the discrepancy type, so a quarterly reconciliation habit that used to be safe no longer is. Fee overcharges have no single published clock but get harder to document the older the data gets, because Amazon doesn't keep every historical fee-calculation input visible forever.

What you need on hand for a claim: the shipment ID and carrier documentation for inbound shortages, the inventory adjustment report for in-FC loss or damage, the return tracking status for customer returns that never made it back to sellable stock, and your own product dimensions and weight for a fee dispute. Amazon's own reports are usually the primary evidence — you're not proving your case from outside data, you're pointing back at Amazon's own numbers and showing where they don't add up.

In the accounts we work on — collectively more than $500M in managed revenue across 100+ brands — reimbursement recovery is one of the most consistently under-filed categories, usually because nobody owns the monthly reconciliation, not because the money isn't there.

When the number is wrong

Amazon's automated reimbursement isn't always the final answer, and it isn't always in your favor. If a case gets auto-approved at a value you think is too low, you can open a follow-up case with your own cost documentation and ask for a recalculation — cite the specific report and line item, not a general complaint. If a claim gets denied outright, read the denial reason literally; a huge share of denials are procedural (wrong report type cited, missing shipment ID) rather than a real rejection of the underlying loss.

If Seller Support closes a case without resolving it, that's not the end — you can reopen or escalate, and doing so with a clean paper trail (screenshots, report exports, dates) moves faster than arguing in the chat window. The mistake is assuming a closed case means Amazon decided you weren't owed anything; often it just means the first agent ran out of patience before you did.

The mistake most sellers make — including one we've made

The most common mistake is treating reimbursement auditing as a one-time cleanup instead of a monthly habit. Discrepancies accumulate quietly — a few units here, a fee tier misapplied there — and by the time someone notices, part of the claim window has already closed on the oldest events.

The mistake we've made ourselves: filing too aggressively on tools that flag every unit-count mismatch as a loss, without checking Amazon's normal operational variance first. Warehouses have some baseline shrink and count noise that Amazon doesn't consider reimbursable, and pushing every discrepancy as a claim wastes time and can draw account-level scrutiny for no real recovery. The fix isn't to file less — it's to file only what's actually outside normal variance, with the specific report as backup, every time.

Where this fits

If the leak you're chasing is in the warehouse — lost units, fee misclassification, returns that never came back — that's inventory-side work, and it's what Dr. Stock, run as a managed product by Fable 5 out of Full Circle, does alongside stockout prevention, aged-inventory decisions, and shipment discrepancy tracking, with Orbit's fee and BSR trackers included and purchasing decisions always going to a human. If the money is actually leaking inside the ad account — wasted spend, a broken ACOS — that's a different diagnosis, and that's Dr. PPC's job, not ours. Either way, the reconciliation habit described above is worth doing whether or not you ever hire anyone to do it for you.