Responding to long-term storage fee dispute the right way

TL;DRA long-term storage fee dispute on Amazon UK arises when charges assessed against a seller's account are incorrect, duplicated, or applied to inventory that was already removed – and resolving it requires a precise sequence of evidence-gathering, case filing, and escalation within Seller Central. The dispute is not simply a refund request: it sits at the intersection of FBA inventory records, the disbursement cycle, and, in some cases, a broader disbursement hold that can freeze working capital for weeks. Getting the sequence wrong on the first filing narrows what remains open afterward.

When inventory bills keep arriving and the funds to cover them are sitting locked in a Seller Central balance, the commercial pressure is immediate. Long-term storage fees – assessed periodically on units held in Amazon's UK fulfilment network beyond the applicable storage thresholds – are among the most commonly disputed charges on the platform. Yet in matters we handle, a significant share of sellers arrive after a failed first attempt, usually because they filed against the wrong charge type or provided evidence that did not match Amazon's internal inventory snapshot.

This guide sets out the exact procedural path for a long-term storage fee dispute on Amazon UK, the decision points that determine whether the dispute succeeds, and where the process routinely goes wrong when sellers work through it alone.

What is a long-term storage fee dispute on Amazon UK, and when does it apply?

A long-term storage fee dispute is a formal challenge to FBA charges that Amazon has applied to units held in a UK fulfilment centre beyond the period after which elevated storage fees become payable. Amazon charges these fees periodically on units that exceed the applicable storage duration thresholds – the precise thresholds and fee rates are published in Seller Central under the FBA fee schedule and are subject to periodic revision, so the operative figure for any given dispute is the schedule in effect at the date the charge was assessed, not the current published rate.

Disputes arise in several recurring patterns. Inventory that was placed on a removal order before the assessment date but not physically removed in time is one of the most common. Commingled stock that was incorrectly counted in the balance is another. Stranded inventory that the seller could not sell – because of a listing suppression or policy hold – but was still charged for is a third. Each pattern requires a different evidentiary approach, which is why a single generic dispute letter rarely succeeds.

What makes this particularly consequential for UK sellers is the relationship between long-term storage fees and the disbursement cycle. Where fees are large enough to push an account balance negative, Amazon may apply an account-level reserve or trigger a payment hold on the next disbursement. At that point, the storage fee dispute becomes inseparable from a broader frozen funds recovery matter, and the procedural path branches.

Step 1 – Map the charge before you file anything

The single most important step is to identify every long-term storage charge by transaction date, ASIN, and unit count before submitting a dispute case. Many sellers skip this and file a global dispute; Amazon's case-management system treats that as a non-specific claim and it is routinely closed without investigation.

Start in the Payments section of Seller Central under Transaction View. Filter for the relevant charge type and export the data. Cross-reference each charge line against the FBA Inventory Ledger report for the same period. The Inventory Ledger is the authoritative record of what Amazon's system believed was in the fulfilment centre at the time of assessment – and discrepancies between what you expected to hold and what the ledger shows are the core of most viable disputes.

Where a removal order was in flight at the assessment date, pull the removal-order report and check the shipment-creation date against the assessment timestamp. Amazon's policy on what constitutes a timely removal is stated in the FBA fee schedule; the burden is on the seller to demonstrate that units were removed or in the removal pipeline before the charge crystallised.

For stranded inventory, export the Stranded Inventory report for the relevant period and note the stranding reason. If the stranding was caused by a platform-side issue – a suppression triggered by Amazon's own system rather than a seller compliance failure – that fact is relevant to whether the charge should stand.

Step 2 – Build the evidence package

Amazon's FBA reimbursement and fee-dispute teams work from specific data artefacts. Submitting narrative alone will not advance a case. The evidence package for a long-term storage fee dispute should contain, at minimum: the Transaction View export showing each disputed charge with its date and amount; the FBA Inventory Ledger report for the same assessment window; any removal order reports with shipment dates; and, where relevant, the Stranded Inventory or Suppressed Listings report.

Label each document clearly. If you are disputing charges across multiple ASINs, group the evidence by ASIN. A case that requires the reviewer to match documents to charge lines is likely to be closed as insufficiently evidenced.

One point we see cause problems repeatedly: sellers submit screenshots rather than exported CSV or Excel files. The Seller Central case system accepts attachments, and structured data is far more useful to a reviewer than a cropped screenshot of a number. Use the native export functions.

Step 3 – File the Seller Central case correctly

Open a case through Seller Central's Help system under FBA Issue, then FBA Inventory, then the charge-specific category. Do not use the general Payments contact path for a storage fee dispute – it routes to a different team that will refer you back to FBA, losing several days in the process.

The case submission should state the dispute clearly in the first paragraph: the specific charge type, the assessment date or window, the total amount disputed, and the basis for the dispute in one sentence. Then attach the evidence package. Keep the case description factual and concise. Lengthy narrative explanations tend to slow reviewer triage; the evidence documents carry the argument.

Amazon's initial response on FBA fee disputes is often a template acknowledgment. If the substantive response is a denial, read it carefully: it will usually cite a specific reason, which tells you whether the evidence package was incomplete, whether Amazon's inventory snapshot differs from yours, or whether the dispute has been assessed on a policy question rather than a factual one. That reason determines the next step.

Where this goes wrong

Most failed long-term storage fee disputes fail at one of three junctures.

The first is filing too broadly. A global dispute across all long-term storage charges for a quarter, without ASIN-level detail, is treated as a low-confidence claim. It typically receives a denial without detailed reasoning, which makes the escalation path harder to navigate.

The second is filing on the wrong basis. A seller who focuses on "I didn't know about these fees" rather than "the inventory ledger shows these units were removed before the assessment date" is arguing policy preference rather than a factual error. Policy-preference disputes almost never succeed. The viable dispute is always grounded in a discrepancy between Amazon's records and the actual inventory position.

The third is missing the interaction with a disbursement hold. Where Amazon has offset long-term storage fees against a pending disbursement – or has placed a reserve because the fee charges pushed the balance – the dispute path has to run in parallel with a disbursement release claim. Running them sequentially means the funds stay frozen while the fee dispute proceeds, which can take several weeks. In matters we handle, mapping both tracks at the outset consistently produces faster resolution than treating them as separate matters.

A mid-market FBA seller on Amazon UK (winter 2025) came to us after two failed dispute cases. The original charges related to inventory that had been on removal orders for several weeks before the assessment date; the seller had filed on a narrative basis without the Inventory Ledger export. We rebuilt the evidence package from the Ledger and removal-order reports, filed a new case citing the specific ASIN-level discrepancy, and the case was resolved in the seller's favour on the substantive review. The disbursement hold that had been in place since the balance went negative was released concurrently once the charge was reversed.

Step 4 – Escalation if the case is denied

If a well-evidenced case is denied, escalation within Seller Central's case system is the immediate next step. Reply to the case with a direct request for supervisory review, reference the specific denial reason, and explain why the evidence addresses it. Keep this brief. Repeat the key data point from the Inventory Ledger or removal report in the case reply itself, not only in the attachment.

If that escalation also fails, the Seller Support management contact path via the Account Health page can sometimes reach a different review layer. This is slower but occasionally effective for cases where the denial reason is clearly inconsistent with the evidence submitted.

For disputes involving significant sums, or where the long-term storage fee charges are symptomatic of a broader account issue, the BSA dispute-resolution mechanism becomes relevant. The path available depends on the BSA version applicable to the account – which we check first in every matter. Depending on that version, a Notice of Dispute and a pre-arbitration demand can be the appropriate lever for a fee dispute that Seller Central has repeatedly declined to resolve correctly. That path is detailed in our guide to stranded inventory and held funds.

Where an account has been deactivated and the long-term storage fee dispute is part of a larger balance-recovery matter, the options and sequencing differ materially. We cover the full spectrum of post-deactivation balance recovery, including the interaction between fee disputes and final settlement calculations, in our guide to closed account balance recovery.

Seller decision points and trade-offs

The key decision at each stage is whether to continue within Seller Central's case system or to escalate outside it. Continuing inside the case system is lower cost and should always be the first route. Escalating to the BSA dispute path carries a higher time and resource commitment, but it carries leverage that Seller Support does not – a formal Notice of Dispute changes the posture of a matter in ways that an internal case ticket does not.

The threshold for considering the formal dispute path is partly financial: a small charge disputed for a modest amount rarely justifies the time of a pre-arbitration demand. But where the fee dispute is tied to a disbursement hold that is keeping a significant balance frozen, the calculus shifts. The hold itself has a daily cost – inventory carrying charges, outstanding advertising invoices, cash-flow shortfall – and that cost can quickly exceed the cost of a formal demand.

A second decision point arises if Amazon accepts the dispute in part but denies it in part. Partial acceptance often indicates that the evidence package was strong on some ASINs and weak on others. Rather than appealing the whole partial denial, it is usually more effective to identify which ASIN-level denials have the strongest remaining evidence and to run a targeted follow-on case, rather than a broad appeal that dilutes the strongest arguments.

Sellers sometimes assume that once an account is deactivated, any held balance – including amounts that should have been returned after a fee reversal – is permanently inaccessible. That assumption is incorrect. Fee reversals secured after deactivation can still be applied to a final disbursement calculation. The timeline is longer and the process is more complex, but the legal basis for recovery does not disappear on deactivation. This is one of the most persistent myths in the Amazon seller community, and it costs sellers real money when they give up on a viable claim.

A software tools seller on Amazon UK (spring 2026) reached us after an account had been closed for several months. Long-term storage fees had been assessed and debited from the final balance during the closing period. We identified ASIN-level discrepancies in the Inventory Ledger for the assessment period, filed the evidence through the relevant post-closure case path, and successfully had a portion of those charges reversed and applied to the remaining disbursement. The seller had been advised informally by others that the claim was unviable once the account was closed. It was not.

Objection: "I tried this already and it didn't work"

This is the most common situation we encounter at intake. A first case was filed – sometimes multiple cases – and each came back denied. The natural conclusion is that the dispute is not viable. In our experience, that conclusion is frequently wrong. What is usually true is that the first filing had a structural problem: it was filed under the wrong case category, it relied on narrative rather than data, or it did not address the specific reason Amazon cited for the denial.

A denial is not a final determination on the merits of a storage fee dispute. It is a determination on the specific submission made. A new submission that addresses the structural defects of the earlier one is treated on its own terms. The question is whether the underlying factual discrepancy between Amazon's records and the seller's inventory position is real and demonstrable – because that is the only ground on which these disputes succeed.

If you have already filed and been denied, the first step is to read the denial carefully and categorise the reason. If the denial cites a missing data artefact, that artefact can usually still be obtained. If the denial cites a policy basis, the question is whether the factual record actually supports the policy ground Amazon has cited – and in our experience it often does not, when the Inventory Ledger data is examined properly.

For a review of a previous filing and a read on whether a new case is viable, email info@tutamenlaw.com. We assess these situations up front, before any engagement begins.

Related areas

• Frozen Funds & Recovery – recovering held balances and disputed charges across Amazon surfaces
• Amazon Account Reinstatement – Plan of Action drafting and appeal strategy for deactivated accounts

Frequently asked questions

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

The timeline varies significantly by the complexity of the charge and the quality of the initial evidence package. A well-evidenced case filed through the correct Seller Central path can receive a substantive response within one to two weeks, though escalated cases or those involving post-deactivation balances typically take longer – sometimes several weeks to several months. Where a disbursement hold is running in parallel, the practical urgency argues for getting the evidence package right before the first filing rather than iterating through rejected cases.

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

The primary risk is filing under the wrong case category or on a non-factual basis, which produces a denial that narrows subsequent options. A second risk is treating the fee dispute and any concurrent disbursement hold as separate matters – if they are not resolved in parallel, the hold can persist well after the fee reversal is secured. Sellers also regularly miss the interaction between long-term storage fee charges and the final disbursement calculation on a closed account, which can result in an avoidable loss of recoverable funds.

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

Not in every case. A single, clearly documented charge against a live account, with strong Inventory Ledger evidence, can often be resolved without legal assistance. Attorney involvement adds the most value where the dispute is large, where Seller Central has already denied a case, where the fee charges are interacting with a disbursement hold or a broader account issue, or where the BSA dispute path is the appropriate escalation route. A preliminary review of the situation – before committing to a full engagement – is usually sufficient to answer this question in a specific case.

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. Our approach to long-term storage fee disputes and frozen funds recovery is evidence-led from the first day, and every engagement is structured around a fixed fee quoted after the initial review. To discuss your situation, email info@tutamenlaw.com.

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.

By James Whitlock – reinstatement & funds analyst, Tutamen. Published May 6, 2026.

Page authored by James Whitlock, Reinstatement & Funds Analyst, Tutamen.