Claude for Amazon Sellers: Plan Restocks, POs and Supplier Payments

Claude for Amazon sellers can do more than summarize sales: it can help you plan a restock, but only if it sees the rest of your supply chain. To decide what to reorder, how much and when to pay for it, the agent needs your stock by location, your open purchase orders, shipments in transit with their lead times, and the payments you owe your supplier and freight forwarder. Connect Claude to that data through an MCP server, and you can ask those questions in plain English.

This guide shows how to connect Claude to Propamp's MCP server, six planning questions worth asking before your next reorder, and what we noticed when we ran them on our own brand's account. It also covers where the agent stops, so you know when to check its work.

Why Claude for Amazon sellers needs more than sales data

A reorder decision depends on things that happen before your units reach Amazon: the deposit you send to the factory, the balance due after the goods ship, the freight and duty bills, and how long each leg of the trip really takes. Those live in your purchase orders, your supplier's invoices and your forwarder's statements.

A chat connected only to sales data can tell you that a SKU is selling faster. It cannot tell you whether the next batch will land in time, or whether you will have the cash to pay for it. Sales data won't tell you when to pay the factory. That answer lives in your purchase orders.

What Claude can see through Propamp's MCP server

The Model Context Protocol (MCP) is an open standard for connecting an AI agent to outside data. An MCP server exposes tools, and the agent calls the ones it needs to answer your question.

Propamp's MCP server has 128 tools: 87 read data, 28 create or update records, and 13 remove or archive them. For supply chain planning, four groups matter most:

1. Inventory: stock by location across FBA, FBM and AWD, plus inventory health: excess, stranded units, days of stock and inventory age.
2. Purchase orders: dates, product lines, costs, payment schedules, and where each order's units have moved, from the supplier to the port, a warehouse and FBA.
3. Shipments: status, costs, and the lead time of each logistics step, planned and actual.
4. Payments: every supplier and freight payment tied to your POs, with its due date, amount, status and type.

The agent reads the data Propamp has already synced from Seller Central, plus the purchase orders and shipments you keep in Propamp. It does not call Amazon on its own.

How to connect Claude

You need a Claude plan that supports custom connectors (Pro or higher) and a Propamp account with Seller Central connected.

1. Start a Propamp trial and connect Seller Central. Let the first sync finish, or the agent's answers will come back empty.
2. In Claude, add a custom connector and paste the server URL: https://mcp.propamp.ai/mcp
3. Sign in on the Propamp page that opens. Claude gets an access token, never your password, and there is no API key to copy.
4. Start a new chat and ask something that needs real data, such as last month's US sales. If Claude calls a Propamp tool and returns your numbers, the connection works.

The exact menu path is in the Claude setup guide. The same server also works with ChatGPT, Codex and Cursor. MCP access is included in the trial; on paid plans, connecting an outside AI client requires the MCP access add-on.

Six questions to ask before your next reorder

Each question below maps to data the agent can reach. The note under each one is what to double-check before you act on the answer.

1. Which SKUs will run out before the next shipment lands?

The agent combines stock by location across FBA, FBM and AWD, days of stock and the arrival dates of shipments in transit. Before you trust the answer, ask where your last PO's units are (question 3). If you would rather see this on a screen than in a chat, the same data powers Propamp's Amazon inventory management views.

2. What do I owe suppliers and forwarders in the next 60 days?

The payment calendar lists each payment with its PO, due date, amount, status (Scheduled, Paid or Overdue) and type (order, shipping or other). One catch: Overdue is set by hand or by a status check, not automatically when the date passes. Ask the agent to flag scheduled payments whose date is already behind you.

3. Where are the units from my last PO right now?

Purchase orders track each movement from the supplier to the port, a warehouse and FBA, so the agent can tell you how many units sit at each stop. Check it before you place a new order, so you don't pay twice for stock that is already on its way. Propamp's purchase order dashboard shows the same flow on screen.

4. How far off were the planned lead times on my last shipments?

Propamp tracks each logistics step of a shipment, such as production, ocean or air freight, customs, domestic freight, prep and AWD, with a planned and an actual duration. Comparing the two shows which step keeps slipping. That is the number to fix before you plan the next order.

5. What did freight and duty add to the unit cost of this PO?

Freight, customs and other costs on a PO are spread across its products by volume, weight, unit count, price or evenly. Ask the agent which method each cost used, because the same freight bill lands very differently on a small SKU and a bulky one. True COGS from your POs is a paid feature.

6. Find the invoice and bill of lading for this shipment

The agent can search documents attached to your shipments and POs, such as invoices, bills of lading, proof of delivery, QC files and FBA labels. That beats digging through email when a forwarder or Amazon asks for proof.

What we noticed on our own brand's account

We run PropVue, a private-label brand that sells projector accessories on Amazon, and its purchase orders live in Propamp. Before writing this guide, we asked these questions on that account. Two things stood out.

First, a purchase order rarely has a single payment. A typical one has a deposit before the goods ship, a balance split into several payments after shipping, and separate freight and duty charges, some billed by the forwarder and some deducted from the Amazon payout. Some duty bills arrive months after the freight. Asking for the coming weeks of payments returned all of that in one list sorted by date, instead of one spreadsheet per supplier.

Second, estimated and actual arrival dates drift in both directions. Some shipments landed later than estimated and others landed early. Without the actual dates, every new lead time estimate is a guess dressed up as a plan.

Reading runs freely, changes ask first

Most planning questions only need the 87 read tools. The 28 write tools create or update records, such as a purchase order, a shipment draft or an expense, and the 13 delete tools remove or archive them. Every tool carries a hint that says whether it only reads, changes data or deletes it, and clients that respect those hints ask you to approve changes. Read each request before you approve it, the way you would review a teammate's edit.

Where the agent stops

1. It works from what Propamp has. If Seller Central has not finished syncing, or a PO was never entered, the agent cannot see it.
2. Restock math is based on sales velocity. Propamp's Restock Suggestion sets safety stock at 14 days of sales and the reorder point at safety stock plus sales velocity times lead time. There is no seasonal forecast, so before Prime Day or Q4, enter your own velocity instead of relying on the lookback average.
3. It gives you numbers, not decisions. Whether to air-freight a top seller or let a slow SKU run out is still your call.

Try it on your own account

Start a two-week free trial (no credit card), connect Seller Central, and add the server to Claude. The Amazon MCP server page shows what the agent can do and how to connect it.

How we made this: drafted with AI assistance, checked against Propamp's public documentation, and tested on our own account. Figures from that account are left out on purpose.