October 19, 2026

Amazon Selling Partner Plugin Review: What It Can't See

We read every skill in Amazon's Selling Partner plugin. About two days behind, one marketplace per question, no ads, no profit per SKU.

Amazon's Selling Partner plugin has been live in Claude for almost a month. Connecting it takes about a minute. Knowing what your AI can actually see once it is connected takes longer, so we did the slow part: we read every skill in Amazon's public toolkit, line by line, and put the same questions to an AI with and without the full picture.

Short version: the plugin is a good, free start for a single US seller who wants to fix listings and watch stock. It cannot see ads, Vendor Central, product costs or other marketplaces, and its numbers trail by about two days. If your AI can't answer a question, it usually can't see enough data to answer it.

New to the plugin? Start with our guide to the Amazon Selling Partner plugin for what it is and how to set it up. Jakob walks through the findings below in this video: Amazon Seller Assistant in Claude: 5 Things to Check.

How we tested

  • The code. Amazon publishes the plugin's skills as an open-source repository, amzn/selling-partner-agentic-toolkit. We read all twelve skill files and the three commands, as of 19 October 2026. Every limit below is quoted from those files, not guessed.
  • The same question, two levels of context. We asked one question, "which product should I push next month?", on an example account, in the same AI. Once it could see only sales, on purpose, and once it could see sales, fees, ad spend, product cost and stock.
  • A question that needs two data sources. Stock and ads together, followed by a dry-run change.

Result 1: same question, opposite answers

The two answers pointed in different directions. The first AI could only rank products by what they sold. The second could weigh what each product actually earns after fees, ads and cost, and whether there was enough stock to sell more of it.

Neither AI made a mistake. Each worked from the data it had. That is the whole point of this review: before you compare AI tools, compare what they can see.

Result 2: what Amazon's plugin can see

The plugin is good at the jobs it was built for. From the toolkit:

  • Sales, traffic and inventory metrics through the seller-analytics skill: units, revenue, sessions, page views, days of supply and restock suggestions.
  • Listing problems, with five skills for suppressed, unbuyable, unsearchable and non-compliant listings, and Amazon-written fix guidance.
  • Stockout checks based on Amazon's own restock forecast.
  • FBA inbound, from planning to placement.
  • Month-end close: a newer skill, finance-month-end-closer, reconciles a completed month's net proceeds against settlement payouts.
  • Changes with approval: it can edit listings and prices and create inbound plans, and Amazon's README says "write actions are always human-in-the-loop".

It is official, it is free during the beta, and it comes from the company that runs the marketplace. For a single US seller who mainly needs listing fixes and stock alerts, that is a lot for nothing.

Result 3: where it stops

These are the limits we found in the code, in Amazon's own words where possible.

About two days behind

The seller-analytics skill tells the AI that "data is delayed ~2 days, so the last two days would be empty", and to default to a window "ending at T-2". Ask how yesterday went and the answer is about the day before yesterday.

One account and one marketplace per question

Every call is pinned to one seller and one marketplace: "Pin one entityId + one marketplaceId per call" and "don't blend accounts or marketplaces". A seller in the US, UK and Germany gets three separate answers that the AI has to add up itself. An agency gets one client at a time. And at launch, only US stores can connect at all.

No ads

No skill touches Amazon Ads. Ad data lives behind a separate Amazon Ads MCP server with its own credentials. With two connections the AI has to join ad spend to sales on its own, which costs time and tokens and is easy to get wrong.

No real profit

The finance skill closes a month against payouts. It does not calculate profit by product, and nothing in the toolkit knows what your products cost you. Profit by SKU needs fees, refunds, ad spend and cost of goods in one place.

No Vendor Central

The plugin is for third-party sellers. Vendors have no first-party AI route yet.

No history you keep

The plugin reads Amazon's APIs on demand. There is no warehouse, no export and no SQL, so your history is whatever Amazon's APIs return on the day you ask.

Two AI clients

Amazon lists Claude, in beta, and Amazon Quick. ChatGPT, Cursor, Gemini and agent frameworks are not on the list yet.

Result 4: stock and ads in one question

On the same example account we asked DataDoe: "Which of my advertised products will run out of FBA stock in the next 30 days, and how much am I still spending on ads for them per day?" It answered in one pass, because inventory and ad spend sit in the same schema. It listed the products that would run out within 30 days and their daily ad spend.

Then we asked it to cut bids on those products by 30% so the stock would last. DataDoe ran the change as a dry run first and showed exactly which bids would move, from what to what. Nothing reached Amazon until it was approved.

The plugin cannot answer the first half of that question, because it has no ad data, and cannot do the second half, because it has no ad actions.

5 things to check before you connect any Amazon AI tool

This checklist works for any plugin, connector or MCP server, ours included. Paste it into your AI along with the tool's documentation.

  1. Does it see the whole business? Seller Central, Vendor Central, Amazon Ads, every account and every marketplace you sell in.
  2. Does it know your real profit? That takes fees, refunds, ad spend and your product costs, joined per SKU.
  3. How fresh is the data, and how far back does it go? Ask for the delay in hours and the oldest date you can query. History is only yours if it is stored somewhere you can reach.
  4. What can it change, and what stops a mistake? Look for actions that are off by default, a preview before anything runs, and a log of every change.
  5. Does it work in your AI? Check the clients you use today and the ones your team might use next year.

How DataDoe answers the same five

  • Whole business: Seller Central, Vendor Central and Amazon Ads in one schema, across all Amazon marketplaces and as many accounts as you connect. Search Query Performance, Amazon Marketing Cloud (beta) and, with Amazon's approval, buyer data are available too. The full schema is public: datadoe.com/hub/data-scheme.
  • Real profit: upload your product costs once and profit by SKU includes fees, refunds and ad spend.
  • Freshness and history: a full refresh every night, intraday updates for orders, inventory and ads performance, and webhooks for near-real-time events. Data is kept for as long as you stay connected, so your history keeps growing, and you can query it in BigQuery.
  • Changes: Actions cover listings, orders, shipments and Amazon Ads. They stay off until you enable them, every change can be previewed with a dry run, most AI clients ask before a change, and every change is logged.
  • Your AI: Claude, ChatGPT, Cursor, Gemini, Codex and any MCP client, plus a REST API, BigQuery and exports.

Every customer also gets an account manager and a reply from a person in about 15 minutes. DataDoe is built by Deltologic, a software house that has worked with Amazon's APIs since 2020.

Should you use the plugin, DataDoe, or both?

  • Use the plugin if you are a single US seller, you mostly need listing fixes, stock alerts and inbound shipments, and Claude or Quick is your only AI.
  • Use DataDoe if you run ads, sell through Vendor Central, sell outside the US, manage several accounts, use ChatGPT or another AI, or need profit and history you can query.
  • Use both if you want Seller Assistant's listing guidance and the full picture in the same chat. Claude can have both connected at once, and each answers the questions it can see.

For a feature-by-feature view, see DataDoe vs Amazon Seller Assistant, or how to connect Amazon to Claude with DataDoe.

Try DataDoe free for 14 days. The plan is $97 a month after the trial. Start your trial.

FAQ

Is the Amazon Selling Partner plugin any good?

Yes, for what it covers. It is official, free in beta, and strong on listing problems, stockouts and FBA inbound for US sellers. It does not cover ads, Vendor Central, product costs, other marketplaces or stored history.

How fresh is the plugin's data?

Its analytics skill says data is delayed about two days and tells the AI to use windows ending two days ago.

Can the plugin see my Amazon Ads?

No. Ads have their own Amazon Ads MCP server with separate credentials. DataDoe puts ads, sales, fees and inventory in one schema.

Does the plugin calculate profit by product?

No. Its finance skill reconciles a completed month against payouts. It does not use product costs or ad spend, so it cannot give profit per SKU.

Can I connect more than one marketplace or account?

Not in one question. Each call is pinned to one seller account and one marketplace, and only US stores are supported at launch.

Can I use the plugin and DataDoe together?

Yes. Connect both to Claude and the AI uses whichever one can answer.

DataDoe is not affiliated with or endorsed by Amazon or Anthropic. Plugin details come from Amazon's public selling-partner-agentic-toolkit repository as of 19 October 2026 and may change during the beta.

• Get started

Put this to work on your own Amazon data.

Connect Seller Central, Vendor Central and Amazon Ads in about 5 minutes, then ask your AI about your own numbers instead of the examples in this post.

  • Seller, Vendor and Ads
  • Any AI client
  • An account manager for every customer
  • $97/mo, 14-day free trial