Long-term storage fee dispute: your questions answered

An unexpected charge appears in Seller Central. The deduction runs larger than expected. The explanation Amazon provides is brief – and disputing it is anything but straightforward. For Amazon UK sellers, a long-term storage fee dispute sits at the intersection of FBA billing, reimbursement rules, and a disbursement cycle that stops the moment a hold is applied. The money is out of the account while the inventory bill, ad spend, and supplier payments keep coming due. That is the commercial reality. This page answers the questions sellers ask us most often when this happens.

TL;DRA long-term storage fee dispute on Amazon UK arises when a seller believes Amazon has charged long-term storage fees incorrectly – whether through miscounted inventory age, wrong ASIN-level calculation, or a charge applied after units were already removed or disposed of. The dispute process runs through Seller Central case management and, where necessary, escalates to the BSA dispute-resolution path. Most errors are correctable, and in many matters a well-documented case is resolved without arbitration.

This FAQ hub covers what the dispute actually is and how it works procedurally, where sellers make avoidable errors, how the decision between self-filing and legal representation plays out, and what to do if a disbursement hold is linked to the fee charge. The sections below move from the foundational to the tactical.

What is a long-term storage fee dispute on Amazon UK, exactly?

A long-term storage fee dispute is a formal challenge to Amazon's calculation or application of long-term storage fees charged against an FBA seller's UK account. Amazon assesses these fees against units that have been in a UK fulfilment centre for an extended period, measured at scheduled charge dates across the year. When the charge appears wrong – because the unit count is inaccurate, the charge date does not reflect a prior removal or disposal instruction, or the per-unit rate is applied to the wrong ASIN – the seller has grounds to open a dispute.

In practice, the disputes we handle tend to fall into a few clear categories. The most common is a discrepancy between what Amazon's inventory ledger shows and what the seller's own records document: units that were removed in advance of the charge date still appearing as chargeable inventory. A second category involves units Amazon itself lost or damaged, for which reimbursement was never processed before the long-term fee was assessed – meaning the seller paid a storage fee on inventory Amazon no longer held. A third involves multi-ASIN consolidation errors, where the fee is allocated to the wrong product record.

What makes this more than a billing query is the financial effect. A single charge event can run to a significant sum, and Amazon's default position is that the charge was correct until the seller demonstrates otherwise. The documentation burden sits with the seller. That asymmetry is where disputes begin to stall.

What distinguishes a fee dispute from a broader disbursement hold is that the fee dispute starts as an accounting question. But the two are often connected: an unresolved long-term storage charge can sit as a negative balance that delays or reduces the next settlement, and a suspended account with unresolved fee disputes will have both issues running in parallel. For a detailed picture of the disbursement hold side, our guide on frozen funds recovery for marketplace sellers sets out the full procedural map.

How does the dispute process actually work?

The procedural path starts inside Seller Central, and the first step is building the evidentiary record before a single case is opened. Sellers who open a dispute first and gather documentation second tend to get an automated rejection that is harder to reverse. The correct sequence runs: pull the FBA inventory event ledger, reconcile it against removal orders and disposal records, cross-reference Amazon's reimbursement history, and only then draft the case with the specific discrepancy documented.

The case itself is opened through the Seller Central help system under the FBA billing and fee category. The submission should state the charge date, the specific ASINs in dispute, the unit count that is challenged, the amount at issue, and the documentary basis. A vague narrative – "this charge seems too high" – is the fastest route to an unhelpful canned response. A precise, evidence-anchored submission reduces the risk that the case is handled by a first-line responder with no authority to adjust the charge.

From there, the process branches. If the Seller Central case is accepted and an adjustment is made, the credit typically appears in the next settlement. If the case is rejected, the seller has a further internal escalation route before moving outside Seller Central entirely. That outside route – the BSA's dispute-resolution mechanism – is a different layer of the process with its own requirements. The path depends on the version of the Business Solutions Agreement that applies to the account, which we always check before advising on escalation options.

One procedural detail matters more than most sellers realize: the window to challenge a specific charge is not unlimited. Amazon's internal adjustment policies set time limits on how far back a dispute can reach. Filing promptly is not optional. Sellers who spend several months trying to resolve a charge informally, and then switch to a formal dispute, sometimes find that the specific charge event is outside the window for an adjustment.

If the dispute involves units Amazon lost or damaged before the long-term fee was assessed, the FBA reimbursement claim runs concurrently with the fee dispute. Both need to be in the record. Our detailed breakdown of inventory recovery options appears in our piece on stranded inventory and held funds, which covers how those two threads interact.

Where do sellers go wrong when disputing alone?

The most consistent error is documentation presented in the wrong format. Amazon's case-management system processes a high volume of fee disputes, and submissions that reference spreadsheets in the wrong structure, or that describe a discrepancy without attaching the specific inventory event report that proves it, tend to close without a substantive review. The threshold for "documented" inside Seller Central is higher than most sellers expect the first time they file.

A second common failure is disputing the wrong amount. Sellers often dispute the total long-term storage charge for a period when only a portion is actually contestable. Overstating the dispute – claiming the entire charge was wrong when a subset of units is the real issue – can cause the whole submission to be dismissed rather than adjusted in part. Precision is protective.

There is also a sequencing problem we see regularly. A seller with a concurrent account health issue or a pending disbursement hold opens the fee dispute as a standalone, without understanding that the fee charge and the hold are interacting. The fee dispute succeeds on paper – the adjustment is credited – but the net effect on the next settlement is zero because the hold absorbs it. Managing the two in parallel, not sequentially, is what produces a real cash outcome. Our overview of the closed account balance recovery path explains how these parallel tracks are managed when an account is no longer active.

Finally, sellers who have already received a rejection on their initial Seller Central case sometimes re-open the same submission with the same documentation and expect a different result. A second identical filing rarely succeeds. What is needed is a reframing of the specific error, additional documentary support the first filing did not include, and, in some cases, escalation to a different channel entirely.

Is there a disbursement hold risk attached to a long-term storage fee dispute?

Yes – and this is the part of a long-term storage fee dispute that sellers underestimate until they see it in the account. A large unresolved long-term storage charge that sits as a negative balance can trigger Amazon's reserve mechanism, holding a portion of the next settlement to cover the outstanding amount. If the account is also under a performance or policy review at the same time, the reserve can become a broader disbursement hold that goes beyond the fee dispute itself.

The situation gets more complicated when a seller's account is deactivated while a long-term storage fee dispute is pending. Amazon continues to accrue storage charges on inventory remaining in UK fulfilment centres even after deactivation – including, in some cases, further long-term storage fees on units that were already in dispute. The balance grows while the account is locked. This is one of the more damaging dynamics in the matters we handle, because the seller has no ability to issue removal orders on a deactivated account without a separate resolution process.

The practical implication is that a long-term storage fee dispute is almost never just a billing correction. It is a funds-recovery exercise. Mapping the full held balance – fee charges, reserves, pending FBA reimbursement claims, and any A-to-z Guarantee impacts – before filing anything is how you avoid resolving one part while making another worse.

What is the realistic picture for a seller whose account is deactivated and whose funds are also affected by an unresolved long-term storage charge? The realistic options are to pursue the fee dispute through Seller Central, press the FBA reimbursement claims in parallel, and address the disbursement hold through the BSA's formal mechanisms if the Seller Central path is exhausted. None of these are fast. But each one has a sequence, and working them out of order costs time and money.

How does a long-term storage fee dispute interact with an FBA reimbursement claim?

An FBA reimbursement claim arises when Amazon is responsible for a unit being lost, damaged, or disposed of without the seller's instruction. A long-term storage fee dispute arises when Amazon charges a fee incorrectly. The two are procedurally distinct but financially linked, and in the matters we handle, they often need to move together.

The link works in both directions. If Amazon lost or damaged a unit that was then included in a long-term storage charge calculation, the reimbursement claim and the fee dispute both need to reference that unit's history. Getting the reimbursement without disputing the fee leaves money on the table. Getting the fee adjustment without the reimbursement does the same. Sellers who run these as separate, independent processes frequently find that one of the two tracks closes before the other, creating a gap in the recovery.

The documentation requirements also overlap. The FBA reimbursement claim needs the shipment record, the receiving confirmation, and the inventory event record showing that the unit was lost or damaged during Amazon's custody. The long-term fee dispute needs the same inventory event record to show that the unit should not have been counted as stored on the charge date. Preparing a single unified evidence set that serves both purposes is more efficient and reduces the risk of inconsistency between two parallel Seller Central cases.

A practical example from our practice: an apparel seller on Amazon UK contacted us in early 2026 after being charged long-term storage fees on a cohort of units that had been flagged as damaged in the fulfilment centre months earlier but never formally reimbursed. We mapped the inventory event ledger against Amazon's damage reports, identified the gap, filed the fee dispute and the reimbursement claim from a single evidence set, and the combined recovery – fee credit plus reimbursement – was processed within a matter of weeks. The seller had previously attempted the reimbursement claim alone and been partially rejected because the damage classification in Amazon's system did not match the claim's characterization of the event.

What are my decision points, and what are the trade-offs?

The central decision is sequencing: what do you file first, how long do you wait for a Seller Central response, and when do you move to an escalated route? There is no single right answer, but the decision turns on three variables: how large the disputed amount is, whether the account is still active, and whether a disbursement hold is already in place.

If the amount is relatively modest and the account is active, self-filing through Seller Central with proper documentation is a reasonable first step. The realistic expectation is a response within a few weeks, and an adjustment or a rejection with a stated reason. If the amount is significant, if the account is deactivated, or if a disbursement hold is already running, the complexity and the financial stakes change the calculation. A misstep in the Seller Central filing can narrow the escalation options that remain open. That is when professional representation changes the practical outcome.

The trade-off between handling it yourself and engaging a specialist is not purely about legal complexity. It is about time. A solo seller or a small operations team running a long-term storage fee dispute alongside a live deactivation, an ongoing inventory issue, and a supplier who wants to be paid is attempting to execute a multi-track process under financial pressure. Errors happen. First filings fail. Windows close. In many matters we see, sellers come to us after the first rejection, and the question then becomes what is still open – not what should have been done first. That is a harder position to work from.

If a first appeal or a Seller Central case already came back rejected, a second read can identify exactly why it failed and what remaining avenues are still viable. Reach out to Tutamen at info@tutamenlaw.com and we will review what was filed and what comes next.

What do the frequently asked questions look like in practice?

How long does resolving long-term storage fee dispute usually take on Amazon UK?

Resolution time varies considerably depending on the complexity of the charge event and whether the case moves past Seller Central's first response layer. A straightforward single-ASIN, well-documented dispute handled at first contact can resolve in several weeks. Cases that require escalation beyond the initial Seller Central case – particularly where the account is deactivated or a disbursement hold is running in parallel – can extend substantially longer. The window to file matters: delay does not pause Amazon's timelines, and the sooner a properly documented case is opened, the more options remain available.

What are the main risks if I handle long-term storage fee dispute alone?

The principal risks are documentation errors, sequencing mistakes, and window expiry. An underdocumented first submission often generates a canned rejection that sets a harder baseline for escalation. Filing one track – say, the fee dispute – without simultaneously pressing an FBA reimbursement claim on related units means one source of recovery closes before the other is addressed. And if the specific charge event has an internal adjustment window, delays in filing can place the charge outside the period Amazon is willing to review, regardless of how strong the underlying case is.

Do I need a lawyer for long-term storage fee dispute?

Not always. For a single, modest, well-documented charge event on an active account, a seller with organized records and time to work through Seller Central can often achieve an adjustment without professional help. The case for specialist involvement strengthens when the amount is material, when the account is deactivated, when a disbursement hold is also running, when an FBA reimbursement claim needs to run concurrently, or when a first Seller Central filing has already been rejected. At those points, the cost of further self-filed errors outweighs the cost of representation – particularly where fees are fixed and quoted up front.

Related areas

• Frozen Funds & Recovery – account-level reserves, disbursement holds, and FBA reimbursement claims for UK and US sellers
• Account Reinstatement – deactivated accounts, Plan of Action drafting, and reactivation across Amazon surfaces

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.

The steps above describe the standard path through a long-term storage fee dispute. Your situation turns on the exact charge event, your inventory records, the current account status, and whether a disbursement hold is already in place – which is what we review first. For a read on where your dispute stands, email info@tutamenlaw.com.

Byline: James Whitlock – reinstatement & funds analyst, 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.