Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Shopify · Business Central
Connect Dynamics 365 Business Central + Shopify / Shopify Plus
Automate sales order, customer, item and price, inventory by location, shipment status between Dynamics 365 Business Central and Shopify / Shopify Plus — 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 Dynamics 365 Business Central and Shopify / Shopify Plus.
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 Dynamics 365 Business Central and Shopify / Shopify Plus, 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 IT and finance leaders who already know Microsoft ships a Shopify connector for Business Central and want a fair comparison before choosing.
What needs to be in place
- Business Central with API access and a service account permitted to create the documents in scope.
- One or more Shopify stores with API credentials available.
- Requirements the standard connector does not cover — custom mappings, extra systems, or operational ownership.
- A named owner for posting groups, dimensions and item mapping decisions.
When you may not need this
Microsoft's own Shopify connector is a genuine option and for a single store with standard posting it may be all you need. Talk to us when your requirements sit outside it: several stores or brands into one company, a 3PL or marketplace in the same flow, custom dimensions and mappings, or a need for someone to own exceptions day to day.
What is out of scope
- We do not claim the native connector is inadequate in general; the comparison depends on your requirements.
- Which native features you keep and which we replace is decided in scoping, not asserted here.
- Shopify theme and app development are out of scope.
What actually moves, and who owns it
A representative Shopify and Business Central scope, confirmed per customer before build.
Dynamics 365 Business CentralAPIWORX (mapping, retries, exception queue)Shopify / Shopify Plus
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Sales order | Shopify | Business Central | Shopify at capture | Order reaches an agreed status | Held in exception queue with the validation error | APIWORX |
| Customer | Shopify | Business Central | Agreed per customer type | New or changed customer | Unmatched customer raises a named exception | APIWORX |
| Item and price | Business Central | Shopify | Business Central | Item or price change | Retried, then queued with the rejected field | APIWORX |
| Inventory by location | Business Central | Shopify | Business Central | Agreed publishing cadence | Last published figure retained; exception raised | APIWORX |
| Shipment status | Business Central or 3PL | Shopify | Shipment record | Shipment posted | Retried, then queued for review | APIWORX |
| Dimensions and channel tags | Store and mapping table | Business Central | Agreed mapping | Applied per document | Unmapped value raises a named exception | APIWORX (maintenance) / you (approval) |
Three decisions that make or break this integration
Several stores, one company file
Multi-brand and multi-region selling often means several Shopify stores posting into one Business Central company. Each store is mapped separately with its own dimensions, so consolidated finance still reports by channel and brand.
- Store-specific customer, item and posting group mapping.
- Dimensions populated so channel reporting works without manual tagging.
- Currency and tax behaviour agreed per store.
- Duplicate prevention keyed on each store's own order identifier.
Mappings the standard path does not cover
Bundles, kits, gift cards, marketplace orders arriving alongside Shopify, and 3PL fulfilment all need decisions. Those decisions are documented as mappings and rules rather than handled by exception each week.
- Bundle and kit handling agreed against your item setup.
- Marketplace and 3PL flows scoped into the same operating model where relevant.
- Gift card and store credit treatment mapped with finance.
- Anything unmapped stops with a named exception rather than defaulting.
Someone owning it after go-live
The difference customers most often cite is ownership. Runs are monitored, failures are retried, and a person works the exception queue instead of a queue waiting for someone in your team to notice.
- Monitored runs with logged source references.
- Retries on a defined schedule; persistent failures queued, not dropped.
- Mapping maintenance included in the ongoing engagement.
- Escalation to your named contacts when a business decision is needed.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every run is logged with the source record reference so an order, shipment or stock update 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, shipment ID, SKU).
- Exceptions are worked by the APIWORX team and escalated to your named operations contacts when a business decision is needed.
- Mapping changes — new SKUs, new locations, new warehouses, new channels — are part of the ongoing engagement.
- Support windows and response commitments live in your agreement; this page does not state an SLA.
How an order is traced
Illustrative — not customer data
An illustrative reference trace between Shopify and Business Central.
| Shopify order name | Business Central sales order number |
|---|---|
| Shopify store identifier | Business Central dimension value |
| Posted shipment | Shopify fulfilment with tracking |
| Posted sales invoice | Reference shown against the store order |
Scope and questions
- Should we just use Microsoft's Shopify connector?
- Possibly. For a single store with standard posting it may cover you. The reasons teams come to us are multiple stores, additional systems in the same flow, custom mappings and dimensions, and wanting someone to own exceptions.
- Can you run alongside the native connector?
- Which parts you keep and which we take over is decided in scoping. We do not assume a rip-and-replace.
- Do you support Business Central on-premises?
- Deployment model and available API access are confirmed in scoping rather than asserted here.
- Is inventory real time?
- No. Availability is published on an agreed cadence with an agreed calculation, stated in your scope.
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 Shopify + Dynamics 365 Business Central integration
Tell us your systems and documents. A specialist confirms scope by email.