Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Warehouse execution · Operations
Connect Microsoft Dynamics 365 Business Central + ShipHero
Automate order release, item and location mapping, shipment confirmation, posted sales shipment, inventory adjustment between Microsoft Dynamics 365 Business Central and ShipHero — 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 Dynamics 365 Business Central and ShipHero.
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 Dynamics 365 Business Central and ShipHero, 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 running Business Central as the ERP of record with ShipHero executing warehouse work.
What needs to be in place
- Business Central with API access and a service account permitted to read orders and post shipments.
- A ShipHero account with warehouses and SKUs already established.
- An agreed release state and event set between ERP and warehouse.
- A named operations contact for hold and exception decisions.
When you may not need this
A low-volume single warehouse can be run with manual handoffs. Integration earns its place when order volume, multi-location routing or posting accuracy make manual work a standing cost.
What is out of scope
- The warehouse event set returned to Business Central is confirmed in scoping.
- Posting groups, dimensions and document types are agreed with your finance team before build.
- Warehouse operating decisions stay in ShipHero.
- Kitting, lot and serial handling are scoped case by case.
What actually moves, and who owns it
A representative scope. Exact documents and events are confirmed before build.
Microsoft Dynamics 365 Business CentralAPIWORX (mapping, retries, exception queue)ShipHero
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Order release | Business Central | ShipHero | Business Central | Order reaches the agreed release state | Held in exception queue with the validation error | APIWORX |
| Item and location mapping | Business Central | ShipHero | Business Central | New or changed item or location | Order held until mapping is corrected | APIWORX |
| Shipment confirmation | ShipHero | Business Central | ShipHero | Shipment completed | Retried, then queued for review | APIWORX |
| Posted sales shipment | ShipHero event | Business Central | Business Central | Shipment confirmation received | Queued with the order reference | APIWORX |
| Inventory adjustment | ShipHero | Business Central | Agreed in scoping | Adjustment posted in the warehouse | Difference reported, not overwritten | APIWORX |
Three decisions that make or break this integration
A shipment posts against the wrong document
Shipment writebacks are keyed on the Business Central document reference, so a replay or duplicate event does not post a second shipment.
- Duplicate prevention on order and shipment identifiers.
- Failed postings held with the document reference.
- Reprocessing uses the original event, not a re-keyed copy.
Finance needs the posting detail right
Posting groups and dimensions are agreed before build so shipments land where the accounting team expects rather than being corrected each month.
- Dimension mapping confirmed in scoping.
- Validation before posting rather than after.
- Changes handled as configuration inside the engagement.
A second warehouse comes online
Adding a location is mapping work, so growth in fulfilment footprint does not restart the project.
- Location mappings maintained by APIWORX.
- Per-warehouse rules kept separate.
- Exceptions labelled with the warehouse they came from.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every order handed to the fulfilment provider is logged with its ERP reference, and every event returned is matched back to that reference.
- Failed sends are retried on a defined schedule; anything still failing is held in an exception queue with the rejection reason.
- Duplicate prevention keys on the order identifier so a replay never creates a second fulfilment request.
- Inventory positions are reconciled on an agreed cadence rather than assumed to be in step.
- Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
- 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 from Business Central order to posted shipment.
| Business Central sales order number | ShipHero order reference |
|---|---|
| Business Central location code | ShipHero warehouse |
| ShipHero shipment identifier | Posted sales shipment number |
| ShipHero adjustment reference | Business Central item journal entry |
Scope and questions
- Does this post shipments in Business Central?
- Yes, when that is the agreed scope, using the document types and posting rules confirmed with your finance team.
- Which events come back from ShipHero?
- The set is confirmed in scoping rather than assumed from a product feature list.
- Can you support multiple locations?
- Yes — location mappings are configuration maintained inside the engagement.
- 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 ShipHero + Business Central integration
Tell us your systems and documents. A specialist confirms scope by email.