Amazon updated its Business Solutions Agreement on March 4, 2026. Most sellers read it as a compliance story about repricers and PPC tools. It isn't.

What does Amazon's new Agent Policy actually do to Rufus and Cosmo — and why does Section 4.2 matter more than Section 19?

The update added two provisions. Section 19 created a formal "Agent" category covering any automated software accessing Amazon Services — repricers, PPC tools, browser extensions, VA dashboards. But Section 4.2 is the clause with structural implications: it explicitly prohibits third-party tools from using Amazon catalog data to train or improve AI models. The same 50+ structured attributes that Rufus and Cosmo query when deciding which products to recommend are now formally off-limits as AI training data for anyone outside Amazon. Amazon's own agents — Rufus, the Seller Assistant, the Ads Agent — are not subject to the policy.

In this episode you'll learn:

• Why Section 4.2 is more consequential than the repricing compliance story everyone is focused on
• How the Agent Policy connects directly to the structured catalog data Rufus uses to generate recommendations
• The compliance asymmetry between Amazon's own AI agents and third-party tools — and why it's intentional
• The three questions to ask every vendor whose tool accesses your Seller Central account
• Why this update shifts the long-term advantage toward native catalog optimization over third-party AI tools

If you find this useful, subscribe to the Amazon Rufus podcast for weekly breakdowns of how Amazon's AI systems actually work — and what that means for your rankings and revenue.

This episode is brought to you by Atomic AMZ. We help brands get discovered, rank and scale on Amazon — for sellers who've outgrown generic agencies. Get your free Rufus audit at atomicamz.com.

#AmazonSellers #AmazonFBA #AmazonRufus #AmazonBSA #AgentPolicy #AmazonAutomation #EcommerceStrategy #AmazonAI