Responding to arbitration for an aggregator portfolio the right way on Amazon UK

A flat rejection from Amazon's seller support feels like the end of the road. For an aggregator holding several acquired brands across Amazon UK, that reaction is understandable but wrong. Dispute-resolution rights exist in the Amazon Business Solutions Agreement (BSA) precisely for situations where support channels fail – and the procedural path, while structured, is workable when you know the sequence. This guide sets out how arbitration for an aggregator portfolio actually works on Amazon UK, what the realistic steps look like, and where the critical decision points sit.

TL;DRArbitration for an aggregator portfolio on Amazon UK is a multi-step process governed by the BSA's dispute-resolution terms: it begins with a formal Notice of Dispute, moves through a defined informal resolution period, and only then proceeds to arbitration before a recognised body if no agreement is reached. Most aggregator disputes are resolved before a formal arbitration hearing, but the preparatory steps – account-mapping, claim consolidation, and the pre-arbitration demand – determine whether leverage exists at all.

This guide covers the full sequence: what the procedure is, what an aggregator's structural complexity adds to it, where things go wrong procedurally, and how to make the right decisions at each stage. The applicable BSA version governs the dispute-resolution path; we check that first in every matter we take on.

What arbitration for an aggregator portfolio actually means on Amazon UK

An aggregator's dispute with Amazon is not a single seller's reinstatement problem scaled up – it is a fundamentally different kind of dispute. A typical aggregator holds multiple seller accounts, each with its own account history, performance metrics, disbursement cycles, and BSA relationship with Amazon EU S.à r.l. When one or more of those accounts faces a suspension, a frozen balance, or a contested policy determination, the aggregator's exposure is multiplied across brands, inventory positions, and forward revenue projections.

What does "arbitration" mean in this context? A Notice of Dispute is a formal written notification that a seller (or, here, an aggregator entity) is raising a claim against Amazon under the BSA's dispute-resolution clause. It is not a complaint to seller support. It is a document that starts a defined legal process – one that Amazon's commercial and legal teams track differently from a Seller Central appeal.

On Amazon UK specifically, the applicable entity is Amazon EU S.à r.l., and the BSA governing the UK marketplace carries its own dispute-resolution terms. The exact arbitration mechanism depends on the BSA version in force for each account. For aggregators that have acquired brands at different times, this matters: the BSA version may differ between accounts, and the dispute-resolution path depends on which version applies. We work through that account-by-account check at the start of every aggregator matter.

A pre-arbitration demand is distinct from the Notice of Dispute, though the two are often confused. The Notice of Dispute opens the formal process and starts the informal resolution clock. The pre-arbitration demand is a more detailed document – it sets out the legal basis for the claim, the relief sought, and the factual narrative – sent if informal resolution fails. Understanding this distinction shapes every tactical decision an aggregator makes.

Step one: map the portfolio before filing anything

Before a single document is drafted, an aggregator must produce an accurate account map – and this is the step that most sellers skip or compress. In matters we handle, incomplete account mapping is the most common source of procedural problems later in the dispute process.

What does account mapping involve for an aggregator? It means identifying every Amazon UK seller account within the portfolio (including accounts acquired from prior sellers), every associated ASIN or brand, every open or closed disbursement hold, every reserve balance, and every open A-to-z Guarantee claim or chargeback that could affect net exposure. It also means confirming which legal entity holds each account and which BSA version governs it.

This step matters because the dispute strategy depends on whether claims are consolidated under one legal entity or must be filed separately per account. Filing separately when consolidation is available leaves money and leverage on the table. Filing jointly when the BSA terms do not support it invites an early procedural challenge from Amazon's side that can delay the entire process.

The practical output of this step is a written account and claims register: a document that lists every account, its current status, the nature and approximate value of each disputed item, and the BSA version that applies. This register is the foundation for the Notice of Dispute and the pre-arbitration demand.

See our guidance on what happens after you file a Notice of Dispute for a seller-focused walkthrough of the formal process that follows this preparation step.

Step two: draft and serve the Notice of Dispute correctly

A Notice of Dispute that is imprecise, incomplete, or addressed to the wrong entity restarts the informal resolution clock – or, worse, prompts a procedural objection that has to be resolved before the substantive dispute can proceed. Getting the Notice right is not a formality; it is the foundation of the entire pre-arbitration sequence.

What must the Notice of Dispute contain for an aggregator's Amazon UK dispute? At minimum, it must identify the filing party (the aggregator's legal entity), the responding party (Amazon EU S.à r.l. under the UK BSA), the nature of each claim being raised, and the relief the aggregator is seeking. For a portfolio dispute, the relief section is where precision pays off: it should specify, per account or per claim category, whether the aggregator is seeking account reinstatement, disbursement of held funds, removal of performance notifications, or some combination.

The Notice is also the document that starts the informal resolution period – typically a defined window during which both parties are expected to attempt resolution before arbitration can be filed. Missing procedural steps in the informal resolution period can affect the arbitration filing itself. An aggregator that files for arbitration before the informal period has run its course may face a threshold objection from Amazon.

In practice, a well-drafted Notice of Dispute does something else: it signals to Amazon's legal and policy teams that the aggregator is prepared to pursue the matter formally. Many aggregator disputes in our practice have moved toward resolution during the informal period because the Notice itself – clear, detailed, and legally grounded – changed the dynamic of the conversation with Amazon's side.

Step three: run the informal resolution period with discipline

The informal resolution period is not a pause in the dispute. It is an active phase with specific obligations and real tactical value – and it is the phase that most aggregators mismanage when they handle the process without legal support.

What should an aggregator actually do during the informal resolution period? First, respond promptly to any outreach from Amazon's seller performance, legal affairs, or account health teams. Delays on the aggregator's side are recorded and can be used later to suggest the aggregator was not acting in good faith. Second, document every communication: who reached out, when, what was said or proposed, and what was accepted or rejected. Third, assess any settlement proposal against the full claims register prepared in step one – partial settlements that leave significant claims on the table may not be worth accepting.

The informal period is also when a pre-arbitration demand is typically most effective. A pre-arbitration demand is a formal written document – more detailed than the Notice of Dispute – that sets out the full legal and factual basis for the aggregator's claims, the evidence supporting them, and the specific remedy sought. It is addressed to Amazon with a clear deadline for response. In many matters, a well-constructed pre-arbitration demand achieves more movement in days than months of support-channel engagement.

The decision to send a pre-arbitration demand versus simply waiting out the informal period is one of the first real tactical choices an aggregator faces. The right answer depends on Amazon's responsiveness, the size and complexity of the claims, and the aggregator's timeline pressures – particularly cash-flow exposure from frozen disbursements.

For aggregators weighing the difference between formal arbitration and faster resolution tools, our guide on small claims versus arbitration for sellers provides useful comparative framing for the cost-benefit analysis at this stage.

Where the process goes wrong: the four most common failure points

An aggregator that reaches step three and still faces no meaningful response from Amazon will need to decide whether to file for arbitration. That decision is consequential – and it comes at the end of a sequence where multiple failure points can quietly undermine the position the aggregator thought it had built. In matters we handle, the same four problems appear repeatedly.

First: filing without a complete claims register. When the Notice of Dispute omits claims – because an account was overlooked, a reserve balance was not identified, or an FBA reimbursement entitlement was not mapped – those claims are not automatically included in the arbitration. Adding them later requires an amendment, which costs time and may require Amazon's agreement.

Second: treating the informal period as dead time. Aggregators that disengage during the informal period and simply wait for it to expire hand Amazon's side an opportunity to argue the aggregator was not genuinely trying to resolve the dispute. That argument has procedural consequences.

Third: sending an under-evidenced pre-arbitration demand. A demand that asserts large figures without account-level documentation – disbursement statements, FBA inventory reconciliation reports, account-health screenshots, and a clear timeline – is far less effective than one that is specific and evidenced. Amazon's legal team is well-resourced; a vague demand does not create pressure.

Fourth: misreading the BSA version. An aggregator that assumes all its accounts are governed by the same BSA and dispute-resolution terms, when in fact acquired brands operate under older BSA versions, may file under the wrong mechanism. That error can be dispositive at the arbitration threshold stage.

A home-goods aggregator on Amazon UK (winter 2025) came to us after six months of unresolved seller-support engagement across three acquired brand accounts. All three accounts shared suspended disbursements tied to a related-account flag on one of the acquired entities. We mapped each account separately, identified that two of the three accounts operated under a different BSA version from the third, filed separate Notices of Dispute structured accordingly, and ran the informal period with coordinated pre-arbitration demands timed to arrive simultaneously. The matter moved to formal resolution discussions within the informal period; the disbursements were released on terms that addressed all three accounts.

The arbitration filing: when to proceed and what to expect

If the informal period closes without resolution, the aggregator faces the central decision: file for arbitration or explore other routes. This is the decision point where the myth that marketplace disputes always require costly, multi-year arbitration does the most damage. The reality is more nuanced – and understanding it is what allows aggregators to make this choice clearly.

What does filing for arbitration actually involve on an Amazon UK BSA dispute? The BSA's dispute-resolution terms specify the arbitral forum and the rules that govern the proceeding. The applicable arbitral body and procedural rules depend on the BSA version; we confirm this before filing. The arbitration itself is typically a document-based process for smaller and mid-sized claims, with a hearing only if the arbitral body or the arbitrator determines one is necessary. The timeline from filing to a final award varies by the complexity of the matter and the arbitral body's current caseload.

The cost-benefit analysis at this stage turns on three variables: the size of the aggregator's claims (total held funds, lost revenue, and FBA reimbursement entitlements), the strength of the documentary evidence assembled across the portfolio, and the aggregator's appetite for a process that, while not multi-year in most cases, does run longer than a successful informal resolution.

In our practice, aggregators with well-documented claims and a complete claims register are in a materially stronger position at arbitration than those who arrive without that preparation. The work done in steps one through three is not overhead – it is the substance of the arbitration case.

For an overview of the full arbitration and pre-arbitration process, including the AAA procedural rules and the Notice of Dispute mechanics, see our complete guide to arbitration and pre-arb demand for sellers.

An electronics-category aggregator on Amazon UK (spring 2026) approached us after a failed first-round appeal and an ignored Notice of Dispute sent without legal input. The original Notice had been drafted without identifying the correct BSA respondent and had omitted two of the four accounts in the portfolio. We refiled with a corrected Notice, ran the informal period with a structured pre-arbitration demand supported by a full FBA reconciliation and account-history timeline, and the matter settled before an arbitration hearing was required.

Decision matrix: which route fits your portfolio?

Not every aggregator dispute follows the same path to resolution. The route depends on the nature of the claims, the accounts involved, and what Amazon has done – or failed to do – at each stage. Here is how to read the signals.

If the dispute centres on suspended disbursements tied to an account-health flag or a related-account determination, and Amazon has not engaged substantively through support channels, the right first move is a Notice of Dispute combined with a strong pre-arbitration demand. The informal period, run with discipline, is often sufficient to produce movement on the disbursement hold. The arbitration filing is the reserve.

If the dispute involves a performance-based deactivation affecting multiple accounts simultaneously – a scenario common in aggregator portfolios where a flag on one account triggers a review of related entities – the claims picture is more complex. Account-by-account mapping is non-negotiable before any formal step is taken. Filing a joint Notice without that map risks procedural fragmentation that Amazon's side can exploit.

If the aggregator has already filed an unsuccessful appeal through Seller Central and received a rejection, the informal dispute-resolution path is still open. A Seller Central rejection is not a BSA rejection. The two processes are parallel, not sequential. In many matters, an appeal rejection is actually useful evidence of Amazon's position – it sharpens the pre-arbitration demand and clarifies the contested issues.

If the claims include FBA reimbursement entitlements (lost, damaged, or disposed inventory) in addition to disbursement holds, those claims require a separate FBA reconciliation analysis before they can be included in the Notice of Dispute at the right figure. Including an unsupported estimate damages credibility on the better-evidenced claims.

The realistic options are: pre-arbitration demand alone (effective for discrete, well-documented claims where Amazon has engaged but not resolved); the full formal sequence through arbitration (appropriate where informal resolution has genuinely failed and the claim size supports the process); or a narrowed filing that carves out the strongest claims for formal pursuit while holding others in reserve. The right mix depends on the account map and the claims register – both of which need to exist before the decision is made.

Related areas

• Amazon account reinstatement – handling deactivation notices and Plan of Action filings across Amazon UK
• Frozen funds recovery – mapping held balances, reserves, and FBA reimbursement claims for disbursement

If the steps above describe your situation and you have not yet filed a Notice of Dispute, the next move is a review of each account in the portfolio against the applicable BSA terms. Your decision on how to proceed – informal demand, formal arbitration, or a phased approach across accounts – turns on that review. To have your account map and claims position assessed, email info@tutamenlaw.com.

Frequently asked questions

How long does resolving arbitration for an aggregator portfolio usually take on Amazon UK?

Timeline depends on which stage produces resolution. Many aggregator disputes settle during the informal resolution period – which is a defined window after the Notice of Dispute is filed – without a formal arbitration hearing. Where the matter proceeds to arbitration, the timeline extends further and depends on the arbitral body's procedures, the volume of claims, and whether a hearing is required. No precise figure applies uniformly; the factors that most affect duration are how complete the claims register is at the outset and how quickly both sides engage during the informal period.

What are the main risks if I handle arbitration for an aggregator portfolio alone?

The primary risks are procedural: filing a Notice of Dispute against the wrong Amazon entity, omitting accounts or claims that cannot easily be added later, or failing to treat the informal resolution period as an active phase with documented obligations. For aggregators, the additional layer is BSA-version complexity across acquired accounts – an error on that point can affect whether the formal process can even proceed. A mis-filed or incomplete Notice may start a clock that runs out before the substantive claims are properly before Amazon's legal team.

Do I need a lawyer for arbitration for an aggregator portfolio?

Legal representation is not formally required, but the complexity of aggregator disputes – multiple accounts, potentially different BSA versions, consolidated versus separate filings, and the evidentiary demands of a pre-arbitration demand that will be read by Amazon's legal team – makes the procedural risks of self-representation significant. An attorney-led process reduces the chance of a threshold error that undermines otherwise valid claims. Fees are quoted up front after a short account review, so the cost-benefit question is one we can address before any commitment is made.

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. Every aggregator matter is handled with full confidentiality and a fixed-fee structure agreed before work begins. To discuss your situation, email info@tutamenlaw.com.

Written by James Whitlock, reinstatement and funds analyst at Tutamen.

Page authored by 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.