Why breach of the Business Solutions Agreement happens

TL;DRA breach of the Business Solutions Agreement (BSA) occurs when either Amazon or a seller fails to perform a material obligation set out in the contract that governs every Amazon US selling account. In practice, the term surfaces in two distinct situations: Amazon alleges the seller violated a policy embedded in the BSA and deactivates the account or withholds funds, or the seller contends that Amazon itself breached the agreement – by terminating without cause, holding disbursements beyond any stated reserve period, or enforcing a policy in a way that contradicts the BSA's own terms. Both directions have real procedural consequences, and which side is asserting breach determines the entire strategy.

A flat rejection from seller support can feel like the end of the road. The account is down, the balance is frozen, and every ticket comes back with a template response. What many sellers miss at that stage is that the rejection is an operational message, not a legal one. The BSA is a contract, not a policy document, and contracts carry enforcement mechanisms that ordinary support escalations do not reach. Understanding why breach happens – and where it can actually be contested – is the foundation of any realistic response.

This analysis covers what BSA breach actually means on Amazon US, how it arises operationally, the realistic procedural path from a Notice of Dispute through to pre-arbitration demand and, where necessary, American Arbitration Association (AAA) proceedings, and the decision points a seller needs to work through before choosing a route. For a consolidated walkthrough of the full procedural sequence, see our complete guide to arbitration and pre-arb demand for sellers.

What is the Business Solutions Agreement and why does it govern everything?

The BSA is the master commercial contract between Amazon and every third-party seller on Amazon US. It incorporates by reference the Seller Central policies, the FBA terms, the Payments Policy, and a range of program-specific addenda. That incorporation clause is what makes the BSA matter: when Amazon alleges a policy violation, it is almost always framing a BSA breach claim, whether it uses that language or not.

From a legal standpoint, the BSA is a unilateral contract of adhesion – Amazon sets the terms, and sellers accept by continuing to use the platform. That does not make it unenforceable. Courts and arbitrators regularly hold that adhesion contracts bind both parties, and that includes the obligations Amazon undertakes. The BSA commits Amazon to defined processes for suspension and termination, to specific disbursement timelines, and to stated grounds for withholding funds. When Amazon departs from those commitments, a breach claim exists regardless of how the deactivation notice is framed.

In matters we handle, sellers often arrive believing the only question is whether their Plan of Action will be accepted. That framing is wrong, or at least incomplete. The Plan of Action is one path. A Notice of Dispute asserting Amazon's own breach is another. They are not mutually exclusive, but they have different leverage, different timelines, and different costs. Knowing which one applies to a given situation requires reading the deactivation notice against the BSA language, not against Seller Central's help pages.

The BSA also contains the dispute-resolution clause that determines how any claim must be pressed. That clause is volatile – it has changed over time, and the version that governs a particular account depends on when the account was opened and whether the seller accepted any subsequent terms update. Checking which version applies is the first step before any formal move. Our analysis of wrongful account termination claims covers how that version question plays out in the termination context specifically.

How does breach of the Business Solutions Agreement actually arise?

BSA breach arises on either side of the commercial relationship, and the mechanics differ enough that they warrant separate treatment. Both are more common than sellers expect, and both are underutilized as a basis for a formal claim.

Seller-side breach as alleged by Amazon is the more familiar scenario. Amazon may assert that a seller engaged in activity that violated an incorporated policy: a related-accounts finding, an inauthentic-goods determination, a product-safety flag, a review-manipulation allegation, or any number of performance metrics that the BSA incorporates by reference. The operative word in each case is "alleged." Amazon's automated enforcement systems generate these findings without human review at the initial stage, and those findings are not self-proving. A finding in an Account Health dashboard entry is not a legal determination. It is an internal administrative output from a system that can be wrong – and in matters we work on, it frequently is.

Amazon-side breach is less visible to sellers, but it is contractually grounded. The BSA imposes obligations on Amazon: to pay sellers the amounts they are owed, to follow defined processes before terminating an account, to release funds that are not subject to a legitimate reserve or hold, and not to enforce policies in an arbitrary or pretextual manner. When Amazon holds a balance for an extended period without a stated legal basis, terminates an account without triggering any of the enumerated grounds in the BSA, or applies a policy in a manner inconsistent with the BSA's own language, those are breach scenarios that a seller can assert formally.

In practical terms, the most common Amazon-side breach claims we see involve three situations. First, funds held well beyond any reserve period without a disclosed reason. Second, termination under a "related accounts" or "verification failure" label where the factual basis is absent or clearly wrong. Third, enforcement of a policy addendum in a way that contradicts the master BSA terms. The third category is the most legally interesting – and the least often spotted by sellers acting alone.

A seasonal pattern is also worth noting. In our practice, a significant share of BSA-breach situations escalate in the fourth quarter, when account volumes are highest, enforcement automation runs hardest, and the cost of a deactivation or freeze is most severe. A kitchenware brand on Amazon US (fall 2025) came to us after their account was deactivated under a related-accounts finding they had never received prior notice of. We mapped the account ownership history against the BSA's stated grounds for deactivation, identified that the notice did not satisfy the procedural prerequisites in the agreement, and filed a Notice of Dispute on that basis rather than a standard Plan of Action. The account was restored and the held balance was released. The path was faster than a typical reinstatement appeal because the framing was contractual, not operational.

What does breach mean commercially for an Amazon US seller?

The commercial reality of a BSA-breach situation is not abstract. An account deactivation stops all revenue immediately. For an FBA seller, inventory is locked in Amazon's fulfillment network – unavailable to sell on other channels, accruing storage fees, and potentially subject to disposal if removal orders are not filed within specific windows. Disbursements stop. Ongoing orders may be canceled, generating A-to-z Guarantee claim exposure. Supplier payment terms don't pause because Amazon did.

When Amazon is the party in breach – holding funds it is contractually obligated to release – the commercial harm compounds in the same way. Cash flow against which inventory and payroll were planned disappears. Lines of credit tied to receivables may be affected. The operational assumptions that supported the business stop being valid.

What sellers most often miss is that the clock on a formal claim starts running from the breach event, not from whenever the seller decides to take it seriously. The BSA's dispute-resolution process imposes procedural steps that must be completed in sequence before formal proceedings are available. Missing those steps, or completing them in the wrong order, can foreclose options that would otherwise have been available. That is the reason a flat support rejection should not be treated as a final answer – it may in fact be the trigger for starting the contractual dispute process.

For a detailed breakdown of the specific fund-recovery path when Amazon holds a balance, see our step-by-step guide to withheld funds arbitration.

What is the realistic procedural path for a BSA breach claim?

The BSA's dispute-resolution clause defines the sequence a seller must follow before any formal proceeding is available. As noted, the precise clause depends on the account's BSA version – but the general architecture of the path is consistent: an informal notice and negotiation period precedes any formal filing.

A Notice of Dispute is the opening procedural step. It is a formal written communication that identifies the party, the claim, and the relief sought, delivered in the manner the BSA specifies. The Notice of Dispute is not a support ticket. It is not an appeal, a Plan of Action, or a Seller Central email. It is a contractual notice that starts the clock on the informal dispute-resolution period the BSA requires before any further step is available.

The informal period typically runs for several weeks. During that window, the parties are expected to attempt to resolve the dispute without a formal proceeding. In practice, Amazon may not engage in a substantive way during this period. That matters, because the absence of a resolution – not a rejection from support, but an actual failure to resolve after the BSA-specified period – is what opens the door to a pre-arbitration demand or a filing with the American Arbitration Association (AAA).

A pre-arbitration demand is the next practical lever for most matters. It is a formal written demand – often structured as a legal letter from counsel – that quantifies the claim, states the legal basis, and signals that AAA proceedings will follow if the matter is not resolved. In our experience, a well-constructed pre-arbitration demand resolves a significant share of matters before a formal filing ever occurs. The reason is economic: the cost and administrative burden of AAA proceedings are real for both sides, and a demand that demonstrates the contractual basis and the damages calculation removes the ambiguity that allowed the dispute to persist.

If the pre-arbitration demand does not resolve the matter, AAA arbitration is the formal path. The BSA version that applies to the account will specify the applicable rules – typically AAA's Consumer Arbitration Rules or Commercial Arbitration Rules, depending on the account type and claim size. Arbitration is private and binding. There is no appeal on the merits in the ordinary case. The award, once issued, can be confirmed in a US federal court and is enforceable as a judgment.

The decision between pressing a pre-arbitration demand and filing for full arbitration is not automatic. If the claim is quantifiable and relatively contained – a held balance, a specific reimbursement amount, a documented loss from wrongful termination – a pre-arb demand may be the most efficient tool. If Amazon has taken a position that requires an adjudicator to actually rule, or if the informal period produced no engagement at all, a full AAA filing may be necessary. That decision depends on the specific facts, the BSA version, and the economics of the claim.

What are the seller's real decision points and trade-offs?

The myth that fighting a marketplace always means a costly, multi-year arbitration is one of the most operationally damaging beliefs we encounter. It causes sellers to abandon legitimate claims or to continue filing appeals long past the point where a formal path would have been faster and cheaper. The reality is more nuanced and, in many cases, more manageable.

The first decision point is whether to pursue a POA or a contractual claim – or both. These are not mutually exclusive. A Plan of Action addresses Amazon's operational concerns and may restore the account. A Notice of Dispute addresses the contractual breach and may release funds or support a damages claim. In matters where the account is gone and the balance is held, the POA path alone is insufficient. The contractual path is necessary. In matters where both are available, sequencing them correctly matters.

The second decision point is timing. Formal claims under the BSA have procedural prerequisites. Starting the Notice of Dispute process early – even before the POA outcome is known – preserves options. Waiting too long can close them. This is especially true where the BSA version includes a limitations provision. The contractual clock runs from the breach event, not from the last support ticket.

The third decision point is claim scope. A seller pressing a BSA breach claim must be specific: which obligation was breached, on what date, and what harm resulted. Vague or overbroad claims weaken the demand and may invite procedural challenges. In matters we handle, the discipline of constructing a specific, documented claim – mapped to the BSA language and supported by account records – is what separates demands that move to resolution from those that stall.

The fourth decision point is economics. Pre-arbitration demands and formal AAA filings have costs. Tutamen's approach is to quote fees up front, typically fixed for pre-arb demand work and often with a success-based component for fund recovery. The relevant question is whether the claim value and the probability of recovery justify the cost at each stage. That is an analysis we do at the outset, not after a filing is already in motion.

A consumer electronics distributor on Amazon US (spring 2026) came to us after a Section 3 termination that they had been appealing, unsuccessfully, for several months. A review of their account timeline against the BSA established that the termination notice had not followed the procedural requirements in the agreement. We filed a Notice of Dispute, completed the informal period, and sent a pre-arbitration demand identifying the breach and the held balance. The matter resolved during the pre-arbitration period. The seller recovered the balance and the account was reinstated. The total time from our engagement to resolution was shorter than the prior months of unanswered appeals.

The steps above describe the standard path. Your situation turns on the exact wording of the deactivation notice, the version of the BSA that governs your account, and the specific balance at issue – which is what we review first. To start that review, email info@tutamenlaw.com.

Where does the BSA breach analysis differ from a standard account appeal?

Most sellers default to the appeals process because that is what Seller Central presents as the available path. It is the path Amazon designed for its own operational purposes – it routes the matter into a system where Amazon makes all the decisions. The BSA breach analysis is a different exercise. It asks whether Amazon's conduct was contractually permissible, not whether the seller can demonstrate enough operational remediation to earn reinstatement.

The practical differences are significant. An appeal is addressed to Amazon's seller performance team. A Notice of Dispute is addressed to Amazon's legal notices address, as specified in the BSA. An appeal is evaluated by Amazon against Amazon's internal criteria. A pre-arbitration demand or AAA filing is evaluated by a neutral third party against the contract. An appeal has no defined response deadline. The BSA dispute-resolution process has defined periods and triggers.

These differences mean that in cases where Amazon has no operational basis to restore the account – where the finding was automated, unsupported, and not tied to any actual policy violation – the appeal path leads nowhere, while the contractual path may still produce a result. We regularly see matters where the account was correctly managed, the seller had full documentation, and every appeal was rejected because the automated system had flagged a false positive. In those matters, the only path that worked was the contractual one.

It is also worth noting that the BSA breach analysis is not limited to deactivations. Sellers with active accounts who have experienced withheld funds, wrongly-deducted FBA reimbursements, or A-to-z Guarantee claim resolutions they believe were incorrectly decided have BSA-grounded arguments. The scope of potential breach is broader than most sellers recognize.

What should a seller document before pursuing a BSA breach claim?

Documentation is the foundation of any contractual claim. Without it, even a well-framed Notice of Dispute may not survive the informal period.

The account record – every notice, metric, deactivation email, and support correspondence in sequence – is the baseline. Sellers should download and preserve their Account Health history, all performance notifications, every deactivation and suspension notice (including the exact wording), all disbursement records showing dates, amounts, and any stated hold reasons, and all Seller Central communications related to the matter. If there is a related-accounts allegation, the ownership and corporate records that disprove it should be compiled before the Notice of Dispute is filed.

The BSA itself – the version that was in force when the account was opened and any accepted updates – should be identified and retained. Amazon's terms pages are updated without advance notice. What was accepted at account opening governs the substantive rights; later versions govern only if the seller accepted them. Identifying the operative version is a legal task, not an administrative one.

In matters we handle, sellers who arrive with organized documentation move faster through the formal process. Those who have lost access to historical notices – because they didn't download them before the account was deactivated – face a harder reconstruction task. The practical instruction is to preserve everything as soon as a deactivation or fund hold occurs, before any escalation. Storage is cheap. Reconstructing a lost account timeline is not.

How does BSA breach analysis interact with other claims?

A BSA breach claim rarely exists in isolation. Sellers pursuing breach claims often have concurrent or overlapping claims that affect strategy and sequencing.

A wrongful termination claim under the BSA is structurally a breach claim – Amazon terminated without meeting the contractual prerequisites, and the seller suffered damages. The relationship between the breach analysis and the termination-specific path is covered in detail in our treatment of wrongful account termination claims. Where a seller has both a reinstatement goal and a fund-recovery goal, the sequencing of POA, Notice of Dispute, and pre-arbitration demand must be coordinated.

IP disputes can generate BSA breach claims. If an IP complaint caused a listing removal or account suspension, and that complaint was filed in bad faith, the seller may have a claim against the complainant under Lanham Act principles and a concurrent claim against Amazon if the takedown violated BSA process. These are distinct claims with different respondents, but their facts overlap, and the documentation gathered for one serves the other.

Sellers named as defendants in US federal Schedule A cases face asset freezes that sweep across marketplace accounts. A BSA breach claim is a separate matter from a Schedule A defense, but the fact of a pending TRO affects what can be filed, when, and in which forum. Coordination across both tracks is essential.

Finally, EU and UK sellers operating on Amazon's European surfaces face a different regulatory architecture. The BSA's dispute-resolution clause interacts with the EU Platform-to-Business (P2B) Regulation, which imposes independent complaint-handling obligations on Amazon that run parallel to – and sometimes provide an alternative path to – the BSA's own process. That interaction is outside the scope of this page, but it is a real consideration for cross-border sellers.

If a first appeal or formal filing already came back rejected, a second review can identify the specific reason it failed and what, if anything, remains open. Email info@tutamenlaw.com to have your situation reviewed by the Tutamen disputes team.

Related areas

Arbitration & Pre-Arb Demand – formal claim strategy from Notice of Dispute through AAA filing
Account Reinstatement – Plan of Action drafting and appeal strategy for deactivated accounts
Withheld Funds Recovery – mapping held balances and pressing disbursement claims against Amazon

Frequently asked questions about BSA breach on Amazon US

How long does resolving breach of the Business Solutions Agreement usually take on Amazon US?

The timeline depends on which stage the matter reaches. The informal dispute-resolution period required by the BSA runs for several weeks; many matters that are properly framed and documented resolve during or shortly after that window. Where a pre-arbitration demand is required, the process typically adds several more weeks. Full AAA arbitration – when it is necessary – operates on a schedule set by the applicable rules and the arbitrator's calendar, and may take considerably longer. The most common pattern in matters we handle is resolution before a formal filing, when the claim is well-constructed and the facts are documented.

What are the main risks if I handle breach of the Business Solutions Agreement alone?

The most significant risk is procedural: missing a required step, addressing the Notice of Dispute to the wrong party, or completing the informal period incorrectly can foreclose formal options. The second risk is framing: treating a contractual breach claim as a support escalation routes the matter into a system that is not designed to resolve it. The third risk is documentation: account records that are not preserved before deactivation are sometimes unrecoverable. A seller who starts down the formal path without preserving the account timeline may not be able to support the breach claim even if it is substantively strong.

Do I need a lawyer for breach of the Business Solutions Agreement?

There is no legal requirement to use a lawyer. However, the BSA is a commercial contract, the dispute-resolution process has specific procedural requirements, and the decision points – POA vs. Notice of Dispute, pre-arb demand vs. formal filing, claim scope and sequencing – each carry real consequences. Sellers who handle these matters alone typically do one of two things: they stay in the appeals track too long and exhaust options that formal process could have preserved, or they file a Notice of Dispute without the documentation or framing needed to move the matter forward. Attorney-led, confidential handling with fees quoted up front removes both failure modes.

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 qualified legal professionals; no work is passed to a non-attorney service or external network. To discuss your situation, email info@tutamenlaw.com.

Written by Claire Donnelly – arbitration & disputes analyst, Tutamen. Published October 1, 2026.

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.

Page authored by Claire Donnelly, Arbitration & Disputes Analyst, Tutamen.