Arbitration for an aggregator portfolio: what to do, step by step

TL;DRWhen Amazon disputes a claim from a portfolio aggregator – whether the issue is suspended account balances, withheld disbursements across multiple ASINs, or a commercial disagreement with a third party about ownership of branded storefronts – the path forward is not always obvious. Arbitration for an aggregator portfolio is a structured process anchored in the dispute-resolution provisions of the Amazon Business Solutions Agreement (BSA) and, where applicable, the rules of the American Arbitration Association (AAA). The sequence starts before any formal filing, and the earliest steps decide what is recoverable.

This guide maps the full procedure, from first identifying the nature of the dispute across a multi-brand portfolio to the decision points that matter most. If you are an aggregator that has just received a flat rejection from Seller Central support – the kind that feels like the end of the road – this is the guide to read before your next move.

We cover: what arbitration in this context actually means on Amazon UK, the realistic procedural path step by step, and the key decision points where the strategy either sharpens or goes wrong.

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

Arbitration in this context means invoking the formal dispute-resolution mechanism in the BSA to resolve a commercial disagreement that Seller Central's internal processes have failed to fix. For an aggregator – a business that owns and operates multiple acquired Amazon seller accounts under a professional portfolio structure – the complexity multiplies because a single dispute may affect several accounts, several brand storefronts, and accumulated balances or FBA inventory claims across all of them.

On Amazon UK, aggregators operate under the same BSA terms that apply to any professional seller, but the scale of the exposure is different. An account-level reserve applied to one entity can trap disbursements across multiple integrated accounts if those accounts share ownership data, bank details, or cross-account ASIN relationships. A counterfeit complaint or an account health action on one storefront can cascade. The underlying legal question – whether Amazon acted within the BSA, whether a rights-owner complaint was valid, whether a withheld balance is properly calculated – does not change because the seller is an aggregator, but the volume of affected records does.

It is also worth pausing on a foundational point: arbitration is not the first step. The BSA imposes an informal dispute-resolution period before any formal filing. A Notice of Dispute must be submitted, after which both parties are expected to attempt resolution before proceeding to AAA arbitration. For an aggregator with disputes spanning several storefronts, this pre-arbitration window is strategically important. Handled correctly, it often resolves matters faster and at lower cost than full proceedings. Handled carelessly, it can foreclose arguments that would otherwise be available in formal arbitration.

In matters we handle for portfolio operators, the single most common error at this stage is treating the Notice of Dispute as a formality – drafting it quickly, without attaching the evidentiary record that shows the full scope of the claim. That record, across multiple accounts, is larger and more complex to assemble than for a single-account seller, and it is the foundation for everything that follows.

Step one: map and quantify the dispute before you file anything

The first practical step is not filing – it is building a clear picture of what you are claiming and why. For an aggregator, that means an account-by-account, balance-by-balance review of what is actually held, disputed, or damaged. You cannot pursue a coherent arbitration claim if you do not have a clean account of the sum in dispute.

This mapping exercise should cover several areas. First, identify all seller accounts in the portfolio and their current account health status. Note any that are deactivated, restricted, or subject to a reserve. Second, extract the disbursement and reserve data: how much is held, in what account, and on what stated basis. Third, document the FBA inventory picture – any reimbursement claims for lost, damaged, or disposed units that are unresolved sit alongside disbursement claims and should be included in the overall demand. Fourth, if IP complaints are part of the picture (a rights-owner complaint that triggered a suspension, for example), document those separately, because they may need to be resolved or contested before the financial claims can move.

Do not conflate disputes of different types in a single demand without distinguishing them clearly. Amazon's internal review processes for performance issues, IP complaints, and reserve policy operate through different channels. In arbitration, bundling them without precision makes the claim harder to adjudicate and gives the opposing party grounds to challenge scope.

This step typically takes more time than aggregators expect. A portfolio with several acquired accounts accumulated across different calendar periods may have inconsistent operational records. If the original acquired accounts had outstanding A-to-z Guarantee claims or chargeback disputes at the time of acquisition, those sit in the record and will be raised. Better to find them first.

Our experience is that aggregators who arrive at the Notice of Dispute stage with a clean, fully documented account schedule move through the pre-arbitration period significantly faster than those who attempt to build the record after filing.

Step two: check which BSA version governs – and what it actually says

The dispute-resolution path depends on the BSA version that applies to the account, which we check first. This is not a procedural technicality. The applicable terms determine the mandatory pre-filing steps, the dispute-resolution mechanism, and the seat and rules of any formal proceeding. For aggregators who acquired accounts from other sellers, the position can be more complicated: a business that took on an existing storefront did not necessarily renegotiate the seller agreement from scratch, and the terms in force at the relevant time may matter.

On Amazon UK, the platform's relationship with professional sellers is also subject to the Platform-to-Business (P2B) Regulation, which sets minimum standards for dispute resolution and transparency that Amazon must provide to business users. The Digital Services Act (DSA) – which applies to Amazon as a Very Large Online Platform – imposes additional statement-of-reasons requirements when Amazon restricts or terminates a seller's service. These EU-derived instruments, now retained and evolved in UK law post-Brexit, create independent grounds on which certain Amazon actions can be challenged. They do not replace the BSA arbitration path, but they sit alongside it and can support specific arguments at the pre-arbitration stage.

The practical step here is to pull the seller agreement for each relevant account, confirm the dispute-resolution section, note whether it requires an informal resolution period and for how long, and identify whether any recent policy updates have changed the mechanism. Do not assume that the terms you agreed when first registering are the terms that apply today. Amazon updates its agreements, and sellers are typically bound by the version in effect at the relevant time – a question that can itself become a point of dispute.

For a fuller walkthrough of how the arbitration mechanism works from the ground up, the guide to arbitration and pre-arbitration demands for sellers covers the BSA's dispute-resolution structure in detail.

Step three: draft and send a Notice of Dispute that creates the right record

A Notice of Dispute is the formal trigger for the pre-arbitration period. It must be sent to Amazon in the manner required by the BSA – typically in writing to the designated legal notice address – and it begins the clock on any required informal resolution period before you can file with AAA.

For an aggregator portfolio, the Notice should do several things that a single-account notice might not need to do at the same scale. It should identify each seller account in the portfolio that is affected, with its merchant token or account identifier, so that the scope of the claim is unambiguous. It should set out the nature of the dispute per account: is the issue a withheld disbursement, a reserve calculated on a stated policy that is disputed, an FBA reimbursement claim that has been denied, an account deactivation, or something else? It should quantify the claim, to the extent the documentation supports it at that point. And it should preserve, without waiving, any arguments available under applicable UK or EU regulatory instruments.

What the Notice should not do is volunteer more than is necessary, concede facts that are still in dispute, or frame the claim in a way that pre-emptively narrows options. We regularly see notices drafted without legal input that make precisely these errors – and they are difficult to walk back once Amazon's legal or policy team has them on file.

The Notice is not a demand letter in the aggressive transactional sense. It is a procedural document that starts a formal process. Its value is in precision and completeness, not in rhetoric. Treating it as an opportunity to vent frustration about Seller Central support has no effect and can make the informal resolution period harder to use productively.

Once the Notice is sent and acknowledged, both parties are in the informal resolution window. This is genuinely the best moment to resolve matters: Amazon has a financial and operational incentive to settle meritorious claims without full proceedings, and an aggregator with a documented multi-account claim has real leverage if the claim is well-constructed. The question is whether to use a pre-arbitration demand – a structured, documented demand that presents the full case – or to negotiate more informally. On complex portfolio matters, a written pre-arb demand that sets out the case clearly tends to produce faster and cleaner resolution than informal back-and-forth.

For a detailed breakdown of what happens after you file, including what to expect from Amazon's response and how to handle a non-response, the step-by-step guide on what to do after you file a Notice of Dispute covers that phase directly.

Step four: the pre-arbitration demand – and why it often resolves the matter

A pre-arbitration demand is a formal, documented presentation of the claim, sent during the informal resolution window, that makes clear what the seller is seeking, why the claim is meritorious under the BSA and applicable law, and what the realistic alternative is if Amazon does not engage. It is not a bluff. It is a litigation-quality document that does real work in a business negotiation.

For aggregators, the demand is often the most important document in the entire process. It is the first time Amazon's legal team sees a structured account of what the claim actually involves – how many accounts, what balances, what the factual and legal basis is for each. A well-constructed demand signals that the claimant is prepared to follow through to formal proceedings if necessary. That signal changes the dynamic of the informal resolution period, and in many matters it produces a negotiated resolution before any AAA filing takes place.

The demand should include: a summary of the claim and the relief sought; account-by-account supporting exhibits; the legal and contractual basis (BSA provisions, P2B Regulation, DSA where applicable); a clear statement of the informal resolution period deadline; and a statement of intent to file with AAA if the matter is not resolved. The tone is professional and factual throughout.

What changes the calculus between settling at this stage and proceeding to full arbitration? Several things. The strength of the evidentiary record matters. The size of the claim matters – costs and time are proportional to the amount in dispute, and AAA arbitration has its own fees and procedures. The availability of ongoing disbursements from any accounts not in dispute also matters to the aggregator's cash position: a firm that is still operating healthy storefronts has more leverage and more patience than one that is fully frozen. And the nature of the dispute matters – pure financial claims (withheld disbursements, reserves) typically resolve faster at pre-arb than claims involving contested IP rights or contested deactivations, which may require a longer engagement.

This is also a good moment to address a common misconception: fighting a marketplace dispute does not automatically mean a costly, multi-year arbitration process. The pre-arbitration route, properly used, is designed for exactly the scenario aggregators face – a documented financial disagreement with a large platform that has declined to fix it through internal channels. A fixed-fee pre-arb demand, handled by an attorney who knows the process, is both faster and less expensive than most aggregators expect. The decision is not "do we fight or accept the loss." It is "what is the right tool for this dispute at this point in time."

An automotive accessories aggregator on Amazon UK (winter 2025) came to us after support closed their reimbursement and reserve claims across three acquired storefronts without explanation. We mapped the full balance across all accounts, identified that two of the reserves had been applied under a policy basis that had not been properly documented by Amazon under the P2B Regulation, drafted a Notice of Dispute and a pre-arbitration demand that set out both the financial claim and the regulatory argument, and reached a negotiated resolution during the informal period. The accounts involved had accumulated balances across multiple disbursement cycles, and resolution avoided the need for any AAA filing.

Step five: formal AAA arbitration – what it involves and when it is the right tool

If the informal resolution period expires without agreement, the next step is filing a demand for arbitration with the AAA under the rules specified in the BSA. For disputes of the scale typical of a professional aggregator portfolio, this is not the nuclear option – it is the contractual mechanism that was always available. Whether it is the right tool depends on the analysis in step four.

The AAA arbitration process involves: filing a demand (which includes the case description, the relief sought, and the filing fee); selection of an arbitrator from a list provided by the AAA; an initial scheduling conference; document exchange and, in larger matters, limited discovery; written submissions or a hearing; and the arbitrator's award. The timeline varies depending on complexity and the procedural track the AAA assigns. It is not as slow as court litigation, but it is not fast either. Aggregators should plan for a process that takes several months at minimum in a straightforward matter.

The decision to proceed to full arbitration should weigh: the strength of the claim on its merits; the size of the balance in dispute relative to the cost of proceedings; whether the informal period produced any partial resolution that reduces the open amount; whether any accounts in the portfolio are still operating and generating revenue; and whether there are time-sensitive elements (an ongoing reserve that is growing, for example, or an FBA inventory claim approaching a deadline for reimbursement).

What does not make sense is proceeding to formal arbitration without having exhausted the pre-arbitration path, or filing without the full evidentiary record assembled in steps one through four. The arbitrator's job is to evaluate the claim on the record that is presented. An aggregator that arrives at arbitration with disorganized documentation, inconsistent account data, or a poorly drafted initial demand is at a significant disadvantage regardless of the underlying merits.

One structural consideration that matters for aggregators specifically: whether the disputed matters are properly treated as a single consolidated claim or as separate claims per account. The BSA's arbitration terms address the permissibility of multiple claims by the same claimant, and how the claims are structured can affect both costs and procedural efficiency. This is a question that should be resolved before filing, not mid-process.

For context on how the small-claims threshold interacts with arbitration choices – relevant where an individual claim within the portfolio might fall below a monetary threshold – the comparison of small claims versus arbitration for sellers is worth reading alongside this guide.

Where this process goes wrong: the four failure points

Most aggregators who come to us mid-process have already made at least one of four errors. Understanding them is, in practice, more useful than a clean procedural checklist, because the process itself is not complicated – the errors are.

The first is treating the Seller Central escalation as the dispute-resolution process. It is not. Seller Central's performance and policy teams operate internal procedures that are not the same as the BSA's formal dispute-resolution mechanism. A seller that has spent months escalating through support tickets has not been running a clock on the informal resolution period – those are separate tracks. When they finally file a Notice of Dispute, they often find the process has to start again from scratch, while the account has been accumulating further holds.

The second failure is filing a Notice of Dispute without the evidentiary record ready. The informal resolution period is the best window for resolution, but only if you can immediately support the claim with documentation when Amazon responds. An aggregator that sends a Notice and then spends the next several weeks trying to gather account data has lost the window's momentum.

The third failure is an incomplete claim: filing a demand that covers one account but not the others, or that addresses the disbursement hold but not the FBA reimbursement claims, or that frames the dispute as a customer service complaint rather than a contractual and regulatory matter. Incomplete claims do not prevent later claims, but they fragment the dispute, extend the overall timeline, and reduce leverage in negotiations.

The fourth failure is misidentifying the right tool. Some matters are better resolved by a strong appeal and Plan of Action than by arbitration. Some are better approached under the DSA's statement-of-reasons process, which gives a seller a documented internal complaint route before or alongside the BSA path. Choosing arbitration when a regulatory complaint path would be faster and sufficient is a cost that aggregators often bear unnecessarily. The right analysis matches the tool to the specific nature of each dispute in the portfolio.

Related areas

• Arbitration and Pre-Arb Demand – full practice overview for marketplace sellers with Amazon disputes
• Amazon Account Reinstatement – when the suspension is the underlying issue driving the financial claim

Frequently asked questions

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

The timeline varies significantly depending on whether the matter resolves in the informal pre-arbitration period or proceeds to a full AAA hearing. Pre-arbitration demands on well-documented portfolio claims typically produce a substantive response from Amazon within several weeks; negotiated resolutions during the informal period can close in one to three months. Full AAA arbitration on a complex multi-account matter takes longer – typically several months at minimum, depending on the procedural track assigned, the volume of disputed accounts, and whether there is a hearing. The single biggest factor in timeline is how complete the evidentiary record is before the Notice of Dispute is filed.

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

The practical risks are procedural and strategic rather than technical. Filing a Notice of Dispute that is not correctly addressed, that omits required identifying information, or that inadvertently narrows the claim's scope creates problems that are hard to correct. Drafting a pre-arb demand that reads as a Seller Central complaint rather than a contractual demand signals that the claimant is not prepared to follow through, reducing leverage at the moment it matters most. For aggregators, the added risk is claim fragmentation – handling each account's dispute separately when a consolidated approach would be more efficient and more powerful. There is also a real risk of missing arguments available under UK-retained P2B Regulation or DSA procedures that sit alongside the BSA path, which require a different analytical frame to identify and use.

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

Not every marketplace dispute requires attorney involvement, but an aggregator portfolio dispute almost always benefits from it. The complexity of multiple account records, the need to map claims correctly across different dispute types, the BSA and regulatory analysis, and the drafting of the Notice and pre-arb demand are all tasks where legal input changes the outcome. Attorney-led representation is also worth considering from a practical standpoint: Amazon's legal and policy teams handle these processes routinely, and a claimant who is unfamiliar with the procedural mechanics is at a structural disadvantage. Tutamen's work in this area is attorney-led and confidential, with fixed fees quoted up front – the engagement does not have to be open-ended to be useful.

If a first attempt at resolution has already been rejected and you are unsure whether anything is still open, a short review of what was filed and what the response actually said can identify the specific gap and clarify the realistic options from here. To discuss your portfolio situation, email info@tutamenlaw.com.

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 with multi-account disputes on Amazon UK and other surfaces, we review the full portfolio scope before recommending a course of action. To discuss your situation, email info@tutamenlaw.com.

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.