How to handle FBA reimbursement for lost inventory: a step-by-step guide

TL;DRFBA reimbursement for lost inventory is Amazon's obligation to compensate a seller when units enter the fulfillment network and are recorded as received but later disappear before they are shipped to a customer or returned to the seller. On Amazon DE – and across the EU fulfillment network – that obligation exists regardless of whether the account is active or under a disbursement hold. The practical problem is that Amazon does not always pay automatically, and the window to file and escalate a valid claim is finite. This guide sets out the exact sequence, the decision points, and the places where sellers most often lose money they were owed.

If your FBA balance shows discrepancies or your account is also carrying a frozen-funds situation, the stakes are double: you are simultaneously chasing reimbursement and watching inventory and advertising bills keep accumulating. The guide below addresses both the routine reimbursement path and the complications that arise when the account itself is under any kind of hold.

What FBA reimbursement for lost inventory actually means on Amazon DE

An FBA reimbursement for lost inventory is a credit – or occasionally a cash disbursement – that Amazon issues when it cannot account for units that were demonstrably in its possession. The key distinction is between units Amazon accepted into a German or EU fulfillment center and units that never arrived: reimbursement only attaches to the former.

On Amazon DE, the fulfillment network spans several facilities across Germany and neighboring EU countries. When a shipment is received, each unit is scanned and logged against the shipment ID. A discrepancy arises when the received quantity is lower than the shipped quantity, or when units that were received and held in the warehouse simply vanish from the inventory ledger before an outbound event – a sale, a return, or a removal order – accounts for them.

Amazon's internal policy commits to reimbursing sellers for inventory lost or damaged while in Amazon's care. In practice, the policy operates through an automated reconciliation layer that catches many – but not all – discrepancies. The gap between what the system flags automatically and what a careful manual audit finds is often material. In matters we handle, sellers routinely discover units that were lost months or even longer ago and never triggered an automatic credit.

A key definitional point that matters for Amazon DE specifically: the reimbursement amount is typically calculated by reference to the estimated sale price or the seller's average selling price, not the seller's cost of goods. That means the reimbursement value per unit can be significantly above cost – which makes thorough auditing worthwhile – but it also means Amazon's estimate and the seller's own valuation can diverge, leading to partial credits that require challenge.

There is also a distinction between lost inventory and damaged inventory. Lost units have simply disappeared from the warehouse record without a documented disposition event. Damaged units exist in the record but have been marked unsellable. Both categories generate reimbursement entitlements, but the claim pathway and the evidence needed differ. This guide focuses on the lost-inventory path. For the damaged-inventory route, see our detailed account of how one seller resolved FBA reimbursement for damaged inventory.

Step 1 – Run the shipment and inventory audit before you file anything

Start with the data, not the claim form. Filing without a clean reconciliation is the single most common mistake we see, and it costs sellers in two ways: underfiling (missing units) and overfiling (claiming units that were actually sold or removed), the latter of which can trigger a flag on the account.

The audit has three components.

Inbound shipment reconciliation. For every shipment sent to German or EU fulfillment centers in the relevant lookback period, compare the quantity shipped (from your own despatch records and the carrier's proof of delivery) against the quantity Amazon recorded as received in Seller Central. Any shortfall at the received stage is an inbound discrepancy – a different claim type than a warehouse-loss claim, but equally compensable.

Inventory event report. Download the inventory event detail report from Seller Central. This report lists every transaction that affected your inventory balance: receipts, sales, adjustments, removals, returns. Map each unit's lifecycle from receipt to a documented disposition. Units that were received but have no documented outbound event are your lost-inventory candidates.

Reimbursements already received. Pull the reimbursements report to identify any units Amazon has already compensated. Subtract those from your candidate list. Filing a duplicate claim is both pointless and counterproductive.

For Amazon DE sellers, it is worth noting that the fulfillment network routes units between facilities across the EU under the Pan-European FBA or European Fulfillment Network program. A unit received in Poland or France on a German seller account is still within scope. The inventory reports in Seller Central aggregate across all networked facilities, but individual event-level data shows the country of the last recorded location – which matters if a discrepancy arises at a specific facility.

How long does this audit take? For a seller with moderate volume and a well-organized Seller Central account, a careful manual audit covers several months of shipment history in a day or two. For high-volume accounts or accounts where the shipment history goes back further, it can take several days. Automated third-party reconciliation tools can accelerate the data extraction step, but the legal assessment of which discrepancies are valid claims still requires human judgment.

Step 2 – Open the initial reimbursement case in Seller Central

Once the audit is complete and you have a validated list of lost-unit discrepancies, open a case in Seller Central's "Contact Us" flow, selecting the FBA reimbursement path. For Amazon DE, the same Seller Central portal handles both English and German-language submissions; there is no requirement to submit in German, though a German-language submission can sometimes reach the relevant support queue more quickly.

A strong initial submission includes:

• The shipment ID and the specific ASIN and FNSKU for each unit at issue.
• Your shipped quantity, drawn from your own despatch records or carrier proof of delivery.
• Amazon's received quantity, as shown in the shipment summary in Seller Central.
• The inventory event detail for those units post-receipt, showing the absence of a documented disposition.
• A clear, single-page summary table: unit, shipment ID, quantity discrepancy, status.

What you do not need at the initial stage is a commercial invoice or a valuation calculation. Amazon's system calculates the reimbursement value internally. However, if you believe Amazon's estimated value will understate the true value – because the ASIN has a volatile pricing history, for example – you should flag that at the outset and attach a 90-day sales history showing the average realized price.

Amazon's first response on a reimbursement case is often automated. The system checks whether an automatic adjustment has already been issued and, if not, whether the discrepancy is within a threshold that allows an immediate credit. If the automated layer resolves the case, you receive a credit confirmation and the case closes. If not, the case moves to a human reviewer – and this is where pace slows significantly.

We regularly see first responses that acknowledge the discrepancy but request additional documentation before issuing a credit. The most common requests are for proof of delivery to the fulfillment center, seller-signed packing lists, and – for older discrepancies – photographs of the outer packaging. Anticipating these requests and attaching the documentation upfront reduces the round-trip time materially.

Step 3 – Escalate when the first case is rejected or stalled

A rejected first case is not the end of the claim. Amazon's first-line support makes errors – both on the facts and on the application of the reimbursement policy. The escalation path matters, and how you frame the escalation matters even more.

The first escalation step is a case reopen with a substantive response to the rejection reason. If the rejection cites "no discrepancy found," the response should attach the shipment-level data showing the exact unit count difference, formatted clearly enough that a reviewer who did not handle the first case can follow it immediately. If the rejection cites "claim filed outside the eligible window," the response should include a timeline showing when the discrepancy first appeared in the inventory event report and calculate whether the filing was, in fact, within the window.

What is the eligible window for FBA reimbursement claims on Amazon DE? This is a detail that changes and therefore falls within the volatile-facts category this guide treats with durable framing: the window has been shortened in recent years, and the current terms govern. Sellers who delay their audit by more than a few months risk losing the right to claim entirely. That is the clearest reason why running the audit promptly – and on a rolling schedule, not annually – is commercially important.

If the reopen is also rejected or simply does not receive a substantive reply within a reasonable period, the next escalation route is the Amazon Seller Central "Executive Seller Relations" or equivalent escalation channel. This route bypasses first-line support and reaches a team with authority to issue credits without the standard documentation workflow. Accessing this channel effectively requires a well-structured escalation letter that cites the case number, summarizes the evidence, identifies the policy basis for the reimbursement obligation, and requests a specific resolution – not a general review.

A specialist in Amazon DE disputes will also consider whether the account's broader situation – a disbursement hold, a reserve balance, or a performance deactivation running in parallel – affects how the reimbursement case should be framed. In matters we handle, the interaction between an open reimbursement claim and an account-level reserve is a real complication: Amazon has, in some cases, applied a pending reimbursement credit against a reserve balance rather than disbursing it. Understanding that dynamic before filing the escalation shapes how the letter is written.

For a fuller picture of how reimbursement claims interact with account-level freezes, see our complete guide to frozen funds recovery for sellers.

The bridge between the first rejection and the escalation letter is the place where many sellers give up. They receive a templated response, conclude the money is gone, and move on. That is the myth we see most often – that held or denied reimbursements are gone for good once the initial claim fails. In a significant share of the escalated matters we work on, the credits were recoverable; the first rejection was not the final word.

Where this goes wrong: the seven failure points sellers hit most often

Knowing the correct procedure is not enough if the execution misses any of several specific failure points. Based on the matters we handle on Amazon DE and across the EU network, these are the patterns we see most frequently.

Filing too late. The reimbursement window is not open indefinitely. Sellers who run a single annual audit or who only check when a major discrepancy becomes obvious will have already lost the right to claim on older losses by the time they file.

Filing without clean data. A claim built on the shipment summary alone, without cross-referencing the inventory event detail, routinely misses units and sometimes includes units that were, in fact, sold or removed. Amazon's reviewers notice the inconsistency and reject the entire case rather than crediting the valid portion.

Accepting the automated valuation without challenge. Amazon's estimated reimbursement value for a lost unit is calculated internally. For ASINs with stable pricing histories, it is usually close to accurate. For ASINs with high seasonality, recent price increases, or limited sales history, it can be materially lower than the unit's actual realized value. Sellers who accept the first valuation without checking it against their own pricing data leave money on the table.

Not separating claim types. Inbound discrepancies (units not received), warehouse losses (received but disappeared), and damaged-inventory credits are distinct claim types in Amazon's system. Combining them in a single case usually results in the entire submission being handled under whichever category Amazon's automated triage selects – which may be the wrong one for most of the units at issue.

Escalating without new evidence. Reopening a rejected case with the same submission and a demand for reconsideration is rarely effective. A productive escalation adds something: a document Amazon did not previously have, a calculation it did not make, or an argument about the policy that the first reviewer did not address.

Ignoring the interaction with an account hold. When an account carries a disbursement hold or a rolling reserve, the treatment of a pending reimbursement credit can be unexpected. Not anticipating this – and not structuring the claim to account for it – can result in a credit that is technically issued but practically inaccessible.

Treating reimbursement as a one-time project. Inventory discrepancies are not a one-time event. They accumulate across every shipment cycle. Sellers who address a backlog once but do not implement a rolling audit process will find themselves in the same position again. The commercial value of a quarterly or monthly reconciliation process – which takes only a fraction of the time of a retrospective audit – is significant.

A home-goods seller on Amazon DE (fall 2025) came to us after a year-long backlog of unfiled reimbursement claims following a temporary account hold. The account had been reinstated but the reimbursement process had never been picked up. We ran the full inbound and inventory-event audit, separated the claim types, and filed a structured submission with the relevant carrier documentation. A material portion of the discrepancies resulted in credits; several older claims had already passed the filing window and could not be recovered. The lesson: the window matters, and the audit should run as close to real time as the business can manage.

Step 4 – Assess whether arbitration or formal escalation is the right next step

Most FBA reimbursement disputes on Amazon DE are resolved at the Seller Central level – either through the standard case process or through an escalation to the specialist support channels. For a subset of cases, however, neither route produces a satisfactory result, and the seller faces a decision about whether to pursue the matter further.

What does "further" look like? The Amazon Business Solutions Agreement (BSA) governs the relationship between Amazon and its marketplace sellers, including German sellers operating on Amazon DE. The BSA contains a dispute-resolution mechanism that determines the available formal options. That mechanism has evolved over time and is treated here with durable framing: the path depends on the BSA version that applies to the account, which we check first. Options that have been used in reimbursement disputes at various times include a Notice of Dispute, a pre-arbitration demand, and, where the BSA permits, formal arbitration before the American Arbitration Association (AAA).

The practical question is whether the amount in dispute justifies the time and cost of formal proceedings. For individual reimbursement claims in the low hundreds of euros, the answer is usually no – Seller Central escalation is the right tool. For aggregated backlogs across multiple shipment cycles, or for accounts where the reimbursement dispute is layered on top of a broader frozen-funds or deactivation situation, the calculus changes. A formal pre-arbitration demand can sometimes produce a settlement without proceeding to full arbitration, and the cost of a fixed-fee demand letter is often modest relative to the amount at stake.

The EU regulatory layer is also relevant for Amazon DE sellers. The Platform-to-Business (P2B) Regulation gives marketplace sellers certain rights when it comes to Amazon's internal complaint-handling process. A well-structured internal complaint under P2B – invoking the statement of reasons and the internal escalation system – is a tool that sits outside the Seller Central case queue and sometimes reaches a different level of the organization. We use this route in appropriate matters involving Amazon DE and other EU marketplaces.

If a reimbursement denial is part of a wider account deactivation or a dispute about withheld funds, the options – and the sequencing – become more complex. See our analysis of FBA reimbursement denial – what changed and what to do for a cross-surface comparison of how different marketplaces handle escalated reimbursement disputes.

The decision matrix in practice looks like this. If the reimbursement case has been open for several weeks without resolution and the total amount at issue is material – say, enough to affect the next inventory purchase cycle – the right move is a formal escalation letter and, in parallel, an assessment of the BSA dispute route. If the account also carries a reserve or a disbursement hold, those two issues should be addressed in a coordinated strategy rather than in parallel, unconnected filings. If the account is deactivated, reimbursement claims should still be filed and tracked, because a credit that is issued during deactivation can be applied against any balance Amazon holds – which affects the funds-recovery analysis.

The bridge between the process steps above and the formal dispute route is the moment where having specialist representation changes the outcome most often. If a first appeal or a Seller Central escalation has already come back rejected, a second read can find the specific reason it failed and identify what remains open.

To weigh your options on an Amazon DE reimbursement matter, email info@tutamenlaw.com with a brief description of the discrepancy and the stage the case is at.

Step 5 – Implement a rolling process to prevent future losses

The reactive audit described in the earlier steps recovers money from past discrepancies. The forward-looking step is building a process that prevents those discrepancies from accumulating unnoticed.

A practical rolling process for an Amazon DE FBA seller has four elements.

• Monthly shipment reconciliation. Every shipment closed in the prior month is reconciled against the received quantity within 30 days of delivery. Discrepancies identified within this window are well within the filing deadline, and the carrier documentation is still readily available.
• Quarterly inventory event audit. Every quarter, download the inventory event detail for the prior quarter and map each received unit to a disposition event. Units without a documented disposition go on the claim list immediately.
• Reimbursement tracking log. A single running log of every case filed, the amount claimed, the status, and the credit received. This allows a seller to identify pattern discrepancies – a specific fulfillment center, a specific carrier route – that point to a systemic problem worth escalating differently.
• Annual BSA review. The terms of the Amazon Business Solutions Agreement change. An annual review of the dispute-resolution section, specifically the section governing reimbursement claims and the formal dispute path, ensures the seller knows which mechanism applies and what the filing windows are under the current terms.

None of these steps requires specialist legal input on an ongoing basis. They require discipline and a clear internal owner. What does require specialist input is knowing when a discrepancy pattern crosses from a routine reimbursement matter into a funds-recovery or account-health issue that warrants a different approach.

A software-accessories seller on Amazon DE (spring 2026) implemented a monthly reconciliation process after an initial reimbursement audit recovered a backlog. Within three monthly cycles, the process identified two further inbound discrepancies before they aged past the filing window. Both were resolved at the first case stage. The total time cost of the monthly reconciliation was under two hours per cycle. The commercial return made that time cost straightforward to justify.

The self-assessment: is your situation routine or escalated?

Before deciding how to proceed, a seller should place their reimbursement situation in one of two categories.

Routine discrepancy. The account is active. The discrepancy is on a specific shipment or a small number of units. The filing window is open. No active hold or reserve complicates disbursement. In this situation, following the step sequence in this guide – audit, initial case, escalation if needed – is the right approach. Many sellers handle routine discrepancies successfully without legal representation.

Escalated situation. The account is deactivated or carries a disbursement hold. The aggregate amount at issue is material. The Seller Central case has already been rejected or is stalled. There is a parallel dispute about withheld funds or account health. The discrepancy spans multiple shipment cycles and multiple ASINs. In any of these circumstances, the step sequence above is still the right foundation, but the execution benefits significantly from specialist input – both to avoid the procedural errors that sink otherwise valid claims and to coordinate the reimbursement work with any broader account strategy.

The myth worth addressing directly: many Amazon DE sellers we speak with believe that once an account is deactivated, the reimbursement claims on that account are automatically lost. That is not correct. Amazon's obligation to reimburse for inventory it held and lost exists independently of the account status. Filing – and pursuing – reimbursement claims during a deactivation is both possible and strategically important, because the credits reduce the net amount Amazon holds and can accelerate the broader funds-recovery process.

Related areas

• Frozen Funds and Recovery – full practice overview for Amazon sellers with held balances and withheld disbursements
• Amazon Account Reinstatement – Plan of Action strategy and appeal support for deactivated accounts

If you are at the stage where Seller Central has not resolved the matter and the amount at stake is material, email info@tutamenlaw.com for a first read on what options remain open on your specific account.

Frequently asked questions

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

The timeline depends on the stage the claim reaches. Cases resolved at first submission by Amazon's automated system close within days. Cases that require human review and a single round of follow-up documentation typically resolve within several weeks. Escalated cases – those reaching specialist Amazon support or involving a pre-arbitration demand – can take several months. The largest variable is the quality of the initial submission: a complete, well-documented first filing shortens the timeline considerably. Sellers should also be aware that the filing window runs from the point the discrepancy becomes visible in the inventory data, so acting promptly after the audit protects the claim regardless of how long the resolution process ultimately takes.

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

The principal risks are filing late (outside the eligible window, forfeiting the claim entirely), filing with insufficient documentation (leading to rejection on technical grounds that are difficult to reverse), accepting an undervalued reimbursement credit without challenging Amazon's valuation, and failing to coordinate the reimbursement case with a parallel account-hold or disbursement issue. For accounts that are active and the discrepancy is limited to a single shipment, most sellers can manage the process themselves using the steps above. For accounts with a disbursement hold, a deactivation, or a significant aggregate discrepancy, the risk of procedural error is higher and the cost of specialist input is typically justified by the amount at stake.

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

Not for routine single-shipment discrepancies where the account is active and the filing window is open. The step sequence in this guide covers the process, and a careful seller can work through it without legal support. A specialist adds real value when the account is under any kind of hold or deactivation, when the aggregate amount at issue is material, when the Seller Central case has already been rejected, or when the reimbursement issue is part of a broader funds-recovery dispute. In those situations, a lawyer who handles Amazon DE matters regularly will know which escalation route is actually effective, how to structure the evidence to meet Amazon's internal documentation requirements, and how to use the formal dispute mechanism under the BSA if the administrative process does not resolve the matter.

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. Every matter is handled by a qualified attorney – not a paralegal or an account manager – and all communications are confidential. To discuss your situation, email info@tutamenlaw.com.

Written by Claire Donnelly – arbitration & disputes analyst, Tutamen. Published June 1, 2026.

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.