How to handle arbitration for an aggregator portfolio: a step-by-step guide

TL;DRWhen an Amazon UK dispute touches an aggregator portfolio, the stakes are not confined to a single account or a single ASIN. A flat rejection from seller support does not close the dispute – it opens the procedural path to a Notice of Dispute, a pre-arbitration demand, and, where necessary, a formal AAA arbitration. Every step in that sequence is a decision point, and the choices made early shape what remains available later.

This guide sets out the step-by-step sequence for handling arbitration across an aggregator portfolio on Amazon UK: what the process actually is, where the realistic inflection points fall, and where unrepresented aggregators most often stall or foreclose their own options. The guide covers the full arc from an initial support rejection through to the formal hearing, with a section on the key trade-offs at each stage.

What does arbitration for an aggregator portfolio actually mean on Amazon UK?

An aggregator portfolio dispute is not simply one seller's complaint scaled up. It is structurally different from a single-brand or single-ASIN matter in ways that determine which clauses of the Amazon Business Solutions Agreement (BSA) apply, how the claims are organized, and what a realistic resolution looks like.

An aggregator, for these purposes, is an entity that has acquired multiple third-party Amazon seller accounts, brands, or ASIN clusters – often through asset-purchase or equity transactions. Each acquired business may have its own seller account, its own account-health history, its own outstanding claims against Amazon (disbursement holds, FBA reimbursement shortfalls, A-to-z reserve deductions, reserve balances), and its own set of open complaints or notices. When an aggregator rolls those businesses together, it often inherits a tangled web of pre-existing disputes.

On Amazon UK, the relevant procedural rules flow from the BSA version governing each seller account, from the UK Platform-to-Business (P2B) Regulation, and from the internal complaint-handling requirements the Digital Services Act (DSA) imposes on Amazon as a Very Large Online Platform. The path to arbitration depends on the BSA version that applies to each account – which we check first before any filing is drafted.

A pre-arbitration demand is a formal written demand served on Amazon before any AAA case is opened, and it is the mandatory precursor under most BSA versions. A Notice of Dispute is the earlier, often informal trigger that starts the clock on the informal resolution window. Understanding where each account sits in that sequence – and which claims are still within time – is the first analytical task in any aggregator dispute.

Step 1: Map the portfolio before you touch anything

The single most important step in an aggregator arbitration is completed before any notice is drafted: a full, account-by-account mapping of every live dispute, every held balance, every reserve claim, and every BSA version in the portfolio.

In matters we handle involving aggregator portfolios, the mapping phase routinely surfaces claims that have never been filed, deadlines that are tighter than the client assumed, and accounts where the facts actually support Amazon's position – which is equally important to know before spending fees. Proceeding without that map is the main reason aggregators later find themselves arguing a diluted or partially time-barred case.

The map should capture, for each account:

• The precise deactivation or hold trigger (performance, policy, or verification-related) and the date of the triggering notice
• Every disbursement hold or reserve balance, including FBA reimbursement claims for lost, damaged, or disposed inventory
• Any A-to-z Guarantee chargeback deductions that were not voluntarily accepted
• Removal-order disputes and any outstanding fee deductions that were challenged or unanswered
• Whether a Notice of Dispute has already been sent for that account, and if so, the date and Amazon's response
• The BSA version on record for that account, and the dispute-resolution clause it carries

This is not a clerical task. It requires cross-referencing Seller Central data with transaction histories, the seller's own acquisition documents, and any prior correspondence with Amazon support. Gaps in acquisition due diligence frequently create gaps in the dispute record. An acquired account may have had a pre-existing Notice of Dispute sent by the prior owner that was never acknowledged or resolved – and that prior filing can affect the procedural posture of a new claim.

Step 2: Serve a Notice of Dispute – and do it correctly

A Notice of Dispute is the formal starting point for the BSA's dispute-resolution mechanism, and under most BSA versions it must be served before a pre-arbitration demand or an AAA case can be opened. Sending it incorrectly, or to the wrong entity, is one of the most common and costly errors aggregators make alone.

Amazon UK operates through a distinct legal entity from Amazon.com, Inc. The Notice of Dispute must identify the correct Amazon contracting party for each seller account – which may differ across the accounts in the portfolio depending on when the underlying BSA was signed and what entity is named on it. A Notice addressed to the wrong Amazon entity risks being returned or ignored without starting any clock.

The Notice itself should be specific. It should name the account, the period of the dispute, the nature of the claims (disbursement hold, reserve dispute, reimbursement shortfall, or another category), and the amount in dispute where quantifiable. Vague Notices – those that reference "various account issues" without specificity – give Amazon's legal team grounds to challenge whether the informal resolution period was ever properly triggered.

In matters we handle across aggregator portfolios, we typically batch the Notices by account cluster where the factual and legal basis is sufficiently common, but file them as separate instruments so that no single defect in one Notice contaminates the others. That sequencing decision matters later if some accounts resolve informally while others proceed to a formal demand.

What is the realistic timeline for the informal resolution window? The BSA sets a period during which the parties are expected to attempt informal resolution after the Notice of Dispute is served. The length of that window, and what happens at its expiry, turns on the specific BSA version – which is why confirming the applicable version before filing is not optional.

Step 3: Assess whether a pre-arbitration demand or direct AAA filing is the right tool

Once the informal resolution window closes without a satisfactory outcome, the aggregator faces the first major strategic decision: send a formal pre-arbitration demand, or open an AAA case directly.

A pre-arbitration demand is a formal, attorney-drafted letter that sets out the legal basis of the claim, the specific loss figures, the relief sought, and a short deadline for Amazon to respond before arbitration is filed. In our practice, a well-drafted pre-arb demand resolves a meaningful share of aggregator disputes without ever reaching a formal hearing. That is not because Amazon always concedes, but because a properly quantified demand – backed by documentary evidence and a credible filing threat – changes the internal economics of the dispute for Amazon's legal team.

The factors that favor starting with a pre-arb demand rather than proceeding immediately to AAA include:

• The total claim value is below the level where the cost and time of full arbitration is clearly proportionate
• The factual record is strong but not yet organized into the form a tribunal requires
• Some accounts in the portfolio have weaker claims that can be separated from stronger ones before any formal filing
• Amazon has not yet had an opportunity to respond at a senior level to a well-documented demand

The factors that favor opening an AAA case more quickly include:

• Amazon has already responded to a pre-arb demand and offered nothing of substance
• The total claim value justifies the filing fee and time investment of formal arbitration
• A filing deadline is approaching that cannot be extended by further pre-filing correspondence
• The structural nature of the dispute (for example, a systematic reserve-policy disagreement across the portfolio) requires a formal record

The myth that fighting a marketplace always means a costly, multi-year arbitration is wrong in practice. Pre-arb demands regularly resolve matters in a fraction of the time and cost of a full AAA case. The question is not whether to fight, but which instrument is proportionate at each stage.

For a broader comparative view of available dispute routes, including small-claims options, the guide on how to handle small claims versus arbitration for sellers explains how the two pathways interact and when one forecloses the other.

Step 4: Build the arbitration record across every account

If the matter proceeds to a formal AAA arbitration, the quality of the record determines the outcome more than any argument made at the hearing. For an aggregator portfolio, building that record is substantially more complex than it is for a single-account dispute.

A kitchen-goods aggregator on Amazon UK (spring 2026) came to us after a portfolio-wide disbursement hold that affected six acquired seller accounts simultaneously. The prior operators had kept inconsistent transaction records, and the acquisition documents did not include a full Seller Central history export. We reconstructed the account timelines from Seller Central data, removal-order confirmations, and the client's own purchase records, then organized the claims by account and by claim category. A formal pre-arb demand covering the full balance was served, and the matter resolved before an AAA case was opened.

The record for an aggregator arbitration should contain, at minimum:

• A chronological account-level narrative for each account in the claim, keyed to the relevant BSA provisions
• Quantified claim schedules: disbursement holds by account, reserve balances, FBA reimbursement shortfalls by ASIN and by date of loss event, A-to-z and chargeback deductions that were contested
• Documentary exhibits: Seller Central screens, settlement statements, removal-order confirmations, and all prior correspondence with Amazon on each disputed item
• A legal-basis section explaining why each claim category is cognizable under the BSA and, where applicable, under UK P2B or DSA requirements

The arbitrator in an AAA case is working from the record the parties put before them. An aggregator that arrives with six accounts' worth of unorganized transaction data and a general complaint about Amazon's reserve policy will not fare as well as one that presents a structured, account-by-account claim schedule with clear documentary support. The legal arguments follow the record; the record has to be built first.

The full procedural guide on arbitration and pre-arb demand – the complete guide for sellers sets out the standard filing sequence for AAA cases arising under the BSA, including the applicable AAA rules and how the case management process typically unfolds.

Step 5: Manage the portfolio strategically during the proceedings

An aggregator dispute rarely proceeds in a clean, linear sequence. While one account's claim is in the formal resolution window, another may be receiving new seller-support correspondence that, if answered carelessly, could affect the arbitration record. A third account may have a reserve that is approaching release under Amazon's standard rolling-reserve timeline, creating a decision about whether to let it release or to include it in the formal demand.

We regularly see aggregators inadvertently prejudice their own arbitration by continuing to correspond with seller support through standard Seller Central channels while a formal Notice of Dispute is in progress. Statements made in seller-support cases – even routine ones – can be pulled into the arbitration record by Amazon's legal team. The cleaner approach, once a formal Notice of Dispute has been served, is to route all material communications through legal counsel.

Parallel to the dispute proceedings, the portfolio also needs to keep operating where accounts are active. Inventory management, removal orders, and reimbursement claims on undisputed items can and should continue. The dispute does not require a full operational freeze – but it does require that the operational team understands which communications go through standard channels and which do not.

A second illustration: a health and beauty aggregator on Amazon UK (winter 2025) was running a simultaneous seller-support appeal on one account while a formal pre-arb demand was pending on two others in the same portfolio. The seller-support response on the first account made a factual concession that was inconsistent with the legal position in the pre-arb demand. We caught the inconsistency before Amazon's team did and corrected the record in the demand. Had it gone unaddressed, it would have significantly weakened the strongest account in the claim set.

Where aggregator arbitration most often goes wrong

The most common failure points we see in aggregator portfolio arbitrations are structural, not legal. They stem from the complexity of the portfolio itself and from the temptation to treat a multi-account dispute as a collection of single-account problems.

Filing Notices of Dispute serially, account by account, as issues arise rather than mapping the full portfolio first is the primary cause of time-bar problems. By the time the aggregator has resolved the most urgent account, the limitation period may have run on a claim for an account that was quieter but ultimately more valuable.

Mixing BSA versions without checking them is a close second. An aggregator that acquired businesses over a period of years may hold accounts governed by different BSA versions with materially different dispute-resolution clauses. Filing a unified demand that assumes a single procedural rule across all accounts is a technical error that Amazon's legal team will not overlook.

Underestimating the significance of the pre-arb stage is the third common error. Aggregators that treat the pre-arb demand as a box-ticking formality – a brief letter before the "real" arbitration – consistently achieve worse outcomes than those that treat the demand itself as the primary advocacy document. A well-evidenced pre-arb demand, drafted as if it may be the only document a senior Amazon decision-maker reads, is often the instrument that resolves the matter.

For a detailed breakdown of what to expect after a Notice of Dispute is filed, including the sequence of Amazon's responses and the realistic timing of each stage, the page on what happens after you file a Notice of Dispute – questions sellers ask covers the questions we hear most often.

The steps above describe the standard path. Your situation turns on the exact wording of the notice, the account history across the portfolio, and the timing of each account's dispute – which is what we review first when an aggregator comes to us.

To discuss the claims in your portfolio, email info@tutamenlaw.com for a confidential review.

Decision matrix: choosing the right move at each stage

Not every account in an aggregator portfolio belongs in the same dispute instrument at the same time. The right framing is a stage-by-stage decision, not a single filing strategy applied uniformly.

If the dispute is at the post-rejection, pre-Notice stage and the claim is clearly quantifiable, the route is a Notice of Dispute served on the correct Amazon entity, followed by a structured informal resolution attempt. The realistic window for informal resolution is measured in weeks, not months, and the outcome of that window determines the next step.

If the informal resolution window has expired without a meaningful response, and the total claim value is significant relative to the cost of a pre-arb demand, the route is a formal pre-arb demand drafted as a complete advocacy document. In many matters, this is where aggregator disputes actually resolve – before any AAA case number is assigned.

If a pre-arb demand has been served and Amazon has responded substantively but insufficiently, or has not responded within the deadline, the route is an AAA case. The filing fee, the case management timeline, and the arbitrator-selection process are then governed by AAA's commercial rules, as modified by the applicable BSA. The cost of that path must be weighed against the claim value and the strength of the record.

If an account's claim is weak on the merits – for example, because the account-health record supports Amazon's reserve position, or because the FBA reimbursement claim is not supported by the removal-order data – the right move is to exclude that account from the formal demand, not to file and hope. A weak claim in the same filing as a strong one can dilute the credibility of the overall demand.

If some accounts are still within the informal resolution window while others are ready for a pre-arb demand, the sequencing decision requires legal judgment: filing too early on the ready accounts may foreclose negotiating room on the others; waiting too long on the ready accounts risks time-bar problems. That is not a decision to make without tracking each account's status independently.

If a first demand has already been rejected or ignored, a second read of the record may identify the specific reason – whether it is a factual gap, a BSA-version mismatch, or a claim-value presentation that Amazon's team can too easily contest. In our practice, a reworked demand on a well-understood fact set regularly performs materially better than the initial filing.

If a first appeal or filing already came back without a satisfactory result, we can review the specific reason it fell short and advise on whether there is still a viable path forward. Email info@tutamenlaw.com with a brief summary of where the matter stands.

Related areas

• Arbitration & Pre-Arb Demand – dispute resolution through formal demand and AAA arbitration for marketplace sellers
• Frozen Funds Recovery – mapping and pressing held balances, reserves, and FBA reimbursement claims

Frequently asked questions

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

The timeline varies significantly depending on how many accounts are in dispute, whether the matter resolves at the pre-arbitration demand stage or proceeds to a formal AAA hearing, and the specific BSA version governing each account. In matters where a well-evidenced pre-arb demand is served after the informal resolution window closes, resolution can come in a matter of weeks to a few months. A full AAA arbitration typically runs considerably longer. The most important variable is the quality and completeness of the claim record, which is why the mapping phase described in Step 1 is the time investment that most often shortens the overall timeline.

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

The principal risks are procedural, not just legal. Aggregators that handle the process without counsel most often encounter three problems: filing Notices of Dispute on the wrong Amazon legal entity, mixing BSA versions without recognizing the different procedural rules that apply, and treating the pre-arb demand as a formality rather than the primary advocacy document. Any of those errors can weaken or foreclose claims that were otherwise well-founded on the merits. The additional risk is inadvertent prejudice through uncoordinated seller-support correspondence while the formal dispute is in progress – a problem that arises specifically because aggregators have multiple operational teams across multiple accounts.

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

There is no formal requirement that compels representation in a BSA arbitration. However, the complexity of an aggregator portfolio dispute – multiple BSA versions, multiple claim categories, a record that spans several Seller Central accounts, and the need to coordinate formal and operational communications simultaneously – means that the practical risk of self-representation is substantially higher than in a single-account matter. Attorney-led handling also ensures that the pre-arb demand reads as a credible filing threat rather than a negotiating letter, which is the difference that most often determines whether the matter resolves before a formal case is opened.

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 practice is structured around fixed or capped fees wherever possible, so clients understand the cost before any work begins. 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.

Written by James Whitlock, reinstatement & disputes analyst at Tutamen. Published September 30, 2026.