Shopify Dynamics NAV integration

NAV stays. Shopify comes alongside.For retailers with a long-established Dynamics NAV who need a modern store without opening up an ERP project first.

When the combination makes sense

Dynamics NAV has been running stably in many companies for years, usually on premise and with customisations that have grown over time. The question is rarely whether NAV gets replaced, but how the store docks onto it without touching the existing logic. That is exactly what makes the integration plannable: the ERP stays as it is.

Unlike Business Central, there is no bundled Shopify extension here. The connection is built through the NAV web services or through middleware that mediates between the two systems. That is not a disadvantage, but it does mean the interface is a component in its own right, with its own operations, rather than a checkbox in the ERP.

Which objects sync in which direction

The split follows the classic ERP pattern: master data and documents in NAV, orders and customer accounts in the store.

Object	Direction	Leading system	Note
Products	→ Shopify	Dynamics NAV	Via web services or export jobs, often restricted to a store-ready subset of the assortment.
Inventory	→ Shopify	Dynamics NAV	Availability rather than raw stock, calculated with reservations and safety stock.
Prices	→ Shopify	Dynamics NAV	From the NAV sales prices, promotional prices stay in Shopify.
Orders	Shopify →	Shopify	Shopify creates the order, NAV takes it over as a sales order via the integration service.
Customers	↔ both ways	Split by field	Created in the store, customer account assignment and duplicate check in NAV.
Fulfillments	→ Shopify	Dynamics NAV	Goods issue from NAV, tracking back into the Shopify order.
Credit notes	→ Shopify	Dynamics NAV	Sales credit note in NAV, status and refund in Shopify.

Which integration pattern holds up

NAV web services directly
SOAP and OData services can be addressed directly. That saves an intermediate layer, but it moves error handling, retries and logging into the calling service. For a small number of objects and manageable volumes, this works well.
iPaaS with a NAV connection
Integration platforms with ready-made NAV building blocks take monitoring and retries off your hands. With on-premise installations, secure access from outside comes on top, usually via an agent inside your own network.
Custom middleware
The usual route with a heavily customised NAV. A dedicated service keeps the translation between the store model and the ERP model in one place, and later survives a move to Business Central, because only one side is swapped.

Common pitfalls

Custom objects
NAV installations that have grown over time often contain their own tables and fields from earlier projects. What the store needs from them has to be named, otherwise the interface is built on fields nobody maintains any more.
Access to an on-premise environment
Shopify calls in from outside. A server inside your own network needs a controlled route outwards for that, including certificates and maintenance windows. This is an IT question rather than a store question, and it tends to be asked too late.
Product support running out
Mainstream support for the last NAV versions has run out. That does not make the integration impossible, but every interface should be cut so that a later move to Business Central does not take half the integration with it.

Frequently asked questions

Is there a ready-made Shopify connector for NAV?

None from Microsoft. The bundled Shopify extension belongs to Business Central, not to NAV. For NAV the connection runs through NAV's own web services, through an integration platform with ready-made NAV building blocks, or through middleware you build and operate yourself.

Is the integration worth it if an ERP migration is coming anyway?

Usually yes, provided the interface is cut cleanly. If the translation logic sits in a layer of its own, only the ERP side is swapped when you move to Business Central. The store, the data model and the processes stay unchanged.

How does Shopify reach a system in our own data centre?

Through a controlled route outwards: either an integration service in the cloud that can reach the NAV web services, or an agent inside your own network that collects orders. Both need coordination with IT, certificates and a maintenance concept agreed in advance.

Which data should stay in NAV?

Everything that touches inventory, documents and accounting: the item master, prices, orders, deliveries and credit notes. Product copy, images and SEO fields belong in the store or in a PIM instead, because an ERP is not a good place for marketing content.

How does the integration handle outages?

Orders must never be lost while NAV happens to be unreachable. That is why a queue with retries and an error overview belongs between the store and the ERP. Without it, you only notice an outage when customers start asking where their order is.

Shopify Dynamics 365 Business Central integrationFor brands already running Business Central as their leading system that no longer want to maintain products, inventory and orders twice.View integration Shopify Dynamics AX integrationFor companies with an established Dynamics AX installation that are building their own D2C channel without renegotiating ERP processes.View integration Shopify Sage integrationFor retailers with Sage behind them who want to know what their specific Sage line can hand over to a Shopify integration.View integration

System integration: patterns and data ownershipThe overarching view of ERP, PIM, WMS and middleware.