Amazon’s Business Solutions Agreement governs every enforcement action Amazon can take against a seller’s account. In 2026, it received two significant updates. The March 4 Agent Policy created binding compliance obligations for every automated tool touching a seller’s account. Meanwhile, the August 24 transfer and pledge ban changed how sellers can structure, sell, and finance their Amazon businesses. Most sellers clicked through the March notification and kept running their repricers and PPC software. Few audited whether those tools meet the Amazon BSA’s new requirements. Meanwhile, most sellers with revenue-based financing arrangements did not know the August update made pledging Amazon payouts as loan collateral a BSA violation. Both updates are now in effect and both carry account-level enforcement consequences. Importantly, the sellers most at risk are largely the ones who assume the updates do not apply to them.
This guide covers what changed in both Amazon BSA updates, what compliance requires in practice, and what enforcement looks like when Amazon determines a violation.
The two 2026 Amazon BSA updates at a glance: On March 4, 2026, Amazon added Section 19 (Agent Policy). It requires all automated tools and AI agents to identify themselves as automated, comply continuously, and cease access immediately if Amazon requests. Section 4.2 was also added, prohibiting use of Amazon materials or data to train AI or machine learning models. On August 24, 2026, Amazon added explicit prohibitions on transferring seller accounts and pledging BSA rights — including future Amazon payouts — as loan collateral. Both updates took effect automatically for all sellers who continued using Amazon Selling Services after their respective effective dates.
Table of Contents
- The March 4 BSA Update: Agent Policy and AI Restrictions
- What Counts as an Agent Under Section 19?
- The Three Requirements Every Agent Must Meet
- Section 4.2: The AI Training Data Prohibition
- How to Audit Your Automation Stack for BSA Compliance
- The August 24 BSA Update: Transfer and Pledge Ban
- The Pledge Ban and Revenue-Based Financing
- What Enforcement Looks Like for BSA Violations
- Frequently Asked Questions
- How DAM Law Firm Can Help
The March 4 Amazon BSA Update: Agent Policy and AI Restrictions
As confirmed in Amazon’s official Seller Central announcement, Amazon notified sellers of the March 4, 2026 BSA update on February 17, 2026, giving sellers two weeks’ notice. The Amazon BSA update added a new Agent Policy with requirements for AI usage and automated systems, along with updates to the dispute resolution process. Continuing to use Amazon Selling Services after March 4 constituted automatic acceptance — there was no opt-out mechanism and no separate signature required. Importantly, the update affected every seller using any form of automation — not only those using AI in the narrow sense.
Why this update matters more than most BSA changes
Most BSA updates adjust specific fee terms, payment timing, or regional policy language. The March 4 update was structurally different. It created a new compliance category — Agent compliance — that applies to third-party software and services, not just the seller’s own conduct. Before this update, a seller who used a non-compliant repricer was not directly in violation of the BSA — the tool provider bore the compliance responsibility. After March 4, however, the seller is responsible for ensuring every Agent on their account complies at all times. That shift in responsibility is the substantive change most sellers missed.
What Counts as an Agent Under Section 19?
Any automated software or AI system that takes actions on a seller’s account counts as an Agent. That includes repricers, PPC managers, listing tools, inventory systems, customer-service bots, and scheduled SP-API scripts. The determining factor is whether the software acts using the seller’s authorization. Notably, the scope is broader than most sellers initially assumed.
Tools that are clearly covered
The Agent Policy covers repricers, PPC automation software, browser extensions, and fulfillment scripts. Beyond those categories, the policy covers reimbursement tracking services, profit dashboards connecting to the SP-API, listing optimization tools that update content automatically, and VA-operated scripts run using the seller’s credentials. If the tool accesses Seller Central or the SP-API using the seller’s authorization and performs any action or data retrieval automatically, it is an Agent under Section 19.
Tools in a grayer area
Tools that rely on browser automation or scraping techniques that mimic human interaction to extract data Amazon does not expose through the SP-API sit in considerably riskier territory under the new policy. This is precisely the kind of covert AI agent access that triggered Amazon’s lawsuit against Perplexity in November 2025, a case widely seen as the precursor to this BSA update. Browser automation tools log in as the seller and navigate Seller Central programmatically rather than through the official API. Because they they mimic human users, they are unlikely to meet the self-identification requirement.
The Three Requirements Every Agent Must Meet
Amazon’s Agent Policy sets three requirements for all AI agents. They must identify themselves as automated systems, comply with the policy at all times, and cease access immediately if Amazon requests. Each requirement has practical implications for how sellers evaluate and manage the tools they use.
Requirement 1: Self-identification as an automated system
Self-identification means the tool discloses to Amazon’s systems that it is automated software rather than a human user. For SP-API tools, self-identification sits in the authentication framework — the developer credentials and application ID identify the tool as a registered third-party application. The self-identification requirement is something the vendor’s API integration should handle — not a stealth scraper pretending to be a browser. Therefore, sellers evaluating this requirement should ask the vendor directly: does their integration use the SP-API with registered developer credentials, or does it use browser automation?
Requirement 2: Continuous compliance with the Agent Policy
Continuous compliance means the tool’s behavior must remain within policy at all times, not just at the point of initial setup. This requirement has two practical implications. First, sellers cannot delegate compliance to a one-time audit at setup. Tool behavior can change through software updates, so ongoing monitoring becomes necessary. Second, sellers remain responsible for tool compliance even when not actively monitoring it. A repricer running overnight is still the seller’s compliance responsibility under the policy.
Requirement 3: Immediate cessation of access on Amazon’s request
Canopy Management’s Chuck Kessler stated it plainly: “If your tools can’t stop on command, you have a compliance problem.” The message is clear — kill switch capability is not optional under the Amazon BSA. Therefore, the kill switch requirement means sellers should verify, for each tool, that access can be terminated immediately — by revoking API credentials in Seller Central or cancelling the subscription. Tools that embed API credentials in ways the seller cannot quickly revoke present a structural compliance problem — regardless of how well they meet the other two requirements.
Section 4.2: The AI Training Data Prohibition
Amazon’s updated BSA Section 4.2 bans the use of Amazon’s data, materials, or services to train or enhance third-party AI models. This means sellers can no longer scrape advertising performance data to create predictive algorithms or reverse-engineer Amazon’s bidding systems. Sellers relying on external AI tools that ingested Amazon advertising data to train their models should review those tools’ data practices against the new Section 4.2 language.
What Section 4.2 means for sellers using AI tools
In practice, Section 4.2 primarily affects sellers building custom AI models using Amazon data. However, it does not target sellers using commercially available tools that happen to use AI internally. A seller using a commercially available PPC tool with internal machine learning is not violating Section 4.2, as long as the tool provider’s data practices comply. However, a seller who exports Seller Central data into a custom model, or uses a tool that trains on Amazon account data without authorization, is in a different compliance position. The line is between using AI tools and training AI models with Amazon’s materials or data.
How to Audit Your Automation Stack for BSA Compliance
The automation audit is the practical first step that compliance requires. Many sellers discover stale, still-running tools during this exercise that they had forgotten about. Because the seller bears compliance responsibility for every Agent operating on their account, an audit that misses tools creates the same risk as an audit that identifies non-compliant tools and ignores them.
Step 1: Build a complete tool inventory
Start with Amazon’s own summary page on BSA changes and the Seller Central announcement thread. List every tool that pulls reports, edits listings, changes pricing, runs ads, sends messages, or automates operations. Include all SP-API apps, repricers, dashboards, refund and reimbursement tools, and any scripts used by staff or VAs. Cross-reference this against the SP-API application list in Seller Central under Apps and Services. That list shows every application currently authorized to access the account. Any application on that list not in the inventory represents either a forgotten tool or an unauthorized access point. In both cases, immediate review is warranted. Both require immediate review.
Step 2: Verify compliance for each tool
For each tool, verify three things. First, does it connect through the SP-API with registered developer credentials? Second, has the vendor published a compliance statement for the March 4 Agent Policy? Third, can the seller revoke access immediately? Tools that cannot be verified on all three points require either a vendor compliance confirmation or replacement with a tool that meets the requirements.
Step 3: Revoke access for tools that cannot be verified
Any tool that cannot demonstrate compliance with the three Agent Policy requirements should have its SP-API authorization revoked in Seller Central while compliance is being verified. Revoking API access pauses the tool’s operation without cancelling the subscription. As a result, the seller gains time to verify compliance before restoring access. Overall, this approach eliminates the compliance risk from unverifiable tools while preserving the option to restore access once the vendor confirms compliance.
The August 24 Amazon BSA Update: Transfer and Pledge Ban
Amazon announced this update on May 29, 2026, giving sellers nearly three months to restructure affected arrangements. As confirmed in Amazon’s Business Solutions Agreement, effective August 24, 2026, Amazon explicitly prohibits sellers from transferring or pledging their rights and obligations under the BSA. Previously, the agreement required Amazon’s written consent to transfer. The August 24 update broadens that restriction and explicitly bans pledging BSA rights as collateral. Two specific transactions now require Amazon’s formal process: transferring the account to another party, and using future Amazon payouts as collateral for a loan.
What the transfer ban covers
The transfer ban covers any arrangement in which the rights and obligations under a seller’s BSA — including the right to operate the account, access its sales history, and receive its disbursements — move to another party without Amazon’s formal process. Importantly, informal account sales — where parties transfer login credentials without notifying Amazon — are now an explicit BSA violation, regardless of business rationale. Violations typically surface during lender collection actions, routine account reviews, or disputes over informally sold accounts. The consequences can include account suspension or frozen balances.
Formal account transfers through Amazon’s process
Amazon’s formal account transfer process remains available and compliant. It exists specifically for legitimate business acquisitions. Specifically, the formal process requires notification to Amazon and verification of the acquiring entity’s identity. Amazon then reviews and approves the transfer before it takes effect. Sellers planning business sales or acquisitions should initiate the formal transfer process rather than transferring credentials informally, even when the transaction is straightforward and the parties are acting in good faith. Our business law for sellers team advises on BSA-compliant account transfer structures for Amazon business acquisitions.
The Amazon BSA Pledge Ban and Revenue-Based Financing
Of the August 24 Amazon BSA changes, the pledge ban most directly affects established sellers — specifically those with revenue-based financing products structured around Amazon payouts as collateral. The update bans pledging rights under the BSA, meaning future Amazon payouts, as collateral for a loan. If a seller’s loan is structured this way, they should contact their lender immediately to discuss shifting the collateral to inventory or other business assets not restricted under the new agreement.
How to identify whether a financing arrangement is affected
The pledge ban affects financing arrangements where the loan agreement explicitly assigns or pledges the seller’s rights to Amazon disbursements as security. Specifically, it applies when a lender’s security interest attaches to Amazon payouts before they reach the seller’s bank account — typically a UCC filing listing “Amazon receivables” as collateral. Common affected structures include merchant cash advances secured by future Amazon receivables and revenue-based financing where repayment draws directly from Amazon disbursements. Loans secured by inventory, general business assets, or funds already in the seller’s bank account are not affected by the pledge ban. Accordingly, sellers with any of these structures should have the agreement reviewed against the new BSA language to determine whether the arrangement needs restructuring.
Why the enforcement risk is real even without immediate detection
Amazon is not auditing seller loan documents or checking UCC filings routinely. The real risk appears later, when something else forces the issue into view — typically during a lender collection action, an account review triggered by another compliance issue, or a dispute over disbursements. Q4 is particularly high-risk because account balances are higher and Amazon’s fund hold on suspended accounts can cause significant financial damage. A seller whose financing arrangement is non-compliant is carrying a latent BSA violation that could surface at the worst possible moment.
What Enforcement Looks Like for Amazon BSA Violations
Amazon BSA violations do not follow the same enforcement pattern as listing-level or performance metric violations. A seller who exceeds the late shipment rate threshold receives a warning before suspension. However, a seller whose automation stack violates the Agent Policy — or whose financing arrangement violates the pledge ban — may receive a Section 3 deactivation with no prior warning. BSA violations are conduct violations, not performance metric failures.
Section 3 deactivation as the enforcement vehicle
Specifically, Amazon enforces BSA violations through Section 3 — the provision authorizing Amazon to terminate or suspend a seller’s account for conduct that violates the agreement’s foundational requirements. In practice, a Section 3 deactivation triggered by an Agent Policy violation looks identical to any other Section 3 deactivation. The account goes offline, disbursements freeze, and the notice typically cites Section 3 without identifying the specific provision violated. See our Section 3 reinstatement guide for the complete appeal framework when a Section 3 deactivation arrives.
The appeal challenge for BSA-specific violations
BSA violations present a specific appeal challenge because the factual pattern is different from the triggers most appeal frameworks are designed to address. A seller whose Section 3 deactivation was triggered by a non-compliant automation tool needs to demonstrate that the specific tool has been brought into compliance or replaced. Simply asserting general compliance is not sufficient. A seller whose deactivation was triggered by a financing arrangement needs to demonstrate that the arrangement has been restructured. Therefore, the appeal must address the specific BSA provision violated — which requires identifying the trigger before writing a single word of the appeal. Our Amazon account suspensions team handles BSA-specific Section 3 appeals where the trigger is automation or financing-related rather than the more common triggers of related accounts, review manipulation, or authenticity complaints.
Frequently Asked Questions About the 2026 Amazon BSA Updates
Does the Agent Policy apply to tools I use occasionally, or only to tools running continuously?
The Agent Policy applies to any automated software or AI agent that accesses Amazon Services using the seller’s authorization — regardless of how frequently it runs. A tool that runs a weekly report pull is an Agent under the policy just as a continuously running repricer is. The compliance requirements — self-identification, continuous compliance, and immediate cessation on request — apply to both. However, frequency of use affects the practical risk level, not the compliance obligation itself.
My tool provider says they are compliant with the March 4 update. Is that enough?
A vendor compliance statement is a useful starting point. However, it is not a complete answer. Because the seller bears compliance responsibility — not the tool provider — a vendor’s assertion does not transfer that responsibility back to the vendor. Verifying the vendor uses the SP-API with registered developer credentials, and confirming immediate revocation capability, provides a more durable compliance basis than a vendor statement alone. Ask the vendor for their SP-API application ID. Then cross-reference it against the authorized applications list in Seller Central to confirm the self-identification requirement is met.
I sold my Amazon business before August 24. Does the transfer ban affect me?
If parties completed the account transfer before August 24, 2026, the ban does not retroactively create a violation for the prior transfer. However, if the account did not go through Amazon’s formal process and still operates under the original seller’s credentials with the new buyer’s products, the ongoing operation may create a present violation. This is true regardless of when parties completed the original transfer. Sellers in this situation should consult legal counsel. The question is whether the current account structure complies with both the new BSA language and Amazon’s existing identity verification requirements.
What should I do if I receive a Section 3 deactivation and I think it is related to the Agent Policy or the pledge ban?
The first step is to identify the specific trigger by reviewing the deactivation notice carefully and cross-referencing the timing against any recent automation changes, tool updates, or financing events. If the timing suggests an Agent Policy or pledge ban trigger, address that specific BSA provision directly. The generic Section 3 framework designed for related accounts or authenticity triggers will not work here. Contact our Amazon account suspensions team for a same-day assessment. BSA-specific Section 3 deactivations require a different appeal structure than the more common trigger types, and the first appeal is the most important one.
How DAM Law Firm Can Help
DAM Law Firm advises Amazon sellers on BSA compliance and handles enforcement consequences when BSA violations produce Section 3 deactivations, fund freezes, or account restrictions. The business law for sellers team reviews financing arrangements against the August 24 BSA update and advises on compliant restructuring. Additionally, our Amazon account suspensions team handles Section 3 appeals for BSA-triggered deactivations. These include Agent Policy and pledge ban violations, which require a different appeal structure than standard Section 3 triggers.
BSA compliance review and account transfer structuring
Sellers planning Amazon business acquisitions or sales can have proposed transaction structures reviewed against the current BSA transfer requirements. Additionally, those with existing revenue-based financing arrangements affected by the August 24 pledge ban can have their loan agreements reviewed for restructuring options. Contact our team before a transaction closes. Restructuring a non-compliant arrangement after the fact is significantly more complex than structuring it correctly from the start.
Section 3 appeal and fund recovery
When a BSA-related Section 3 deactivation has frozen disbursements, our Amazon withheld funds team pursues fund recovery simultaneously with the reinstatement appeal rather than sequentially. For deactivations where standard Seller Central appeals have not produced reinstatement, our arbitration against Amazon team handles AAA arbitration for fund recovery when the hold period has extended beyond its authorized basis. Contact our team for a same-day assessment of your Amazon BSA compliance or enforcement situation.
Related DAM Law Firm services:
- Amazon Account Suspensions — Section 3 appeals for BSA-triggered deactivations
- Amazon Withheld Funds — fund recovery for BSA enforcement-related freezes
- Business Law for Sellers — BSA compliance review, account transfer structuring, financing arrangement review
- Arbitration Against Amazon — AAA arbitration for fund recovery when appeals are exhausted
This article is for general informational purposes only and does not constitute legal advice. Amazon’s BSA and related policies are subject to change. Contact DAM Law Firm for legal advice tailored to your situation.
