Amazon Vendor Central · NetSuite · InfiPlex OMS Integration
NetSuite + Amazon Vendor Central Integration: Direct Fulfillment and Retail Procurement, run correctly as two different programs
Vendor Central is Amazon's 1P umbrella, but it covers two genuinely different workflows. Direct Fulfillment is individual consumer orders you ship straight to the customer, on Amazon's EDI-document clock (850, 855, 856, 810). Retail Procurement is Amazon buying wholesale inventory in bulk, where every PO line has to be confirmed, revised, and accepted before it becomes a NetSuite order. InfiPlex connects both to NetSuite over the SP-API, but treats them as the separate connections and workflows they actually are, not one generic “Amazon order” flow.
How it works
Two programs, two workflows, one NetSuite connection
Direct Fulfillment runs on a purchase-order document flow: Amazon issues an 850, expects an acknowledgment, and requires a compliant 856 ASN and 810 invoice for every shipment, with orders shipping straight to the customer on Amazon's clock. InfiPlex pulls those POs through the SP-API about every 20 minutes, posts them into NetSuite as sales orders, then reads the tracking NetSuite creates and generates the ASN and invoice to Amazon automatically, no EDI contract needed. See the Direct Fulfillment integration page for the full document lifecycle.
Retail Procurement works differently: Amazon proposes a wholesale PO and expects a line-level response before anything is agreed. InfiPlex evaluates every line against your own auto-confirm rules, one of four types (a minimum inventory threshold, a fixed quantity, a minimum cost, or a minimum price), confirms or rejects accordingly, and re-runs those same rules whenever Amazon sends a revision. Only the order your team accepts is transformed and pushed into NetSuite. See the Vendor Central Retail integration page and the Retail PO lifecycle guide for the full confirmation process.
Both programs share the same NetSuite connection: any standard or custom NetSuite field can be populated or filtered on, and Amazon SKUs map to your NetSuite SKUs and back, so the relationship survives the round trip in either direction.
What’s included
Everything this integration handles for you
-
1P POs Without EDI
Both Amazon Vendor Central programs run over the SP-API, eliminating EDI contracts and per-document fees
-
Line-Level Retail Confirmation
Per-SKU auto-confirm rules evaluate every Retail PO line, and re-run automatically on every revision
-
Custom Field Mapping
InfiPlex configures the NetSuite fields this channel requires, so no one has to build it by hand
-
Warehouse & 3PL Routing
Fulfillment runs through NetSuite exactly as it does for every other channel you sell on
-
Automatic Tracking Push
Tracking numbers created in NetSuite are read back and posted to Amazon Vendor Central automatically
-
On-Demand Order Pull
Select specific NetSuite orders and pull them immediately, without waiting for the next cycle
Related resources
Real questions, answered on our FAQ hubs
These hubs answer real setup and operational questions for the systems this page connects.
Connect the rest of your stack
Pair this with the systems you already run
- Amazon Vendor Central1P orders and Amazon's compliance bar, fully covered
- NetSuiteEvery channel into your ERP, on your own rules
- ShipStationPrefer shipping outside NetSuite? That works too
- 3PL ConnectorRoute these orders straight to your 3PL instead
Direct Fulfillment guides
Running Amazon Direct Fulfillment well
Three guides on the program’s clocks, the chargebacks they trigger, and how Direct Fulfillment compares to Vendor Central retail and Seller Central.
- Direct Fulfillment integrationAcknowledgments, Amazon labels, confirmations, and invoices automated
- Direct Fulfillment order lifecycleEvery deadline, API call, and failure mode, PO to invoice
- Direct Fulfillment chargebacksWhat triggers each one, the cause, and the fix
- DF vs Vendor Central vs Seller CentralWho owns inventory, price, and payment in each program
Vendor Central Retail guides
Running 1P purchase orders well
Confirmation rules, chargebacks, and the case for SP-API over EDI, all written from the Vendor Retail Procurement APIs.
NetSuite guides
Keeping this connection running
Request limits, inventory reads, and field mapping, the parts of a NetSuite integration that actually break.
Ready to run Vendor Central from inside NetSuite?
Your OMS is typically live in 1–3 business days, and our USA‑based team handles onboarding with you — no coding required.
Questions about your exact setup?
Our team configures integrations like this every week. Contact us, email info@infiplex.com, or call 888‑770‑0857 and we’ll walk through your channels, warehouses, and volume together.
