Table of Contents
- Damaged, lost or defective: why the label decides the claim
- The damage types Amazon reimburses
- Where to find damaged units in Seller Central
- Proving the damage was not your fault
- Mistakes sellers make with damage claims
- When to escalate to a reconciliation service
Damaged, lost or defective: why the label decides the claim
Damaged inventory is one of the most misunderstood reimbursement categories because the word "damaged" hides several very different events. A unit can be damaged inside the fulfillment center, damaged in transit by Amazon's carrier, returned damaged by a customer, or marked defective for a reason that has nothing to do with physical condition. Each of these carries a different disposition code, and that code — not your judgment — determines whether Amazon owes you anything.
This matters because sellers tend to react to the visible number: units that left sellable inventory. But the recoverable cases are a subset defined by who caused the damage and whether a credit was already issued. The job is not to claim every damaged unit. It is to isolate the damaged units where Amazon was responsible and no reimbursement has appeared.
The damage types Amazon reimburses
Reimbursable damage almost always traces back to a unit that was harmed while in Amazon's custody and was never offset by a credit. The clearest cases fall into a few buckets.
- Warehouse-damaged units. Inventory damaged during storage, picking, packing or movement inside the fulfillment center. Because the unit was in Amazon's care, the lost sellable value is its responsibility.
- Carrier-damaged units. Inventory damaged in transit between fulfillment centers or during outbound handling by Amazon's carrier. Same principle: damage in Amazon's custody is Amazon's liability.
- Disposed or removed without credit. A damaged unit that was disposed of or removed but never reimbursed at the appropriate value. The disposal is recorded, but the matching credit is missing.
- Damaged then reimbursed below value. A credit exists, but it was issued at an amount lower than the correct cost basis, which turns a closed case into an underpayment case.
Customer-damaged returns sit in a related but separate lane — we cover those in detail in the guide to FBA customer return reimbursements. Keeping the two apart is what prevents both double-filing and missed claims.
Where to find damaged units in Seller Central
Damage rarely announces itself. It surfaces as adjustment codes and disposition labels buried in inventory reporting, which is exactly why it goes unclaimed. Reviewing the right reports together is what makes the pattern visible.
| Report | What it tells you |
|---|---|
| Inventory adjustments / ledger | Which units were marked warehouse- or carrier-damaged, with date and reason code |
| Reimbursements report | Whether a damaged unit was already credited, and at what amount |
| Removal / disposal reports | Whether a damaged unit was disposed of or removed without a matching reimbursement |
| Inventory event detail | Whether the unit re-entered sellable stock, was found, or remains unresolved |
The case you are looking for is a damage adjustment with no offsetting reimbursement, or a reimbursement amount that falls short of the unit's correct value. Both are clean, defensible claims once the event trail is lined up.
Proving the damage was not your fault
Amazon approves damage claims when responsibility clearly sits with its operation, and it declines vague ones. The strength of the claim comes from the disposition code and the timing, not from a description of the problem.
- Confirm the disposition. Establish that the unit is flagged as warehouse- or carrier-damaged rather than customer-damaged or defective.
- Check for an existing credit. Review the reimbursement ledger so you do not re-file a case Amazon already settled.
- Validate the value. Where a credit exists, confirm the amount matches the correct cost basis under current policy.
- Document the cost basis. Keep the manufacturing or purchase cost evidence the 2025 rules require, because under-documented claims are reimbursed at the lower figure or denied.
Mistakes sellers make with damage claims
Damage claims are lost in the reading, not the filing. The units are recorded; the problem is that nobody reconciles them against the reimbursement ledger in time.
- Treating all damaged units as one bucket. Only certain dispositions are reimbursable, so a blanket claim invites denials that weaken future cases.
- Assuming a disposal means a reimbursement. Disposal and credit are separate events; one can happen without the other.
- Ignoring underpaid credits. A credit that exists but is too low is still money owed, and sellers stop the moment they see any reimbursement at all.
- Reviewing damage in isolation. The same ASINs often leak value through lost inventory and returns too, so a combined audit recovers far more than a damage-only pass.
When to escalate to a reconciliation service
At low volume, a careful monthly read of the adjustment ledger can keep you whole. As your catalog and unit throughput grow, separating reimbursable damage from non-reimbursable damage — and doing it inside a 60-day window — becomes specialist work that competes with everything else on your plate.
Damaged inventory is one component of a full Amazon FBA reconciliation workflow that also covers lost units, returns and fee errors. For the complete picture, start with the Amazon FBA reimbursement guide or the current 2026 reimbursement policy summary. For an account-specific answer, request a free audit through our contact page.
Damaged Units Quietly Draining Margin?
We separate warehouse and carrier damage from the rest, check every credit against the correct value, and file the eligible claims before the window closes.
