Amazon Vendor Central Retail · InfiPlex OMS Integration

Amazon Vendor Central Retail Integration: 1P purchase orders, confirmed by rules, not by hand

Vendor Central Retail is the first-party program where Amazon buys wholesale on purchase orders, receives cartons into its fulfillment centers, and sells as Sold by Amazon. The daily work is PO confirmation inside Amazon's 24-hour window, revision tracking, routing and ASN compliance, and invoicing that matches the confirmed cost. The InfiPlex™ OMS connects your Vendor Central account through the Vendor Retail Procurement SP-API, no EDI fees, pulls every PO, confirms each SKU against rules you set, re-runs those rules on every revision Amazon sends, keeps every revision on record, and invoices per PO from your ERP or by hand.

  • SP-API, Not EDIVendor Retail Procurement APIs through Amazon's approved app; no VAN or per-document fees
  • 24-Hour PO Confirmation, AutomatedPer-SKU rules confirm, partially confirm, or reject before the clock runs
  • USA-Based Support TeamOnboarding, SKU rules, and Vendor Central testing included

How it works

How the InfiPlex Vendor Central Retail integration works

Amazon issues a retail PO with a ship window, a destination fulfillment center, and a unit cost per SKU, and expects a complete acknowledgment within 24 hours: every line accepted, backordered with a new date, or rejected, with quantities that reflect what will actually ship. Amazon can then revise the PO, and each revision expects the same treatment. InfiPlex pulls each PO, runs your confirmation rules against it SKU by SKU, sends the acknowledgment, records the revision, and runs the rules again when Amazon changes anything. Confirmed orders move to your warehouse or 3PL for the routing, labeling, and ASN steps, and once shipped the invoice posts per PO at the agreed cost. The retail PO lifecycle guide walks each step; this page covers what the connection does with them.

Flow diagram: Amazon Vendor Central Retail sends wholesale purchase orders to the InfiPlex Order Management System, which confirms each SKU by rule. InfiPlex pushes confirmations, shipment notices, and invoices back to Amazon, and routes orders to Your Warehouses, 3PL / WMS Partners, Other Channels for fulfillment. Amazon 1P Vendor Central Retail purchase orders Vendor account (SP-API) InfiPlex OMS Orders · Inventory · Shipping 100+ carriers · buffers · automation SINGLE SOURCE OF TRUTH POs pulled, confirmed by per-SKU rules Confirmations, ASNs, invoices back to Amazon Orders routed for fulfillment Ship confirmations + stock levels return Your Warehouses Ship with 100+ carriers 3PL / WMS Partners ShipStation, ShipHero, Extensiv & more Other Channels Amazon & Walmart share the pool
The InfiPlex Vendor Central Retail rail: Amazon purchase orders flow into the OMS and are confirmed SKU by SKU against your rules, ship from your warehouse or 3PL to Amazon’s fulfillment centers, and return confirmations, ASNs, and invoices to Amazon, while inventory stays reconciled across every other channel in one pool.

Auto-confirm rules

Four ways a SKU can confirm itself

Confirmation rules are set per SKU, so a fast-moving core item, a made-to-order item, and a SKU whose cost Amazon keeps drifting can each be handled differently. Four rule types, mixed as needed:

Rule What it does Typical use
Minimum inventory threshold Keeps a floor of M units. If stock covers M plus the requested quantity, confirm it all; if not, confirm what is above the floor; if stock is at or below the floor, reject the SKU, or send a fixed quantity instead Core SKUs that also sell on Seller Central, Walmart, and your own store
Specific inventory amount Confirms a fixed quantity regardless of current stock Made-to-order, drop-in, or replenished-on-demand items
Minimum cost Confirms only if Amazon’s PO cost is at or above your floor SKUs where Amazon’s cost has drifted below the agreed price
Minimum price Confirms only if the PO price is at or above your floor Margin protection on promotional or negotiated items

A SKU with no rule, or one that fails its rule, is not guessed at: it goes to the alert email you configure and waits for a person, while the rest of the PO confirms. Every rule runs on every revision Amazon issues, and the OMS order can either keep the quantity Amazon first requested or follow the quantity you and Amazon finally agreed on, with the full revision history kept either way. Details on the PO automation article.

What’s included

Everything the Vendor Central Retail integration handles for you

  • Per-SKU Confirmation Rules

    Inventory threshold, fixed quantity, minimum cost, and minimum price rules, set SKU by SKU. The full PO acknowledges inside Amazon's 24-hour window without anyone opening Vendor Central.

  • Revisions Tracked and Re-Run

    Amazon changes quantities and dates after the fact. Every revision is stored against the PO and the rules run again, so the acknowledgment on file always reflects the current PO.

  • Requested or Agreed Quantities

    Choose whether the OMS order holds Amazon's original request or the final agreed quantity. Some finance teams want one, some the other; both are supported and the history is preserved.

  • Exceptions to a Human

    A SKU that cannot be auto-confirmed triggers an alert email and waits, while the rest of the PO proceeds. Nothing is confirmed by default that your rules did not approve.

  • Invoices Per PO, From Your ERP

    Invoices post per purchase order at the agreed cost, automatically from NetSuite or manually from the OMS, so cost on the invoice matches cost on the acknowledgment.

  • Warehouses, 3PLs & No EDI Fees

    Ship-from warehouses sync to the connection, orders route to the warehouse or 3PL that ships to Amazon, and the whole exchange runs on SP-API instead of a VAN.

Vendor Central Retail guides

Running retail purchase orders well

Three guides written from Amazon’s vendor rules and the Vendor Retail Procurement APIs, for vendors who are shipping to Amazon or about to be.

Frequently asked

Top Vendor Central Retail questions, answered

The questions vendors ask in their first month, answered in the guides and the Vendor Central integration FAQs:

View all Vendor Central FAQs →

Also in Vendor Central

Retail and Direct Fulfillment are separate connections, in one queue

Retail POs ship to Amazon's fulfillment centers on Amazon's routing rules; Direct Fulfillment POs ship to the customer on Amazon-issued labels. They are separate connections in InfiPlex with separate settings, and they land in the same order queue alongside Seller Central, Walmart, and your own store. Vendors often run both: core SKUs Amazon stocks, and a long tail Amazon lists but does not hold. The Direct Fulfillment integration covers the other half; the Vendor Central overview covers both together.

Connect the rest of your stack

Pair Vendor Central Retail with the systems you already run

InfiPlex connects Vendor Central Retail with 130+ marketplaces, carts, shipping platforms, 3PLs, WMS, and ERP systems, and our Growth Packages include building new API integrations you need at no additional cost.

Ready to stop confirming POs by hand?

Per-SKU rules inside the 24-hour window, every revision tracked, invoices per PO from your ERP, no EDI fees. Live in 1–3 business days with USA‑based onboarding.

Shipping to Amazon and paying an EDI provider to do it?

We connect Vendor Central Retail accounts every week. Contact us, email info@infiplex.com, or call 888‑770‑0857 and bring your PO volume, your ERP, and your current EDI bill.

Amazon, Vendor Central, and Selling Partner API are trademarks of Amazon.com, Inc. or its affiliates. All other marketplace and product names are trademarks of their respective owners. InfiPlex is an independent integration provider and is not endorsed by or affiliated with Amazon. Program rules and deadlines are set by Amazon and are subject to change. ©2026 InfiPlex. All rights reserved.