Does Amazon reimburse for lost or damaged inventory?

What Amazon actually reimburses (and what it doesn't)

Amazon's reimbursement obligation is tied to fault and to the unit being sellable. If Amazon loses or damages a unit inside its own network, or loses it during the fulfillment leg of a customer return, that is on Amazon. If a customer is refunded but never returns the item (or returns a different, damaged, or empty item), that can also trigger a reimbursement or chargeback to the customer rather than to you. The common thread is that the loss happened while Amazon controlled the inventory or the transaction.

Just as important is what is not Amazon's fault. Inventory that arrives at the fulfillment center short because the carrier you chose lost it, units damaged by defective packaging you supplied, or expired and unsellable goods are generally not reimbursable to you. Knowing the boundary matters because it's the difference between a valid claim and a denied one, and filing denied claims repeatedly is a good way to get your claim privileges throttled.

Storage cost at Amazon sits on the same side of the line: it's yours to absorb, not a loss to claim. Units that sit long enough to trigger Amazon long term storage fees are an inventory-planning problem, and the fix is a removal order or liquidation before the charges compound, not a case.

• •Units lost or damaged inside an Amazon fulfillment center
• •Inventory lost during inbound receiving once Amazon has checked it in
• •Lost or damaged items during the carrier leg of a customer return
• •Customer-refunded orders where the item is never returned within the policy window
• •Disposed or destroyed inventory removed without your authorization

How Amazon now values a lost unit: the 2025 change

The single biggest recent shift is in how Amazon prices the inventory it owes you for. Historically, Amazon estimated a unit's value from its own data on sale price, which could land high or low and was hard to predict. Beginning in 2025, Amazon moved FBA inventory reimbursements to a manufacturing-cost (sourcing-cost) basis. It reimburses based on what you paid to source or make the unit, not an estimated retail price.

That change makes accurate cost data essential. If Amazon doesn't have a cost on file for a SKU, it will apply its own estimate, and that estimate may not reflect what you actually paid: landed cost including freight, duties, and prep. Sellers who keep a clean per-SKU cost basis are in a position to confirm Amazon used the right number; sellers who don't are accepting whatever Amazon decides. Verify the current valuation rules and your stored costs in Seller Central, because Amazon's reimbursement policy language continues to evolve.

There's a wrinkle if you buy the same SKU at different prices across purchase orders: you need one defensible cost per unit to file. Of the standard inventory accounting methods, the weighted average cost of inventory (total cost of the units on hand divided by the quantity on hand) is where most sellers land, because FIFO layers are painful to reconcile against a pooled FBA network where units from three different shipments sit in the same bin. Pick a method, apply it consistently, and make sure the cost you give Amazon is the same cost sitting in your books.

Notice the asymmetry this creates. Amazon now pays you cost, not retail, so a reimbursement never makes you whole on lost profit; it only returns your capital. That's one more reason the volume of small leaks matters. You aren't recovering upside, you're recovering your own money, and every unclaimed case is capital you already spent evaporating quietly.

The claim window, auto-reimbursements, and why you're underpaid

Amazon auto-detects and reimburses a large share of discrepancies without you lifting a finger, and it has also shortened the time you have to file the cases it misses. Recent policy changes compressed claim windows. For example, fulfillment-center loss and damage cases now run on a much tighter timeline than the older multi-month windows (commonly cited around 60 days for FC cases; verify the current window for each case type in Seller Central, as Amazon sets different deadlines for inbound, FC, removal, and customer-return cases). Once a window closes, an unfiled claim is gone.

The deeper issue is that auto-reimbursements are often under-paid rather than absent. Amazon may reimburse fewer units than were actually lost, value them with an estimate instead of your real cost, or net a reversal against a later found unit and never surface the difference. Because the credit shows up buried in your settlement as an adjustment, it looks like the matter is handled, when in fact you were partially paid. Catching this requires reconciling Amazon's inventory adjustments and reimbursements against your own ledger, line by line, which is the work most sellers never do by hand.

• •Many lost/damaged cases are auto-reimbursed by Amazon's systems
• •Auto-credits are frequently underpaid: fewer units or a lower value than owed
• •Claim windows have shortened; FC cases commonly cited near 60 days; verify current
• •Different case types (inbound, FC, removal, returns) have different deadlines
• •An expired window means the money is permanently forfeited

A worked example: what the leak looks like in dollars

Hypothetical numbers, but a realistic shape. Say you move 3,000 FBA units a month at an average landed cost of $8. Suppose warehouse handling loses or damages a fraction of a percent of them, call it 10 units a month, and a handful of refunded orders each month are never returned, say 6 units. That's 16 units, or $128 of your capital going missing monthly. Amazon's automation catches, say, 10 of the 16 and reimburses them, but values 3 of those at a $5 estimate because your cost data wasn't on file. You were owed $128; you received $71.

None of those individual numbers would ever catch your eye. A $9 adjustment here, a missing unit there, spread across dozens of settlement lines. But in this example the gap compounds to roughly $680 a year, and it scales with volume: run 30,000 units a month with the same rates and it's a four-figure annual leak. That's the core insight about FBA reimbursements. It's rarely one big theft; it's a steady drip that's invisible without reconciliation and completely recoverable with it.

This is also a cost of custody that sellers weighing amazon fba vs dropshipping never put in the model. A dropshipper never hands stock to anyone, so there's nothing sitting in a warehouse to lose. An FBA seller carries this leak permanently, which is fine as long as you're recovering it.

Where the evidence lives: the reports that prove a claim

Every reimbursement case is won or lost on records, and Amazon publishes the records you need. The Inventory Ledger report is the backbone: it tracks every unit's movements (received, sold, returned, lost, found, damaged, disposed) and is where discrepancies first become visible. The inventory adjustments data shows Amazon's own loss and damage events with reason codes. The reimbursements report lists what Amazon has already paid, which you need so you don't file duplicates. And for return cases, you pair the refund data with return receipts to find customers who were refunded but never sent the item back.

The workflow is a three-way match: what your records say Amazon should be holding, what Amazon's ledger says happened to each unit, and what the reimbursement report says you were paid for. Any unit that left the ledger through a loss or damage event without a matching reimbursement at the right value is a case. File it as a case with Seller Support inside Seller Central, report excerpts attached, before that case type's window closes. Documentation quality decides these; a claim that cites specific ledger lines gets paid, and a vague "I think units are missing" gets denied.

All of this assumes you run perpetual inventory. Under a perpetual inventory system, accounting records update on every receipt, sale, return, and adjustment, so your counts and Amazon's can be compared on any given day. The periodic method only counts stock at the end of a period, which tells you the total shrank without telling you which units went where or when. Periodic vs perpetual inventory accounting usually gets framed as a tax or reporting choice. For FBA it's a recovery choice, because a periodic count can't produce the unit-level trail a claim has to cite.

How to actually recover what you're owed

Recovery comes down to reconciliation. You compare what you sent to Amazon and what Amazon reports as on-hand, in-transit, lost, found, damaged, and reimbursed, then flag every gap. For inbound shortages you need your shipment records; for FC losses you need Amazon's inventory adjustment and ledger reports; for returns you need to confirm refunded units were either returned or reimbursed. Each discrepancy becomes a documented case filed before its specific window closes, with the evidence Amazon requires attached.

Doing this manually across thousands of SKUs and continuous adjustments is impractical, which is why automated reconciliation exists. BeanHawk continuously cross-checks Amazon's inventory and settlement data against your own records, surfaces both missing and underpaid reimbursements, and packages each into a filable case. If you want to see what you're currently owed without committing to anything, start with a free FBA reimbursement audit and let the numbers make the case.

Two habits make every dollar of this easier to capture: keep an accurate per-SKU landed cost so reimbursements are valued correctly, and check your discrepancies on a cadence tighter than the shortest claim window so nothing expires unfiled. The money Amazon owes you is real, but it is a use-it-or-lose-it asset.

DIY, software, or a service: picking your recovery approach

You have three honest options. Doing it yourself costs nothing but time, and at low volume (a few hundred units a month, a handful of SKUs) it's genuinely viable: pull the ledger monthly, match it against reimbursements, file what's missing. The trade-off is discipline; miss two months and short windows mean some of that money is gone for good.

Amazon reimbursement software automates the detection: it monitors the ledger continuously, flags underpaid and unfiled cases, and keeps you inside every deadline. An amazon reimbursement service goes further and files on your behalf, typically charging a percentage of whatever it recovers. The percentage model is worth scrutinizing: paying a quarter or more of recovered funds is fine for a one-time historical cleanup, but expensive as a permanent arrangement when software can surface the same cases for a flat cost. Also confirm any fba reimbursement service complies with Amazon's rules on claim filing, since aggressive third-party behavior lands on your account, not theirs.

Whichever route you take, connect it to your books. Reimbursements are income your amazon fba accounting needs to categorize correctly (they're recovered inventory cost, not sales revenue), and if you keep books in QuickBooks, Amazon FBA credits should land in a dedicated reimbursements account rather than drifting into sales. A good accounting setup is also where your per-SKU landed costs live, which, as covered above, now determines what each claim is worth. Sellers who treat recovery and accounting as one system stop leaking from both ends.