Long-term storage fee dispute: your questions answered on Amazon UK

TL;DRA long-term storage fee dispute on Amazon UK arises when a seller believes Amazon has charged incorrectly for inventory held in a fulfilment centre beyond the standard storage threshold – or when those charges have triggered or compounded a funds hold that blocks disbursement. The dispute is not simply a billing question: it intersects with reserve policy, account health, and in some cases a broader deactivation. Understanding the correct procedural path is the first decision that matters.

This page answers the questions sellers most often bring to us the day they discover the problem: what the charge actually is, how it is calculated in principle, what Amazon's internal processes look like from the outside, and where the real decision points sit. If the money is held while your inventory bills and advertising invoices keep coming due, the pressure to act quickly is real – but acting without a clear read of the situation tends to make the position worse, not better.

Below, each section addresses one cluster of questions directly. The first sentence of each section is the direct answer; the rest fills in the procedural and commercial context.

What is a long-term storage fee dispute on Amazon UK – and what triggers it?

A long-term storage fee dispute is a formal challenge to charges Amazon has applied to inventory stored in its UK fulfilment network beyond the defined storage threshold, either because the charge appears incorrect in amount, because it was applied to inventory that should have been removed or disposed of before the assessment date, or because it has combined with other holds to freeze a disbursement the seller was expecting.

Amazon's FBA programme charges sellers for storage on a recurring basis. Charges are assessed on inventory that exceeds the storage threshold at the measurement date – typically assessed monthly – and are calculated against the volume or units held, depending on the product category. The long-term rate applies once inventory has been held beyond the defined threshold period. When a seller believes the charge is wrong, the grounds are usually one of three things: the inventory count used was inaccurate; inventory that had already been marked for removal or was the subject of a reimbursement claim was still included; or the charge was applied after a system error that mislabelled units as unsold.

The complexity that sellers consistently underestimate is this: a disputed long-term storage charge rarely sits in isolation. In matters we handle on Amazon UK, the charge is frequently one line in a broader reserve or balance adjustment, and it is the aggregate balance – not the single fee line – that is blocking the next disbursement. That means resolving the storage dispute alone may not release the funds; you may also need to address the reserve calculation and any outstanding A-to-z Guarantee or chargeback provisions sitting in the same ledger.

What typically triggers the dispute on Amazon UK is the disbursement cycle. A seller notices that the payout is lower than expected, checks the account-level transaction history, and finds a large storage fee charge has been applied. Alternatively, an account deactivation occurs and the seller, reviewing the held balance, discovers that long-term storage charges have been running unaddressed for several months, quietly eroding the disbursable amount. In the second scenario the dispute has to run in parallel with – or after – the reinstatement or funds-recovery process. For a grounding in how that broader funds picture fits together, our guide on frozen funds recovery for sellers explains the full map.

How does Amazon UK calculate the charge – and where do errors actually occur?

Amazon calculates long-term storage fees by measuring the units held in its fulfilment network on a set assessment date each month, identifying those that have been in storage beyond the threshold period, and applying the applicable per-unit or volumetric rate for that product category – but errors in the inventory data Amazon holds can produce charges that do not reflect reality.

The most common sources of dispute we see on Amazon UK fall into a recognizable pattern. First, inventory that the seller submitted a removal order for before the assessment date sometimes remains in the system as "available" because the removal order was not processed in time, or was cancelled by a fulfilment centre backlog. The units are, in practice, not sellable and not in the seller's control – but they are still counted for the fee. Second, units subject to an open FBA reimbursement claim (for lost or damaged inventory) may still appear in the storage count even though Amazon has effectively taken possession of them. Third, in multi-marketplace accounts where stock is shared between Amazon UK and other EU fulfilments, cross-border stock movements sometimes leave a unit's "home" fulfilment centre recorded incorrectly.

Sellers also encounter a category of error that is harder to identify without a transaction-by-transaction reconciliation: double-counting. This occurs when a unit is returned by a customer, recorded as a separate unit added back to inventory, and then assessed as though it were a newly received unit with a fresh clock start. The practical effect is that the system treats one physical unit as two for storage-assessment purposes.

It is worth understanding what Amazon's own internal processes can and cannot do at this stage. Seller Central provides a storage fee report and an inventory age report. Both are useful as a starting point. Neither is audited in real time, and the data in each report can lag the actual fulfilment-centre state by a meaningful window. When we are reconstructing a storage fee dispute, we cross-reference those reports against the fulfilment shipment data, the removal-order history, and the reimbursement ledger – because a challenge that rests only on the surface-level report is frequently rejected on the grounds that the report is not an audit document. Our separate piece on why stranded inventory and held funds happen and how sellers respond sets out that reconstruction approach in detail.

What is the procedural path for challenging the charge – and what are the realistic options?

The procedural path for a long-term storage fee dispute on Amazon UK runs through Seller Central's case-management system, and the realistic options are: a self-service case submission with supporting data; escalation to a specialist internal team if the first-level response is a template refusal; and, where the dispute connects to a broader funds hold or account deactivation, a parallel or subsequent funds-recovery action that addresses the entire balance.

Step one is building the evidentiary base. That means pulling every relevant report – inventory age, storage fees, reimbursements, removals, and the transaction-level detail – and laying them side by side to identify where the discrepancy originates. A case submitted without this underlying reconciliation typically receives a response that cites the report Amazon itself generated, which is circular: Amazon says the charge is correct because the report says it is.

Step two is the case submission itself. The case should state the specific assessment date, the specific units in dispute, the grounds for challenge (removal order timing, reimbursement overlap, system error, or data lag), and the supporting documentation. Precision matters: a submission that says "the charge seems too high" invites a template response. A submission that says "units [ASIN] were subject to a removal order submitted on [date], as shown in removal order [reference], and should not have been included in the [date] assessment" creates a specific factual question the agent must address.

Step three is the first-level response. Amazon UK agents handling storage fee cases typically have limited authority to issue credits. If the submission is straightforward and well-documented, a credit may be issued within a short period. If the first-level response is a refusal or a partial adjustment, escalation becomes necessary. Escalation outside the standard case system requires a clear articulation of the specific policy or system error that produced the wrong charge – and it needs to be routed to a team with authority to adjust the storage ledger, not just to customer service.

Step four is the hardest to navigate alone: where the storage fee dispute connects to a frozen balance or disbursement hold. In that scenario, resolving the fee dispute does not automatically unblock the funds. The reserve policy and any other open provisions in the account may still be holding the disbursable balance below zero or near zero. The route to fund release involves a separate – though related – process, addressed in our step-by-step piece on closed account balance recovery. The practical decision point for sellers is whether to pursue the storage dispute alone (faster, limited scope) or to run a full balance reconciliation that addresses every line item holding the disbursement back (slower, higher potential recovery).

What is the CTA point for sellers at this stage? The steps above describe the standard path. Your situation turns on the exact data Amazon is using, the account history, and whether any related holds are compounding the problem – which is what we review first.

If you are at the point of understanding your options and need a read on the dispute, email info@tutamenlaw.com for a short initial review.

What does a first-level Amazon rejection actually mean – and what can still be done?

A first-level rejection of a storage fee dispute case on Amazon UK does not close the matter; it typically means the agent lacked the authority or the information to issue the credit, and the case needs to be rebuilt and escalated with more precise supporting evidence.

In matters we handle, first-level rejections follow a recognizable pattern. The response either states that the charges are correct per the system data (without addressing the specific error the seller raised), or it offers a partial credit that does not cover the full discrepancy. Neither response is a final determination. Amazon UK's internal case system has multiple tiers, and a well-constructed second submission that directly addresses the stated reason for rejection – or that explicitly notes the agent did not address the specific factual question – has a realistic chance of escalation to a team with broader credit authority.

Where sellers lose ground after a first rejection is by resubmitting the same case with additional frustration but no new supporting data. The second submission needs to be structured differently: it should acknowledge the first response, identify the specific point the agent did not address, and add any supplementary documentation that closes the remaining evidentiary gap. If the first submission showed the removal order was submitted before the assessment date, the second submission should also show that the units were no longer available-for-sale in the inventory ledger at that date – two data points instead of one.

There is also a point at which escalation through the standard Seller Central case path has run its course. At that stage, the options shift to the broader dispute-resolution mechanism available under the Amazon Business Solutions Agreement (BSA). The BSA contains a dispute-resolution path, and the applicable version for the account determines what that path looks like. We check the BSA version first before advising on whether and how to use it – because, as noted in Appendix X of our practice standards, the arbitration and dispute-resolution terms in the BSA are volatile and the correct framing depends on the version binding the specific account.

One practical note on timing: there are informal windows within which the dispute is more tractable. In the period immediately after a charge is applied, the data underlying it is closer to the live fulfilment-centre state. As months pass and inventory is moved, consolidated, or disposed of, the audit trail becomes harder to reconstruct and the case becomes harder to win. Sellers who delay because they are not sure the dispute is worth pursuing often find that the evidentiary position has deteriorated by the time they engage.

How do long-term storage charges interact with a frozen balance or account deactivation?

When an Amazon UK account is deactivated, long-term storage charges do not stop – and in some cases they accelerate the erosion of the held balance during the period when the seller cannot actively manage inventory – which means a storage fee dispute and a funds-recovery claim may need to run together to protect the full disbursable amount.

This is one of the dimensions of this problem that sellers least expect. The assumption is that once the account is deactivated and the balance is frozen, the meter stops. In practice, FBA storage fees continue to accrue against inventory that Amazon continues to hold – because the fulfilment centres hold the physical stock regardless of the account status. If the seller cannot create removal orders while the account is deactivated (which is frequently the case in a Section 3 deactivation), the inventory sits, and the charges accumulate against the same balance that Amazon is holding.

The commercial effect is not abstract. The money is held while inventory and advertising bills keep coming due outside the Amazon system, and inside the system the disbursable balance is being reduced by storage charges the seller has no practical ability to prevent. A seller who was expecting a five-figure disbursement in thirty days may find, ninety days later, that the storage charges have materially reduced that balance – and that some of the reduction is attributable to charges that would not have been levied if the account had been active and the seller had been able to manage inventory normally.

The myth that held funds are gone for good once an account is deactivated is exactly that – a myth. Disbursable balances are recoverable, and incorrectly applied storage charges are challengeable, even after deactivation. What changes is the procedural complexity: the storage dispute and the reinstatement or funds-recovery process have to be coordinated, not run sequentially, because the ledger is still moving.

In matters we handle on Amazon UK where this overlap exists, we map every held balance and reserve, press the disbursement and reimbursement claims, and run the storage fee dispute in parallel – so the full recoverable amount is identified and pursued within the same engagement rather than discovered piecemeal.

What are your decision points and how do you choose the right path?

The central decision a seller faces in a long-term storage fee dispute on Amazon UK is whether to treat it as a standalone billing correction or as part of a broader funds-recovery action – and that choice turns on whether the storage charge is the only thing holding back the disbursement, or whether it is one of several contributing holds.

If the account is active, the disbursement is otherwise flowing, and the dispute is a discrete charge on a specific assessment date, a targeted Seller Central case – built correctly and with full supporting documentation – is often the right and proportionate first step. The cost and time of a broader engagement may not be warranted for a dispute that, once the evidentiary basis is clear, Amazon can resolve internally.

If the account is deactivated, or if the balance has been frozen for reasons that include but go beyond the storage charge, the standalone case approach almost certainly leaves money on the table. In that scenario, the decision matrix looks like this: if the hold is attributed solely to a storage fee overcharge → build the targeted case, escalate on rejection, and use the BSA dispute path if escalation fails. If the hold combines a storage charge with a reserve adjustment, outstanding A-to-z claims, or a post-deactivation balance – → a full balance reconciliation and coordinated funds-recovery action is the more effective route. If the storage charge has been applied during a deactivation and the account has not yet been reinstated → reinstatement and storage dispute may need to run in parallel, and the order of operations matters because getting the account back changes what removal and inventory management options are available.

A practical signal: if the discrepancy between what you expected to receive and what Amazon shows as disbursable is significantly larger than the storage fee line on its own, the storage dispute is probably not the whole picture. That gap is worth mapping before you commit to a filing strategy.

A home-goods FBA seller on Amazon UK (winter 2025) came to us after noticing that a long-term storage fee applied during a seasonal slow period had been calculated against units that were already the subject of open removal orders. The first-level Seller Central case had been rejected. We reconstructed the removal order timeline, cross-referenced the inventory age report against the removal-order submission confirmation, and refiled with a precise date-matched case that identified the specific units and the specific error. The credit was issued on second escalation, and the corrected balance was included in the next disbursement cycle.

A second scenario: a kitchenware brand selling on Amazon UK (spring 2026) came to us after a deactivation in which the held balance was lower than expected. The account history showed long-term storage charges had been accumulating during a multi-month deactivation period, against inventory the seller had been unable to remove. We mapped the full balance, challenged the storage charges that had accrued post-deactivation on grounds of inventory management impairment, ran the FBA reimbursement claims on units lost during the same period, and worked the reinstatement in parallel. The disbursement, when it came through, reflected the corrected balance including the challenged storage lines.

Related areas

• Frozen Funds & Recovery – full practice area for disbursement holds, balance disputes, and reimbursement claims
• Amazon Account Reinstatement – for cases where the storage dispute is connected to a deactivation

If a first appeal or filing already came back rejected, a second read can find the specific reason it failed and what, if anything, is still open. Email info@tutamenlaw.com and describe what has been filed so far.

Frequently asked questions

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

Timelines vary materially depending on the complexity of the dispute, whether the first-level case succeeds or requires escalation, and whether the storage charge is connected to a broader funds hold or deactivation. A well-documented, straightforward dispute involving a discrete charge on an active account can sometimes be resolved through the Seller Central case system within a few weeks. Where escalation is needed, or where the dispute runs alongside a reinstatement or full balance-recovery action, the process typically takes several weeks to a few months. The strongest predictor of a shorter timeline is the quality and precision of the initial submission: underdocumented cases that require multiple rounds of clarification extend the process significantly. If the account is deactivated, the overall timeline is also shaped by how quickly the reinstatement or funds-release process moves, since the two are often linked.

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

The primary risk is a well-intentioned but underpowered submission that uses the formal filing opportunity without resolving the underlying factual question – which tends to harden Amazon's position rather than open it. A first rejection that could have been avoided with better documentation creates a harder path on the second attempt. The second risk is scope: sellers handling the dispute alone often focus on the storage charge in isolation and miss other holds or charge errors in the same ledger, leaving recoverable amounts unaddressed. Third, where the dispute connects to an account deactivation, handling the storage challenge separately from the reinstatement process can create sequencing problems – for example, submitting a storage dispute while a Plan of Action is pending can, in some cases, complicate the account health review. Understanding which process to run first, and how to coordinate them, is the practical value of getting a specialist read before filing.

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

Not always. For a straightforward, isolated storage fee charge on an active account, a seller who is organized, comfortable reading Amazon's inventory reports, and willing to invest the time in a detailed, data-supported case submission can often handle the matter through Seller Central without legal assistance. The case for engaging a specialist increases sharply when the dispute has already been rejected once; when the storage charge is one element of a larger frozen balance or deactivation; when the amount at stake is significant relative to the business's monthly cash flow; or when the dispute has a BSA or arbitration dimension. In those scenarios, the cost of a specialist is generally small relative to the amount in dispute and to the risk of foreclosing options through a poorly structured submission. Tutamen's work on storage fee disputes is attorney-led and confidential, with fees quoted up front after a short review – so the first step is understanding what you are dealing with before committing to a course of action.

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.

James Whitlock is Tutamen's reinstatement and funds analyst. He works with sellers across Amazon's global surfaces on account deactivations, held balances, storage fee disputes, and FBA reimbursement claims. Our practice is grounded in attorney-led review and confidential instruction, with fixed fees quoted up front after an initial read of the matter.

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.

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