Connect a module

Amazon Seller

Connect an Amazon Seller Central account to ShopMCP through Amazon's Selling Partner API authorization flow. Each approved seller account is stored as its own encrypted connection.

1. Before you start

You need access to the Amazon Seller Central account you want to connect and permission to approve third-party app access. If you manage more than one seller account, connect them one at a time so each account can be labelled and managed separately in ShopMCP.

Amazon Ads is separate

This connection covers Selling Partner API operations such as listings, catalog, pricing, FBA inventory, orders, reports, finance, feeds, A+ Content, and notifications. Sponsored Products, Sponsored Brands, Sponsored Display, and campaign reporting belong to Amazon Ads and will use a separate connection when that module ships.

2. Choose the seller region

In ShopMCP, open Settings - Integrations, choose Amazon Seller, then pick the region where that seller normally signs in:

US seller for Amazon.com accounts. ShopMCP targets marketplace ATVPDKIKX0DER.
UK seller for Amazon.co.uk accounts. ShopMCP targets marketplace A1F83G8C2ARO7P.
AU seller for Amazon.com.au accounts. ShopMCP targets marketplace A39IBJ37TRP1C6.

Amazon may return additional marketplace participations for the seller. ShopMCP stores those so tools can route requests to the correct Amazon SP-API region.

3. Approve ShopMCP in Amazon

Amazon opens a consent page in Seller Central. Sign in as the seller account owner or an authorized user, review the access request, and approve ShopMCP. Amazon then redirects back to ShopMCP with a Selling Partner authorization code and seller id.

ShopMCP exchanges that code with Amazon Login with Amazon, stores the resulting refresh token encrypted at rest, checks marketplace participation, and activates the connection. You do not need to paste a refresh token into ShopMCP for normal production onboarding.

4. Connect more seller accounts

Agencies and operators with multiple seller accounts can repeat the connect flow for each account. Use labels such as US brand account or AU wholesale account, then choose a primary connection for default questions.

Keep merchant boundaries clean

If the seller accounts belong to different clients or legal entities, use separate ShopMCP workspaces where possible. That keeps credentials, audit trails, billing, and team access separate.

5. What you can ask

Find listings with issue errors, suppressed offers, or incomplete attributes.
Compare current price, competitive pricing, featured-offer signals, and estimated fees.
Show FBA inventory at risk of stockout by marketplace.
Review recent orders and seller financial transactions.
Request report jobs such as Sales and Traffic where the seller has access.
Check A+ Content documents and notification subscriptions.

Some Amazon datasets depend on the seller's Amazon roles and eligibility. Brand Analytics and A+ Content, for example, may require the seller to have Brand Registry or the matching Amazon-side permission.

6. Optional writes

Amazon Seller write tools are off by default. They only appear when ShopMCP's global launch gate allows writes and your workspace enables Allow writes for Amazon Seller.

Preview listing changes before applying them.
Target one seller account for every write action.
Review price, inventory, feed, A+ Content, and shipment-confirmation actions carefully before approving them.

Troubleshooting

Amazon says you cannot authorize the app - confirm you are signed in as a Seller Central user allowed to manage app authorizations.
The wrong Amazon account opened - sign out of Seller Central in that browser, return to ShopMCP, and start the region button again.
A marketplace is missing - reconnect from the Seller Central account that owns that marketplace participation, then check the connected account row in ShopMCP.
A tool says Amazon rejected the role - the seller account may not have the Amazon role, Brand Registry status, or restricted-data permission required for that SP-API operation.