Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Shipping · Supply chain
Connect Microsoft Business Central + ShipStation
Automate releasable sales order, shipment confirmation, tracking number and carrier service, shipping charge, item, location and store mapping between Microsoft Business Central and ShipStation — 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 ShipStation.
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 ShipStation, 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 operations teams shipping from ShipStation while Dynamics 365 Business Central holds orders, inventory and invoicing.
What needs to be in place
- Business Central (cloud, or on-premises with a supported connection path agreed in scoping) and a service account permitted to post shipments.
- A ShipStation account with the stores, warehouses and carrier services you ship on.
- Agreed rules for which orders release to the warehouse and when.
- A decision on whether shipments post as posted shipments, warehouse shipments or another document.
When you may not need this
If a single warehouse ships a handful of parcels a day from channel data alone, integration may be unnecessary. It earns its place when ERP and warehouse states need to agree every day across multiple locations or channels.
What is out of scope
- The Business Central document a shipment posts against is confirmed in scoping; this page does not assume one.
- Charge data availability depends on your ShipStation plan and carrier setup and is confirmed before build.
- APIWORX does not manage carrier accounts, rates or label compliance.
- Rate shopping and packing decisions remain warehouse responsibilities.
What actually moves, and who owns it
A representative scope. Objects, direction and cadence are confirmed in scoping.
Microsoft Business CentralAPIWORX (mapping, retries, exception queue)ShipStation
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Releasable sales order | Business Central | ShipStation | Business Central | Order reaches the agreed release state | Held with the missing address or item detail named | APIWORX |
| Shipment confirmation | ShipStation | Business Central | ShipStation | Label created / shipment marked shipped | Retried, then queued for review | APIWORX |
| Tracking number and carrier service | ShipStation | Business Central | ShipStation | With the shipment confirmation | Queued with the shipment reference | APIWORX |
| Shipping charge | ShipStation | Business Central | ShipStation | Where charge data is available and in agreed scope | Held for review rather than posted incomplete | APIWORX |
| Item, location and store mapping | Business Central | ShipStation | Business Central | Mapping change | Change held for confirmation | APIWORX |
Three decisions that make or break this integration
Orders release on your rules, not everything at once
Only orders in the state you nominate are pushed to ShipStation, so credit holds, backorders and unapproved orders do not reach the pick queue.
- Release conditions agreed in scoping.
- Held orders release automatically when the condition clears.
- Address and item validation happens before the push.
A shipment must post against the right document
Shipment writeback targets the Business Central document you nominate, so inventory and invoicing behave the way your finance and warehouse processes expect.
- Target document confirmed in scoping before build.
- Partial shipments leave remaining quantities open.
- Duplicate prevention keys on order and shipment identifiers.
Multiple locations and channels stay separated
Store and location mappings keep each warehouse and sales channel distinguishable, so exceptions can be routed to the team that owns them.
- Per-location ship-from mappings.
- Channel-specific rules where they differ.
- New locations handled as configuration work in the engagement.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every shipment message is logged with the source order reference so a parcel can be traced back to its order.
- Failed writebacks are retried on a defined schedule; anything still failing is held in an exception queue rather than silently dropped.
- Duplicate prevention keys on the order number and shipment identifier so a replay does not create a second fulfilment.
- Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
- New warehouses, carriers, service levels and store mappings are handled as configuration work inside the ongoing engagement.
- Support windows and response commitments live in your agreement; this page does not state an SLA.
How a shipment is traced
Illustrative — not customer data
An illustrative reference trace between Business Central and ShipStation.
| Business Central sales order number | ShipStation order number |
|---|---|
| Business Central location code | ShipStation ship-from location |
| ShipStation shipment identifier | Business Central posted shipment |
| Carrier tracking number | Tracking value on the Business Central document |
Scope and questions
- Which Business Central document do shipments post to?
- Confirmed in scoping. The right target depends on whether you use warehouse shipments, posted shipments or invoice-driven fulfilment.
- Do shipping charges come back?
- Where charge data is available from your ShipStation setup and you have agreed the accounts. Otherwise shipments post without a charge value rather than an estimated one.
- Does this work with on-premises Business Central?
- A supported connection path is confirmed in scoping. Cloud uses 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 Business Central + ShipStation integration
Tell us your systems and documents. A specialist confirms scope by email.