Amazon FBA Reimbursement: What You're Owed, and How to Actually Get It

What Actually Counts as a Reimbursement

An FBA reimbursement is Amazon paying you back for inventory it lost, damaged, or destroyed inside its own network, or for fees it charged incorrectly. It's not the same thing as a customer refund. A refund is money you give back to a buyer; a reimbursement is money Amazon gives back to you.

Five situations trigger a legitimate claim: units lost or damaged inside a fulfillment center, units lost or destroyed in transit before check-in, customer returns Amazon never actually got back or received in worse condition than reported, removal or disposal orders that went wrong, and FBA fee errors — wrong weight, wrong dimensions, wrong category — that overcharge you on every unit sold until someone catches it.

That last category gets missed most because it doesn't announce itself. A cookware brand like HexClad, shipping heavy, easy-to-damage units, tends to generate more in-warehouse damage claims. A brand shipping something small and durable, like Ridge's wallets, sees almost none of those but can still lose money quietly to a fee stack that's misclassifying its dimensional weight. The categories that need watching aren't the same for every catalog.

The Claim Windows You're Actually Working Within

Every claim type carries its own clock, and the clocks are short compared to a few years ago. Miss the window and the case usually can't be reopened, because eligibility itself expired — not just your chance to ask.

The practical effect: if you check reconciliation monthly instead of weekly, you can lose eligibility on lost-in-transit claims before you've even noticed the unit is missing. The table below covers the general structure; exact figures shift, so treat this as the shape of the rule, not the final word.

How Amazon Calculates What It Owes You

This is the part most articles on the subject still get wrong, because Amazon changed it. Under the updated FBA inventory reimbursement policy — announced by Amazon in its Seller Forums News channel and effective 31 March 2025 — lost and damaged inventory is reimbursed at your manufacturing cost, not at the item's sale price. Amazon defines manufacturing cost as what you paid to source the product from a manufacturer, wholesaler or reseller, or your cost to produce it if you make it yourself, and it explicitly excludes shipping, handling, customs duties and other landed costs.

Worked example. A fulfillment center loses 40 units of a product you sell for $35, that you buy from your factory at $14, and that lands at $18 once freight and duty are counted. The old sale-price basis would have paid out around $23.75 a unit after fees — near $950 for the 40. The current basis settles against the $14 manufacturing figure: roughly $560, less than the $720 you actually have in those units. Budget recovery at sale price and you will be short every time. The number that decides the payout is the cost figure Amazon holds for your SKU, which you can set yourself on the Manage Your Manufacturing Cost page in the Inventory Defect and Reimbursement portal — and if you don't, Amazon estimates it from comparable products.

We've reviewed enough inventory books to say this plainly: the automatic number is usually close, and periodically wrong in ways that only surface when someone lines it up against the unit's actual sale history. Full Circle's group manages more than $500M in revenue across over 100 brands, and reconciliation errors show up in that population often enough to be worth checking every time, not just when a number looks obviously off.

What the Automatic Program Catches — and What It Doesn't

Since November 2024, Amazon proactively reimburses some FBA losses in fulfillment centers as soon as the loss is logged, with no claim required. That covers the cleanest case: a unit enters the warehouse and never leaves through any order or adjustment.

It doesn't reliably catch customer returns that were never actually processed back into inventory, weight and dimension fee overcharges, or removal orders that go missing after leaving the warehouse. Those still need someone to notice the gap and file manually inside the window.

If the leak you're actually chasing is in ad spend rather than the warehouse — a stockout that killed your organic rank mid-campaign and burned budget on a listing that couldn't fulfill — that's a different problem with a different fix. That one belongs with whoever runs your PPC, not your inventory reconciliation.

The Mistakes That Cost Sellers the Most

The biggest mistake is treating "reimbursed" as "correct." A credit lands and sellers assume the case is closed and the amount is right. It's sometimes short, especially on bundled or multi-pack SKUs, where the per-unit manufacturing cost Amazon calculates against can be wrong.

The second is filing manually for something already auto-reimbursed, which gets auto-rejected or, worse, flagged for review and slows other claims for the same SKU. We've made this mistake ourselves: early on, we filed a batch of manual claims for units already silently reimbursed under the new program, and had to withdraw and refile against the right report instead.

The third is waiting for a monthly reconciliation cycle to check for lost units, which is too slow now that some windows run as short as 15 days from the transit event, not the discovery date.

When the Claim Gets Denied

A denial usually means one of three things: the unit fell outside the eligibility window, the discrepancy report didn't match Amazon's own inventory ledger closely enough to prove the loss, or the reimbursement was already issued automatically and Amazon is correctly telling you there's nothing left to pay.

If you believe the denial is wrong, reopen the case citing the specific inventory adjustment report and date range, not a general description of "missing units." Reimbursement decisions live inside fixed reports — Inventory Adjustments, Inventory Ledger, Reimbursements — and a case referencing the exact report line moves faster than one that doesn't.

If it's denied a second time on the same evidence, further escalation rarely changes the outcome. Put that attention into flagging future discrepancies faster, inside the window, instead of relitigating a closed case.