FBA reimbursement for lost inventory: a seller's checklist

TL;DRFBA reimbursement for lost inventory is Amazon's obligation to compensate a seller when Amazon loses, misplaces, or destroys units held in its fulfillment network – including Amazon DE warehouses. The reimbursement window is finite, documentation requirements are strict, and a poorly filed or untimely claim will be denied on procedural grounds even when the underlying loss is clear. This checklist sets out each phase of the claim process so you can move immediately and protect what you are owed.

Amazon's fulfillment network handles millions of units across dozens of European warehouses. When a unit goes missing – whether in transit from a seller's shipment, during storage, or in the outbound fulfillment cycle – Amazon's own records often show the discrepancy. The problem is that those records do not automatically trigger a payment. The seller has to claim it, in the right way, within the right window, with the right evidence.

In matters we handle, the gap between what a seller is actually owed and what they eventually recover is almost always a documentation and timing problem, not a question of whether the loss happened. Amazon DE sellers face an additional layer of complexity: multi-country inventory movements, VAT-linked record-keeping requirements, and a Seller Central interface that reports in EUR but draws on inventory data that crosses several national warehouses. That combination creates real exposure for sellers who do not track the claim lifecycle carefully.

Phase 1: Understand what Amazon DE actually owes you

Before filing anything, you need a clear picture of the categories of loss Amazon is liable to reimburse – because conflating them leads to claims filed under the wrong mechanism, which get rejected.

FBA reimbursement for lost inventory is not a single product. It is a set of distinct obligations that arise at different points in the fulfillment cycle:

Inbound shipment discrepancies – units you shipped to a fulfillment center that were not received into inventory. Amazon's receiving scan is the key record here.
Lost in warehouse – units that were received, entered inventory, but disappeared from the warehouse count without being sold, returned, removed, or disposed of.
Damaged in warehouse – units damaged by Amazon during storage or handling. (For the full process on damaged goods, see our guide on handling FBA reimbursement for damaged inventory step by step.)
Lost or damaged in outbound – units that left the warehouse in the fulfillment process but were not delivered, and where Amazon accepted carrier liability.
Customer returns not credited – units the customer returned, Amazon received back, but which were not credited to your balance or placed back into sellable inventory.

Each category has its own reconciliation report, its own evidence standard, and its own claim window. Running all five against your inventory records before you open a single case is the foundation of an effective claim process. If you skip this step and file reactively – opening cases only when you notice a number looks off – you will miss losses that are real but not visible without a full reconciliation.

For Amazon DE specifically, confirm that your inventory report data reflects the correct marketplace. Multi-country inventory (MCI) arrangements mean that a unit shipped to a German warehouse may be stored temporarily in Poland or the Czech Republic. The reimbursement obligation runs from the marketplace where the seller's account is registered, but the underlying data trail crosses borders. Pull your reports at the account level, not the national-marketplace level, before you calculate the claim.

What documentation must you have before you file?

Documentation is the single point at which most self-managed claims fail. Amazon's reimbursement team will not reconstruct the evidence trail for you; they will reject on the basis of what is in the case. Gather each of the following before you file a case or open a research request:

Inventory Adjustment report – download and retain for the full period you are claiming. Filter for reason codes that indicate a loss: "lost," "damaged," "disposed," "found," "warehouse transfer."
Reconciliation report for each inbound shipment – the shipment-level reconciliation shows received vs. expected quantities. Any shortfall that has not been reconciled within the standard receiving window is a potential inbound reimbursement claim.
FBA Returns report – cross-reference every customer return against your credit ledger to identify returns received by Amazon but not credited.
Carrier proof of delivery for inbound shipments – essential for inbound discrepancy claims. Without POD showing the quantity tendered to Amazon, Amazon can dispute the count.
Original purchase invoices or cost-of-goods records – Amazon's automated reimbursement uses an estimated sales value, which may be below your actual landed cost. Having your own cost records lets you challenge a low reimbursement amount.
Account-level reserve and disbursement history – if the account has a disbursement hold or frozen balance running in parallel, cross-reference the reimbursement amounts against the disbursement ledger. In some matters we have seen reimbursement credits applied to a frozen balance without being released to the seller, which requires a separate recovery action.

Retain all of the above in a version-controlled file. Seller Central reports can be regenerated, but historical data older than a certain period rolls off or becomes less granular. Export and save as soon as you identify the problem.

This documentation phase is also the point at which you should make a preliminary assessment of total exposure. A mid-size FBA seller on Amazon DE running multi-SKU inventory can accumulate reimbursement entitlements across dozens of separate loss events. Treating each one as an individual case, opened as you notice them, is operationally inefficient and risks missing the claim window on early losses. A structured, document-first approach covers the full exposure in a single controlled process.

Phase 2: Run the reconciliation and calculate your claim

Reconciliation is where the documentation becomes a number – and getting the number right before you file is critical because Amazon's case system records the initial claim amount, and underclaiming at the start often sets a ceiling on recovery in that case.

Work through each category in turn:

Inbound shortfalls: For each shipment in the period, compare the "Units shipped" column in the shipment detail against the "Units received" column in the reconciliation report. Where received is less than shipped, check whether Amazon has already auto-reimbursed the shortfall. If not, that shipment is a live claim. Calculate the shortfall quantity and your cost per unit.
Warehouse losses: In the Inventory Adjustment report, sum all units with a loss-type adjustment code. Cross-reference against auto-reimbursements already posted to your account (these appear in the Payments report as a transaction type). Subtract what has been auto-credited. The remainder is your open loss-in-warehouse claim.
Unrecredited returns: For each return in the FBA Returns report, check the corresponding payment entry. Returns that were received by Amazon but show no corresponding credit or return-to-inventory entry are open claims. Note: some units are categorized "unfulfillable" and require a removal order or a reimbursement request; do not conflate the two.
Total EUR exposure: Aggregate the open claims across all categories. Express the inventory value using your cost records, not Amazon's automated estimate, so that you have a documented basis for challenging a low reimbursement offer.

In the matters we handle involving Amazon DE accounts, it is common to find that auto-reimbursement has covered the most visible losses – large inbound discrepancies, for example – while leaving smaller but numerous warehouse-loss entries open for extended periods. The aggregate of those smaller entries is frequently the larger part of the real exposure.

If the reconciliation turns up a disbursement hold or a frozen-balance issue alongside the reimbursement claims, the two problems interact. Our complete guide to frozen funds recovery explains the full landscape of fund holds and how reimbursement claims fit into the broader recovery strategy.

Phase 3: File the cases in the right sequence

Filing order matters. Amazon's Seller Support system processes reimbursement cases in a queue, and the way a case is opened affects how it is routed and who reviews it. A disorganized batch filing of dozens of cases at once, each poorly described, increases the risk of a form rejection and generates a backlog that is hard to manage.

Follow this sequence:

Step 1 – Auto-reimbursement check first. Before opening any manual case, confirm that Amazon has not already issued an auto-reimbursement for the loss event. Auto-credits appear in the Payments report. Filing a manual case for a loss already covered wastes time and creates account noise.
Step 2 – Inbound shipment claims via the shipment interface. Inbound discrepancy claims should be opened through the "Problem with a shipment" workflow in Seller Central, not through the general Seller Support contact form. This routes the case to the correct team and triggers the standard reconciliation review period.
Step 3 – Warehouse-loss and return claims via Seller Support case. Open a separate case for each category of loss. Do not bundle warehouse losses with return credits in a single case; the review teams are different. In each case: state the specific loss event (date, ASIN, quantity), attach the relevant report extract, and state the amount claimed. Be precise. A vague case description ("I am missing inventory") is far more likely to generate a canned response than a specific, documented claim.
Step 4 – Follow the escalation path if the first response is a denial. A first-level denial is not a final decision. Amazon's case system has an escalation path that most sellers do not use effectively. Request a manual review, cite the specific report data, and – for larger claims – escalate to Seller Support management. If the denial persists and the amount is material, the path moves outside Seller Central entirely.

The timing constraint here is real. Amazon's reimbursement policy imposes a claim window: losses older than a specified period may no longer be eligible. This is one of the most common reasons otherwise valid claims are rejected in the matters we review – not because the loss did not happen, but because the claim was opened too late. Act as soon as you identify the discrepancy, not after you have gathered every document perfectly.

A practical note on language for Amazon DE sellers: while Seller Central for a German-marketplace account is typically available in German and English, the underlying reimbursement case system is handled by Amazon's global Seller Support. Filing in clear, documented English often produces faster routing to specialist teams. If your account is managed in German, maintain bilingual records.

Phase 4: Respond to denials and manage escalation

A reimbursement denial is the point at which most sellers stop. That is a mistake. A first-level denial, particularly a templated one citing "policy" without specific reasoning, often signals that the case was routed to a general-queue reviewer who applied a default response. It is not a substantive determination of whether the reimbursement is owed.

When you receive a denial:

Read it carefully for the stated reason. Is the denial based on the claim being out of the claim window? That is usually final. Is it based on insufficient documentation? That is addressable. Is it a boilerplate response with no specific reasoning? That should be escalated.
Respond within the case thread. Do not open a new case for the same loss event. Respond in the existing thread with additional documentation and a clear restatement of the claim. Explicitly ask for a manual review by a specialist team.
Escalate to Executive Seller Relations if the standard escalation path stalls. Amazon operates an Executive Seller Relations (ESR) function that can review cases that have not been resolved through standard Seller Support. This channel is not always easy to access, but it exists and is sometimes the only path to a substantive review of a disputed reimbursement.
Assess whether the amount justifies formal dispute resolution. For larger reimbursement amounts, the Amazon Business Solutions Agreement (BSA) provides a dispute-resolution path. The first step under the BSA is typically a Notice of Dispute, which initiates a formal review period before any further proceedings. The path from there depends on the BSA version governing the account – we check this first in every matter.

For context on how other sellers have resolved reimbursement denials at this stage, see our account of how one seller resolved an FBA reimbursement denial.

A denial on the basis of "policy" without a specific clause reference is a reason to press, not to accept. The reimbursement obligation exists independently of whatever automated decision was made on the case. If Amazon lost the inventory and the documentation supports the claim, the fact that the first reviewer said no is a process issue, not a legal bar.

The steps above describe the standard path. Your situation turns on the exact wording of the denial, the age of the claim, the documentation you have, and the total amount at stake – which is what we review first. To get a read on your claim, email info@tutamenlaw.com.

Phase 5: Decide whether to claim alone or with counsel

That held funds are gone for good once an account is deactivated or a claim is denied – that belief costs sellers real money. In our practice, a significant share of reimbursement claims that arrive at us labeled "final denial" have procedural options still open, whether through escalation within Amazon's system or through the formal dispute-resolution path under the BSA. The question is not whether to give up; it is whether the amount at stake justifies the time and cost of pressing the claim further.

A practical decision matrix:

If the open reimbursement amount is small and the documentation is complete and recent → file the cases yourself using this checklist and escalate once if denied. The process is within reach of a competent operations team.

If the amount is material, the documentation trail is complex, the account also carries a disbursement hold or a frozen balance, or the claim has already been denied once → the case benefits from attorney-led management. We review the denial notice, map every held balance and reserve, and press the disbursement and reimbursement claims through the appropriate channel, including the formal BSA dispute path where that is the right tool.

If the account has been deactivated and the reimbursement credits are being applied to a held balance rather than released → this is a combined frozen-funds and reimbursement problem. The commercial pressure here is real: inventory bills, advertising costs, and storage fees continue to run while the balance is held. Treating the reimbursement claim in isolation misses the broader recovery opportunity.

As enforcement automation has tightened across Amazon's fulfillment operations, the number of accounts where reimbursement and disbursement problems overlap has grown. A seller managing a mid-size FBA business on Amazon DE can be owed a meaningful sum in reimbursements while also carrying a frozen balance from an Account Health issue – and the two problems need to be resolved in a coordinated way, not as separate tickets.

The decision to handle this alone versus with counsel is ultimately a cost-benefit question. Attorney-led work at Tutamen is conducted on fixed fees quoted up front after a short review, so the cost side of that equation is transparent before you commit. What that fixed fee buys is a complete claim audit, proper documentation of the entire loss exposure, and management of the escalation and formal dispute path if Seller Central does not resolve the claim. That is materially different from opening individual cases reactively as you notice discrepancies.

One illustrative example: an electronics accessories seller on Amazon DE (winter 2025) came to us after receiving denials on a cluster of warehouse-loss and inbound-discrepancy claims spanning two shipment cycles. We ran a full reconciliation against the Inventory Adjustment and Payments reports, identified that several of the denials were based on incomplete documentation rather than a substantive determination, refiled with complete records and a clear claim statement, and escalated through the appropriate internal channel. The credits were applied to the seller's account over a period of several weeks.

A second example: a home-goods FBA seller on Amazon US (spring 2026) came to us with a frozen-balance situation in which Amazon was applying incoming reimbursement credits to a held reserve rather than disbursing them. We mapped the full disbursement and reserve ledger, identified the mechanism creating the offset, and filed under the BSA dispute-resolution path to require a formal review of the reserve calculation. The matter was resolved in the seller's favor over the following weeks.

Phase 6: Prevent future losses with ongoing reconciliation

A one-time claim recovers what has already been lost. An ongoing reconciliation process prevents the problem from compounding. The sellers who recover the most over time are not necessarily the ones with the largest single claim; they are the ones who catch discrepancies early, before the claim window closes, and who maintain documentation discipline between claims.

Build the following into your standard operating cycle:

Monthly Inventory Adjustment review: pull the report, filter for loss-type codes, and cross-reference against auto-reimbursements. Any open loss events should trigger a case within the same month.
Shipment reconciliation at close of each inbound: do not wait for the quarterly reconciliation. As soon as a shipment is marked "Closed" in Seller Central, run the received-vs-shipped comparison. Flag discrepancies immediately.
Returns reconciliation every 30 days: the FBA Returns report is available in near-real time. A monthly pass against the payment ledger catches unrecredited returns before they age out.
Annual full audit: even with monthly checks, an annual full-period reconciliation often catches loss events that slipped through the monthly process or were incorrectly categorized. For accounts with high SKU counts or multi-country inventory movements, this is particularly important.

For Amazon DE sellers with MCI arrangements, note that inventory moving between national warehouses generates transfer records that can look like a loss event in the adjustment report. Filter carefully for legitimate transfer codes before treating a quantity reduction as a claim. Getting this wrong in either direction costs you: filing false claims damages your account standing; missing genuine losses costs you money.

The cost of not reconciling is asymmetric. You will not be penalized for inventory that went missing without being claimed. You will simply not be paid for it. Over a year of FBA operations, the cumulative value of undetected and unclaimed losses at a mid-size seller is typically meaningful. The reconciliation process described in this checklist is an investment in recovering what you are already owed.

Related areas

Frozen Funds & Recovery – full practice area covering disbursement holds, reserves, and fund recovery across Amazon and other marketplaces
FBA Reimbursement Checklist – this page, bookmarkable as your operational reference

If a first appeal or claim filing already came back rejected, a second read of the denial notice often identifies the specific procedural reason it failed and whether anything is still open. To have your reimbursement denial reviewed, contact Tutamen at info@tutamenlaw.com.

Frequently asked questions: FBA reimbursement for lost inventory

How long does resolving FBA reimbursement for lost inventory usually take on Amazon DE?

The timeline varies with the complexity of the claim and whether it requires escalation. A well-documented case that Amazon accepts at the first review can be resolved within a few weeks. Cases that require escalation within Seller Support, referral to Executive Seller Relations, or formal dispute-resolution under the BSA typically take considerably longer. In the matters we handle, the single largest driver of delay is incomplete documentation at the initial filing stage – which is why the reconciliation and document-gathering phases of this checklist come before any filing.

What are the main risks if I handle FBA reimbursement for lost inventory alone?

The principal risks are missing the claim window through delay, underclaiming because the reconciliation was incomplete, and accepting a first-level denial as final when it is actually a procedural rejection. A seller managing reimbursement claims alongside an active FBA business also risks deprioritizing claim follow-up in a way that lets winnable claims age out. For smaller, well-documented claims, self-management is often appropriate. For material amounts, complex multi-category losses, or cases where a disbursement hold is also involved, the risk of a mistake is higher than the cost of professional management.

Do I need a lawyer for FBA reimbursement for lost inventory?

Not always. Many reimbursement claims can be handled by a competent operations team using this checklist. A lawyer adds real value when: the total amount is material and the claim has been denied; the account also carries a disbursement hold or frozen balance; the denial notice cites the Business Solutions Agreement or invokes a formal dispute mechanism; or the claim requires a Notice of Dispute and use of the BSA dispute-resolution path. Tutamen handles FBA reimbursement matters on fixed fees quoted up front, so the question of cost versus claim size is transparent from the start.

About Tutamen

Tutamen is an independent law firm for online marketplace sellers. We represent Amazon, Walmart, Etsy and eBay sellers in account deactivations, frozen-funds recovery, intellectual-property disputes, arbitration and Notices of Dispute, and US federal Schedule A defense, plus EU marketplace regulation. Our work is attorney-led and confidential, with fees quoted up front. We act for founders, brand owners and in-house teams who need a specialist for a marketplace dispute. To discuss your situation, email info@tutamenlaw.com.

This page was written by Claire Donnelly, arbitration and disputes analyst at Tutamen.

Disclaimer: This article is general information, not legal advice, and does not create an attorney-client relationship. Marketplace policies and the law change, and every account and case is different. For advice on your situation, contact Tutamen at info@tutamenlaw.com.