Inside long-term storage fee dispute: the seller's real options

TL;DRA long-term storage fee dispute on Amazon UK arises when a seller believes Amazon has charged storage fees incorrectly – wrong inventory quantities, miscategorised units, or fees applied after removal orders were already submitted. The money leaves the disbursement balance silently, and by the time a seller notices, several charge cycles may have passed. The realistic options range from a structured Seller Central reimbursement claim to a formal Notice of Dispute under the Business Solutions Agreement (BSA), depending on how much is at stake and how far the standard process has already failed.

This analysis covers what a long-term storage fee dispute actually involves on Amazon UK, the procedural path, and the decision points that determine which route is worth taking. It is written for sellers whose money is held while inventory and advertising bills keep coming due – and who need a clear-eyed account of what is open to them, not a list of things that rarely work.

What is a long-term storage fee dispute, and why does it keep catching Amazon UK sellers out?

A long-term storage fee dispute is a formal challenge to Amazon's calculation or application of the fees it charges for inventory held in a fulfilment centre beyond the standard storage period. On Amazon UK, these fees apply to units that have been in an FBA warehouse for an extended period, assessed periodically in line with Amazon's then-current fee schedule. The dispute arises when the charge does not match the seller's own inventory records – or when Amazon charges for units the seller believes were already removed, returned, or disposed of.

In matters we handle, the most common root causes fall into a handful of categories. First, a removal order is submitted close to the fee assessment date; the units are physically still in the warehouse when Amazon runs its snapshot, so the fee fires even though the seller acted in time. Second, inventory is miscounted – Amazon's system shows more units than the seller's own records, because lost or damaged units that should have triggered an FBA reimbursement were never reconciled. Third, fee category errors: units assigned to an oversized tier when the actual dimensions place them in a standard tier, resulting in a higher rate.

What makes this commercially damaging is the compounding effect. Long-term storage fees accumulate over assessment cycles. A seller who does not catch the discrepancy in the first cycle will see the disputed amount grow, and each new charge is debited directly from the disbursement balance. That means the problem intersects directly with the broader frozen funds dynamic: when the total held or wrongly deducted balance grows large enough, it can push an otherwise-healthy disbursement into a shortfall or trigger a reserve threshold. The inventory and advertising bills do not pause. That asymmetry – Amazon deducts in real time, while a reimbursement claim can take weeks or longer – is the core of the operator problem.

A further complication on Amazon UK specifically is the regulatory context. As enforcement automation has tightened and Amazon's own fee infrastructure has grown more complex, sellers are increasingly dealing with automated charge decisions that are hard to contest through a single ticket. The Platform-to-Business (P2B) Regulation, which applies across the EU and was retained in UK law post-Brexit, gives sellers certain transparency rights regarding the terms under which fees are calculated and applied. That legal context matters when escalation becomes necessary.

How does the fee assessment mechanism actually work, and where does it go wrong?

Amazon calculates long-term storage fees based on a periodic inventory snapshot – a specific date on which it counts units present in the fulfilment centre and applies the applicable rate per cubic foot or per unit depending on the category. The fee is then debited from the seller's account balance, not invoiced separately in the conventional sense. This creates the first point of failure: sellers who are not actively monitoring Seller Central's inventory age report and the Payments report can miss the deduction entirely until it accumulates.

The snapshot date is the critical variable. If a removal order is submitted before the snapshot date but fulfilment centre processing has not completed, Amazon's system may still record those units as present. The seller acted correctly; the charge fires anyway. In our practice, removal-order timing disputes represent a significant share of the long-term storage fee claims we see from Amazon UK FBA sellers. The resolution path is documentary: the seller needs the removal order confirmation with its timestamp, the inventory event log, and ideally the shipment tracking showing the units in transit.

Miscounted inventory is a separate and often larger problem. When Amazon loses or damages a unit inside a fulfilment centre, the unit may remain on the inventory ledger as "available" or "unfulfillable" for an extended period before the disposition event is recorded. During that window, the seller is paying storage fees on a unit Amazon effectively controls and cannot return to the seller in sellable condition. The correct remedy is an FBA reimbursement claim for the lost or damaged unit, which also removes the unit from the storage fee calculation going forward. Many sellers attempt to resolve these two things separately – the storage fee dispute in one ticket, the reimbursement in another – when they are causally linked and should be presented together.

Category and dimension errors are less common but tend to produce higher per-unit overcharges. Amazon's product detail page dimensions determine the fee tier. If the detail page carries incorrect dimensions – either because the brand owner filed them incorrectly or because Amazon's own catalogue data is stale – every unit assessed at the wrong tier produces an overcharge. Correcting the detail page may not retroactively fix already-debited fees; a separate reimbursement claim is required for the historical period.

What is the realistic procedural path for disputing long-term storage fees on Amazon UK?

The procedural path has three stages, and most sellers who fail do so by jumping to stage three without completing stage one properly, or by treating stage one as a one-shot process when it is a documentation-intensive iterative one.

Stage one: internal Seller Central reconciliation and reimbursement claim. The starting point is the FBA inventory reports: the Inventory Reconciliation report, the Inventory Adjustment report, and the Long-Term Storage Fee report. These three together tell the complete story of what was in the warehouse, what left, and what was charged. The reimbursement claim filed through Seller Central should reference specific ASIN, FNSKU, removal order confirmation numbers, and fee assessment dates. It should not be a general complaint; Amazon's Seller Support system is pattern-matched, and a specific, document-supported claim moves faster than a narrative.

Stage one can involve multiple case submissions if Amazon's first response denies or partially resolves the claim. Each denial should be read carefully for its stated reason, because Amazon's denial logic tells the seller which documentation gap to address in the next submission. In matters we work on, sellers frequently bring us cases after receiving two or three form denials – and the issue is usually that the prior submissions described the problem without attaching the specific event-log evidence that makes the case conclusive.

For straightforward cases – a single removal order timing issue, a modest amount, clean documentation – this stage should resolve the matter. But stage one has a practical ceiling. Amazon's Seller Support system is not designed for complex multi-cycle, multi-ASIN disputes. When the disputed amount is material, when the pattern spans several assessment cycles, or when the root cause involves a systemic Amazon error (e.g., a catalogue dimension problem affecting many units), internal Seller Central escalation often stalls.

Stage two: structured pre-dispute escalation. At this stage, the seller (or their representative) prepares a formal written analysis of the discrepancy, cross-referencing the inventory event log against the fee charge history, and submits it through Amazon's escalation route. On Amazon UK, this may include the Seller Central "Contact Us" escalation to a specialist team, or a direct written communication to Amazon's Seller Performance or Payments teams. The tone and structure of this communication matters: it should read as a legal-quality memorandum, not a frustrated support ticket.

The P2B Regulation's transparency rights are relevant here. A seller has the right to request a reasoned explanation of how a specific fee was calculated. Invoking that right explicitly, in writing, changes the nature of the communication – Amazon is operating under a legal obligation to respond meaningfully, not to issue a form reply.

Stage three: formal dispute resolution. If the matter remains unresolved after stages one and two, the seller's options depend on the amount at stake and the BSA version applicable to the account. The BSA contains a dispute-resolution mechanism, and the path under that mechanism – whether it involves informal dispute resolution, a Notice of Dispute, mediation, or a different process – depends on the specific agreement terms that apply to the account. We always check the applicable BSA version first; this is not a step to skip. For significant sums, formal arbitration under the American Arbitration Association (AAA) rules may be available. For smaller but still material amounts, a pre-arbitration demand letter can produce resolution without the cost of full proceedings.

One further option on Amazon UK, distinct from the BSA route, is a complaint under the P2B Regulation's internal complaint-handling system. Amazon is required to operate such a system, and filing a formal complaint through it creates a record that may support escalation to the UK's relevant competent body if needed.

For a broader grounding in how funds disputes work at the account level, the analysis at frozen funds recovery: the complete guide for sellers sets out the structural context within which storage fee disputes sit.

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

The first decision is whether the claimed amount justifies the time and documentation cost of a full dispute. This sounds obvious, but sellers regularly either over-invest in small discrepancies (spending more in time and professional fees than the disputed amount) or under-invest in large ones (treating a material overcharge as just a support ticket). A rough calibration: if the disputed fee total is a few hundred pounds or less and the root cause is a single, documentable event, stage one with clean documentation is usually the right and sufficient answer. If the total is in the thousands – or if the charge pattern spans multiple cycles and intersects with a broader account or funds issue – stage two and potentially stage three are proportionate.

The second decision concerns timing. Long-term storage fee disputes are not indefinitely open. Amazon's reimbursement window for FBA claims is not unlimited, and a seller who delays investigation is working against their own position. Acting early – as soon as a discrepancy appears in the Payments report or the Long-Term Storage Fee report – preserves options. Waiting until a disbursement hold or an account health issue surfaces, and then trying to unwind several cycles of fee disputes simultaneously, is a materially harder case to make.

The third decision is whether to run this alone or with representation. The AUDIENCE_MYTH here is worth addressing directly: held or wrongly deducted funds are not gone for good once a dispute begins. We regularly see sellers who have written off material amounts as lost because Amazon denied a first or second claim, when the real problem was a documentation gap rather than a case with no merit. The question is not whether to accept a denial but whether there is a specific evidentiary reason the claim was denied – and whether that reason can be addressed.

That said, professional representation is not always necessary. A single-cycle, single-ASIN dispute with clean documentation is something a methodical seller can often resolve through stage one. Representation adds the most value when: the dispute spans multiple cycles; the root cause involves linked issues (an FBA reimbursement claim and a storage fee dispute arising from the same lost-unit event); the matter has already been denied twice or more; or the amount justifies the cost of stage three proceedings.

To understand where a storage fee dispute sits within the wider pattern of stranded and held inventory problems, the analysis at inside stranded inventory and held funds: the seller's real options covers the intersection of these issues in detail.

The steps described here apply to ongoing accounts. If the account itself has been closed and the question is whether the disputed fee amounts can still be recovered, the considerations in closed account balance recovery: is this the end? are directly relevant.

Bridge: The stages above describe the standard path. Your situation turns on the exact assessment dates, the documentation in your inventory event logs, and whether a linked FBA reimbursement claim has already been filed – which is what we review first.

To get a read on your specific dispute, email info@tutamenlaw.com.

Micro-case one: removal order timing on Amazon UK

A kitchenware FBA seller on Amazon UK (winter 2025) came to us after receiving a long-term storage fee charge for a batch of units she had submitted a removal order for prior to the assessment date. Amazon's Seller Support had denied the reimbursement request twice, citing the units as "present" on the snapshot date. We reviewed the removal order confirmation timestamp, the inventory adjustment log, and the outbound shipment record from the fulfilment centre. The evidence established that the removal order had been accepted and the units were in outbound processing before the snapshot ran; the delay was on Amazon's processing side, not the seller's. We prepared a structured written submission cross-referencing each data point, escalated through the specialist team route, and the fees were credited to the seller's account balance.

What the escalation route looks like when internal processes fail

When Seller Central denials pile up and the amount at stake justifies a more formal approach, the escalation route on Amazon UK has a specific shape. Understanding it in advance is the difference between an efficient resolution and months of circular support tickets.

The first escalation step within Amazon's own system is to move the case from general Seller Support to a specialist team – typically the Payments or Seller Performance team – with a formal written submission rather than a chat or phone contact. The written submission should be structured as: (a) a factual summary of the discrepancy with specific dates and amounts; (b) the documentation relied on, referenced by attachment; (c) the specific credit amount being claimed; (d) the legal basis if relevant (P2B transparency rights, BSA terms). A submission in this form is harder for Amazon to dismiss with a form response.

If specialist team escalation does not resolve the matter, and the amount justifies it, the seller's next step is a Notice of Dispute under the BSA. This is the formal opening of the dispute-resolution process, and it is a necessary procedural prerequisite before any further steps can be taken. The notice should be specific: the amounts, the charge dates, the documentation, and the remedy sought. Ambiguous notices often result in a generic response that does not advance the matter.

The path from Notice of Dispute to resolution depends on the BSA version applicable to the account. As noted above, the dispute-resolution mechanism is a volatile fact – the terms have changed over time and can differ between account types. We check the applicable version first because the procedural obligations and timelines are different depending on which version governs. What we can say durably is that a well-framed Notice of Dispute, backed by the documentation from stage one, gives a seller significantly more leverage than a Seller Central ticket, because it places Amazon on a formal response obligation under its own contractual terms.

For sellers on Amazon UK, the P2B Regulation complaint route runs in parallel and does not require the BSA dispute-resolution path to be completed first. These two routes can support each other: a P2B complaint creates a documentary record of Amazon's response (or non-response) to a transparency request, which in turn strengthens the factual record for a BSA-based claim.

Micro-case two: multi-cycle fee dispute linked to FBA reimbursement claim

A health-and-beauty seller on Amazon UK (spring 2026) had accumulated long-term storage fees across three assessment cycles on a group of units that Amazon had marked as "unfulfillable" following a warehouse damage event. The seller had filed an FBA reimbursement claim for the damaged units but had not connected the storage fee dispute to the same underlying event. Amazon's reimbursement team had partially resolved the damage claim while the storage fees continued to accrue. We reconstructed the complete inventory event timeline – the damage event, the reimbursement claim history, the storage fee assessment dates, and the inventory ledger entries – and reframed the combined claim as a single matter arising from one root cause. The integrated submission was filed through the specialist escalation route, resulting in a credit that addressed both the unresolved portion of the reimbursement and the storage fees that should not have accrued post-damage-event.

What sellers consistently get wrong when they handle this alone

The most common error is treating each denial as a final answer rather than a data point. Amazon's denial messages are often formulaic, but the reason code embedded in the response – if the seller reads it carefully – usually points to a specific documentation gap. A denial citing "inventory records do not support the claim" means Amazon's system did not receive (or did not process) the specific event-log evidence. That is a correctable problem. A denial citing "removal order submitted after the assessment date" means there is a timestamp dispute – which is also correctable if the seller has the right documentation.

The second error is filing a storage fee dispute and a linked FBA reimbursement claim as separate, unconnected matters. As the second micro-case illustrates, many storage fee overcharges exist precisely because a unit that should have been removed from the fee calculation was not – because a reimbursement event (damage, loss) had not been fully processed. Running these as separate tickets creates fragmented records and often leads to partial resolution of each without either being fully resolved.

The third error – and the one most relevant to the AUDIENCE_MYTH – is writing off the claim after the first or second denial. In our experience, a well-evidenced claim that has been denied twice often lacks one specific piece of documentation, not a sound legal or factual basis. The question to ask after any denial is not "is this over?" but "what specific evidence is Amazon's system not seeing, and do I have it?"

Timing matters too. Sellers who wait until a disbursement hold or an account deactivation surfaces, and then try to address a multi-cycle storage fee dispute as part of a larger crisis, face a harder problem. The storage fee dispute documentation is harder to pull together under time pressure, and the commercial urgency may push toward a quick settlement rather than full recovery.

Decision matrix: which route fits your situation?

If the notice or charge cites a single assessment cycle, the amount is modest, and you have a removal order confirmation with a timestamp that predates the assessment date – the route is a stage one Seller Central reimbursement claim with the specific event-log documentation attached. This can typically be resolved within a few weeks if the submission is clean.

If the dispute spans multiple cycles, or involves an FBA reimbursement claim for the same units, or has already been denied twice without a specific reason you can remedy – the route is a structured written escalation to a specialist team, framed as a combined claim with a complete inventory event reconstruction. This is a heavier lift but materially more effective than re-filing the same stage one claim.

If the amount is significant and internal escalation has stalled – or if the account is deactivated and the disputed fees form part of a larger withheld balance – the route involves a formal Notice of Dispute under the BSA, potentially alongside a P2B Regulation complaint on Amazon UK. The timeline for formal dispute resolution is longer, but the leverage is proportionally greater. A pre-arbitration demand letter, at a fixed professional fee well below the cost of full arbitration proceedings, often produces resolution at this stage without going further.

What determines which path is appropriate is not just the amount but the state of the documentation, the account status, and whether any linked claims (reimbursement, disbursement hold, reserve policy) are in play simultaneously. These variables are what we assess in a first review.

Related areas

Related areas

• Frozen Funds & Recovery – account-level reserve, disbursement holds, and balance recovery after deactivation
• Amazon Account Reinstatement – Plan of Action, appeal strategy, and reactivation for deactivated UK seller accounts

Bridge: If a first reimbursement claim or escalation has already come back denied, a second structured read of the evidence trail can identify the specific gap – and whether what remains is still recoverable.

To discuss your long-term storage fee dispute, contact Tutamen at info@tutamenlaw.com.

Frequently asked questions

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

Resolution timelines vary significantly based on which stage the dispute reaches. A well-documented stage one Seller Central reimbursement claim for a single assessment cycle can be resolved in several weeks. Multi-cycle disputes requiring specialist team escalation typically take longer – often several months. Formal dispute resolution under the BSA, including a Notice of Dispute and any subsequent steps, extends the timeline further. Acting early, with complete documentation, is the single factor most directly within a seller's control.

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

The main risks are: filing incomplete documentation that produces denials which narrow the later case; treating a linked FBA reimbursement event and a storage fee dispute as separate matters when they share a root cause; and accepting a denial as final when it reflects a correctable documentation gap rather than a case without merit. There is also a timing risk – Amazon's reimbursement window is finite, and delay reduces the recoverable period. The most costly mistake is writing off a legitimate claim after one or two form denials.

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

Not always. A single-cycle dispute with clean documentation and a modest amount is often resolvable through Seller Central without professional assistance, if the seller is methodical about the evidence. Representation adds material value when: the dispute spans multiple cycles or involves linked claims; the matter has been denied twice or more; the account is deactivated and the disputed fees form part of a larger withheld balance; or the amount justifies escalation to a formal Notice of Dispute. At that point, the cost of representation is typically a fraction of the amount at stake.

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 long-term storage fee and FBA reimbursement work is handled directly by qualified attorneys; every engagement is fully confidential and starts with a fixed-fee review quoted before any work begins. To discuss your situation, email info@tutamenlaw.com.

Written by James Whitlock, reinstatement & funds analyst at Tutamen. Published May 27, 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.