DEV Community

Gio Rich
Gio Rich

Posted on

How to find FBA inventory Amazon lost (and claim it before the window closes)

If you sell through Fulfillment by Amazon, some of your inventory will get lost or damaged inside Amazon's warehouses. That's normal at their scale. What surprises most sellers is that Amazon doesn't always pay for it automatically, and the window to ask is short, roughly 60 days for most warehouse losses.

This guide walks through how to find those units yourself using two reports you already have in Seller Central. No tools or spreadsheets beyond Excel or Google Sheets are needed.

Step 1: Download the Inventory Ledger

In Seller Central, go to Reports > Fulfillment, then open Inventory Ledger (on some accounts it sits under the Inventory section of the left menu).

Choose the Detailed View, set the date range to the last 90 days, and request the report. Download it as a CSV once it's ready.

The Detailed View lists every event that touched your inventory: receipts, customer shipments, returns, transfers between warehouses, and adjustments. The adjustments are the part you care about.

Step 2: Filter to adjustments

Open the file and filter the Event Type column to Adjustments. Each adjustment row has a Reason code that tells you why Amazon changed your count.

The three that matter most:

  • M – the warehouse misplaced the unit. Your count goes down.
  • F – the warehouse found a unit it had misplaced. Your count goes back up.
  • E and other damage codes – the unit was damaged at an Amazon fulfillment center.

Add a column for the absolute quantity and sort by FNSKU (or ASIN) so every product's events are grouped together.

Step 3: Net out misplaced vs. found

A misplaced unit isn't a loss yet. Amazon often finds it a few days or weeks later, and an F row cancels the M row.

For each FNSKU, add up the quantity on its M rows and its F rows. A quick pivot table does this in seconds:

  • Rows: FNSKU
  • Columns: Reason
  • Values: sum of Quantity

If an FNSKU shows more units misplaced than found, and the oldest unmatched M row is more than a couple of weeks old, those units are likely lost for good. Write down the FNSKU, the number of units, and the date of the M event.

Damage rows (E and similar) don't get "found". Each one is a candidate on its own.

Step 4: Check what Amazon already paid

Before you file anything, make sure Amazon hasn't already reimbursed you. Duplicate claims waste your time and can annoy the support team.

Go to Reports > Fulfillment > Reimbursements (under the Payments section). Download the same 90-day range.

This report lists every reimbursement Amazon has issued, with the FNSKU, a reason, the quantity reimbursed in cash, and the quantity reimbursed as replacement inventory.

For each FNSKU on your list from Step 3, subtract the units that already show up in the Reimbursements report for a lost or damaged warehouse reason. Whatever is left is what you're still owed.

Step 5: Put a dollar value on it

Amazon reimburses based on its estimate of the item's value, which is usually tied to your sale price minus fees, not your cost. A rough way to estimate it:

  • Take the item's recent average sale price.
  • Subtract the referral fee and the FBA fulfillment fee.

Multiply by the units still owed. This tells you which claims are worth your time. A seller with a few hundred SKUs commonly finds a handful of products with several units each, which adds up quickly on higher-priced items.

Step 6: File before the window closes

Sort your remaining list by the date of the M or damage event, oldest first. The oldest ones are closest to aging out, so they go first.

To file, go to Help > Get support in Seller Central, choose the FBA option for lost or damaged inventory, and enter the FNSKU, the quantity, and the Inventory Ledger date. Keep it short and factual. Paste the relevant ledger rows if the form allows it.

Amazon will either reimburse, show you a reimbursement you missed, or say the unit was found. Note the case ID and the result for each one so you don't file twice.

The same check works for two other leaks

Once you're comfortable with these reports, the same approach finds two other common gaps:

  • Inbound shipment shortages. Compare the units you shipped on each FBA shipment against the units Amazon received. If a shipment is short and no reimbursement shows up after it closes, it's worth asking about.
  • Refunds with no return. If a customer was refunded but the item never came back to the warehouse, the Customer Returns report won't show it. Match refunded orders against that report, and anything missing after about 45 days is worth a claim.

Make it a habit

Losses keep happening, so this isn't a one-time job. Running the check once a month keeps every claim well inside the window and takes about an hour after the first time.

If you'd rather not do it yourself, I run this audit for FBA sellers for free and file the claims for 20% of whatever Amazon pays, with nothing upfront. Email grich1356@gmail.com.

Written with AI assistance.

Top comments (0)