Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Retailer EDI · Supply chain
Connect Microsoft Business Central + SPS Commerce
Automate purchase order (850), po acknowledgement (855), ship notice (856), invoice (810), inventory advice (846) between Microsoft Business Central and SPS Commerce — 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 SPS Commerce.
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 SPS Commerce, 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
This page is for supply-chain and customer-service teams trading with retailers through SPS Commerce while Dynamics 365 Business Central runs orders, inventory and invoicing.
What needs to be in place
- An active SPS Commerce relationship with the retailers and document types you trade already identified.
- Business Central (cloud, or on-premises with a supported connection path agreed in scoping) and a service account permitted to create sales documents.
- Item and customer mappings — retailer item numbers, UPC/GTIN, ship-to locations — available or ready to be built.
- A warehouse or 3PL able to act on released orders and return the detail a ship notice requires.
When you may not need this
One retailer with a few orders a week can be keyed in the SPS web portal. A managed integration earns its place once retailer count, document volume or chargeback exposure makes portal work a standing cost.
What is out of scope
- The exact transaction set and format are confirmed per trading partner during scoping — requirements differ by buyer and we do not claim a fixed set here.
- APIWORX does not negotiate partner terms, allowances, discounts or compliance programmes on your behalf.
- Label and packaging compliance remains a warehouse responsibility; the integration supplies the data it needs.
What actually moves, and who owns it
A representative scope using commonly-traded retailer documents. Which documents apply to each of your retailers is confirmed before build.
Microsoft Business CentralAPIWORX (mapping, retries, exception queue)SPS Commerce
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Purchase order (850) | SPS Commerce | Business Central | Retailer | PO received | Held in exception queue with the validation error | APIWORX |
| PO acknowledgement (855) | Business Central | SPS Commerce | Business Central | Order confirmed or amended | Retried, then queued for review | APIWORX |
| Ship notice (856) | Business Central / warehouse | SPS Commerce | Warehouse | Shipment posted | Held with the missing carton or tracking detail flagged | APIWORX with your warehouse |
| Invoice (810) | Business Central | SPS Commerce | Business Central | Posted sales invoice | Queued; retailer rejections reported back | APIWORX |
| Inventory advice (846) | Business Central | SPS Commerce | Business Central | Agreed publishing cadence | Last good file retained; failure raised | APIWORX |
Three decisions that make or break this integration
A retailer order arrives with an item you do not recognise
Inbound purchase orders are validated against your item and customer mappings before anything is written to Business Central, so an unmapped retailer item number does not create a half-built sales order.
- The document is held with the offending line identified rather than partially imported.
- APIWORX adds or corrects the mapping and reprocesses the original document.
- Recurring gaps are raised as a mapping change, not repeated one-off fixes.
A shipment goes out before the warehouse returns carton detail
Ship notices depend on data your warehouse produces. When detail is missing, the notice is held rather than sent incomplete and rejected.
- Missing carton, weight or tracking values are named in the exception.
- Once the warehouse supplies the detail, the notice is sent against the original shipment.
- Repeat gaps are escalated to your named warehouse contact.
Invoices and availability run on defined rules
Invoices are generated from posted Business Central sales invoices with purchase-order and shipment references attached; availability files are published on an agreed cadence where the retailer expects them.
- Invoice content derives from the posted Business Central document.
- PO and ship-notice references carried through for traceability.
- Cadence is agreed in scoping; no real-time claim is made here.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every document is logged with its control reference and the trading partner it belongs to, so a transaction can be traced end to end.
- Failed documents are retried on a defined schedule; anything still failing is held in an exception queue rather than partially processed.
- Duplicate prevention keys on the partner's own purchase order or document identifier.
- Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
- New partners, new document types and changed requirements are handled as mapping work inside the ongoing engagement.
- Support windows and response commitments live in your agreement; this page does not state an SLA.
How a document is traced
Illustrative — not customer data
An illustrative reference trace across the retailer document cycle and Business Central.
| Retailer purchase order number | Business Central sales order number |
|---|---|
| Retailer ship-to location | Business Central location and address |
| Business Central posted shipment | Outbound ship-notice reference |
| Business Central posted invoice | Invoice submission reference |
Scope and questions
- Which documents do you support?
- Confirmed per retailer in scoping. Commonly traded transactions include the purchase order, acknowledgement, ship notice, invoice and inventory advice.
- Do we replace SPS Commerce?
- No. SPS stays as your trading network. APIWORX handles the mapping into Business Central and the daily exception work.
- Does this work with on-premises Business Central?
- A supported connection path is confirmed in scoping. Cloud environments use the standard APIs; on-premises requires an agreed access route.
- Who owns exceptions?
- APIWORX works the queue and escalates to your named contacts when a business decision is required.
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 SPS Commerce + Business Central integration
Tell us your systems and documents. A specialist confirms scope by email.