Arbitration for an aggregator portfolio: the response checklist

An aggregator's relationship with Amazon UK is not a single account. It is a portfolio – multiple brands, multiple ASINs, multiple seller accounts, often acquired under different agreements and structured for different entities. When Amazon raises a dispute that cannot be resolved through Seller Central support, that structural complexity does not pause. It becomes part of the problem. The funds sit. The inventory sits. And the window to act on the correct legal footing narrows.

TL;DRArbitration for an aggregator portfolio on Amazon UK is the formal dispute process available under the Business Solutions Agreement (BSA) when standard escalation has failed. The path depends on the BSA version that applies to each account, the nature of the dispute, and whether a pre-arbitration demand can resolve it first – which it frequently does. For aggregators, the analysis must run across every affected account simultaneously, because each carries its own timeline, reserve position, and procedural status.

This checklist works through the process in phases: what to document before anything is filed, how to assess each account's dispute profile, what a Notice of Dispute triggers, and where the real decision points lie. A micro-case follows each phase where the pattern is instructive.

Phase 1: What does "arbitration for an aggregator portfolio" actually mean on Amazon UK?

The dispute mechanism available to an Amazon UK seller is rooted in the BSA – specifically, the provisions that govern how Amazon and its selling partners resolve disagreements that cannot be worked out informally. For an aggregator, the key threshold question is whether each account in the portfolio is bound by the same BSA version and whether the dispute mechanism points to the same procedure.

In matters we handle involving UK-based aggregators, a common situation is that the portfolio was assembled by acquiring seller accounts that were originally registered under different BSA vintages or with materially different account structures. A brand acquired in 2021 may have been onboarded under a BSA version that refers to one dispute mechanism; an account opened directly by the aggregator in 2023 may carry a different version. That gap is not academic. It determines the exact steps the seller must take, the notice period that applies, and the forum that has authority to hear the dispute.

A pre-arbitration demand is not the same as filing for arbitration. It is the formal written step – typically sent after an informal dispute period has run without resolution – that puts Amazon on notice that the seller considers the matter unresolved and intends to escalate unless a satisfactory response is received. In a significant share of the matters we see, that demand letter resolves the issue without any formal arbitration proceeding. The demand carries weight because it triggers obligations for Amazon and imposes costs on delay.

For an aggregator, that sequence must be coordinated. Filing a demand for one account while the same underlying issue is being escalated informally on another account in the portfolio creates a procedural record that can complicate both. Phase 1 is about understanding what you have before anything is filed.

Phase 1 checks:

• Identify every seller account in the portfolio that is currently in a dispute state – active hold, unresolved support escalation, or deactivated with unreleased funds.
• Pull the BSA version for each account. The version and amendment history are accessible through the account legal terms and through your onboarding documentation from the acquisition.
• Confirm the corporate entity that holds each seller account. Aggregator portfolios frequently involve SPVs, trading subsidiaries, or name changes post-acquisition. The Notice of Dispute must be sent by, and name, the contracting party.
• Identify the nature of each dispute: is it a funds hold (disbursement or reserve), a deactivation, an FBA reimbursement shortfall, an A-to-z Guarantee chargeback, or a combination?
• Note the date of the triggering event for each account – the date of the deactivation notice, the date the disbursement was last made, the date the A-to-z claim was decided. These dates anchor the informal dispute period and the escalation timeline.

What stops aggregators at this stage is the assumption that all accounts are the same. They are not. Do not proceed to Phase 2 until the portfolio map is complete.

Phase 2: How do you assess the dispute profile for each account in the portfolio?

Each account in an aggregator portfolio must be assessed individually before any dispute step is taken, because the strength of the position, the likely outcome of a pre-arb demand, and the cost-benefit of escalation all differ account by account.

A dispute profile for each account should capture: the balance at stake, the category of the dispute, the account's trading history since the triggering event, and whether any previous appeals or support escalations have been filed. In matters we handle, we find that aggregators often have one or two accounts where the documentation is clean and the position is strong, alongside others where the paper trail is mixed or incomplete. Treating them identically – either by filing jointly or by ignoring the weaker accounts – is a mistake in both directions.

The category of the dispute matters for the legal theory and the form of the demand. A funds hold after a deactivation implicates the BSA's payment and withholding provisions. An FBA reimbursement shortfall implicates Amazon's fulfillment and reconciliation terms. An A-to-z decision involves a different internal process entirely. Each has its own documentary basis and its own response path.

Phase 2 checks:

• For each account, calculate the held or disputed balance. Include: reserved funds, disbursements withheld, open FBA reimbursement claims, and unrecovered A-to-z credits. Keep the figures per account, not aggregated – you may pursue them on different timelines and through different mechanisms.
• Document the account's performance history: order defect rate, late shipment rate, A-to-z claim rate, and any policy warnings received in the prior twelve months. This is the record Amazon will reference; you should know it first.
• Review all support cases opened on each account since the triggering event. Note case IDs, the date of each Amazon response, and whether the case was closed unilaterally by Amazon or left open. This is the paper trail for the informal escalation period.
• Assess the documentary evidence available for each dispute category. For a disbursement hold: bank statements, settlement reports, VAT filings. For an FBA reimbursement claim: reconciliation reports, shipping confirmations, inventory event logs. For an A-to-z: the customer order trail, the tracking evidence, and the communication record.
• Identify any accounts where a prior reinstatement appeal was filed. If that appeal addressed the same underlying issue now in dispute, the prior filing will be part of the record. The complete guide to arbitration and pre-arb demand for sellers sets out how prior filings interact with the dispute timeline.

After Phase 2, you should have a ranked list: which accounts have the strongest position, the largest balance at stake, and the cleanest documentation. That ranking drives the order and method of escalation in Phases 3 and 4.

Phase 3: Filing a Notice of Dispute – the procedural path for an aggregator

A Notice of Dispute is the formal document that opens the dispute-resolution process under the BSA, and for an aggregator it must be prepared with more precision than for a single-account seller, because errors in the sending entity, the account identification, or the statement of the dispute can create grounds for Amazon to contest the notice itself.

The path depends on the BSA version that applies to the account – which is why Phase 1 is not optional. For an aggregator that acquired accounts under a mixture of BSA vintages, the notice requirements may differ, and each notice must be calibrated to the version that applies.

In a matter we handled for a UK-based aggregator in fall 2025, the portfolio included six seller accounts across four entity structures. Two of the accounts had been acquired with ongoing support escalations that the previous owner had opened but never resolved. We mapped the dispute status of each account, confirmed the contracting entity for each Notice of Dispute, and sent coordinated but separately worded demands on the three accounts where the position was strong and the balance material. The informal resolution period ran on each account simultaneously, and two of the three were resolved before any formal arbitration step was required.

Phase 3 checks:

• Confirm the BSA version and the dispute-resolution clause that applies to each account. If the BSA has been updated since the account was registered or since the acquisition closed, establish which version governs the dispute.
• Identify the contracting entity for each Notice of Dispute. The notice must be sent by the legal entity that is party to the BSA for that account. Where the aggregator holds accounts through subsidiaries, this means subsidiary-level notices, not a consolidated notice from the parent.
• Draft the notice to state: the account identifier, the nature of the dispute, the amount or relief sought, and the basis in the BSA. The notice is a legal document, not a support ticket.
• Send the notice through the method specified in the BSA for formal legal correspondence. Email to a general support address is not sufficient; the mechanism for formal notices under the BSA is specific and must be followed.
• Log the date of sending for each notice. The informal dispute resolution period begins to run from that date. Note it per account, because the periods run independently.
• Do not file for arbitration simultaneously with the Notice of Dispute. The informal period must run first; filing simultaneously is procedurally premature and may be rejected on that basis.

The informal resolution period is not a formality to endure. It is the window in which a well-argued pre-arbitration demand can resolve the matter. In many matters, a detailed demand letter sent during this period – one that identifies the precise BSA provisions engaged, the account history, and the documented balance – produces a substantive response from Amazon that it does not provide through Seller Central support. What does a genuinely effective pre-arb demand include? It includes a clear statement of Amazon's breach, the financial impact on the seller, and a specific remedy requested by a specific date.

For guidance on the post-Notice path, what happens after you file a Notice of Dispute covers the seller's realistic options at that stage.

Phase 4: Decision points and trade-offs before escalating to formal arbitration

Escalating to formal AAA arbitration is not always the right move – and for an aggregator managing a portfolio of disputes, the decision to file for arbitration on any one account must be weighed against its effect on the others. The costs of arbitration, the time commitment, and the relationship with Amazon as a selling partner are all real variables.

A flat rejection from support feels like the end of the road. It is not. The informal resolution period and the pre-arbitration demand stage exist precisely for situations where internal escalation has stopped. The myth that fighting a marketplace always means a costly, multi-year process is exactly that – a myth. Most disputes that reach the formal Notice of Dispute stage resolve before formal arbitration is ever filed, provided the demand is credible, evidenced, and directed at the right level of Amazon's organization.

That said, some disputes do not resolve at the pre-arb stage, and formal arbitration is the correct tool. The decision matrix for an aggregator looks roughly like this:

If the disputed balance per account is material, the documentation is strong, the BSA version clearly supports the seller's claim, and the informal period has run without a substantive response from Amazon – formal arbitration is a realistic and proportionate step. The AAA has administered these cases before; the process is structured, and the timeline, while not short, is finite.

If the balance is modest relative to the cost and management time of formal arbitration, the pre-arb demand route is the proportionate tool. A credible, lawyer-drafted demand letter that signals readiness to file – but presents a clear settlement – frequently moves matters that months of support escalation did not.

If the documentation is incomplete or the account's performance history creates vulnerabilities, the first step is not filing but reconstructing the record. Filing on a weak evidentiary basis against a well-resourced counterparty produces a poor outcome and closes the room for a negotiated resolution.

Phase 4 checks:

• Assess the response received during the informal period for each account. Did Amazon acknowledge the dispute? Offer any remedy? State a position? A substantive response that falls short of resolution is a different situation from silence or a template reply.
• For each account where you are considering formal arbitration: confirm the balance at stake, the strength of the documentary record, and the legal theory. Do not file for arbitration on an account where any of these three is unclear.
• Consider the portfolio sequencing. Filing formal arbitration on one account while the others are still in the informal period can affect the overall negotiating posture. Coordinate the timing intentionally.
• Review any indemnification or liability provisions in the acquisition agreements that cover the acquired accounts. If the dispute relates to events that predate the acquisition, the prior owner's warranties may be engaged.
• For the accounts where formal arbitration is the right tool: review the AAA Commercial Rules (Consumer Rules where they apply) to confirm the filing requirements, the initial fees, and the case management process. The analysis of small claims versus arbitration provides useful framing for the cost-benefit assessment even for UK-seated disputes.
• Confirm the seat of arbitration and the governing law clause in the BSA. For Amazon UK accounts, this may differ from US accounts, and the practical implications for the aggregator's management of the process differ accordingly.

Phase 5: Operational steps to protect the portfolio during the dispute

Arbitration proceedings take time – typically several months at minimum from filing to a preliminary hearing, longer to a final decision. For an aggregator, the portfolio does not pause during that period, and the operational decisions made while the dispute runs can affect the outcome.

An aggregator running a dispute on one account while continuing to sell on others in the same portfolio needs to be clear about what Amazon can and cannot do with balances and reserves across accounts during an active dispute. The rules here are account-specific, but in matters we handle, we regularly see situations where funds on accounts not formally in dispute are affected by Amazon's internal linking of accounts under common ownership. Understanding that risk upfront is essential.

Phase 5 checks:

• Identify all accounts in the portfolio that are currently trading and disbursing normally. Map any account-level linkages that Amazon may use to connect them to accounts in dispute.
• Review disbursement schedules and reserve levels on all active accounts. If reserves have been adjusted without notice on accounts not formally in dispute, document it immediately – it may be relevant to the dispute proceeding.
• Continue fulfilling orders and maintaining account performance metrics on all trading accounts during the dispute. A performance decline on an account not in dispute creates a second, independent risk.
• Ensure VAT compliance, EPR obligations, and product safety documentation are current for all active ASINs in the portfolio. A regulatory compliance issue on any ASIN during a funds dispute creates leverage for Amazon that it does not otherwise have.
• Keep a contemporaneous log of every material event during the dispute: support case responses, disbursement changes, reserve adjustments, policy notifications. This log is the real-time record that supplements the pre-dispute documentation if the matter proceeds to formal arbitration.
• Where the aggregator holds accounts in both the US and the UK, review whether the US and UK disputes are procedurally linked or independent. In most cases they are independent, but the negotiating strategy should be coordinated.

A fall 2026 matter illustrated why operational continuity matters during a dispute. A UK aggregator managing nine accounts filed a Notice of Dispute on two accounts where funds were held following a related-account review. While the dispute ran, a third account – trading normally – experienced a sharp drop in its Account Health Rating due to a supplier's documentation lapse. Amazon used that compliance gap in its response to the dispute demand. We rebuilt the compliance record and reframed the pre-arb demand to separate the issues, and the funds matters were resolved on their own terms. The lesson: a dispute proceeding is not an isolated event in the portfolio. Everything that happens on every account during the dispute is potentially relevant.

Related areas

• Arbitration & Pre-Arb Demand – full practice coverage for marketplace sellers in arbitration and pre-arbitration dispute proceedings
• Account Reinstatement – Amazon UK and global account deactivations, Plans of Action, and appeals

Before the FAQ below, a note on timing. If you have already sent a Notice of Dispute and received a response that does not resolve the matter, the window to decide whether to escalate to formal AAA arbitration is real and finite. The checklist above covers the pre-escalation work; if that work has already been done and the question is what to do next, a second read of the position – specifically the evidentiary record and the BSA version – is where to start. To discuss an aggregator portfolio dispute or review where your accounts stand, email info@tutamenlaw.com.

Frequently asked questions: arbitration for an aggregator portfolio on Amazon UK

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

The timeline depends on whether the dispute resolves at the pre-arbitration demand stage or proceeds to formal AAA arbitration. A well-evidenced pre-arb demand sent during the informal resolution period often produces a response within several weeks. If formal arbitration is filed, the process from filing to a preliminary hearing typically takes several months, with the full proceeding potentially running longer depending on complexity. For an aggregator with multiple accounts, each dispute runs on its own timeline, though they can be coordinated strategically.

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

The primary risks are procedural and strategic rather than substantive. A Notice of Dispute sent by the wrong legal entity, a demand that misstates the BSA basis for the claim, or a filing that is premature because the informal period has not run can give Amazon grounds to contest the process itself. For a portfolio, the sequencing risk is significant: filing on one account at the wrong stage while others are still in the informal period can compromise the overall position. An incomplete evidentiary record is a further risk that is often only visible once the demand has been sent and Amazon responds.

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

Legal representation is not a formal requirement at every stage, but for an aggregator portfolio the complexity strongly justifies it. The BSA version analysis, the entity mapping, the coordination across multiple accounts and timelines, and the drafting of a pre-arb demand that is both legally precise and strategically positioned are all tasks where the margin for error is low. In matters we handle, attorney involvement from the Notice of Dispute stage measurably changes the quality of Amazon's response. Fixed fees quoted up front make the cost predictable, and the engagement is confidential.

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. For aggregators managing portfolio disputes on Amazon UK and other surfaces, we review the full account picture before any step is filed. 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.