Connecting Business Central to the online shop: What the Microsoft Connector can do

We have Business Central, we have a shop—what does the integration cost? Many conversations begin this way. The honest answer is: It depends on which shop you run. Because with one of the four major systems, Microsoft now includes the integration itself—but not with the other three.

This article explains what the included connector can do, where its limitations are proven, and how you can determine which approach is right for your business. No sales pressure: If the standard connector is sufficient, we'll tell you.

The reason for this article is an observation from practical experience. Companies often plan the integration of their online shop as a purely technical project and only realize late in the process that the real decisions lie in the details: regarding pricing, returns, and who will be responsible for future updates.

Microsoft offers a connector for Shopify.

Since 2022, Business Central has included a Shopify connector, developed and maintained by Microsoft itself. It is free, pre-installed in new Business Central environments, and can be installed in existing environments from the Marketplace. The only requirements are a Business Central license and a Shopify license.

The connector synchronizes in both directions: products and variants, stock levels, orders, and customer data. For a merchant who runs a manageable Shopify store and already keeps their processes close to the standard, this is good news—and a reason not to commission a connection they don't need.

Technically, the connector works via Shopify 's GraphQL admin interface . Microsoft makes the source code openly available and documents the extension points that allow for customization of individual processes. Details can be found in the technical FAQ page for the Shopify connector on Microsoft Learn.

Three limitations that Microsoft itself has documented

It's worth reading the documentation before planning. In practice, three points often determine whether the standard is suitable.

First: Business Central only online

The connector is only available for the cloud version. Those who run Business Central on-premises or are still using Dynamics NAV or Navision cannot use it. For these organizations, there is no alternative to a dedicated connection – technically, this isn't a problem, it's just a different approach.

Secondly, it depends on the Shopify API versions.

Shopify releases a new interface version quarterly and supports each version for twelve months. The connector is tied to the version corresponding to the major version of Business Central. Specifically, this means that anyone who doesn't upgrade Business Central to the new major version in time risks having synchronization blocked.

This isn't an isolated incident or a mistake, but a fixed cycle that needs to be planned from the outset—including who will perform the update and who will test it afterward. Those who fail to clarify these responsibilities won't realize the problem until orders stop coming in.

Thirdly: It does not work with other Dynamics 365 applications.

Those who use Dynamics 365 Sales or Supply Chain Management alongside Business Central and need cross-platform data integration won't get it this way. The connector connects Business Central with Shopify—nothing more.

What else comes into play in practice

Besides the documented limitations, there are four issues that regularly cause projects to stall. They don't appear in any product description , but they determine whether a connection works in everyday use.

Returns and refunds. The returns process is significantly less developed than the outbound process. Those with a high volume of returns—in the fashion and footwear industry, rates exceeding 40 percent are common—quickly notice this.

Customer-specific pricing and booking groups. For B2B retailers, this is often the primary reason for integration: each business customer should see their own terms and conditions, maintained exclusively in the ERP system. This is precisely where the standard system reaches its limits.

Tax cases beyond the norm. Tax exemptions, differing rates for each product group, deliveries abroad – the more complex the situation, the more carefully one should examine beforehand what is transferable and what is not.

Very high order volume. Shopify limits the number of API calls. During peak times, this can cause synchronization to become slower than the business can handle. Anyone expecting triple-digit order volumes per hour during the Christmas season should test this under load beforehand.

Business Central Magento Integration: There is no Microsoft connector for Magento, Shopware, and WooCommerce.

ERP-CRM Integration Connecting JTL-Wawi to Shopware 6: Setting up the connector, synchronizing products and orders

That's the crucial difference. If you operate one of these three shops, there's no built-in solution—the connection is established via the OData and interface endpoints of Business Central. This is well-documented and stable, but it does require configuration.

The advantage of this approach: It avoids the limitations of the standard system. Pricing logic, approval processes, returns, multiple warehouses, differing units of measure—anything the ERP system can handle can be mapped. The disadvantage: It's a project, not a simple installation.

Business Central Magento Connector: what replaces the standard

Who after one Business Central Magento Connector A search will find nothing at Microsoft —
and from third-party providers, building blocks of varying maturity. One Magento Business Central Integration It therefore usually arises as a built interface: articles, inventory,
Prices, orders and customers are managed via the OData v4 endpoints of the Business Central API v2.0.
For Microsoft Business Central Magento 2 There is a limit that needs to be known early on.
The API should limit calls to 6.000 per user and five-minute window. For large...
Catalogs determine the architecture — full synchronization or delta synchronization.

In practice, this is rarely more complex than businesses expect. The scope depends less on the number of items than on the number of special cases: A company with a clean product structure and clear pricing logic will finish faster than a company with five historically grown discount systems.

How you decide

Four questions are usually sufficient for an initial assessment.

Is Business Central running in the cloud or on-premises? If it's an on-premises installation or with Dynamics NAV, the question is already answered — the standard connector is not an option.

Which shop? For Shopify, it's worth taking a look at the standard connector first. With Shopware, Magento, or WooCommerce, this option isn't available from the outset.

How much B2B is involved? Customer-specific pricing, approval processes, and payment terms are the most common reasons why the standard solution isn't sufficient. A purely retail online store can handle these requirements much more easily.

Who handles the updates? If no one in-house is responsible for the version cycle, that's an argument for a solution that isn't dependent on it — or for support that takes care of this part.

Conclusion: Test first, then build

The included connector is a real step forward—for Shopify merchants in the cloud whose processes are close to the standard. For everyone else, the integration remains a task that requires planning: technically manageable, but demanding in terms of content, because the decisions lie in the details.

If you'd like to know which approach is right for your business, we'll analyze your specific setup—shop system, Business Central version, B2B share, and volume. You can find more information about how we connect Dynamics 365 and Business Central to your online shop on our services page. And if your inventory management system isn't from Microsoft: We also integrate other ERP and inventory management systems.