Amazon Vendor Central purchase orders to Excel
Amazon first-party (1P) vendors see new purchase orders under Confirm New POs in Vendor Central, and the same orders are available through the Selling Partner API’s Vendor Orders endpoints. To get Amazon POs into one order sheet, add one row per PO line, map the ASIN to your SKU, check whether the quantity is in cases or eaches, and plan against the ship and delivery windows, which are date ranges rather than single dates.
Checked against public Amazon Vendor Central and EDI provider documentation in September 2026. Sources are listed at the end of the page.
How Amazon Vendor Central purchase orders reach you
- Vendor CentralNew POs appear under Confirm New POs, where the vendor accepts or rejects them.
- Selling Partner API: Vendor OrdersAmazon’s public API returns purchase orders (getPurchaseOrders, getPurchaseOrder), their status (getPurchaseOrdersStatus) and takes acknowledgments (submitAcknowledgement). It suits teams with a developer or an integration partner.
Fields on a Amazon Vendor Central PO and where they go in your sheet
| On the Amazon Vendor Central PO | In your order sheet | Watch for |
|---|---|---|
| purchaseOrderNumber | PO number | Add one row per item line on the PO. |
| purchaseOrderType | Notes | For example RegularOrder. |
| purchaseOrderState | Status | New, Acknowledged or Closed. A New PO still needs your answer. |
| shipToParty (partyId) | Ship-to | An Amazon party ID, not an address. Keep a list of the IDs you ship to. |
| ASIN (amazonProductIdentifier) | SKU (mapped) | Amazon’s product ID. Map it to your SKU so totals by SKU line up across channels. |
| vendorProductIdentifier | SKU | Your own product ID, when Amazon has it. Match on it first. |
| orderedQuantity (amount, unitOfMeasure, unitSize) | Cases / Case pack | The unit can be Cases or Eaches, and unitSize says how many eaches are in a case. Read all three before you add up. |
| netCost | Unit price | The cost Amazon pays per unit. listPrice is a separate field. |
| shipWindow / deliveryWindow | Ship by | Date ranges, not single dates. Write the start and end, and plan to the start. |
| isBackOrderAllowed | Notes | Whether Amazon accepts a back order on that line. |
What you send back
- Acknowledgment
- Accept, partially accept or reject each line in Vendor Central or with submitAcknowledgement. Item statuses are ACCEPTED, PARTIALLY_ACCEPTED, REJECTED and UNCONFIRMED. Check the confirmation deadline in your Vendor Central account.
- Shipping inside the window
- Vendor guides describe chargebacks for missing the PO window, along with ship notice, receiving, prep and packaging issues.
- Invoices
- The Selling Partner API also has a Vendor Invoices API for vendors who submit invoices that way.
Where it goes wrong
- Reading a quantity of 10 cases as 10 units ships short. Check unitOfMeasure and unitSize on every line.
- Windows are ranges. Planning to the last day leaves no room for a late truck.
- POs change after they arrive. The API can list orders changed in a time range, so refresh your sheet from changes, not only from new POs.
- The API returns at most 7 days of orders per call and looks back at most 6 months, so a backfill needs several calls.
Turn Amazon Vendor Central POs into one order sheet
- 1Collect the day’s POs from Confirm New POs or from the Vendor Orders API.
- 2Add one row per PO line with the PO number, ASIN mapped to your SKU, ship-to party ID, quantity, unit and unit size.
- 3Convert every quantity to cases using unitSize when the unit is Eaches.
- 4Write the start of the ship window in Ship by and the full window in Notes, then check totals by SKU against stock before you accept.
- 5Record accepted, partial and rejected lines in Status so the sheet matches what you told Amazon.
In Markhub
Combine Amazon Vendor Central POs with every other channel
- 1Download the day’s Amazon Vendor Central POs the way you already do, and post the files in Markhub with the other channels’ files, as csv, xlsx or pdf.
- 2The Order Consolidator agent reads every file and fills one sheet, one row per line, with totals by SKU.
- 3You check short lines and changes, then confirm in Amazon Vendor Central’s own system. Markhub prepares the sheet and does not send anything to Amazon Vendor Central.
Then add the Order Consolidator from the agent library in your workspace.
Questions
What do New, Acknowledged and Closed mean?
They are the purchaseOrderState values. New means the PO is waiting for your answer, Acknowledged means you have answered, and Closed means the order is finished.
Is the quantity in cases or eaches?
Either. orderedQuantity carries an amount, a unitOfMeasure of Cases or Eaches, and a unitSize. Multiply cases by unitSize to get eaches, or divide eaches by it to get cases.
Can I get Amazon POs without the Vendor Central screens?
Yes, through the Selling Partner API’s Vendor Orders endpoints, which need a developer or an integration partner. It returns up to 7 days of orders per call.
Does Markhub connect to Amazon?
No. Markhub does not connect to Vendor Central or the Selling Partner API. You post the PO files you already export, and the Order Consolidator agent combines them with your other channels in one sheet for a person to review.
Other retailers
Sources
- Amazon SP-API: Vendor retail procurement orders
- Amazon: Vendor Orders API model (GitHub)
- Amazon SP-API: Vendor retail procurement FAQ
- Acadia: Amazon Vendor Central orders tutorial
- Carbon6: Amazon vendor chargeback types
Markhub is not affiliated with, endorsed by or connected to Amazon Vendor Central. Amazon Vendor Central is a trademark of its owner. Supplier requirements change, so confirm the details in your own supplier agreement and portal.