How to Run Your Amazon Seller Business From Claude (2026)
What changed on September 23, 2026
At Amazon Accelerate, its annual seller conference in Seattle, Amazon opened Seller Central to outside AI agents for the first time. The announcement had three parts:
- Seller Assistant with persistent memory. It now remembers each seller’s pricing patterns, inventory cycles and growth goals across sessions and across surfaces.
- Seller Assistant workflows. Always-on automations that monitor and act with guardrails and audit trails.
- A selling partner plugin that puts Seller Assistant inside Amazon Quick (GA) and Anthropic’s Claude (beta), connected in about 60 seconds with no code.
Seller Assistant runs on Amazon Bedrock using Claude models alongside Amazon Nova. Amazon’s stated goal, from VP of Worldwide Selling Partner Experience Mary Beth Westmoreland: sellers “would never have to log into Seller Central.” Roughly 90% of sellers already use some outside AI to run parts of their business; independent sellers account for over 60% of units sold on Amazon, and seller fees brought in $46.8 billion in Q2 2026, more than AWS.
Step 1: Decide on Claude or Amazon Quick
| Claude (plugin, beta) | Amazon Quick (plugin, GA) | |
|---|---|---|
| Best if | You already run your business in Claude with accounting, supplier and channel data connected | You want Amazon’s own desktop assistant and the free Quick Plus year |
| Region | US beta | US |
| Cost | Your Claude plan | Free 12-month Quick Plus for primary account holders, through Dec 31, 2026 |
| What you get | Seller Assistant reasoning, recommendations and actions next to your existing Claude connections | The same, inside Amazon’s assistant with a canvas for modeling scenarios |
| Memory | Shared with Seller Central and Quick | Shared with Seller Central and Claude |
Most sellers who already use Claude for the rest of the business (QuickBooks, supplier spreadsheets, Shopify, ad reports) should take the Claude route: the value is having Amazon data in the same conversation as everything else. Sellers who do not use a general assistant should take the free Quick Plus year.
Step 2: Connect the plugin (about 60 seconds)
- Sign in to Claude (or Amazon Quick) with the account you want to use for the business.
- Open the plugin or connected-apps directory and choose the Amazon selling partner plugin.
- Authenticate with your primary Seller Central account credentials when Amazon’s consent screen appears. The plugin is available to primary account holders; secondary users should check their permissions in Seller Central first.
- Confirm the scopes shown (inventory, pricing, listings, analytics, account health). No code, no API keys.
- Ask a first question: “Give me an account checkup.” Amazon’s launch screenshot shows exactly this prompt returning account-health, inventory and pricing signals in Claude.
Step 3: Run the daily checks from chat
Once connected, the tasks that used to mean five Seller Central tabs become prompts:
- Inventory: “Which ASINs will stock out in the next 14 days at current velocity, and what should I reorder?”
- Pricing: “Where am I losing the Buy Box, and what price change would win it without going below my margin floor?”
- Listings: “Assess my top 20 listings for improvements and draft the changes.”
- Performance: “How is [product] performing this week?” Seller Assistant will connect a competitive signal to an advertising or cross-promotion opportunity and draft a recommendation with its reasoning.
- Modeling: in Quick, open a canvas to compare pricing strategies or diagnose campaign performance on live data through conversation.
Every recommendation comes with the reasoning behind it, so you can evaluate, adjust or ask for alternatives before approving.
Step 4: Set up workflows with guardrails
Workflows are where the time savings compound. Describe the job, set the limits, approve the actions:
- “Alert me if any of my top 10 products drops below a 4-star rating and draft a response plan.”
- “Restock any ASIN that falls below 21 days of cover, up to $X per order, and send me the PO for approval.”
- “Monitor my top category for competitive openings; propose price moves within my floor and never above list.”
Guardrails you should always set: a margin floor per ASIN, a maximum spend per action, and approval required for anything that touches price or inventory. Amazon ships workflows with full audit trails; review them weekly for the first month.
Step 5: Keep the data boundary in mind
Amazon says Seller Assistant keeps seller data within Amazon’s infrastructure and never shares it outside Amazon. In practice that means the plugin brokers actions and answers; your catalogue does not get exported into Claude’s storage. Two things to verify for your own compliance: what your Claude plan’s data-retention settings are for the conversation side, and whether your accounting or supplier connectors in Claude have their own retention terms. For the general pattern of letting agents act on commerce data, see How to control AI shopping agents on your website.
Limits at launch
- Claude integration is beta and US-only; Amazon promises more integrations to follow.
- Actions still require your approval for anything consequential; this is deliberate, not a gap.
- The plugin exposes Seller Assistant’s capabilities, not raw Selling Partner API access; developers who need the latter still use the SP-API.
- The FTC’s antitrust case over seller fees goes to trial in March 2027, and nothing in the plugin changes fee structures or Buy Box rules.
Why this matters beyond Amazon
This is the largest merchant platform to let a third-party model act on seller accounts, and it chose Claude first because Seller Assistant already runs on Claude via Bedrock. Expect the same pattern from Shopify, Etsy and Walmart Marketplace: the assistant a seller already lives in becomes the console. It also explains part of why Anthropic just committed $11.6 billion to Akamai for CPU capacity: every one of these workflows is general-purpose compute running around the clock.
Last verified: September 25, 2026.