Shopify Dynamics 365 Business Central integration

Business Central and Shopify. One source of truth.For brands already running Business Central as their leading system that no longer want to maintain products, inventory and orders twice.

When the combination makes sense

For many growing brands, Business Central is the system where purchasing, warehousing and accounting come together. Shopify is the channel in front of it. As long as the two stay separate, someone maintains products twice, inventory figures drift apart and every order is typed into the ERP by hand. That works up to a certain order volume, after which it gets expensive.

What makes the combination attractive is that Microsoft ships its own Shopify connector extension with Business Central. For standard processes you therefore do not necessarily have to buy middleware. As soon as your pricing logic, your variants or your B2B business depart from the standard, you still need a decision about what the connector covers and what it does not.

Which objects sync in which direction

The direction is not a matter of taste. It follows from which system creates the object and who corrects it when something goes wrong.

Object	Direction	Leading system	Note
Products	→ Shopify	Dynamics 365 Business Central	Master data and variants are created in the ERP, Shopify receives the sales-relevant fields.
Inventory	→ Shopify	Dynamics 365 Business Central	After the warehouse posting, and depending on the site also split by Shopify location.
Prices	→ Shopify	Dynamics 365 Business Central	Sales prices and price groups come from Business Central, promotions usually stay in Shopify.
Orders	Shopify →	Shopify	Shopify creates the order, Business Central takes it over as a sales order including the payment method.
Customers	↔ both ways	Split by field	Created in the store, duplicate check and customer account number in the ERP.
Fulfillments	→ Shopify	Dynamics 365 Business Central	Shipping confirmation and tracking flow back from the ERP into the Shopify order.
Credit notes	→ Shopify	Dynamics 365 Business Central	Returns and cancellations are posted as credit notes in the ERP and mirrored in Shopify.

Which integration pattern holds up

Native connector extension
The bundled Shopify connector covers products, customers, orders and inventory as standard. For a D2C assortment without special logic, this is the fastest and cheapest route, and the one your Business Central partner can look after themselves.
iPaaS between the two systems
As soon as a third system joins in, such as a warehouse, marketplaces or a PIM, an integration platform starts to pay off. You get monitoring, retries and mapping interfaces, but you pay an ongoing fee per transaction or per connection.
Custom middleware
When price determination, bundles or B2B terms depart from the standard logic, a dedicated integration service is often more honest than an over-configured connector. The effort sits at the front, in exchange the logic stays readable and testable.

Common pitfalls

Variant mapping
Business Central works with variant codes, Shopify works with options and variants across a maximum of three dimensions. Assortments with four or more attributes need an upfront decision on what becomes a variant and what becomes a metafield.
Price groups and discounts
Customer-specific prices from the ERP cannot be mapped one to one onto Shopify prices. For B2B the route runs through catalogs and price lists, not through the standard price on the product.
Inventory across several warehouses
If several storage locations are posted in the ERP, it has to be defined which of them feed into which Shopify location. Without that mapping, the store oversells at exactly the moment when it hurts.

Frequently asked questions

Do I need middleware for Shopify and Business Central?

Not necessarily. Microsoft ships its own Shopify connector extension, which covers products, customers, orders and inventory as standard. Middleware only becomes necessary once further systems join the picture, or when your pricing and variant logic departs from the standard that the connector assumes.

Which system owns the product master data?

In almost every setup the ERP, because purchasing, costing and inventory all hang off it. Shopify receives the sales-relevant fields. Marketing copy, images and SEO fields, on the other hand, sensibly stay in the store or in a PIM, not in Business Central.

How often should inventory be synchronised?

Inventory is the most critical object, because errors lead directly to overselling. Short intervals in the range of minutes are common, as are event-driven updates after every stock posting. A nightly full reconciliation as a safety net is a sensible addition, but it is not a replacement.

Does this work for B2B on Shopify as well?

Yes, but not through the standard price. Company accounts, catalogs and price lists are modelled separately in Shopify and populated from the ERP terms. Which types of pricing condition can be transferred cleanly is a question that belongs before implementation, not after it.

What happens with returns and credit notes?

The reversal belongs in the ERP, because inventory, document and accounting are connected there. Shopify shows the status, Business Central posts the credit note. What matters is that the refund is triggered exactly once, otherwise payment data and accounting drift apart over time.

Shopify Dynamics NAV integrationFor retailers with a long-established Dynamics NAV who need a modern store without opening up an ERP project first.View integration Shopify Oracle NetSuite integrationFor brands that use NetSuite as the single source of truth for inventory, orders and accounting, with Shopify as the fast sales channel in front.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.