FBA damage rows need to be separated by where the damage occurred and what happened afterward. A fulfillment-center damage event, a carrier event, and a customer return can follow different reimbursement paths. Reconcile the condition code and later adjustment first, then use the current Amazon policy to decide whether the row is open, too early, expired, or already resolved.
A reimbursement export can make two unlike events look similar because both end with an inventory adjustment. The Inventory Ledger and Returns reports provide the timeline around that adjustment. If the unit later returns to sellable inventory or receives a credit, the original damage line does not remain an open claim.
What the record changes
Keep the event identifier, SKU, condition, quantity, date, and any linked reimbursement in one row. If the physical condition matters, preserve the seller's own photos and receiving records, but never describe evidence that is not attached. The case wording should identify the discrepancy in the seller's reports and ask Amazon to review it under the cited policy version.
- Amazon's reimbursement process uses separate claim types and eligibility rules for different inventory events.
- Sellers in the research record describe units classified as customer damaged even when the shipment history raised questions, which is why the return timeline matters.
- Amazon changes claim types and windows, so every delivered list records the policy version and date used for the classification.
How to use this answer
A reimbursement check compares events in the Inventory Ledger, Reimbursements, Returns, and Fee Preview exports. The same unit or fee can appear in more than one report, so the reports have to be reconciled before a claim is counted. Each surviving line receives a claim type, value at Amazon's policy basis, current window state, case wording, and a reference to the policy version used.
- Export fresh reports from Seller Central and keep the marketplace and report date with each file.
- Match inventory, return, reimbursement, and fee events before treating any single row as an open claim.
- File the oldest open lines first, but leave out rows that are too early, already reimbursed, expired, or unsupported.
Where the service stops
You download the reports and file every case yourself. Reality Contact, LLC never logs into Seller Central, keeps credentials, files a case, or contacts Amazon for you. A listed event only appears claimable under the policy version cited on the delivery date. Amazon decides whether it pays. This is not legal advice, tax advice, or accounting advice.
Sources: Amazon reimbursement eligibility-window update; Seller discussion of damage classification; Amazon Seller Central forums.