Long-term storage fee dispute: a seller's checklist

When Amazon UK raises a long-term storage fee charge that looks wrong – or when a dispute over those fees triggers a payment hold – the practical damage starts immediately. Inventory and advertising bills keep coming due while the money sits in a reserve or disbursement queue that stops moving. The deactivation notice, if there is one, does not pause the cost of running the business.

TL;DRA long-term storage fee dispute on Amazon UK arises when Amazon charges fees for inventory that has been held at a fulfilment centre beyond a set threshold, and the seller believes those charges are incorrect, duplicated, or the product of a fulfilment error. Resolving the dispute requires documentary evidence, the right submission path in Seller Central, and a clear view of which balances are actually in play. The checklist below walks through the process phase by phase so you know exactly where you stand before you act.

This checklist covers five phases: confirming what has been charged and why; gathering the evidence that supports a dispute; filing correctly the first time; responding if the initial submission is rejected; and deciding when professional involvement changes the outcome. Work through each phase in order – skipping ahead is the most common reason a valid dispute fails.

Phase 1 – What is a long-term storage fee dispute, and what is actually being held?

A long-term storage fee dispute is a formal challenge to Amazon's charge for holding FBA inventory beyond the applicable storage duration threshold, where the seller has grounds to argue the charge was applied incorrectly or that underlying inventory data is wrong.

Before you file anything, you need to understand three distinct money pools that are often confused. The first is the fee charge itself – a debit applied to your Seller Central account. The second is any account-level reserve triggered because the charge pushed your balance into the negative or because Amazon flagged the account during a fee audit. The third is the disbursement hold – a separate mechanism that can pause all outgoing payments while a balance dispute is unresolved. In matters we handle, conflating these three pools is the single most expensive mistake sellers make, because each requires a different submission path and a different evidence set.

Ask yourself now: is the problem a fee I am disputing, a reserve I cannot explain, or a disbursement that stopped moving? The answer drives everything that follows. If you are unsure, pull the Payments – Transaction View report and the FBA Inventory Adjustments report from Seller Central before going to Phase 2.

• Log in to Seller Central and go to Reports > Fulfillment > Inventory Adjustments. Export the relevant date range.
• Go to Payments > Transaction View and filter by "Service Fees." Identify every long-term storage fee line item in the dispute window.
• Cross-reference the ASIN, quantity, and date on each fee line against the Inventory Adjustments report to check whether Amazon has already recorded a removal, disposal, or loss for the same units.
• Note whether the account has an open A-to-z Guarantee claim or chargeback that is contributing to the reserve independently of the storage fee.
• Confirm the account's disbursement status: is the next disbursement scheduled, delayed, or shown as "Payment not yet sent"?

Why this matters: Amazon's fee assessment and your reserve calculation run on different data pipelines. A fee can be wrong even if your reserve looks correct, and vice versa. Getting both reports before you file gives you a single coherent picture rather than a piecemeal one.

Phase 2 – Gathering the evidence that supports your dispute

A well-evidenced dispute submission is the only kind that moves – a narrative explanation without supporting documentation is typically dismissed at the first review, and that first rejection narrows what is still open.

The core evidence set for a long-term storage fee dispute on Amazon UK has four components. First, the fee itself: the transaction date, the ASIN, the number of units charged, and the per-unit rate. Second, inventory records showing the actual state of the units on the date the fee was applied – were they available, reserved, unfulfillable, or already subject to a removal or disposal order? Third, any earlier correspondence with Amazon acknowledging a fulfilment error or an inventory discrepancy. Fourth, the FBA Reimbursement report, which shows whether Amazon has already compensated you for lost or damaged units that were nonetheless charged a storage fee.

• Pull the FBA Manage Inventory Health report (under Inventory > Inventory Planning). This is the report Amazon itself uses to calculate long-term storage fee eligibility – your copy is the most direct evidence.
• Download the Reimbursements report from Reports > Fulfillment. Filter for the ASINs and date range in dispute. If a unit was reimbursed as lost or damaged, it should not also have attracted a long-term storage fee for the same period.
• Export any Removal Order records for the relevant ASINs. A removal order that was submitted before the fee assessment date is strong evidence that the inventory was no longer eligible to be charged.
• Pull the Received Inventory and Stranded Inventory reports. Stranded inventory – units held in the FC but not attached to an active listing – is often charged long-term storage fees even though the seller cannot sell those units without Amazon's co-operation.
• Save every report as a dated export with the filename including the date range. Amazon's case management system requires you to attach specific files, and mislabelled attachments are a common reason for a case being closed without review.
• If you submitted a removal order that Amazon failed to execute, locate the removal order ID and any Seller Central case IDs that document the failure. These are critical.

A pattern we regularly see in UK FBA disputes: the long-term storage fee was charged against units that were already flagged as unfulfillable following damage at the fulfilment centre. Those units generate an FBA reimbursement entitlement and a disputable fee – but the two claims need to be pursued in parallel, not sequentially. Starting only with the fee dispute and missing the reimbursement claim leaves money on the table even if the fee is reversed.

For a broader view of how balances and reserves interact across a closed or partially closed account, the guide on stranded inventory and held funds covers the mechanics in detail.

Phase 3 – Filing correctly the first time in Seller Central

The filing path matters as much as the evidence, because submitting a storage fee dispute through the wrong channel in Seller Central will route it to a team that has no authority to reverse fees – and you may not realize the case was mis-routed until the window has passed.

On Amazon UK, fee disputes are filed through Seller Central's Help system, not through the Account Health dashboard. The correct path is: Help > Contact Us > Selling on Amazon > Other Issues > FBA Issue > FBA Inventory > Other FBA Issue. Selecting the wrong branch – particularly "Account Health" or "Payments" without specifying the fee issue – often routes the case to a generalist team that will offer a standard acknowledgment and close the case without a substantive review.

• In the subject line, state the specific issue concisely: "Long-term storage fee dispute – [ASIN(s)] – [month/year]."
• In the body, open with the factual claim – not a narrative. For example: "Amazon charged a long-term storage fee of [unit count] units of ASIN [X] on [date]. Our records show these units were subject to a removal order submitted on [earlier date] / were recorded as unfulfillable by Amazon on [date]." Name the fact first; context second.
• Attach the Inventory Health report, the relevant Reimbursements report page, and any removal order confirmation. Keep the attachment set to the minimum needed – a case with 20 attachments is harder to process than one with four clear exhibits.
• Do not submit multiple cases for the same dispute. Duplicate cases are a compliance flag and can cause all related cases to be merged and deprioritized.
• Note the case ID immediately. Log every case ID, the date opened, and the team that responded. If a case is closed without resolution, the ID is required to escalate.
• Set a calendar reminder for the expected response window. If Amazon has not responded substantively within the window, a follow-up message in the same case thread (not a new case) is the correct action.

The first submission is also the moment to decide whether this is a single-ASIN dispute or a systemic one affecting many ASINs across multiple fee cycles. If the error is systemic – for example, a fulfilment centre receiving error that caused fees to apply across a product range – that needs to be stated in the opening submission, because a case filed as a single-unit dispute will only generate a single-unit resolution even if the broader pattern is accepted.

The steps above describe the standard path. Your situation turns on the exact wording of the fee notices, the account history, and whether there are parallel holds on disbursements – which is what we review first. If you would like a read on your specific position before filing, email info@tutamenlaw.com.

Phase 4 – If the first submission is rejected or ignored

A rejected or closed case is not the end of the dispute – but the response to it needs to be different from the original submission, not a re-send of the same content.

When a case is closed without a substantive resolution, the first question is why. Amazon's automated case-closure messages use standard language that rarely identifies the actual gap. In the matters we handle, the three most common real reasons for closure at this stage are: the evidence set was incomplete (the critical report was missing or covered the wrong date range); the case was mis-routed and was never seen by a fee-specialist team; or the dispute window for that specific fee cycle has a time limit that has now passed.

• Read the closure message carefully for any reference to a specific report, an account restriction, or a pending verification. These are actionable signals.
• Pull the exact fee line from the Transaction View report again and confirm the date. Some fee cycles have a formal dispute window – if you are near or past that window, the escalation path changes.
• If the case was clearly mis-routed, reopen using the correct path from Phase 3 and reference the previous case ID: "This is a fee dispute, not an account health issue. The prior case [ID] was closed without review by the correct team."
• If the evidence was incomplete, do not resubmit with the same set plus one new document. Rebuild the submission from the Phase 2 checklist with the full set, correctly labelled.
• Escalate to the Seller Support leadership team via the "escalate this case" option if the case has been closed twice without substantive engagement. This option is not always visible; if it is not available, a concise written escalation in the case thread addressed to "Seller Support management" creates a documented record.
• Consider whether the matter has reached a point where the BSA's dispute-resolution provisions are the more appropriate route. The Amazon Business Solutions Agreement sets out the process for formal disputes between Amazon and sellers – the path that applies depends on the BSA version governing the account, which we check first in any matter.

If an earlier appeal or case submission already came back rejected or closed, a second professional review can identify the specific gap and what remains open. Email info@tutamenlaw.com with a summary of where the case stands.

One pattern worth flagging: sellers who experience a long-term storage fee dispute at the same time as a broader account review sometimes find that the fee case and the account review are treated as related by Amazon's systems, even when the underlying issues are entirely separate. In that situation, resolving the fee case first – or in parallel rather than sequentially – can materially shorten the overall disbursement hold. The step-by-step guide on closed-account balance recovery explains how these concurrent holds interact.

Phase 5 – Decision points, trade-offs, and when professional involvement matters

The decision to handle a long-term storage fee dispute alone or with legal support depends on the size of the disputed amount, the complexity of the account history, and whether there is a parallel disbursement hold or account deactivation in play.

There is a widely held belief that funds held in connection with a deactivated account are effectively gone. That is the myth. In the matters we handle on Amazon UK, disbursement holds linked to fee disputes are regularly resolved after a well-structured submission – sometimes weeks after an initial rejection. The money is held, not forfeited, and the distinction matters enormously.

Here is a realistic decision framework. If the dispute involves a single ASIN, a clearly documented fulfilment error, and no parallel account issues, a seller with the right reports can often resolve it without legal support – Phases 1 through 4 above cover the process. If the dispute involves multiple ASINs or fee cycles, a disputed amount that is material to the business, a concurrent disbursement hold or reserve that is not moving, or a rejection that references policy language rather than just missing evidence – those are the conditions where professional involvement typically changes the outcome, not because the process is different but because the evidence construction and submission framing require a practitioner's read.

• Assess: is the disputed amount material to the business's cash flow, or is it a nuisance charge? The answer affects how much time and resource is proportionate.
• Assess: is there a parallel disbursement hold or account-level reserve that stops all outgoing payments, independent of the fee dispute? If so, that needs to be mapped and pressed separately.
• Assess: is the account's disbursement cycle currently showing any flags in the Account Health Rating? A fee dispute that escalates to an account health issue is a different problem.
• Assess: has Amazon raised any identity or verification (KYC) request that is blocking the case? Verification holds are procedurally separate and need to be resolved before fee disputes can be actioned.
• Assess: does the dispute overlap with an FBA reimbursement claim for lost or damaged inventory? If so, the two tracks should run in parallel – pursuing one and pausing the other extends the overall timeline and the period during which the money is unavailable.

If the notice you received references the Amazon Business Solutions Agreement, cites specific policy provisions, or has triggered a reserve that is affecting the full disbursement cycle – not just a single fee – the complete guide to frozen funds recovery covers the broader landscape and the legal levers that apply.

A mid-market electronics accessories FBA seller on Amazon UK (winter 2025) came to us after a long-term storage fee charge was applied to a range of units that had been flagged as unfulfillable by Amazon's own FC damage report. The seller had filed two cases that were both closed without substantive engagement. We reconstructed the inventory adjustment timeline, identified a parallel FBA reimbursement entitlement for the same units, and submitted both the fee dispute and the reimbursement claim with a consolidated evidence set. Both the fee reversal and the reimbursement were processed, and the disbursement hold lifted within weeks of the combined submission.

A second matter: a consumables FBA seller on Amazon UK (summer 2025) had a long-term storage fee dispute that was, on its face, a routine single-ASIN error. When we reviewed the account, the fee had been charged against units under a stranded-inventory flag that the seller had not been able to clear because of a category-approval issue – a separate problem that Amazon had not linked to the fee case. We cleared the stranded flag first, then disputed the fee on the basis that the units were not eligible for long-term storage charges while under a stranded status the seller could not resolve. The fee was reversed.

Related areas

• Frozen Funds & Recovery – disbursement holds, account reserves, and FBA reimbursement claims on Amazon US and UK
• Account Reinstatement – Section 3 deactivation, Plan of Action, and related account issues affecting disbursements

Frequently asked questions

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

Resolution timelines vary significantly depending on the complexity of the dispute and whether a disbursement hold is running in parallel. A straightforward single-ASIN fee dispute with complete documentation can move within a few weeks of a correctly filed submission. A multi-ASIN or multi-cycle dispute, or one that involves a concurrent reserve or account review, typically takes considerably longer – often several months if there are rejection cycles before the matter is resolved. The first submission's quality has the biggest single effect on the overall timeline, because a rejected or mis-routed first case adds delay that a stronger opening would have avoided. In matters we handle, the most time-consuming phase is almost always the reconstruction of the inventory adjustment evidence, not the filing itself.

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

The primary risk is a mis-framed or incomplete first submission that is rejected and narrows what remains available. Amazon's case-closure process treats repeated submissions on the same issue as a signal of nuisance rather than merit, and that reputation effect is real. A second risk is missing a parallel FBA reimbursement claim for the same inventory – sellers who pursue only the fee dispute and overlook the reimbursement entitlement leave that second balance unaddressed even when the fee is reversed. A third risk, specific to Amazon UK, is the interaction between the fee dispute and the account's disbursement cycle: a fee that pushes the account into a negative balance can trigger a reserve that outlasts the fee dispute itself, and that reserve needs separate action. Missing that distinction is common and costly.

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

Not always. A single-ASIN dispute backed by clear inventory records and a straightforward fulfilment-error fact pattern is something a well-prepared seller can resolve through Seller Central without legal support, provided the phases above are followed carefully. Legal involvement becomes more likely to change the outcome when the disputed amount is material to the business, when there are concurrent disbursement holds or account reviews, when prior submissions have been rejected and the reasons are unclear, or when the dispute touches the Amazon Business Solutions Agreement's dispute-resolution provisions. The honest answer is that the threshold is the complexity of your account situation, not the mechanics of the fee dispute itself. If you are unsure where your situation falls, a short review costs much less than a failed second attempt.

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 Amazon UK frozen-funds practice covers the full range of disbursement holds, FBA reimbursement claims, and fee disputes – including matters that have already been through one or more rejection cycles. 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.