Units go missing inside Amazon's warehouses: lost, damaged, disposed of, or received short of what you sent. Amazon reimburses many of them automatically, but not all, and it never tells you which ones it missed. The Recovery screen shows the candidates in one place so you can check them in Seller Central and claim what you are owed.
Every row is a candidate, not a proven debt. The evidence is Amazon's own: events its inventory ledger marks as unreconciled with no reimbursement matched, and shipments it closed with fewer units than you sent. SeroBooks does not put a dollar value on them: the ledger reports quantities only, and a value worked out from your own cost price would never match what Amazon pays.
How to open it
Amazon ▸ Recovery.
The screen is not filtered by period: a candidate stays until Amazon reconciles or reimburses it. Amazon's inventory ledger is fetched once a day.
The summary tiles
| Tile | Meaning |
|---|---|
| Units to claim for | Units across both sources (red when above zero; nothing outstanding otherwise). |
| Unreconciled events | Ledger events, with the units they involve. |
| Shipments short | Closed inbound shipments received short, with the missing units. |
| Oldest event | Date of the oldest unreconciled event and how many days ago it was (red when over a year). |
Below the tiles, a banner either explains that these are candidates and that the oldest rows are the most urgent (Amazon limits how far back a claim can be raised), or reads Nothing outstanding… when every event is reconciled or reimbursed and no shipment closed short.
Units Amazon has not reconciled
Amazon publishes an inventory ledger of every movement inside its warehouses. These are the rows it flags as unreconciled, oldest first:
| Column | Meaning |
|---|---|
| Date | When the event happened. |
| Age | Days since (red over 365). Age is what decides urgency. |
| SKU / product | The SKU (or ASIN), with Amazon's title beneath. |
| Event | Amazon's event type, for example an adjustment. |
| Disposition | Amazon's own word for the unit's state or the reason, shown exactly as Amazon wrote it. |
| FC | The fulfilment centre. |
| Units owed | The unreconciled quantity (red). |
Up to 200 events are listed. Double-click a row to open the product's sales history; if the SKU is not mapped to a SeroBooks item you are told to map it on Products.
Shipments received short of what was sent
Inbound shipments Amazon has closed with fewer units received than you sent, largest shortfall first (up to 100):
| Column | Meaning |
|---|---|
| Shipment | Amazon's shipment id. |
| To | Destination fulfilment centre. |
| Sent, Received | Units you sent and units Amazon booked in. |
| Missing | The difference (red). |
Double-click a row to see which SKUs went short. A claim has to name them; see Inbound shipments.
Working the list, step by step
- Open Amazon ▸ Recovery and read the Oldest event tile: anything over a year old is shown in red and is the most urgent.
- In Units Amazon has not reconciled, sort by Age (oldest first is the default) or by Units owed to find the largest.
- Note the Date, SKU, FC and Units owed of the row, or use Export to keep the list.
- In Shipments received short of what was sent, double-click each shipment to see which SKUs went short.
- Check each candidate in Seller Central before you claim, as described below.
Claiming a reimbursement
SeroBooks does not file inventory claims for you: Amazon provides no way for software to open a Seller Support case.
- Start with the oldest rows.
- Look the event or shipment up in Seller Central and check it has not already been reimbursed. A duplicate claim costs more credibility with Seller Support than it recovers.
- Open a case in Seller Central, quoting the SKU, date, fulfilment centre and quantity (or the shipment id and the missing SKUs).
- When Amazon pays, the reimbursement arrives in a settlement. It posts to Inventory Adjustment (Shrinkage), offsetting the loss, and appears under Reimbursements on Returns. The candidate drops off this list once Amazon's ledger matches it.
For customer refunds where the item was never returned, use the claims list on Returns, which writes the case for you.
Common problems
"Recovery tracking is not installed on this server yet." The screen's data is not available for your company yet.
A row I already claimed is still listed. It stays until Amazon's own ledger shows it reconciled or reimbursed.