Connecting an E-commerce Store to Business Central: Native Connector, Third-Party, or Custom Integration?

If you run Microsoft Dynamics 365 Business Central and an online store, the question is not whether to connect them. It is how deeply. There are three ways to integrate an e-commerce store with Business Central: the free native Shopify connector, a paid third-party connector, and a custom integration built to your business logic. Each fits a different level of operational complexity, and choosing the wrong one is what turns a simple project into a painful re-platform a year later.

This guide is written for the merchant who is tired of typing the same order into two systems. It covers what the free connector handles cleanly, where growing operations outgrow it, and how to decide which route fits your business, before you commit to any of them.

In Brief

• There are three routes, not two: the free native Shopify connector, a paid third-party connector, and a custom integration. Most coverage of this topic omits one of them, usually for commercial reasons.
• The native connector is free with a Business Central SaaS licence, covers products, inventory, orders, customers and fulfilment bidirectionally, and supports more than one Shopify shop.
• It is Shopify-only and cloud-only. It does not work with on-premises Business Central, and it does not connect Amazon, Magento or WooCommerce.
• Five limits account for most upgrades away from it: complex B2B pricing, multi-channel selling, high peak volume, multi-currency complexity, and intricate product-variant mapping.
• Map pricing, channels, volume and currency against those limits before choosing. That mapping, not the price tag, is what decides the route.
• Cross-border matters in Ireland: 44% of Irish SME online sales are now generated outside Ireland, and cross-border is precisely what stresses a basic store-to-ERP connection.

The Real Question Is Not Whether to Integrate, but How Deeply

The right way to choose a Business Central e-commerce integration is to match the integration depth to the complexity of your business, not to a single product. Most coverage of this topic frames the decision as "use the free connector" versus "buy our paid one." That framing is convenient for whoever is selling the paid connector, and it misses the point entirely.

A single Shopify store with standard products and standard pricing has very different needs from a business selling across Shopify, Amazon, and its own WooCommerce site with customer-specific contract pricing and multi-currency orders. The first is well served by free, native tooling. The second is not. The decision is an architecture question: what does your store-to-ERP connection actually need to do, now and over the next two or three years?

That is the lens this guide uses throughout. Map your real requirements first. Then pick the route that fits them.

The Three Ways to Connect an E-commerce Store to Business Central

There are three integration routes for connecting an online store to Microsoft Dynamics 365 Business Central, and they sit on a spectrum from free and standard to bespoke and business-specific.

The native Shopify connector is built into Business Central and is free with a SaaS licence; you need both a Business Central licence and a Shopify account to use it (Microsoft Learn). It gives bidirectional synchronisation of products, inventory, orders, customers, and fulfilment, and it supports more than one Shopify shop. It is the right starting point for a straightforward Shopify operation.

A third-party connector (an iPaaS platform or an ISV product) is a paid option that adds deeper configuration, support for platforms beyond Shopify such as Amazon, Magento, and WooCommerce, and more advanced B2B features. It fits when the native connector is close but not quite enough.

A custom integration is built to your exact business logic. It is the route when your pricing rules, workflows, sales channels, or order volumes are too specific for any off-the-shelf option to handle cleanly. This is where bespoke development comes in, and it is where Zoosh Digital combines its Business Central expertise with its in-house engineering capability. The wider version of that same build-or-buy judgement, applied across your whole software estate, is set out in our guide to bespoke software development.

The point of laying out all three is not to push you up the spectrum. It is to help you place yourself honestly on it. The table below summarises where each route fits.

What the Native Shopify Connector Does Well

For a single Shopify store with standard products and pricing, the native Business Central Shopify connector handles the essentials cleanly, and for many smaller retailers it is genuinely all they need. Microsoft built it directly into Business Central as part of Shopify's Global ERP Program and made it available in 2022 (Microsoft Dynamics 365 Blog, 26 May 2022).

Here is what it covers without any custom work. Inventory levels synchronise so stock stays accurate and you avoid overselling. Online orders flow into Business Central for fulfilment, including orders from Shopify POS and B2B. Fulfilment and tracking information flows back to the customer, and sales, payments, refunds, and payout information land in Business Central for accurate reporting. Customers and companies sync bidirectionally, with smart mapping by phone, email, or tax number. The connector also supports more than one Shopify shop, each with its own setup and pricing (Microsoft Learn).

Microsoft has continued to invest in it. As of June 2026, the connector handles price synchronisation, inventory location mapping, and B2B support: since April 2024 it has synced Shopify's B2B features, including companies, B2B prices, and payment options (Microsoft Learn release plan). For a business whose operation matches what the connector was designed for, this is a strong, no-cost starting point. Being fair about that is the whole basis for being trusted about the rest.

Where the Native Connector Runs Out of Road

The native Shopify connector covers the basics well, but "the basics" has a ceiling that growing operations tend to hit sooner than they expect. Knowing where that ceiling sits, before you commit, is what prevents an expensive surprise later.

The limits that come up most often across the field fall into five areas.

Complex B2B pricing. Customer-specific tiers, contract rates, and volume discounts are where standard sync gets strained. Recent versions have improved B2B and pricing support, but businesses with genuinely intricate pricing logic still find the edges.

Multi-channel selling. The connector is a Shopify connector. If you also sell on Amazon, Magento, or your own WooCommerce site and you want Business Central to be the single source of truth across all of them, the native option was never designed for that job.

High volume and sync frequency. Operations that spike hard during peak season can find that sync frequency does not keep pace with the volume of orders and inventory movements.

Multi-currency complexity. Multi-currency orders can be mapped, but as the number of currencies, regional storefronts, and tax rules grows, the configuration gets more demanding than a standard setup handles comfortably.

Intricate product-variant mapping. Complex variant structures and attribute mapping can exceed what the standard connector models cleanly.

Note one important constraint that has nothing to do with complexity: the native connector is cloud-only. It does not work with on-premises Business Central deployments (Microsoft Learn). When a business hits any of these limits, the realistic choice is a third-party connector or a custom build.

How to Decide Which Route Fits Your Business

The decision comes down to mapping four dimensions of your operation against the native connector's known limits before assuming free is enough. These four questions do most of the work:

Pricing. Do you run standard pricing, or customer-specific tiers, contract rates, and volume discounts? Standard pricing favours native. Complex B2B pricing pushes you towards third-party or custom.

Channels. Do you sell only on Shopify, or across Shopify, Amazon, Magento, and WooCommerce? A single Shopify store favours native. Multi-channel, with Business Central as the single source of truth, favours third-party or custom.

Volume. Does your order volume stay steady, or spike hard at peak? Steady volume favours native. High, spiky volume needs an architecture designed for it.

Currency and geography. Do you sell domestically, or cross-border across multiple currencies and regional storefronts? Domestic favours native. Cross-border complexity favours a deliberately designed integration.

A simple test: if your honest answer to most of these is the first option, start native. If most of your answers are the second option, the native connector will likely strain, and you should evaluate third-party or custom before you build on a foundation you will outgrow. The same three-layer logic applied to the ERP itself, rather than to the connection into it, is covered in Custom ERP Development: When Off-the-Shelf Genuinely Fails.

The Irish Angle: Cross-Border Selling Is Exactly What Stresses the Native Connector

For Irish online sellers, integration is rarely a domestic-only problem, and that matters because cross-border is precisely the scenario that stresses a basic store-to-ERP connection. PayPal research among 200 Irish SME owners who sell online, conducted in April 2026, found that 44% of their online sales are now generated outside Ireland, and that 80% of those already selling overseas expect cross-border revenue to grow over the next year (ThinkBusiness, 21 May 2026).

Cross-border selling brings together several of the limits described above at once: multiple currencies, multiple regional storefronts, and varied tax handling. These are exactly the areas where the native connector moves from comfortable to demanding. For an Irish merchant whose growth depends on international sales, a well-designed integration, often a custom one, stops being a back-office nicety and becomes a growth enabler.

It is also worth being realistic about platform mix. Shopify is widely used, but plenty of Irish retailers run WooCommerce or other platforms, and a story that assumes everyone is on Shopify understates what Irish businesses actually operate. If your store is not on Shopify at all, the native connector is not an option for you, and the decision moves straight to third-party or custom from the start.

How the Default Has Shifted: From "Build Something" to "Start Native, Extend When Needed"

The right starting assumption for a Business Central e-commerce integration has reversed over the past few years, and many teams still carry the old one without realising it. Before the native connector existed, any link between Business Central and an online store meant a custom integration or a third-party add-on. Integration was, by definition, a development project.

The free native connector flipped that default. Now the sensible path for a straightforward operation is to start native and only move to third-party or custom when the business genuinely outgrows it. That is the real shift: not "build something" and not "the free connector solves everything," but start native if the operation is simple, having first mapped pricing, channels, volume, and currency against the connector's known limits so the integration still fits as the business grows.

Where This Decision Gets Made Badly

The most expensive mistakes in Business Central e-commerce integration are decision mistakes, not technical ones. Five patterns account for most of them.

Choosing an integration route before mapping your actual pricing, channel, volume, and currency needs is the root cause behind most of the others. Buying a paid third-party connector for needs the free native one already meets wastes money on capability you will not use. Commissioning a full custom integration when a third-party connector would have sufficed does the same on a larger scale. Picking a route that fits today but not your direction of travel sets up the painful re-platform that the whole exercise was meant to avoid. And treating integration as a one-off switch to flip, rather than an architecture to design, is the mindset that produces all four.

Zoosh Digital's position on this is deliberately neutral. As both a Business Central partner and a bespoke developer, Zoosh Digital recommends the free native connector when it genuinely fits and builds custom only when a business has outgrown the standard options. In Zoosh Digital's experience advising Irish and UK retailers, the businesses that arrive expecting to need a bespoke integration quite often do not: a correctly configured native connector, or a third-party product, meets the need at a fraction of the cost. Equally, the businesses that assume the free connector will carry them forever are usually the cross-border, multi-channel, or complex-B2B operations that will outgrow it within a year or two. The argument here is not that everyone eventually needs custom. For a large share of smaller retailers, the right match is the free native connector, and moving off it would be spending money to solve a problem they do not have. It is matching the route to the business, in both directions, that matters.

The Questions to Ask Any Integration Partner

Before you commit to an integration route, a sophisticated buyer asks the partner questions that reveal whether the recommendation is driven by your needs or by what the partner sells. These four are a good start:

"Have you mapped our pricing, channels, volume, and currency needs before recommending a route, or are you recommending your default?"

"Where, specifically, will the free native connector stop meeting our needs as we grow, and how far away is that point?"

"If you are recommending a paid connector or a custom build, which exact requirement of ours does the free option fail to meet?"

"What does this cost over three years, including maintenance, not just the initial build?"

A partner who is comfortable answering all four, including pointing you to the free option when it fits, is a partner working from your side of the table. Where the work is done, and by whom, is worth asking in the same conversation; our guide to custom software development in Ireland sets out why that moves the total cost more than the day rate does.

FAQ

Is the native Business Central Shopify connector really free?

Yes. The native Shopify connector is included with a Microsoft Dynamics 365 Business Central SaaS licence at no extra cost, and has been since the 2022 release wave 2. You do need both a Business Central licence and a Shopify account to use it, and it is available for cloud (SaaS) Business Central only, not on-premises deployments (Microsoft Learn).

Can Business Central connect to WooCommerce, Magento, or Amazon, not just Shopify?

Not through the native connector, which is Shopify-only. Connecting Business Central to WooCommerce, Magento, Amazon, or other platforms requires a third-party connector or a custom integration. For businesses selling across several of these channels at once, a custom integration is often what makes Business Central a true single source of truth.

When should we move from the free connector to a third-party or custom integration?

Move when you hit the native connector's known limits: complex B2B pricing, selling across multiple platforms, high peak-season volume, or multi-currency cross-border complexity. The signal is not "the connector broke" but "we are working around it manually." If you map your pricing, channels, volume, and currency needs first, you can usually predict this point before you reach it.

How much does a custom Business Central e-commerce integration cost?

It depends entirely on scope, so any figure quoted without understanding your business is a guess. The more useful framing is total cost over three years, including maintenance, compared against the cost of the manual work and errors the integration removes. A reputable partner will scope the requirement before pricing it, and will tell you if a free or third-party option meets the need for less.

We are on on-premises Business Central. What are our options?

The native Shopify connector does not support on-premises Business Central; it is cloud-only. On-premises deployments need a third-party connector that supports them or a custom integration. This is also a good moment to weigh up a move to cloud Business Central, which opens up the native connector and the wider integration tooling.

Does the native connector handle multi-currency orders?

It maps multi-currency Shopify orders to Business Central currency ledgers, which works for straightforward setups. The strain appears as currencies, regional storefronts, and tax rules multiply, which is common for cross-border Irish sellers. At that level of complexity, a deliberately designed integration usually handles it more reliably than the standard configuration.

Closing Thought: The Cheapest Integration Is the One That Still Fits in Three Years

The temptation with store-to-ERP integration is to optimise for today's invoice. Free connector, switch it on, done. For a genuinely simple operation, that is the correct answer, and no one should talk you out of it. But for a business that is growing, selling cross-border, or adding channels, the cheapest integration over its real lifespan is rarely the cheapest one to start. It is the one designed for where the business is going, so you never have to tear it out and start again.

That is why the route matters more than the price tag. The native connector, a third-party product, and a custom build are not better and worse options. They are right and wrong fits for a given business. The work that pays off is the mapping you do before you choose, not the money you spend after.

If you are weighing up how to connect your store to Business Central and want a straight answer about which route fits, rather than a pitch for the most expensive one, that is exactly the conversation Zoosh Digital is set up to have.

Related Reading

Bespoke Software Development: Custom Solutions for Irish & UK Businesses: the cluster hub, and the wider build-versus-buy decision this integration choice sits inside.

Custom ERP Development: When Off-the-Shelf Genuinely Fails (and When It Does Not): the same three-layer logic applied to the ERP itself rather than the connection into it.

Custom Software Development in Ireland: Why Local Delivery Beats Offshore: how Zoosh Digital approaches bespoke builds when standard tooling runs out.

Business Central Custom Apps: How to Extend Your ERP Without Breaking It: how to extend Business Central itself with upgrade-safe apps, the companion piece to this guide on connecting Business Central to an external store.

Sources

Shopify Connector Overview, Microsoft Learn, Microsoft Dynamics 365 Business Central documentation.

FAQ for technical details, Shopify Connector, Microsoft Learn, Microsoft Dynamics 365 Business Central documentation.

Connect Business Central to Shopify B2B, Microsoft Learn, 2024 release wave 1 plan.

Dynamics 365 Business Central now includes a Shopify connector, Microsoft Dynamics 365 Blog, 26 May 2022.

44% of Irish SME online sales are cross-border, ThinkBusiness, reporting PayPal research conducted April 2026, published 21 May 2026.

From Customisation to Integration: The New ERP Development Mindset, Zoosh Digital.