Mercive Logo
Caret right

Business Central and Shopify: ERP Integration That Works

Why connect Business Central and Shopify

An integration between Business Central and Shopify is about letting one system be the source of truth for numbers and the other the source of truth for sales. When your store and your ERP work in separate silos, staff end up keying in orders by hand, stock becomes unreliable, and bookkeeping falls behind. Microsoft Dynamics 365 Business Central is built to give small and mid-sized businesses an overview of finance, inventory and purchasing, and Shopify is built to sell. Together they close the gap between the storefront and back-office operations.

At Mercive we see many brands reach a point where order volume makes manual handling unsustainable. That is typically where a Dynamics 365 Business Central Shopify integration delivers the most value: orders flow automatically into the ERP, stock levels are pushed back to the store, and your customer records are created without duplicate work. The result is fewer errors, faster fulfillment, and accounts that always reconcile.

What the Shopify connector actually syncs

Microsoft has its own Shopify Connector built into Business Central, and it covers the core flows: orders, customers, inventory, fulfillment status and product data. On the product side it can keep images, variants, barcodes, vendor item numbers, descriptions and tags synchronized between the systems, so you edit in one place instead of two.

The important decision is the direction of each data flow. Should products be created in Business Central and pushed to Shopify, or the other way around? Which system owns the price, and which owns the final stock count? For a B2B-oriented store, customer management and price lists are often the core, while a pure B2C store mainly needs solid order and stock synchronization. We always recommend mapping these flows before configuring anything, because an unclear data direction is the most common cause of trouble later on.

Standard connector or custom integration

The built-in connector covers many needs, but not all of them. If you run Shopify Plus with complex price lists, multiple sales channels, B2B with company-specific pricing or special fulfillment rules, you quickly hit the connector's limits. In those cases we instead build an integration via the Shopify API that matches your exact business logic.

Our approach is to start with the simplest thing that solves the problem. If the standard connector covers the need, we use it and save you the development cost. If it does not, we design a robust Shopify Business Central integration with clear error handling, logging and retry logic, so a temporary API outage does not leave orders in limbo. That is the difference between an integration that works in a demo and one that holds up in daily high-volume operations.

How Mercive approaches an integration project

We start by mapping your current processes: where orders originate, who updates stock, how returns are handled, and where bookkeeping happens today. We then define the data model and the data direction for each object, so there is no doubt about which system wins in a conflict.

We run the implementation in a test environment first, where we validate order and stock flows on real scenarios before go-live. We test edge cases such as partial deliveries, cancellations and discounts, because that is where integrations usually fail. Once the flow is stable, we set up monitoring so you are notified if something goes wrong, rather than finding out through an unhappy customer. If accounting should be fully automated too, we connect it to your bookkeeping setup, in the same way we do in our work with automatic bookkeeping.

Common pitfalls and how to avoid them

The classic mistake is underestimating product data. If SKUs, barcodes and variants do not match exactly between Shopify and Business Central, the sync fails in the most unexpected places. We always clean up master data before turning on any flows, because an integration is only as good as the data it moves.

The second pitfall is real-time stock. Most integrations run in batches with a delay of a few minutes rather than instantly. For high-volume stores with limited inventory, you therefore need to decide how to handle overselling and reservation, so the same last unit is not sold twice.

How Mercive can help

Want to take this further? Read more here:

Frequently asked questions

The built-in connector handles orders, customers, inventory, fulfillment status and product data. At the product level it covers images, variants, barcodes, vendor item numbers, descriptions and tags, so you can maintain data in one place instead of two.

For many stores the built-in connector covers the need. If you have complex price lists, B2B with company-specific pricing, multiple sales channels or special fulfillment rules, you hit its limits, and an API-based integration gives more control and better error handling.

Most integrations run in batches with a delay of a few minutes rather than instantly. For high-volume stores with limited inventory, you therefore need to address overselling and reservation, so the same last unit is not sold twice.

The most common source of errors is master data. Make sure SKUs, barcodes and variants match exactly between the systems before you turn on the sync, and define a clear data direction for each object so conflicts do not arise.

Yes, but the focus differs. A B2C store mainly needs solid order and stock synchronization, while a B2B store often requires customer management and company-specific price lists. We tailor the flows to your business model.