Drop your Seller Central exports in and see which losses were never reimbursed and which claim windows are about to close.
Your reports never leave your browser — this page contains no networking code at all. Pull the plug and it still works. Try it.
In Seller Central, open the FBA inventory reimbursement / cost section and check whether your SKUs have a sourcing cost on file.
Do they?
| Report | Where | Without it, what can't be checked |
|---|---|---|
| Inventory Adjustments | Reports → Inventory | Losses that were never reimbursed at all — usually the largest bucket |
| Reimbursements | Reports → Payments | What you were actually paid, and on what basis |
| FBA Customer Returns | Reports → Inventory | Refunds where the unit never came back |
Bring whatever you have. Whatever is missing gets named explicitly in the results — a check that did not run is never reported as a check that passed.
"General inventory loss gets 18 months" is everywhere. In Amazon's own help pages,
18 months is the value being struck out.
Amazon publishes policy changes as redlined documents — insertions underlined, removals struck through. Copy the text out by ordinary means and both marks vanish, so the old figure and the new one run together into one sentence. That is how a deleted number ends up quoted across the whole industry. The sentence reads:
You must submit your claim no later than 18 months 60 days after the date
the item was reported lost or damaged in your Inventory Ledger report.
Claims submitted outside of this window are not eligible for reimbursement.
That last clause is the point: outside the window, not eligible.
| Claim type | Window | Counted from |
|---|---|---|
| Fulfilment centre operations lost or damaged by Amazon after receiving |
60 days |
the date the loss was reported in your Inventory Ledger |
| Customer return never came back | 45–105 days two-sided |
the customer refund or replacement. Filing before day 45 is rejected outright — earlier is not safer |
| Removal order · lost in transit | 75 days | the removal shipment's creation date; and no sooner than 14 days after its last confirmed movement |
| Removal order · damaged in transit | 60 days | the date it was delivered back to you. Claimable as soon as you receive it |
| Disputing an amount already paid | 60 days | the date Amazon issued the reimbursement (the approval date column in your report) |
| Shipment to Amazon | not obtained | ⛔ This window is in none of the four official documents I hold. Not knowing is reported as not knowing — no figure is given |
⭐ The two removal anchors (creation date / delivery-back date) are not in the Inventory Ledger — they live in the Removal Order Detail and Removal Shipment Detail reports. So this tool lists removal rows without a countdown: a deadline that looks precise but is wrong is worse than no deadline, because nobody goes and checks it.
⚠ These day counts come from Amazon's UK/EU redlined help pages, not the US ones.
Here is why that is as far as it goes. The main policy page does not contain the windows — it delegates them to four claim-type sub-pages (shipment to Amazon, fulfilment centre operations, customer returns, removals). The US versions of those four sub-pages sit behind a login wall and cannot be retrieved publicly. The only one obtainable in full is the UK/EU redlined PDF.
⭐ Which is probably why the whole industry still quotes 18 months: the authoritative page is not publicly readable, the readable artefact is a redline, and copying text out of a redline fuses the old figure and the new one into a single sentence.
The four marketplaces run the same template — the wording matches sentence for
sentence, with only local term swaps (Canada says manufacturing cost where the US says sourcing
cost) — so the direction is sound. ⛔ But I will not call it US-verified.
Check the day count on your own marketplace's claim page before you file. In the JSON at the
bottom of this page these rows are tagged verifiedOtherMarketplace, not
verified.
verified Read from Amazon's own documents. The exact sentence is quoted below.
reported From public industry sources. Amazon's own wording was not obtained. Direction is sound; verify the exact figure yourself before filing.
It decides which numbers you can file on and which are only leads. All six windows above come from Amazon's own redlined documents — the URL, retrieval date and byte count of all four PDFs are in the JSON at the bottom of this page.
| What it means | Amazon's wording |
|---|---|
| Lost before a customer order → reimbursed at your sourcing cost excludes shipping, handling, customs duties |
"For shipment to Amazon claims, removals claims, and fulfillment center operations claims that occur before fulfillment, we will reimburse you the sourcing cost of the item." |
| No cost supplied → estimated from comparable products, not from zero | "we evaluate the sourcing cost of comparable products sold by Amazon, by other sellers, and through other wholesale channels" |
| Where to enter it: the Sourcing cost page in the IDR portal | "You can provide your sourcing cost for an item on the Sourcing cost page on the Inventory Defect & Reimbursement (IDR) portal." |
| Already unsellable when lost → a reduced cost | "we will reimburse at a reduced estimated cost of the unit" |
| Customer return claims → order price minus applicable fees | "we calculate the reimbursement value as the sales price of the replacement item on the original order minus applicable fees." |
| Ceiling: $5,000 per unit | "The maximum reimbursement amount for a single unit of any FBA eligible item is $5,000." |
| ⛔ Reimbursement at estimated proceeds is the old rule struck through in the redline. Most secondary sources still describe it |
So the first thing to do is not to open a case — it is to put a sourcing cost on every SKU on the Sourcing cost page in the IDR portal. Leave it blank and Amazon values your unit from somebody else's product.
"Examples of such activities include submitting insufficiently researched or premature requests, or submitting a large number of requests in a short time. Sellers who repeatedly engage in these activities may receive delayed support on their cases or be subject to monitoring, investigation, and account action."
That is why this tool will not hand you a "you were underpaid $X" figure. To produce it you would need to know what fraction of cost Amazon actually paid, and Amazon has never stated one. The cost of an invented number is not a rejected claim — it is the account.
What you get instead: the cost ceiling, and every actual per-unit amount from your own report, so you can do the subtraction yourself against costs only you know.
Kept here because the only difference between a figure with no provenance and a figure
that was corrected is whether anybody wrote it down. Amazon's exact sentence for each is in
corrections in the JSON at the bottom of this page.
| What this page said | What the official wording says |
|---|---|
| 60 days, from the Inventory Ledger date. "18 months" is the struck-through value | |
| 45–105 days. both bounds were wrong | |
| 75 / 60 days, two windows. "90" appears in no official document | |
| Withdrawn. Amazon estimates from comparable products. a secondary paraphrase published as verified — exactly what this page criticises other tools for | |
| The official 60 days is to dispute a valuation after reimbursement. a remedy after the fact was published as an obligation before it | |
| The US term is sourcing cost; 2025-03-10 comes from the Canada document and is when cost estimates start being refreshed, not an effective date. the US document says March 31 2025 and Japan says April 1 2025 — three marketplaces, three dates |