ERP integration
Shopify Dynamics AX integration
AX at the core. Shopify at the front.
For companies with an established Dynamics AX installation that are building their own D2C channel without renegotiating ERP processes.
When the combination makes sense
Dynamics AX usually sits in larger organisations with several legal entities, languages and storage locations. The store is rarely the leading system there, but one channel among several. That is exactly why Shopify pays off: the sales channel can be moved quickly, while the ERP processes keep their own, slower cadence.
The challenge lies less in the technology than in the scope. AX models price determination, discount tiers, inventory dimensions and legal entities in a very differentiated way. A store only needs a section of that. The actual work consists of defining that section, instead of rebuilding the ERP model one to one in Shopify.
Which objects sync in which direction
With several legal entities, a second question attaches to every object: which entity and which storage location apply to this store?
| Object | Direction | Leading system | Note |
|---|---|---|---|
| Products | → Shopify | Dynamics AX | Released products per legal entity, with dimensions as Shopify variants. |
| Inventory | → Shopify | Dynamics AX | Per storage location, calculated as available quantity rather than physical stock. |
| Prices | → Shopify | Dynamics AX | Trade agreements go far beyond what Shopify prices can express, so only a defined section goes into the store. |
| Orders | Shopify → | Shopify | Shopify creates the order, AX takes it over as a sales order of the responsible legal entity. |
| Customers | ↔ both ways | Split by field | Created in the store, customer number and assignment in AX. |
| Fulfillments | → Shopify | Dynamics AX | Delivery note from AX, tracking back to the Shopify order. |
| Credit notes | → Shopify | Dynamics AX | Credit note and return order in AX, refund via Shopify. |
Which integration pattern holds up
AX services via an integration layer
AX exposes business logic through services that can be called from outside. Calling them straight from Shopify is not a good idea, because a layer belongs in between that translates formats, throttles calls and catches errors.
iPaaS with an enterprise connection
For organisations with several channels and systems, an integration platform is the pragmatic route. It comes with logging, roles and operating processes that are required in an enterprise environment anyway.
Custom middleware
The usual route with a heavily customised AX. A dedicated service keeps the store model lean and bundles the translation in one place. That pays off at the latest when you move to Dynamics 365 Finance & Supply Chain Management.
Common pitfalls
Inventory dimensions
AX knows sites, bins, batches and more. Shopify knows locations. Which dimensions the store should see at all has to be decided in advance, otherwise you end up with an inventory figure nobody can explain.
Rebuilding price determination
Trade agreements with tiers, customer groups and validity periods cannot be modelled completely in Shopify. The attempt ends in a second pricing logic in the store, which at some point diverges from the first.
Several legal entities in one store
As soon as one store generates revenue for several legal entities, every order needs an unambiguous assignment. That rule belongs in the integration, not in an Excel list in customer service.
FAQ
Frequently asked questions
Can Shopify talk to Dynamics AX directly?
Technically AX services can be called from outside, but without an intermediate layer that is fragile. Error handling, retries, format translation and rate limiting belong in an integration layer of their own, otherwise the store hangs directly off the availability of the ERP.
How does the integration handle multiple legal entities?
Every order needs an unambiguous assignment to a legal entity and a warehouse. A rule per market or per store is the usual approach. Without that decision, documents end up in the wrong posting logic, and correcting them after the fact is laborious.
Should we move to Dynamics 365 before building the store?
Not necessarily. If the integration is built as a layer of its own, the store stays largely unaffected by a later ERP change. Conversely, a migration project already under way should not block the store launch, because both timelines can be decoupled.
Which prices belong in the store?
Only the section the store genuinely needs: the sales price for the relevant customer groups. Complex trade agreements stay in AX. For B2B terms the route runs through Shopify catalogs and price lists, not through the standard price on the product.
How often does inventory need to be updated?
Often enough that overselling stays unlikely. In practice that means short intervals or event-driven updates for fast-moving items, plus a nightly full reconciliation as a safety net. Safety stock levels absorb whatever gap is still left between two synchronisation runs.
Keep reading
Related integrations
Next step
Not sure which pattern carries your setup?
A 30-minute intro call. We look at your systems, ask which data belongs where and give you a clear assessment before anything gets built.
Free and non-binding · 30 min.