Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Amazon 1P wholesale · EDI
Connect Microsoft Business Central + Amazon Vendor Central
Automate purchase order (850), po acknowledgement (855), po change (860 / 865), advance ship notice (856), invoice (810) between Microsoft Business Central and Amazon Vendor Central — with monitoring and managed support from APIWORX.
APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.
ERP + eCommerce Specialists
Managed & Monitored Integrations
Expert Integration Team
APIWORX Provides the Service
Yes. APIWORX connects Microsoft Business Central and Amazon Vendor Central.
But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.
APIWORX automates that process end to end — the objects moving between Microsoft Business Central and Amazon Vendor Central, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.
How it works
From requirements to a managed integration
We Design the Integration
APIWORX recommends the integration architecture, mappings and implementation approach.
We Build, Monitor & Support It
APIWORX implements the integration and provides ongoing monitoring and support as applicable.
Who this is for
For vendors selling to Amazon first-party (1P) whose orders, stock and invoicing live in Business Central. Vendor Central is wholesale — this is not the Seller Central marketplace flow.
What needs to be in place
- An active Amazon Vendor Central account with the vendor codes you trade under.
- Confirmation of which Amazon vendor programme applies to each account — standard retail purchase orders and direct-fulfilment programmes behave differently and are scoped separately.
- Business Central sales-document permissions for the integration service account.
- A warehouse or 3PL able to produce carton-level shipment detail.
When you may not need this
A single vendor code with a handful of POs a week can be worked by hand. Integration pays off when acknowledgement windows, carton detail and invoice matching start consuming a person's day, or when deductions become hard to explain.
What is out of scope
- APIWORX does not manage your Amazon commercial terms, cost negotiations or vendor programme enrolment.
- Chargeback and deduction disputes remain yours to file; we make the underlying transaction data traceable so a dispute can be evidenced.
- Retail analytics and forecasting data are out of scope unless explicitly agreed.
What actually moves, and who owns it
The Amazon vendor cycle maps to a well-defined document set. Which of these apply to you depends on your programme, and is confirmed before build.
Microsoft Business CentralAPIWORX (mapping, retries, exception queue)Amazon Vendor Central
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Purchase order (850) | Amazon Vendor Central | Business Central | Amazon | New PO received | Held in exception queue with the failing line identified | APIWORX |
| PO acknowledgement (855) | Business Central | Amazon Vendor Central | Business Central | Confirmed availability per line | Retried; unacknowledged POs alerted before the window closes | APIWORX (delivery) / you (accept, substitute, reject) |
| PO change (860 / 865) | Amazon Vendor Central | Business Central | Amazon | Change received | Escalated when the order has already been picked or shipped | APIWORX (delivery) / you (decision) |
| Advance ship notice (856) | Business Central / WMS | Amazon Vendor Central | Business Central | Shipment posted with carton detail | Rejections queued with Amazon's reason code | APIWORX |
| Invoice (810) | Business Central | Amazon Vendor Central | Business Central | Posted sales invoice | Rejected invoices queued for correction and resubmission | APIWORX |
| Item and cost mapping | Agreed mapping table | Business Central | Business Central | Applied per PO line | Unmapped ASIN/model raises a named exception | APIWORX (maintenance) / you (approval) |
Three decisions that make or break this integration
Which vendor programme you are actually on
The single most common cause of a failed Amazon vendor project is building for the wrong programme. Standard retail purchase orders, where Amazon buys into its own network, behave differently from direct-fulfilment programmes where Amazon passes a consumer order through to you. The documents, the timing expectations and the shipment detail all differ.
- Vendor codes are enumerated per account before mapping starts.
- Each programme is scoped as its own flow rather than forced into one mapping.
- Seller Central activity, if you also sell 3P, is kept separate so vendor invoices are never mixed with marketplace settlements.
PO acknowledgement mapping
Acknowledgement is where availability meets commitment. Amazon expects a per-line answer, and the answer has to reflect what Business Central can actually ship. We agree the rule — confirm, partial, substitute, reject — and then apply it consistently instead of relying on whoever is at the portal.
- Per-line quantity confirmation derived from Business Central availability and your buffer rules.
- Backorder and rejection reasons mapped to the codes Amazon expects.
- Unacknowledged POs surfaced before the window closes, so a missed acknowledgement is an alert rather than a discovery.
Shipment and invoice lifecycle
Amazon's shipment notice and invoice have to agree with each other and with the PO. Building both from the same posted Business Central documents removes the class of deduction caused by mismatched quantities.
- Carton and pallet detail carried from the warehouse or 3PL feed into the shipment notice.
- Invoices built from posted Business Central invoices, referencing the Amazon PO.
- Quantity and cost differences flagged before submission where they can be caught, and traceable afterwards where they cannot.
- Deductions and chargebacks are visible against the original documents so your team can evidence a dispute.
Reliability and ownership
Amazon vendor programmes punish silence. These arrangements make sure a stalled document is noticed by us, not by your buyer.
- Every run is logged with the source record reference so a document can be traced end to end.
- Failed messages are retried on a defined schedule; anything that still fails lands in an exception queue rather than being dropped silently.
- Duplicate prevention keys on the source system's own identifier (order number, PO number, document ID) so a replayed message does not create a second record.
- Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
- Mapping changes — new SKUs, new accounts, new dimensions, new trading-partner requirements — are handled as part of the ongoing engagement.
- Response commitments and support windows are set in your agreement; this page does not state an SLA.
Document cycle at a glance
Standard EDI document reference
These are the standard EDI transaction sets used across Amazon vendor programmes. Which apply to your account is confirmed in scoping.
| 850 — Purchase order | Amazon → you: initiates the order cycle |
|---|---|
| 855 — PO acknowledgement | You → Amazon: per-line accept, partial or reject |
| 860 / 865 — PO change and response | Change requests before despatch |
| 856 — Advance ship notice | You → Amazon: carton-level shipment manifest |
| 810 — Invoice | You → Amazon: invoice referencing the PO |
Scope and questions
- Is this the same as an Amazon Seller Central integration?
- No. Vendor Central is first-party wholesale — Amazon issues purchase orders and you invoice Amazon. Seller Central is marketplace selling with settlements and fees. They are separate flows and we scope them separately.
- Do you handle direct fulfilment?
- Direct-fulfilment programmes are supported as their own flow where your account is enrolled and the applicable interface is confirmed. It is not assumed to be in scope for a standard retail PO integration.
- Can you post acknowledgements automatically?
- Yes, against rules you approve — availability source, buffer, and how partials and rejections are decided. We do not invent a commercial rule on your behalf.
- What happens to chargebacks?
- Deductions stay Amazon's to raise and yours to dispute. What the integration gives you is a traceable chain from PO to shipment to invoice so a dispute is evidenced rather than argued from memory.
- Do we need an EDI VAN?
- That depends on how your account exchanges documents today. Existing network arrangements are usually retained; we confirm the connection path in scoping.
- How long does implementation take?
- It depends on the document set, the number of vendor codes and your warehouse feed. We give you a scoped timeline in the integration plan rather than a number on a web page.
Your integration plan
Get My Integration Plan
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Ready to map your integration?
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Next step
Scope your Amazon Vendor Central + Business Central integration
Tell us your systems and documents. A specialist confirms scope by email.