Why FBA reimbursement for lost inventory happens and how sellers respond

TL;DRFBA reimbursement for lost inventory is Amazon's mechanism for compensating a seller when units entrusted to the Fulfillment by Amazon network go missing – at a warehouse, during a transfer between fulfillment centers, or in the inbound shipping process. On Amazon DE, the same core rules apply as across other Amazon surfaces, but German-market sellers face additional complexity around cross-border inbound routes, multi-warehouse distribution, and the interaction between open reimbursement claims and any wider disbursement hold on the account. The realistic options range from filing a straightforward Seller Central case to pressing a formal legal claim under the Business Solutions Agreement (BSA) – and choosing the wrong path at the wrong moment costs both money and time.

Every week, FBA sellers on Amazon DE discover a gap between the inventory they shipped and the units Amazon shows as available or sold. The discrepancy might appear as a Seller Central reconciliation alert, a mismatch between shipment confirmation and received quantities, or simply a line item that vanished from the inventory ledger. The money the missing units represent is already tied up – and the inventory and advertising bills that funded those units keep coming due regardless.

This analysis covers what FBA reimbursement for lost inventory actually is, why it happens, how the procedural path works on Amazon DE, and the decision points that determine whether a seller recovers what is owed or writes off the loss.

What does FBA reimbursement for lost inventory actually mean?

FBA reimbursement for lost inventory is a credit to a seller's account – calculated at Amazon's assessed replacement value of the missing units – triggered when Amazon acknowledges that units in its custody cannot be accounted for. It is not a discretionary gesture; it flows from the seller's agreement with Amazon and from Amazon's own published FBA inventory reimbursement policy, both of which recognise that Amazon bears custodial responsibility for inventory once it has been accepted into the fulfillment network.

The practical trigger is a unit that entered the network – confirmed by a shipping carrier or an Amazon warehouse scan – but that Amazon cannot locate in any active, reserved, or disposed state. Three situations produce that outcome most often.

First, inbound shipment loss. A seller ships a box of units to a DE fulfillment center. The carrier confirms delivery. Amazon's receiving scan credits fewer units than the manifest shows. The difference sits in "shipment reconciliation" and, if Amazon does not find the units within the reconciliation window, it should trigger a reimbursement case.

Second, warehouse-to-warehouse transfer loss. Amazon moves inventory between fulfillment centers without seller instruction – a standard practice for DE market logistics. Units sometimes disappear between the outbound scan at one center and the inbound scan at another. The seller's Manage Inventory screen shows a drop in available count, but no corresponding sale or removal order.

Third, fulfillment-center loss. Units confirmed as received sit in storage but go missing from the inventory ledger – most often attributed to mislabeling, physical misplacement, or damage events that are never formally logged as disposals. Amazon's own reconciliation process is supposed to catch these, but in practice it does not always do so within the expected window, and some cases require a seller-initiated case to surface.

The reimbursement itself is calculated by Amazon at a value Amazon determines, not at the seller's cost or the item's actual sale price on the DE marketplace. That gap – between what Amazon offers and what the units were actually worth in the market – is one of the core commercial tensions in reimbursement practice. Sellers who accept the first automated credit without checking the valuation often leave a material sum on the table.

Why does inventory go missing inside the FBA network?

Amazon's fulfillment network is a logistics system operating at enormous scale, and errors at scale are statistically inevitable – but that generic answer does not help a seller who is trying to understand why a specific shipment came up short or why units vanished mid-transfer. The causes matter because they affect which documentation a seller needs and which escalation route is appropriate.

Receiving errors are probably the most common root cause. Warehouse receiving is partly automated and partly manual. Label misreads, box damage on arrival, and high-volume receiving periods all contribute to undercounts on inbound acceptance. Amazon's system assigns units to a "pending" state during reconciliation, but if the physical units are not located, the shortfall moves toward a reimbursement trigger rather than a receipt correction.

Transfer discrepancies arise from the structure of the European Amazon network. An FBA seller on Amazon DE may have units distributed across warehouses in Germany, Poland, the Czech Republic, and elsewhere under Amazon's pan-European or European Fulfillment Network programs. Each transfer between those sites creates a handoff where a scan failure or a mis-sort can cause units to fall off the inventory ledger. For DE sellers, this is particularly relevant because the cross-border distribution footprint is larger than in markets where fulfillment is geographically concentrated.

Disposal without notification is a third category. Amazon is permitted to dispose of units that are deemed unsellable, but the seller should receive either a credit under the removal/disposal fee structure or notification that the units were destroyed. In practice, units sometimes disappear from the ledger without a corresponding disposal record or reimbursement credit, which produces the same reconciliation gap as a genuine loss.

System-level reconciliation lag accounts for a proportion of apparent losses that resolve themselves. Amazon's internal reconciliation runs on its own cadence, and a unit that appears missing today may surface in inventory in a few weeks. The difficulty is that a seller cannot know, from the outside, whether the missing unit will be found or not – which means waiting passively risks missing the filing window, while filing too early generates a case that may be closed when the unit surfaces.

In matters we handle, the distinction between a recoverable reconciliation lag and a genuine unresolved loss is one of the first things we assess – because pursuing a case too early, or too late, changes the outcome.

What is the procedural path for a DE seller pursuing a reimbursement case?

The procedural path starts in Seller Central and escalates through a series of steps that most sellers do not complete in full – which is a significant reason why legitimate reimbursement claims go uncollected. Understanding the path and its timing is essential for a DE seller managing cash flow against an outstanding inventory gap.

Step one is reconciliation auditing. Before opening a case, a seller should run a reconciliation of all shipments across the relevant period, cross-referencing carrier proof-of-delivery, Amazon's shipment-received records, inventory adjustments, and any removal or disposal orders. This is not a quick task for a seller with high-volume, multi-SKU operations – but it is the foundation that determines what to claim, against which shipment reference, and in what amount. Sellers who skip this step often open cases based on a total inventory deficit rather than a specific, documented event, which is one of the main reasons cases are rejected at the Seller Central level.

Step two is the Seller Central case. Once the reconciliation identifies a specific discrepancy – a particular shipment that shows fewer received units than shipped, or a transfer loss linked to an identifiable event – the seller opens a case through Seller Central, attaches the relevant documentation (carrier proof of delivery, shipment manifest, discrepancy summary), and requests a reimbursement review. On Amazon DE, the language of the case matters; filing in German does not always produce a different outcome, but it is worth noting that DE Seller Support is operated through a European service structure that may have different escalation paths than the US teams.

Step three is escalation within Seller Central. A first-level case is often closed with an automated or templated response that denies the claim or offers a partial credit. Sellers frequently stop here and accept the denial. A better path is a documented escalation that attaches additional evidence – a more granular reconciliation showing the specific units, dates, and discrepancy amounts, plus any correspondence that establishes the unit count at each stage of the chain of custody. In our experience, well-evidenced escalations at this stage recover credits that a first-level denial would have left uncollected.

Step four is the BSA dispute path. If Seller Central escalation does not resolve the matter, the BSA – Amazon's standard seller agreement – contains a dispute-resolution mechanism. The exact form of that mechanism depends on the BSA version applicable to the account, which we check first, because the path depends on it. For DE sellers, there are also considerations under the Platform-to-Business (P2B) Regulation, which creates specific rights for marketplace sellers operating in the EU, including access to a complaint-handling process and the right to a statement of reasons for adverse decisions.

For a thorough grounding in the full spectrum of fund-recovery options on Amazon, our guide to frozen funds recovery for sellers sets out the complete framework – including what happens when a reimbursement claim sits alongside a wider disbursement hold or account suspension.

A practical note on timing: the window to open a reimbursement case is not indefinite. Amazon's published policy sets a filing period measured from the relevant event – whether the close of a shipment reconciliation window or the date of an inventory adjustment. Sellers who discover a discrepancy months after the fact may find that the standard Seller Central path is already closed, which shifts the matter toward the BSA dispute route or, in some cases, to a formal legal claim. Filing late narrows the options materially.

How does a disbursement hold complicate FBA reimbursement claims?

For many DE sellers who come to us, the FBA reimbursement issue does not exist in isolation. It sits alongside a disbursement hold – Amazon withholding payment of the seller's account balance – either because the account has been deactivated, because an account-level reserve policy has been applied, or because Amazon has flagged the account for a verification or compliance review. The interaction between a reimbursement claim and a disbursement hold is one of the more commercially damaging situations a seller can face.

The damage is not the policy notice. It is the inventory bill that still comes due while the account balance is frozen and the reimbursement claim is unresolved. A seller running a mid-volume FBA operation on Amazon DE may have a significant sum tied up in unreimbursed lost inventory at the same time as their account balance is being held under reserve. Neither pot of money is accessible. Meanwhile, supplier invoices, warehouse rental, and advertising costs run on.

The myth that circulates in seller communities is that held funds are gone for good once an account is deactivated. That is almost never correct, and believing it causes sellers to stop pursuing what they are owed. In most cases we handle, the balance held in a deactivated account remains recoverable – the path to recovery depends on the reason for the hold and the state of any underlying appeal or dispute, but the funds are not forfeited by deactivation alone.

When a reimbursement claim and a disbursement hold exist simultaneously, they need to be addressed in parallel rather than sequentially. The reimbursement case can proceed – and credits can be applied to the account balance – even while an account is deactivated. But if the broader hold is not also addressed, the credited reimbursement simply adds to a balance that remains inaccessible. Our approach in these matters is to map every held balance and open credit, and to work both tracks simultaneously so that any recovery compounds rather than gets trapped.

This is also where the difference between handling the matter in-house and working with a specialist becomes most apparent. Seller Support and Seller Central case management are designed to handle one issue at a time, through sequential queues. The legal and procedural tools available through the BSA dispute path, the P2B Regulation complaint mechanism, and the Digital Services Act (DSA) – which designates Amazon as a Very Large Online Platform (VLOP) with specific obligations toward sellers – operate in parallel and, in our experience, move cases that have stalled in the standard queue.

A closely related analysis of how damaged-inventory reimbursements interact with the same procedural path is available in our review of FBA reimbursement for damaged inventory.

What are the seller's decision points and trade-offs?

Every seller facing an unresolved FBA reimbursement claim on Amazon DE reaches a set of forks in the road. The choice at each fork affects cost, timeline, and the probability of recovery. A clear-eyed assessment of those trade-offs is more useful than a general recommendation to "fight harder."

The first decision is whether to pursue at all. For a small discrepancy – a handful of low-value units – the time cost of a thorough reconciliation and a multi-stage Seller Central escalation may exceed the recoverable amount. This is a straightforward commercial calculation, and for very small claims the honest answer is sometimes to write off the discrepancy. For anything above a modest threshold, however, the math reverses quickly, and the cost of not pursuing is higher than the cost of a structured effort.

The second decision is how far to escalate within Seller Central. Most sellers stop at the first denial. Some pursue one escalation. Very few complete a full, documented escalation with a granular reconciliation and a specific, line-by-line claim. That final group recovers a materially higher proportion of what they are owed. The trade-off is the time and expertise needed to build the escalation correctly – which for a high-volume, multi-SKU DE seller can be substantial.

The third decision is whether to use the BSA dispute path. A Notice of Dispute under the BSA, followed by a pre-arbitration demand, is a different tool from a Seller Central case. It is a formal legal claim, and Amazon's legal and compliance teams – rather than Seller Support – respond to it. In matters we handle, a well-structured pre-arbitration demand regularly moves claims that have stalled in the Seller Central queue for months. The trade-off is that it is a more formal step, with its own process requirements, and it is not proportionate for the smallest claims.

The fourth decision, for DE sellers, is whether the P2B Regulation adds a useful lever. The Platform-to-Business Regulation gives EU marketplace sellers the right to a statement of reasons for an adverse decision and access to an internal complaint-handling process. For a reimbursement denial that appears to apply a policy inconsistently or without adequate explanation, the P2B route can produce a substantive response that the Seller Central queue does not. It is not a guarantee of recovery, but it is a procedural right that DE sellers have and US sellers do not – and it is underused.

Consider a mid-sized consumer-electronics accessory seller on Amazon DE (fall 2025) who came to us with a multi-shipment reconciliation gap spread across several inbound deliveries over a six-month period. Seller Central had closed three cases with templated responses, and the seller had accepted two of the denials. We reconstructed the full chain of custody for each shipment using carrier records, Amazon's reconciliation reports, and inventory-adjustment logs, then filed a consolidated escalation and a Notice of Dispute under the BSA. The consolidated approach – treating the losses as a pattern rather than individual isolated cases – produced a substantive review, and a significant portion of the claimed amount was credited.

The decision matrix in prose: if the loss is tied to a specific, documented inbound shipment with carrier proof of delivery showing a quantity that exceeds Amazon's received count, the Seller Central escalation with documentation is the right first move, on a timeline of several weeks to a few months. If the loss is a warehouse-to-warehouse transfer discrepancy without a specific carrier-delivery anchor, the evidence base needs to be built from inventory-adjustment logs before filing, which takes longer. If Seller Central escalation has already been exhausted without resolution, the BSA dispute path and the P2B complaint mechanism run in parallel and represent the realistic remaining options. If the account is simultaneously deactivated with a disbursement hold, both tracks – the reimbursement claim and the disbursement appeal – need to run concurrently or the reimbursement credit remains trapped.

Where do sellers commonly go wrong when handling this alone?

Handling an FBA reimbursement claim without specialist support is entirely possible for straightforward, small-value cases. For anything material, the patterns of error we see repeatedly are worth setting out.

The most common mistake is opening a Seller Central case before completing the reconciliation. A case that claims a general inventory deficit, without linking the deficit to specific shipment events or inventory adjustment records, gives Amazon's review team nothing to work with. The case is denied – correctly, in a narrow sense – and the seller concludes the claim has failed when in fact the underlying right has not been properly exercised.

The second mistake is accepting the first automated credit without checking the valuation. Amazon's reimbursement calculation uses its own assessed replacement value, which may be lower than the item's actual market value or the seller's cost basis. Sellers who accept the credit immediately – because cash flow pressure makes any credit welcome – may be accepting a materially undervalued settlement for lost inventory they are entitled to recover at full value.

The third mistake is not filing within the applicable window. Amazon's policy sets a window for raising inbound-shipment discrepancies and for claiming reimbursement for inventory adjustments. Sellers who discover discrepancies through an annual stock-take rather than through systematic monthly reconciliation often find that the standard Seller Central path is time-barred. The BSA dispute path and the P2B complaint mechanism have different, and sometimes longer, windows – but they require more structured preparation.

The fourth mistake is treating a reimbursement issue as isolated when it is concurrent with a disbursement hold or account suspension. Addressing only the reimbursement case while the broader hold sits unresolved means that any credit recovered immediately becomes inaccessible again. The two issues need to be worked together.

A useful resource for sellers who have already received a denial and are assessing their remaining options is our detailed review of FBA reimbursement denials, which works through the most common denial reasons and what each one means for next steps.

What the regulatory context adds for Amazon DE sellers

Amazon DE sellers operate in a regulatory environment that gives them tools US-only sellers do not have. Understanding those tools – and their limits – is part of making the right decision about how to handle a reimbursement claim.

The Platform-to-Business (P2B) Regulation requires Amazon, as a platform intermediary operating in the EU, to provide a statement of reasons for any restriction, suspension, or termination of a seller's access to the platform, and to maintain an internal complaint-handling mechanism. A reimbursement denial is not technically a restriction on platform access, but where the denial is connected to an account-level decision – a hold on disbursements, a deactivation, or a policy enforcement action – the P2B obligation to explain and provide recourse is engaged. We have found that explicitly invoking the P2B Regulation complaint-handling route in a formal submission tends to produce a more substantive response than a Seller Central case alone.

The Digital Services Act (DSA), which designates Amazon as a Very Large Online Platform (VLOP) with specific transparency and accountability obligations toward business users, adds a further layer. The DSA's statement-of-reasons requirement for content moderation decisions and the obligation to maintain an internal complaint-handling system both create pressure points that a well-structured formal complaint can use. The DSA is not a direct reimbursement mechanism, but it supports the argument that a seller is entitled to a clear explanation of why a claim has been denied and what the basis for any valuation is.

For DE sellers facing a reimbursement dispute that has stalled in the Seller Central queue, these EU-law tools represent genuinely additional options. They are not a substitute for a well-prepared Seller Central escalation – they are the next rung on the ladder when that escalation has run its course.

One more cross-surface note for sellers operating on multiple European Amazon marketplaces: the same inventory loss can, in principle, be reconciled across DE, FR, IT, and ES accounts if the seller is enrolled in pan-European FBA. That cross-market reconciliation is more complex than a single-marketplace analysis but is worth undertaking for sellers whose European FBA footprint is broad enough that losses across surfaces aggregate to a material amount.

A second micro-case: a specialty food seller on Amazon DE and Amazon FR (spring 2026), enrolled in European Fulfillment Network, came to us after discovering a recurring transfer discrepancy between a Polish fulfillment center and a German one. The seller had opened individual Seller Central cases for each event, all of which had been denied. We rebuilt the claim as a systematic reconciliation across both marketplaces, used the P2B Regulation's internal complaint mechanism to escalate formally, and obtained a substantive review. The pattern of consistent transfer loss – rather than isolated incidents – formed the basis of the consolidated claim, which was ultimately credited in part.

What should a seller do before contacting a specialist?

Before reaching out to Tutamen or any specialist, a seller can take several concrete preparatory steps that will make any subsequent review faster and more productive.

Pull a complete shipment history from Seller Central for the period in question, including all FBA shipments, received quantities, and reconciliation status. Export the inventory-adjustment report for the same period, filtering for adjustment types that correspond to losses, disposals, and transfers. Cross-reference the carrier proof-of-delivery documentation against Amazon's received-unit records for any shipment where the received count is lower than the shipped count. Note the date of each discrepancy event, because the filing window runs from that date.

Identify whether any reimbursement credits have already been applied to the account. Amazon sometimes applies automatic credits that the seller has not explicitly requested – and those credits affect the net amount of any further claim. Check whether any cases are already open, closed with denial, or closed with a partial credit.

Establish whether there is a concurrent account issue – a disbursement hold, an active appeal, or a pending compliance review – because that context shapes the strategy significantly. A seller who can arrive at a first conversation with this documentation organised will typically reach a substantive assessment of their claim in a first session rather than a second or third.

The core question a seller at this stage is really asking is: how much of this am I actually likely to recover, and what is the most efficient path to recovering it? The honest answer is that it depends on the documentation, the specific cause of the loss, the timeline since the discrepancy events, and whether the matter is isolated or sits alongside a broader account issue. That is exactly what a short initial review is designed to establish.

If you have identified an inventory discrepancy and are assessing whether and how to pursue it, email info@tutamenlaw.com for an initial read. We review the shipment documentation, map the reimbursement exposure, and give a direct assessment of the realistic options before any engagement is formalised.

Related areas

• Frozen Funds & Recovery – disbursement holds, account reserves, and fund-release strategy
• FBA Reimbursement Denial – why denials happen and what options remain after a rejection

Questions sellers ask about FBA reimbursement for lost inventory on Amazon DE

If your first Seller Central escalation or pre-arbitration demand came back without a satisfactory outcome, a second read of the claim and the supporting documentation often identifies the specific gap – whether in the evidence package, the framing of the root cause, or the invocation of the applicable regulatory rights. Email info@tutamenlaw.com with the denial correspondence and shipment records, and we will assess what is still open.

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

Timeline depends heavily on the route taken and the complexity of the claim. A well-documented Seller Central case for a single inbound shipment discrepancy can resolve within several weeks of filing. A multi-shipment consolidated claim, or one that escalates to the BSA dispute path or the P2B complaint mechanism, typically takes longer – often several months from the date of formal filing. Where a concurrent account suspension or disbursement hold is also being addressed, the overall timeline reflects the longer of the two tracks. Filing early and completely is the single factor most within a seller's control.

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

The primary risks are filing a poorly prepared case that gets denied and is then treated as a final determination, accepting a first automated credit that undervalues the claim, and missing the applicable filing window because the discovery of the discrepancy comes too late. A fourth risk, specific to Amazon DE, is failing to use the P2B Regulation and DSA procedural levers that are available for EU sellers but require formal invocation. Each of those errors can be corrected, but each one narrows the realistic recovery from the point it occurs.

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

Not necessarily for a straightforward, small-value case with clean documentation. For material claims, for cases involving concurrent disbursement holds or account deactivations, for multi-shipment or cross-marketplace reconciliations, or for matters that have already been denied at the Seller Central level, specialist input typically recovers more than it costs. The BSA dispute path, the P2B complaint mechanism, and the DSA lever all involve formal legal procedures that are most effective when invoked correctly and in the right sequence.

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.

Two grounded trust signals: every matter at Tutamen is handled by a qualified attorney, not a paralegal or account manager; and our engagement terms are fixed-fee where the matter permits, so the cost is known before any work begins.

Authored by Claire Donnelly, arbitration & disputes analyst – May 18, 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.