// Vendor Central

Your purchase orders, in the assistant you already use.

Vendor teams live in purchase orders, and Vendor Central makes you go and look at them one screen at a time. An MCP connection brings the PO data into a conversation: what arrived, what was accepted, what it is worth, how it compares to last quarter. And because honesty is more useful than a feature list — this page also tells you which vendor data Amazon does not let anyone read.

Connect a vendor account See the full tool list

You"How many POs came in over the last 30 days, and what were they worth?"

Assistant via VendoolyAggregates your authorized purchase orders and reports counts, values and item states.

Then"Which items were rejected?" → drills into the line items behind the summary.

Authorized vendor API data · no Vendor Central scraping

What you can ask

Purchase orders, without opening twelve screens.

Flow

"Which POs arrived in the last 30 days?"
"Break them down by item state."
"Which items were rejected, and on which POs?"

Value

"What is the aggregate value of this period?"
"How does it compare with the previous one?"
"What is the estimated net cost per PO?"

Context

"Which products sit behind these POs?"
"Pull the catalogue detail for these ASINs."
"Summarise what changed this week."

The honest part

What Amazon does not expose — to us or to anyone.

Vendor teams usually want three things first, and two of them are not available through the API. Better you know now than after subscribing.

Invoices: not readable

The vendor API supports submitting invoices, but offers no read endpoint for retail vendor invoices. Nobody can pull your invoice documents through it. Our tool says so explicitly rather than returning an empty result.

Remittances: estimated only

Real remittance advices are not exposed for reading. What we can do is estimate payment figures from purchase order data, including net cost per PO — useful for forecasting, not a substitute for the actual remittance.

Trading terms: not readable

Payment terms, discounts and agreements are not available through the API. For those, Vendor Central remains the source.

If another tool promises full vendor financial visibility, ask how it obtains the data. Scraping the Vendor Central interface is the pattern Amazon's agent rules exclude — see the agent policy.

Setup

Vendor authorization is its own grant.

Separate from seller

Seller Central and Vendor Central are different relationships with Amazon and different API surfaces. If your company runs both, you authorize each one and the contexts stay separate.

Official OAuth

Authorization happens on Amazon. No Vendor Central credentials are shared, and the grant is revocable by you at any time.

Read-first by nature

The vendor surface is largely analytical. Where actions exist elsewhere in the product, the same rule applies: proposed first, executed only after confirmation.

Ask your POs a question.

Authorize one vendor account and start with the last thirty days.

Start free