FC Operations Reimbursements Explained: How Amazon Pays You Back When It Loses or Damages Your Inventory
You shipped in enough inventory to cover the sales you expected this quarter. A few weeks in, you check the numbers, and they don’t add up. Your inventory dropped by more than what you actually sold. It’s the same realization as finding a hole in your pocket. You don’t blame the pants. You just notice that things you meant to hold onto have been spilling out a little at a time, without you ever feeling it happen.
That gap between what you sold and what disappeared isn’t random. It’s how the FC Operations reimbursement claim system works today, after two policy changes reshaped it within about six months of each other in 2024 and 2025. Understanding the mechanism is the difference between feeling that gap every quarter and actually knowing where it goes.
I spent years inside this exact system, first founding the reimbursement service Inventory Detective in 2017, then through its acquisition by Getida in 2019, where I worked until the end of 2025, building claim types and handling Amazon disputes directly. What follows is what I actually watched happen, not a policy summary from the outside.
Table of Contents
- What Counts as an FC Operations Reimbursement Claim
- The History: How Automated Reimbursements Replaced the Old System
- The Sourcing Cost Change
- Why Amazon Might Have Made These Changes
- Damaged Inventory: Two Reasonable but Different Interests
- Tracking and Disputing an FC Operations Reimbursement Claim
- What to Actually Do
What Counts as an FC Operations Reimbursement Claim
If this is the first post of mine you’re reading on FBA reimbursements, here’s the short version. FBA inventory reimbursements are Amazon’s mechanism for compensating you when something happens to your inventory that was Amazon’s responsibility, not yours: a unit lost inside a fulfillment center, damaged in transit, or never properly returned to your account. Amazon offers this because once you ship inventory into its network, you lose direct custody and oversight of it. You can’t inspect a warehouse shelf or watch a forklift the way you could in your own facility, so when something goes wrong on Amazon’s side, the policy exists to make you whole rather than leave you absorbing a cost you had no way to prevent. How that plays out on your account is concrete. Amazon makes you whole either with cash, which shows up in your Reimbursements report, or with replacement inventory, which you can track in the IDR Portal. But the amount, the timing, and how much say you get in disputing it all depend on which of Amazon’s four reimbursement claim types applies.
Amazon’s FBA inventory reimbursement policy covers four distinct claim types, and which one applies depends entirely on where in the fulfillment process your item was misplaced or damaged. Shipment to Amazon claims cover loss or damage in transit to a fulfillment center. Customer returns claims cover items damaged or lost after a customer’s order. Removals claims cover items lost while being shipped back to you. FC Operations claims cover everything in between: an item that arrived at the fulfillment center intact, was registered in your inventory, and was then lost or damaged inside the warehouse before a customer ever ordered it. This post is about that fourth type: FC operations reimbursements.
Amazon’s policy states the underlying commitment plainly:
“If an item you send to us as part of the Fulfillment by Amazon (FBA) service is lost or damaged at a facility or by a carrier operated by Amazon or on behalf of Amazon, we replace that item with a new item of the same product or reimburse you for it.” — Amazon, FBA Inventory Reimbursement Policy
That distinction matters because each claim type has its own claim window, its own documentation requirements, and, as you’ll see in the next two sections, its own reimbursement math. An FC Operations claim is, in plain terms, Amazon telling you: we had it, we lost or broke it, and we owe you something for it.
But “we lost it” isn’t instant, and Amazon’s own reporting tracks that gap explicitly rather than treating it as a single event. In the Inventory Ledger report, an inventory adjustment with reason code “M” marks a unit as misplaced:
“M: Inventory misplaced. A decrease to your inventory level because inventory is missing from a bin location in a fulfillment center.” — Amazon, Inventory Ledger Report
That’s the misplaced state, and on its own, it isn’t a reimbursement. The report only moves a unit into the column Amazon calls “Lost” once it clears a separate bar, which Amazon defines this way:
“Lost: Units that are missing from your inventory in fulfillment centers and that may be eligible for reimbursement or for which you have already been reimbursed.” — Amazon, Inventory Ledger Report
Misplaced and lost are two different stages, not two words for the same thing. Misplaced just means Amazon can’t currently find the unit. Lost means Amazon has decided it’s gone for good, and even then, it’s only “may be eligible” for reimbursement, not guaranteed. A unit can sit as misplaced forever without ever crossing into Lost. That gap is where most of this post lives.
The “owe you something” part is where this post spends most of its time. What Amazon owes you, how it calculates that number, and how much say you have in either, changed substantially in late 2024 and again in early 2025.
The History: How Automated Reimbursements Replaced the Old System
For years, FC Operations reimbursements worked through a claims process you had to initiate yourself. If you suspected a unit had been misplaced or damaged inside a fulfillment center, you checked your Inventory Adjustments report, gathered supporting documentation, and filed a claim. Sellers running larger catalogs often used reimbursement services to comb through that data and find the high volume of historical claims that this manual system made possible.
That changed on November 1, 2024. Amazon announced it would begin proactively reimbursing sellers for items lost or damaged in fulfillment centers, crediting the reimbursement as soon as the loss or damage was reported rather than waiting for a seller to file a claim. The announcement included this line:
“Almost all reimbursement claims related to warehouse lost and damaged and customer returns cases will now be proactively reimbursed.” — Amazon, Update on Reimbursement Automation and Eligibility Window to File Reimbursement Claims
The word doing the real work in that sentence is “almost.” Amazon never defined where the boundary sits, what falls inside automated coverage, and what still requires a manual claim. If your reimbursement doesn’t arrive automatically, the burden is back on you to notice your unit is still just misplaced rather than officially lost, and file manually.
Alongside automation, Amazon also rewrote how much time you get to do that filing. The old policy was generous:
“You must submit your claim no later than 18 months after the date the item was reported lost or damaged in your Inventory Adjustment report. Claims submitted outside of this window are not eligible for reimbursement.” — Amazon, FBA Inventory Reimbursement Policy: Fulfillment Center Operations Claim (archived, January 2022)
Starting October 23, 2024, that window shrank to a fraction of its former size:
“A fulfillment center operations claim for an item that is lost or damaged in the fulfillment center must be submitted no later than 60 days after the item was reported lost or damaged.” — Amazon, Update on Reimbursement Automation and Eligibility Window to File Reimbursement Claims
Eighteen months down to 60 days is about a nine-fold reduction in filing time. For a seller managing a large catalog, that used to mean batching reimbursement research once a quarter or so. Now, a unit that gets misplaced today and doesn’t get automatically reimbursed has to be caught, documented, and filed within two months, or the claim is gone for good. That compressed window is the real cost of automation for the cases automation doesn’t catch, and it’s exactly why the word “almost” carries so much weight. A gap that used to give you a year and a half to find now gives you nine weeks.
What sellers gave up in that trade is concrete. The old manual process doubled as a dispute lever. If you believed Amazon’s initial assessment was wrong, you had a year and a half to build a case and argue it. Now you have 60 days, and that’s only if you catch the miss yourself.
Timing wasn’t the only thing Amazon changed. A few months after this filing window tightened, it also rewrote how it calculates what a lost or damaged unit is worth in the first place.
The Sourcing Cost Change
The second major change affects the size of FC Operations reimbursements, not just their timing. Effective March 31, 2025, Amazon shifted how it values pre-order losses and damage, items lost or damaged before a customer ever bought them, from a sales-price basis to a sourcing-cost basis.
Amazon defines the term precisely:
“‘Sourcing cost’ means your cost to source a product from a manufacturer, wholesaler, reseller, or produce the item if you are the manufacturer. It excludes costs such as shipping, handling, customs duties, or other costs.” — Amazon, FBA Inventory Reimbursement Policy
So if an item costs you ten dollars to manufacture, four dollars to ship internationally, two dollars to clear customs, and another dollar-fifty in inbound fees, the reimbursement covers the ten dollars. Everything else you spent to get that item into Amazon’s warehouse isn’t part of the calculation.
You can submit your own sourcing cost with proof-of-value documentation, like a manufacturer invoice, or Amazon will estimate it for you by evaluating comparable products sold by Amazon, other sellers, and wholesale channels. Either way, the number doesn’t necessarily stay fixed. Amazon can revise a previously approved sourcing cost on its own initiative, a status it labels “Scheduled update”:
“Sourcing cost will update to $10.95 on July 15.” — Amazon, Manage Your Sourcing Cost
You get a window to review and contest the new figure before it takes effect, and you’re limited to two cost-update or reimbursement-amount disputes per FNSKU within any 30 days. The mechanics of actually managing that process, what documentation Amazon accepts, how the bulk-update tool works, when filing a re-evaluation request is worth the time, are enough to fill a post of their own, and we will. This one is staying focused on what changed and why it matters to your bottom line.
None of this is obviously wrong as a methodology. It’s a real question with no single correct answer: does “made whole” mean Amazon replaces what the unit would cost you to source again, or what it was actually worth to you, landed costs included, the moment it disappeared from the warehouse? Amazon picked the narrower definition. That’s a defensible choice, but it’s worth naming as a choice rather than treating it as simply how reimbursement has always worked, because for FC Operations claims specifically, it hasn’t.
Why Amazon Might Have Made These Changes
Amazon hasn’t published a single document laying out its full reasoning for any of this. Some of what follows is in Amazon’s own words, quoted directly. The rest is informed speculation, flagged as such, written as a genuine attempt to understand the incentives at play rather than an attempt to expose them. Both deserve a real hearing, because dismissing Amazon’s side as obviously self-serving misses how coherent the logic actually is from the inside. It’s the same buyer-first hierarchy that explains most of Amazon’s seller-facing decisions, including how Amazon designed FC operations reimbursements.
Why automate at all? This is the one place Amazon gave a partial answer in its own words:
“We’re constantly refining our operations and processes to prevent products from being lost or damaged and having to be reimbursed. For cases where reimbursement is necessary, we’re focused on ensuring timely compensation. We now offer automatic reimbursements for items lost in our fulfillment centers, saving you time, and eliminating the need for you to submit a claim to receive reimbursement.” — Amazon, Update on Reimbursement Automation and Eligibility Window to File Reimbursement Claims
Read generously, that’s a real efficiency gain for the large majority of cases. Amazon’s fulfillment network processes an enormous volume of inventory movement every day, and a system that requires a human to review documentation for every reported loss doesn’t scale to that volume without either a large adjudication team or long processing delays. Proactive reimbursement removes a manual review step for most sellers, most of the time. Amazon’s own framing, “saving you time,” holds up for the cases automation actually catches.
Why “almost” instead of “all”? Amazon never explained this, so this part is speculation. Some defects are probably ambiguous enough, with multiple possible causes, conflicting report data, and a unit that could plausibly still turn up, that an automated system can’t confidently resolve them without a human reviewing the case. Keeping a manual path open for that unresolved fraction is a reasonable design choice on its own. What’s harder to defend, and Amazon hasn’t tried to, is leaving that fraction permanently undefined instead of telling sellers roughly how big it is or what kind of defect tends to fall into it.
Why sourcing cost instead of sales price? Amazon did publish a stated rationale for this one:
“We’re updating our Fulfillment by Amazon (FBA) inventory reimbursement policy to help provide you greater transparency and more predictability in how reimbursements are calculated for items that are lost or damaged before a customer order. This will help drive a more consistent approach that works as we support sellers with supply chain services across their sales channels.” — Amazon, Changes to Program Policies: Update to the FBA Inventory Reimbursement Policy
“Transparency,” “predictability,” and “consistency” are real benefits, and a sourcing-cost basis is genuinely easier to audit than a sales-price basis that moves with every price change, promotion, and marketplace a seller lists on. It’s also, not incidentally, a cheaper basis for Amazon to sustain at scale. A reimbursement tied to sales price varies with each seller’s margin and pricing strategy, which makes Amazon’s total liability harder to predict, and it arguably pays sellers for value Amazon itself never captured, such as Amazon’s own fees or the seller’s markup, on a unit that never reached a customer. Both things can be true at once. The stated rationale doesn’t have to be false for the cost savings to also be real.
Damaged Inventory: Two Reasonable but Different Interests
When Amazon damages a unit and determines the damage is its own fault, the inventory reimbursement policy gives Amazon ownership of that unit by default. Amazon’s own language draws the fault line clearly:
“Amazon-fault damages are a result of transit or handling issues and include inventory dispositions such as ‘carrier damaged’ and reconciled ‘warehouse damaged.'” — Amazon, FBA Damaged Inventory Ownership
Once a unit is classified as Amazon-fault, Amazon can resell it through Amazon Resale (formerly Amazon Warehouse), Liquidations, or another recovery channel.
From a seller’s side, this is often unwelcome even with the reimbursement in hand. A damaged-but-still-recoverable unit showing up at a discount on Amazon Resale can undercut your own listing, and you have no say in how it’s graded, priced, or presented once Amazon takes ownership. For brands that care about price consistency or how a product looks when it reaches a customer, losing control of that unit is a real cost that the reimbursement check doesn’t cover.
Amazon’s side of this is also worth a fair hearing, even though Amazon hasn’t stated it directly here, so take this as informed speculation rather than confirmed policy. Warehousing damaged units indefinitely so each seller can individually decide what to do with their own damaged stock ties up fulfillment center space and throughput that Amazon would rather allocate to sellable inventory. Liquidating or reselling damaged units quickly, through Amazon Resale or Liquidations, converts a dead asset into at least partial recovery and keeps the warehouse moving. From a pure operations standpoint, that’s a reasonable default, even though it’s a default plenty of sellers would not choose for their own inventory if given the option, which, since the FBA Damaged Inventory Ownership program launched, they now are.
Amazon’s answer to this tension is the FBA Damaged Inventory Ownership program. Enroll eligible ASINs, and you take ownership of Amazon-fault damaged units instead of Amazon. Those units get marked “defective,” return to your unfulfillable inventory, and you decide what happens to them: remove them, sell them through FBA Grade and Resell, or dispose of them yourself. The tradeoff is real, and the program states it plainly:
“By participating in this program, you agree to be the damage-fault owner for enrolled damaged inventory; hence you will not be reimbursed for this inventory.” — Amazon, FBA Damaged Inventory Ownership
You’re trading the cash payout for control over the unit. Whether that trade is worth it depends on how much you’d make selling that unit yourself versus what Amazon would have reimbursed you for it. That tradeoff is one of the clearest places where FC operations reimbursements put a real decision in your hands instead of Amazon’s.
Tracking and Disputing an FC Operations Reimbursement Claim
The Inventory Defect and Reimbursement (IDR) Portal is the central place to track FC operations reimbursements. Amazon describes its purpose directly:
“This portal provides you with visibility into all defect statuses, including defects eligible for claims, defects under review (where no action is required from you), and resolved defects with the reason for our decision.” — Amazon, Inventory Defect and Reimbursement (IDR) Portal
It organizes everything into three tabs: Eligible for Claim, where defects need your input before Amazon can act; In Progress, where Amazon is already reviewing a defect and no action is needed from you; and Resolved, where you can see what happened and why, including whether the resolution was a cash reimbursement, a reconciliation, or a denial.
Reimbursements can also be reversed. Amazon’s policy lays out exactly when:
“Reversed reimbursements happen in the following situations: (1) when you receive replacement inventory units of the same product instead of the reimbursement, or (2) when the original defect has been fixed after you were reimbursed for it.” — Amazon, Reversed Reimbursement
In plain terms, a reversal happens in one of two ways. Either Amazon finds your missing unit and ships you a replacement instead of keeping the cash reimbursement in place, or Amazon later realizes the unit wasn’t actually lost. That second case usually means a “Warehouse Lost” defect gets matched to inventory Amazon finds it had all along. Once that happens, the reimbursement built on the original “lost” classification gets undone.
Reversed reimbursements show up in your Reimbursements report under that label, with a reference back to the original reimbursement ID. If you see a reversal but no inventory was restored to your account, check the original transaction before assuming it’s a mistake.
What to Actually Do
A few practical takeaways follow directly from how FC operations reimbursements actually work.
Check the IDR Portal regularly instead of assuming you’re covered just because Amazon says “almost all” cases are handled automatically. Automation handles most cases, but you won’t know if yours fell outside it unless you look, and you now have 60 days instead of 18 months to act once you do.
Reimbursement services still have a real job here, not because Amazon is acting in bad faith, but because “almost all” is an undefined fraction, not a hard number. I saw this gap from the inside during my own years in the reimbursement-services industry, and it’s real. I watched sellers fall into it regularly. If you’d rather not monitor the portal yourself, that’s a legitimate reason to use one, not a sign the relationship with Amazon has broken down.
Decide deliberately whether the Damaged Inventory Ownership opt-out is worth it for your catalog. It makes the most sense for products where brand presentation matters more than the reimbursement amount, and less sense for low-margin or low-differentiation products where the cash is the better trade.
Treat your sourcing cost on the Manage Your Sourcing Cost page as something to actively maintain, not a number Amazon sets once and you forget about. We’ll cover the full mechanics of managing and disputing it in a dedicated post.
None of this requires assuming bad faith on Amazon’s part or the seller’s. It requires knowing how the mechanism works, and knowing exactly where its edges are vague enough that you still have to watch it yourself.
Sources
Amazon, FBA Inventory Reimbursement Policy https://sellercentral.amazon.com/gp/help/G200213130
Amazon, Inventory Ledger Report https://sellercentral.amazon.com/help/hub/reference/external/G4FKT5KQWFFJ7LDN
Amazon, FBA Inventory Reimbursement Policy: Fulfillment Center Operations Claim https://sellercentral.amazon.com/gp/help/external/GGEV4254LJJ9BAEG
Amazon, FBA Inventory Reimbursement Policy: Fulfillment Center Operations Claim (archived pre-automation version, 18-month claim window) https://web.archive.org/web/20220125033739/https://sellercentral.amazon.com/gp/help/external/GGEV4254LJJ9BAEG
Amazon, Update on Reimbursement Automation and Eligibility Window to File Reimbursement Claims https://sellercentral.amazon.com/seller-forums/discussions/t/81c3235d-4c44-47ba-96c5-883cecab3244
Amazon, Changes to Program Policies: Update to the FBA Inventory Reimbursement Policy https://sellercentral.amazon.com/seller-forums/discussions/t/da761b17-58cc-4734-98d2-5608e1d11419
Seller Central, Manage Your Sourcing Cost https://sellercentral.amazon.com/inventory-reimbursement/cost-management
Seller Central, Inventory Defect and Reimbursement (IDR) Portal https://sellercentral.amazon.com/inventory-reimbursement/overview
Seller Central, FBA Damaged Inventory Ownership https://sellercentral.amazon.com/help/hub/reference/G9MAM9ELJTSSNYS5
Seller Central, Reversed Reimbursement https://sellercentral.amazon.com/help/hub/reference/external/GL9ZDED52WXZUMFD
