Amazon's fulfillment centers move millions of units a day, and a slice of yours will get dropped, crushed by a forklift, or shelved in the wrong bin and never seen again. Amazon's policy says you're entitled to compensation when that happens — but Amazon warehouse damaged inventory reimbursement is only mostly automatic, and "mostly" is exactly where sellers lose money. This guide shows you where FC damage and warehouse lost inventory actually show up in your reports, how to verify what Amazon paid you, and how to claim the rest before the clock runs out.
- The Inventory Ledger (Reports → Fulfillment) is the source of truth: every warehouse lost, damaged, found, and disposed event is an adjustment row there.
- A "lost" or "damaged" adjustment with no later "found" event and no matching reimbursement = money Amazon owes you.
- Since late 2024 Amazon proactively reimburses most FC lost/damaged events — but automation misses units, pays partial quantities, and values items at a low estimated manufacturing cost.
- FC operations claims must be filed within 60 days of the item being reported lost or damaged. A monthly ledger review is the only safe cadence.
- Clean cases win: one issue per case, transaction IDs, ledger rows, cost documentation, factual tone.
The Inventory Ledger: Where Warehouse Damage Actually Shows Up
Every unit Amazon touches leaves a paper trail. That trail is the Inventory Ledger, found in Seller Central under Reports → Fulfillment → Inventory Ledger. It works like a bank statement for your stock: starting balance, receipts, customer orders, and — the part that matters here — inventory ledger adjustments, the events where Amazon changes your unit count without a sale.
Run it in the "Detailed" view for the date range you're auditing, and pay attention to the event type and reason columns. Amazon labels adjustment reasons with short codes (single letters like M, D, E, and F are commonly discussed, though Amazon can change or add codes, so trust the on-screen description over any cheat sheet). What matters is what each event means functionally:
| Adjustment event | What it means | Does this mean you're owed? |
|---|---|---|
| Misplaced / warehouse lost | Amazon can't locate the unit. It was received, then vanished — wrong bin, mislabeled, or genuinely gone. | Yes — unless a later "found" event restores it or a reimbursement is issued. |
| Warehouse damaged | The unit was damaged inside the fulfillment center: handling, storage, equipment. | Yes — FC damage is Amazon's responsibility. Verify a reimbursement exists at full quantity and fair value. |
| Carrier damaged | The unit was damaged in transit by an Amazon partnered carrier or during Amazon-controlled transfers. | Usually — when the carrier movement was under Amazon's control, it's claimable like FC damage. |
| Found / inventory restored | A previously lost unit turned up and was added back to your sellable (or unsellable) count. | No — this cancels a lost event. If you were already reimbursed, Amazon may reverse it. That's normal. |
| Disposed / destroyed | Amazon removed the unit from inventory permanently — sometimes at your request, sometimes not. | Sometimes — if you never authorized it, that's a separate claim. See Disposed Without Consent. |
A "lost" or "damaged" adjustment is only resolved in two ways: a later "found" event that restores the unit, or a reimbursement that pays for it. If neither exists, Amazon still has your money. Match every negative adjustment in the ledger against the Reimbursements report — every unmatched row is a potential claim.
One boundary worth drawing: the Inventory Ledger tracks units after Amazon has received them. Units that disappear between your warehouse and Amazon's check-in are a different animal with a different process — that's covered in our guide to lost inbound shipments.
Amazon Warehouse Damaged Inventory Reimbursement: Automatic vs. Manual
Here's the part that lulls sellers to sleep. Since late 2024, Amazon says it proactively reimburses most inventory lost or damaged in its fulfillment centers. You'll see these appear in your Reimbursements report without ever opening a case, and for many events the system genuinely works.
But "most" is doing a lot of work in that sentence. In practice, the automation fails in three specific ways:
- Missed units. Some lost and damaged events simply never trigger an automatic payment. The adjustment sits in the ledger; the reimbursement never arrives.
- Partial quantities. Six units get damaged; the auto-reimbursement covers four. Unless you count units, the payment looks complete.
- Low valuations. Since March 10, 2025 (US), inventory lost or damaged before a customer order is reimbursed at manufacturing cost — your product cost excluding shipping, duties, and handling — not the sale price. And unless you've uploaded your actual cost data, Amazon substitutes its own estimated manufacturing cost, which is frequently lower than what you really paid. (Items lost or damaged after a customer order are still reimbursed at sale price minus fees.)
The fix for the valuation problem is straightforward: upload your real per-unit costs in Seller Central so Amazon reimburses from your numbers instead of its estimate. The fix for missed units and partial quantities is auditing — checking each auto-reimbursement against the ledger row it supposedly covers:
- Quantity check: does the reimbursed quantity equal the adjusted quantity for that FNSKU on that date?
- Value check: does the per-unit amount match your actual manufacturing cost (or sale price minus fees, if the unit was already ordered)?
- Coverage check: does every negative adjustment have a reimbursement ID at all?
Any "no" is a manual claim — filed through Seller Central's reimbursement claim flow (or a case referencing the exact transaction) — and manual claims are where the deadline bites. For the full rulebook on windows and valuation across every claim type, see Amazon's FBA reimbursement policy explained in plain English.
The 60-Day Window: Why Annual Audits Are Dead
Before October 23, 2024, you had 18 months to catch a missed reimbursement. That era is over. Under the current policy, fulfillment center operations claims — items lost or damaged in an Amazon FC — must be submitted no later than 60 days after the item was reported lost or damaged. The clock starts at the ledger event, not when you notice it.
60 days is the entire lifespan of an FC operations claim. A unit damaged on March 1 is unclaimable by May 1 — no appeal, no exception. If you audit warehouse lost inventory once a quarter, roughly a third of your discrepancies are already expired by the time you find them. A monthly Inventory Ledger review is the only safe cadence. Full breakdown of every deadline in The 60-Day Deadline.
This is also why the auto-reimbursement system is quietly dangerous: it trains you not to look. Every event the automation misses is on a 60-day fuse, and the longer you trust the system unaudited, the more expires unclaimed.
The Monthly Ledger Review, Step by Step
Here's the exact monthly routine. Budget 30–60 minutes depending on catalog size.
Pull the Inventory Ledger
Seller Central → Reports → Fulfillment → Inventory Ledger. Select the "Detailed" view, set the date range to the last 60 days, and download the report so you can filter in a spreadsheet.
Filter to adjustments
Keep only adjustment events and sort by reason. You want the negative events: misplaced/lost, warehouse damaged, carrier damaged, and disposed. Set aside "found" and other restorative events for step 3.
Net out the found events
For each FNSKU, match "found"/restored quantities against earlier "lost" quantities. A loss that was later found is closed. What remains is your open discrepancy list.
Match against the Reimbursements report
Open Reports → Fulfillment → Reimbursements for the same window. Every open discrepancy should have a matching reimbursement — same FNSKU, same quantity. Flag rows with no match, and rows where the quantity or per-unit value falls short of your documented cost.
File claims for the gaps
For each unmatched or short-paid event still inside its 60-day window, file a claim: one issue per case, with the ledger row, transaction ID, and cost documentation attached (format below).
Log and repeat monthly
Track case IDs and outcomes, and put the review on a recurring calendar slot. Miss a month and you're gambling with the deadline.
Evidence and Case Format That Get Approvals
Amazon's investigators process enormous queues. Cases that make the decision easy get approved; cases that make them dig get denied or bounced back with template replies. The format that works:
- One issue per case. Don't bundle five SKUs and three event types into one ticket. A single FNSKU, a single event, a single ask. More cases, faster decisions, cleaner paper trail.
- Lead with the transaction ID. Quote the ledger adjustment's transaction ID, date, fulfillment center, FNSKU, and quantity in the first two lines.
- Attach the ledger row. A screenshot or excerpt of the exact Inventory Ledger line, plus the Reimbursements report showing no matching payment (or a short one).
- Attach cost documentation. A supplier invoice or manufacturing cost record for the SKU. This is what stops Amazon from defaulting to its low estimate.
- State the ask in one sentence. "Please reimburse 4 units of FNSKU X0012ABCDE damaged at ABE8 on 2026-07-14 (transaction ID …), at our documented cost of $7.80/unit."
- Stay factual. No frustration, no essays, no threats. Investigators approve numbers, not narratives.
A Worked Example: One Month, One Ledger, $214 Recovered
The numbers below are illustrative, not a promise — but the pattern is one we see constantly. A kitchenware seller runs the June review on a catalog of 40 SKUs:
- Ledger shows: 14 units warehouse damaged and 6 units misplaced across the month. 2 of the misplaced units later show a "found" event → 18 open discrepancies.
- Reimbursements report shows: auto-reimbursements covering 13 of the 18 units.
- Gap 1 — missed units: 5 units (one damaged event) never triggered a payment. Documented cost $18.40/unit → claim filed for $92.00.
- Gap 2 — low valuation: 9 of the 13 auto-reimbursed units were paid at Amazon's estimated manufacturing cost of $4.10, against a documented actual cost of $7.80. Case filed with the supplier invoice for the $3.70/unit difference → $33.30.
- Gap 3 — partial quantity: a damaged event for 6 units was reimbursed for 4. Two units at $44.50 documented cost → claim filed for $89.00.
Total recovered: $214.30 — from a month where the dashboard said everything was already reimbursed. Scale that across a year and every event type, and you're in the territory industry audits keep finding: 1–3% of annual revenue leaking to unclaimed discrepancies. If you want to put your own number on it, start with How Much Does Amazon Owe Me?
FAQ: Warehouse Lost and Damaged Inventory
Does Amazon automatically reimburse warehouse damaged inventory?
Mostly, yes. Since late 2024 Amazon proactively reimburses most FC lost and damaged events without a case. But the automation misses units, pays partial quantities, and values items at Amazon's own estimated manufacturing cost — which is often lower than your real cost. Every auto-reimbursement needs a quantity check and a value check against your Inventory Ledger and cost records.
How long do I have to file a claim for warehouse lost or damaged inventory?
Under the policy effective October 23, 2024, fulfillment center operations claims must be submitted no later than 60 days after the item was reported lost or damaged. The clock starts at the ledger event, not when you discover it — which is why a monthly review is the only cadence that reliably beats the deadline.
How much will Amazon reimburse for a warehouse damaged unit?
Since March 10, 2025 (US), units lost or damaged before a customer order are reimbursed at manufacturing cost — product cost excluding shipping, duties, and handling — using Amazon's estimate unless you upload your actual costs. Upload real cost data if Amazon's estimate runs low. Units lost or damaged after a customer order are still reimbursed at sale price minus fees.
What if a lost unit is found after Amazon reimburses me?
Amazon can restore the found unit to your inventory and reverse the reimbursement — that's normal and correct. The case you're hunting for is the opposite: a lost or damaged adjustment with no later "found" event and no matching reimbursement ID. That unresolved row is money owed, and it needs a claim inside the 60-day window.
The bottom line: Amazon's FCs will keep breaking and losing a small percentage of everything you send them. The policy makes you whole — but only if someone actually reconciles the inventory ledger adjustments against the payments, every month, before the 60-day window closes. Do it by hand with the routine above, or let a tool do it at unit level and only pay when money comes back.