Arbitration & Pre-Arb Demand for aggregator and portfolio sellers

When Amazon's internal support channels stop responding, or when a flat rejection arrives on a claim worth six figures, aggregators and portfolio operators face a decision that most standard seller advice doesn't cover: what formal dispute option actually exists, and is arbitration a realistic step or a theoretical one? Those questions are not academic. For a business holding ten, twenty, or fifty ASIN portfolios, a locked disbursement or an unresolved infringement dispute has a direct effect on working capital, acquisition pipelines, and debt covenants.

TL;DRArbitration and pre-arbitration demand are the formal dispute mechanisms available to Amazon US sellers under the Business Solutions Agreement (BSA) when internal escalation has failed. A pre-arbitration demand is a structured written demand sent to Amazon before any filing, triggering an informal resolution period that resolves a meaningful share of disputes without the cost of a full proceeding. For aggregators and portfolio sellers managing multiple brands or acquired businesses, the process requires careful sequencing – the BSA version that governs each account must be confirmed first, because the path depends on it.

This page explains what arbitration and pre-arb demand actually mean in practice on Amazon US, how the procedural path runs for a multi-brand operator, where sellers lose leverage through avoidable errors, and how Tutamen approaches these matters for aggregator clients. The relevant background on Notice of Dispute mechanics and the pre-arb demand letter as a standalone tool appears in the linked guides below.

Why aggregators face a different exposure than single-brand sellers

A portfolio seller's dispute risk is not just larger in dollar terms – it is structurally different, and that difference shapes every decision from the initial notice to the point of filing.

A single-brand seller dealing with a frozen disbursement has one account, one reserve balance, and typically one precipitating event: a policy action, a Section 3 deactivation, an IP complaint. The root cause is usually traceable. An aggregator may be running acquired seller accounts under separate legal entities, with different Business Solutions Agreements in place, different account histories, and different reserve accumulations. When Amazon takes action – whether a disbursement hold, a withholding after deactivation, or an unresolved reimbursement claim – the exposure aggregates across those accounts in ways that are not always visible in a single Seller Central dashboard.

In matters we handle for aggregator clients, a recurring pattern is the acquired account with legacy compliance gaps. A seller acquired in a roll-up may have had a related-account issue, a prior intellectual property complaint, or a reserve tail from a chargeback period – none of which surfaced in due diligence but all of which become the acquirer's problem the moment Amazon cross-references the accounts. That context matters enormously when constructing a Notice of Dispute or assessing whether a pre-arb demand is the right first formal step.

There is also a scale effect on Amazon's response posture. A pre-arbitration demand from a seller with a low-volume account and a $4,000 held balance lands differently than one from an aggregator with a mid-seven-figure annual disbursement history and a claim that touches multiple accounts. That does not mean the larger claim is easier to resolve – sometimes Amazon's internal handling becomes more cautious, not less – but it does mean the framing and evidential build of the demand letter needs to reflect the actual commercial relationship.

What the pre-arbitration demand actually is – and what it is not

A pre-arbitration demand is a formal written demand sent to Amazon pursuant to the dispute-resolution provisions of the BSA, asserting specific claims and demanding specific relief before any AAA arbitration filing is made.

It is not another support ticket. It is not a seller performance appeal or a Plan of Action. The pre-arb demand sits in a different procedural register: it is a legal document that triggers Amazon's internal resolution period under the BSA, creates a written record of the claims and Amazon's response, and sets the stage for arbitration if that period does not produce resolution. A pre-arb demand letter that reads like a support escalation is one of the most common errors we see from sellers who draft their own – the tone, the legal grounding, and the specificity of the relief demanded all carry weight that an informal escalation message does not.

For aggregators, the demand must be precise about which legal entity is making it, which account or accounts are at issue, which BSA version governs, and what the exact claim is. A demand that conflates accounts, or that asserts a claim under a BSA provision that does not apply to the account in question, gives Amazon a procedural basis to reject the informal resolution process rather than engage with the substance.

The practical detail on structuring an effective demand letter – timing, required elements, how Amazon typically responds during the informal period – is covered in depth in the guide to pre-arbitration demand letters for sellers. For aggregator clients, we apply that same structure but layer in the entity-level and multi-account considerations specific to a portfolio operation.

How does the procedural path actually run on Amazon US?

The path from dispute to resolution follows a defined sequence under the BSA, though the exact requirements depend on the version of the agreement that governs the account – which is why confirming that first is not a formality but a threshold step.

The sequence, in its standard form, runs as follows. A Notice of Dispute is submitted to Amazon, identifying the parties, the nature of the dispute, and the relief sought. The BSA then provides an informal resolution period – a defined window during which Amazon and the seller are supposed to attempt resolution before arbitration can be filed. For aggregators, we track these windows carefully across accounts, because the clock runs from the Notice, and a missed or poorly documented period can create complications downstream.

If the informal period does not produce resolution, the next step is a pre-arbitration demand letter: a more detailed, legally framed assertion of the claims and the specific relief demanded, with a final opportunity for Amazon to resolve the matter before a formal AAA filing. In a meaningful share of matters – including several we have handled for portfolio operators – the demand at this stage produces a substantive response from Amazon's legal or seller experience teams where all prior support contacts had failed. That is not a guarantee of resolution. It is a reflection of the fact that a properly structured demand creates different institutional incentives within Amazon than a Seller Central case.

If the pre-arb demand does not resolve the dispute, the seller may proceed to arbitration before the American Arbitration Association (AAA) under the BSA's arbitration clause. Full AAA arbitration is a real proceeding with filing fees, a neutral arbitrator, and an evidentiary record. It is not a rubber stamp in either direction. The cost and timeline of a full arbitration are material considerations – which is exactly why the pre-arb demand, done well, is often the highest-value step in the sequence.

For a detailed breakdown of the Notice of Dispute mechanics, see what to know about Notice of Dispute to Amazon.

What are the common mistakes aggregators make before engaging counsel?

Aggregators and portfolio operators are sophisticated buyers of legal services, but marketplace dispute procedures are a specialized domain. Several recurring errors compress the realistic options by the time a matter reaches us.

The first is conflating BSA versions across the acquired portfolio. An aggregator operating a dozen acquired accounts may find that those accounts are governed by different versions of the BSA, with different dispute-resolution terms and different informal-period requirements. We regularly see situations where a seller has sent a Notice of Dispute that mirrors the requirements of one BSA version applied to an account that is actually governed by another – and then cannot understand why Amazon's response is non-substantive.

The second common error is delay. The instinct to exhaust every Seller Central escalation channel before turning to formal dispute mechanisms is understandable. But the informal support path and the formal dispute path are not sequential obligations. A pre-arb demand can be initiated while support tickets are open, and in many matters earlier intervention shortens the overall timeline materially. Waiting until support has definitively failed can also narrow what relief is available if, for example, the underlying claim has a time dimension.

The third error is treating the Notice of Dispute as a template exercise. The entity identification, claim framing, and relief specification in the Notice carry forward into the pre-arb demand and, if it comes to it, the arbitration record. A vague or poorly structured Notice constrains the pre-arb demand letter and creates record gaps that a competent arbitrator will notice. We address this in the context of aggregator portfolios in the complete guide to arbitration and pre-arb demand for sellers.

A fourth pattern worth naming: aggregators sometimes assign the dispute process to an operations team member who has deep expertise in Seller Central but no experience with the legal register of a formal demand or an arbitration filing. That mismatch regularly produces demand letters that read like escalated support cases – and Amazon treats them accordingly.

What does Tutamen do, step by step?

Our work in arbitration and pre-arb demand matters for aggregator clients follows a consistent methodology, beginning with the threshold confirmations that many sellers skip.

We start by reviewing the deactivation notice, account history, and BSA version that applies to each account in dispute. For a portfolio client, that may mean reviewing multiple accounts with different histories and different governing terms – something we do as a single engagement rather than account by account. We map every held balance and reserve across the portfolio, identify which claims are strongest on the merits and the procedural record, and advise on the sequencing of the formal steps.

We then send a Notice of Dispute that is precise about the legal entity, the account or accounts, the claim, and the relief demanded. We track the informal resolution period and maintain a contemporaneous record. If the informal period does not produce resolution, we prepare a pre-arbitration demand letter that addresses the substantive claims in the register of a formal legal demand – not a support escalation.

If the matter proceeds to AAA arbitration, we prepare and file the demand, manage the case through the arbitration process, and represent the client before the arbitrator. At each stage, we assess whether proceeding is the right tool against the cost, the strength of the record, and the realistic range of outcomes. Arbitration is not right for every dispute, and we say so plainly when it is not. The pre-arb demand is often where the matter resolves – and in many cases that is the correct result.

A mid-market aggregator on Amazon US (winter 2025) came to us with a cluster of held disbursements across three acquired accounts following a related-account cross-reference. Prior support escalations had stalled for several weeks. We reviewed each account's BSA version, mapped the reserve and disbursement positions, and sent a coordinated Notice of Dispute followed by a pre-arbitration demand that addressed the entity structure and the acquisition history directly. The matter resolved during the informal resolution period, with disbursements released on the two largest accounts and a structured process confirmed for the third.

For the seller meeting these issues for the first time, the steps above describe the standard path. Your situation turns on the exact wording of the notice, the account history, the BSA version in play, and the specific claims available – which is what we review first.

To start a review, email info@tutamenlaw.com.

What are the realistic timelines and what changes them?

Timeline expectations matter for aggregators managing working capital and debt service. We are careful not to state specific day-counts as invariants, because the timeline in any given matter depends on a cluster of variables that are not under the seller's control or ours.

The informal resolution period runs from the Notice of Dispute for a defined window set by the BSA. During that window, the outcome can range from substantive engagement and resolution to silence. Amazon's responsiveness during the informal period varies by the nature of the claim, the account relationship, the complexity of the issue, and internal routing – none of which the seller controls. In matters we handle, we aim to use the informal period actively: following up, maintaining a written record, and pressing for substantive engagement rather than waiting passively.

Pre-arb demand letters, when properly structured and directed to the right Amazon contact point, often produce a response within a timeframe shorter than the prior support history might suggest. The mechanism is different. Amazon's internal handling of a legal demand with an explicit arbitration threat is procedurally distinct from its handling of a Seller Central case.

If the matter proceeds to full AAA arbitration, the timeline extends significantly. Arbitration involves filing, respondent service, preliminary conference, case management, and ultimately a hearing or written submission – a process that typically takes several months at minimum. That timeline, and the cost that runs with it, is a core input into the decision of whether to file. For many aggregator disputes involving disbursement holds or reserve balances, the pre-arb demand is the right tool precisely because it can achieve resolution at a fraction of the cost and time of a full arbitration proceeding.

What changes the timeline, in our experience: the quality and completeness of the seller's own records (account history, correspondence, inventory and disbursement data); the clarity of the BSA version governing the account; whether the claim is clean and singular or involves multiple overlapping issues; and whether the seller has taken any prior steps that complicate the procedural record.

How do fees work for this type of matter?

Tutamen's approach to fees is fixed where possible, quoted up front after a short review, with no ambiguity about what is included. For aggregator and portfolio matters, which often involve more than one account and more than one claim, we scope the engagement at the outset and confirm the fee before work begins.

For pre-arbitration demand work – Notice of Dispute through the formal pre-arb demand letter – we typically quote a fixed fee. For full AAA arbitration, we quote a fixed engagement that covers the preparation and filing of the demand, with any additional stages (hearing, briefing) quoted separately as they become relevant. We are straightforward about the point at which a pre-arb path and a full arbitration path diverge in cost and realistic outcome, and we do not push sellers toward arbitration when the pre-arb demand is the higher-value option.

For frozen-funds recovery where the claim is primarily about held disbursements or reserve balances, a success-based component may apply alongside the fixed engagement fee. We clarify the structure during the initial review.

There is a persistent myth among aggregators that challenging Amazon means committing to a costly, multi-year arbitration. In practice, most disputes we handle resolve before a formal filing. The pre-arb demand is a fixed-cost, time-limited step that produces resolution more often than sellers expect after a flat rejection from support. That rejection feels like the end of the road – it is not. It is often the point at which the formal path begins to work.

Is this the right path for your situation? A self-assessment

Not every Amazon dispute is suited to arbitration or a formal pre-arb demand. A quick self-assessment helps identify where this service fits.

If the notice Amazon issued cites a performance or policy violation and the account is newly suspended, the first path is a Plan of Action and the standard appeal process, not a pre-arb demand. Formal dispute mechanisms are for situations where the internal appeal process has been exhausted or where the claim is not about a correctable policy issue but about a commercial right – a held disbursement, a reimbursement owed, an IP-related dispute that support cannot resolve.

If you are an aggregator holding multiple accounts and Amazon has taken action – whether a disbursement hold, a cross-account flagging, or an unresolved reserve balance – and direct support has produced no substantive response after a meaningful period, the pre-arb demand path is worth a formal assessment. The key questions: What is the BSA version governing the affected accounts? Is the claim one that falls within the BSA's scope? Is there a written record sufficient to support a demand? Those are the questions we work through in a short initial review.

If you are facing a multi-account dispute with material dollar exposure and the informal support path has definitively stalled, the decision matrix runs roughly as follows. If the claim is primarily about held funds or a reserve balance across one or more accounts and the record is documented – the pre-arb demand is likely the right first formal step, on a timeline of weeks to a few months. If the claim involves a broader contractual dispute or an IP issue where Amazon's conduct has a pattern component – the pre-arb demand is still the starting point, but the assessment of whether to proceed to full arbitration is part of the engagement from the beginning. If the prior filings have been weak or the record is incomplete – the engagement begins with reconstructing that record before the formal demand is sent.

A specialty chemicals distributor operating three acquired Amazon US accounts (summer 2026) came to us after two of the accounts were placed on disbursement hold following an inauthentic-goods flag that the acquirer believed was tied to the selling history of the prior owner. Internal support had been unresponsive for an extended period. We reviewed the acquisition documentation, traced the flag to a complaint predating the acquisition, and structured a pre-arbitration demand that set out the entity transition and the basis for the disbursement claim. The informal resolution period produced substantive engagement from Amazon's seller experience team, and the disbursement hold was lifted on both accounts during that period.

Related areas

Related areas

• Arbitration & Pre-Arb Demand – formal dispute mechanisms and pre-arb demand strategy for Amazon sellers
• Amazon Account Reinstatement – Plan of Action, Section 3 appeals, and deactivation recovery
• Frozen Funds Recovery – mapping and pressing held disbursements and reserve balance claims

Frequently asked questions

How long does resolving arbitration & pre-arb demand usually take on Amazon US?

The timeline depends on which stage the dispute reaches and the quality of the record behind it. A pre-arbitration demand, properly structured, can produce a substantive Amazon response and resolution during the informal resolution period set by the BSA – a process that in many matters runs over weeks rather than months. Full AAA arbitration, if it becomes necessary, takes significantly longer: from filing through a hearing typically spans several months at minimum. For aggregators, the informal resolution period and the pre-arb demand stage are where most matters close, which is one reason the quality of the initial Notice of Dispute and demand letter matters as much as it does.

What are the main risks if I handle arbitration & pre-arb demand alone?

The most significant risks are procedural: using the wrong BSA version as the basis for the demand, omitting required claim elements that Amazon can use to deflect engagement, conflating accounts or entities in a way that creates ambiguity, or missing the informal resolution window through poor documentation. For aggregators, there is an additional layer of entity-level complexity that makes pro se handling more likely to produce a non-substantive Amazon response. A poorly structured demand also creates a weak evidentiary record if the matter escalates to full arbitration, compressing the realistic options at that stage.

Do I need a lawyer for arbitration & pre-arb demand?

Not every pre-arb demand requires attorney involvement, but for aggregators and portfolio sellers with material dollar exposure, the procedural complexity and the consequences of a mis-structured demand make attorney-led work the right approach. The BSA version question alone – which governing terms apply to which account – is a threshold legal question that is not always accessible from Seller Central. More practically: Amazon treats a legally framed pre-arb demand differently from an escalated support case, and that difference is most pronounced when the demand is clearly attorney-prepared. For smaller, straightforward claims, a seller familiar with the process may manage a Notice of Dispute without counsel, but a pre-arb demand with a credible arbitration threat is a different exercise.

---

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 matter is handled by an attorney from the first review through any formal filing. To discuss your situation, email info@tutamenlaw.com.

By Claire Donnelly – arbitration & disputes 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.