Seller Agent

A Seller Agent is like a staff member who sits next to the store owner, flips through the ledger, and offers advice. If there's a separate agent handling customers on the storefront side, this one sits in the back office, looks at sales charts, points out items running low in stock, suggests how much to raise prices, and drafts promotional copy.

The important part is that this staffer doesn't hold the keys to the safe. Any suggestion to change a price or launch a campaign goes into an approval queue, and it only takes effect once the actual person in charge clicks confirm. In an example Anthropic published, this Seller Agent is designed to pull out five kinds of tasks as needed: performance analysis, catalog management, inventory operations, pricing and promotions, and marketing campaigns.

Articles describe it this way: "The Seller Agent runs on the merchant-facing side. It analyzes sales, tracks inventory, suggests pricing and promotions, and drafts marketing campaigns." A common misunderstanding is assuming the agent changes prices or moves money on its own — in reality, it only suggests, and a human must approve before anything executes.

1. Look up the anthropics/commerce-agents repository on GitHub.
2. Examine the seller-side example code to see how the five skills (performance analysis, catalog management, inventory operations, pricing/promotions, marketing campaigns) are separated.
3. Find where actions like changing a price or launching a campaign get queued for approval instead of executing directly.