Shopify to Dynamics 365: A Complete Integration Guide

Last verified: May 2026

Running Shopify and Dynamics 365 Business Central as separate systems is a slow leak. Orders land in Shopify, someone manually keys them into Business Central, inventory counts fall behind, and eventually a customer buys something you don't actually have. It's a familiar story. The fix — connecting the two platforms — sounds simple enough, but the method you pick determines how much maintenance you're signing up for long-term.

Microsoft's own documentation puts it plainly: synchronise orders, stock, and customer information to fulfil orders faster and serve customers better. That's the right frame. This guide covers all three realistic integration paths — native connector, third-party platform, and direct API — with step-by-step instructions for each, plus the errors you'll actually hit along the way.

Whether you run a single Shopify store or manage multiple storefronts feeding one ERP, there's a method here that fits. The right choice depends on your Business Central deployment, your tolerance for ongoing maintenance, and how much custom field mapping you need. We'll get into all of it.

Before you start

• A Shopify account and an active online store.
• A Microsoft Dynamics 365 Business Central account.
• The Shopify Connector app must be installed in Business Central.
• The user must have the Shopify – Admin (SHPFY – ADMIN) permission set in Business Central.

Methods at a glance

Method 1: Native Shopify Connector for Business Central

This is the cleanest option if you're on Business Central SaaS. Microsoft built the connector into the product — it's not something you cobble together from add-ons; it's a first-party integration maintained alongside Business Central updates. As of early 2026, it runs on the January 2026 Shopify API release, which means expanded metafield support and more granular payout data are now available out of the box.

1. Open Business Central and use the search bar (the magnifying glass icon or Alt+Q) to find Shopify Shops.
2. Click New to create a new shop connection. Enter a short code (e.g. MAIN-UK) — this is Business Central's internal identifier for the store, not the Shopify URL.
3. Enter your Shopify store URL in the Shopify URL field (e.g. yourstore.myshopify.com). Business Central will prompt you to authenticate via OAuth.
4. Authorise the connection in the Shopify authentication window that opens. You'll need to be logged into Shopify as a store owner or have the relevant API permissions. Click Install app to confirm. The Shopify App Store listing confirms what permissions are requested.
5. Configure sync settings in the Shopify Shop Card that appears. Here you'll define: which Business Central location maps to which Shopify location, how inventory is calculated (committed stock, available stock, or a formula), and whether Business Central or Shopify is the master for pricing.
6. Set up customer and order sync by scrolling to the Orders and Customers sections of the Shop Card. Decide whether incoming Shopify orders create new BC customers automatically or map to a default customer (useful for B2C where individual customer records aren't needed).
7. Run an initial product sync by navigating to Shopify Products and clicking Sync Products from Shopify. Expect a few minutes for large catalogues. Check the resulting list — each product line should show a mapped BC item number.
8. Run an initial inventory sync by going to Shopify Inventory and clicking Sync Inventory to Shopify. Business Central pushes current stock levels to Shopify. Verify in Shopify admin that quantities updated correctly for two or three SKUs.
9. Enable automatic background sync by setting the Sync Items, Sync Orders, and Sync Inventory job queues to Active in Business Central's Job Queue Entries. These run on a schedule (typically every 30 minutes, configurable).
10. Place a test order in your Shopify store (use a discount code to zero out the charge if needed) and confirm it appears in Business Central under Shopify Orders within one sync cycle.

If your operations extend beyond a single storefront — say you run a UK store and a German store separately — repeat this process for each. Business Central supports multiple Shopify shop configurations, each with independent pricing, inventory locations, and customer mapping. Handy if you're managing stock across multiple channels with different fulfilment rules.

Method 2: Third-party connector / iPaaS platform

Sometimes the native connector doesn't cut it. Maybe you're on Business Central on-premises (the native connector is SaaS-only — more on that below). Maybe you need to sync custom metafields in both directions, or you're feeding data into additional platforms at the same time. That's where third-party integration platforms — broadly called iPaaS (Integration Platform as a Service) — come in. They sit between Shopify and Business Central and handle the translation.

The specific tool you pick matters less than getting the data mapping right. The setup process is broadly the same across platforms.

1. Choose a connector platform that explicitly lists both Shopify and Dynamics 365 Business Central as supported endpoints. Check that it supports your Business Central version (online vs. on-premises) before committing — this trips people up. Paid tiers are typically required for Business Central connectivity.
2. Create a Shopify private app or custom app in your Shopify admin under Apps > App and sales channel settings > Develop apps. Generate API credentials (API key and secret). Note: Shopify now requires custom apps rather than private apps for most API access — follow the in-platform prompts.
3. Create a Business Central API integration. In BC, register the iPaaS tool as an OAuth application or generate API credentials via Azure Active Directory App Registrations if your BC environment uses Azure AD authentication. Your BC partner or admin can help if this is unfamiliar territory.
4. Connect both endpoints in your iPaaS platform using the credentials from steps 2 and 3. Test the connection for each — most platforms show a green tick or equivalent confirmation.
5. Build your data flow mappings. This is where the real work happens. Map Shopify order fields to BC sales order fields, Shopify product variants to BC item variants, and so on. Pay close attention to: tax fields (Shopify stores tax inclusive/exclusive differently than BC expects), currency codes, and any custom metafields you use for product data.
6. Set trigger conditions — e.g. "when a Shopify order reaches Fulfilled status, create a posted shipment in BC" or "when BC inventory drops below zero, send an alert". Most iPaaS tools use trigger-action logic that's reasonably intuitive.
7. Run a test flow with a single order. Trace it end-to-end: Shopify order → iPaaS log → BC sales order. Check that line items, quantities, and customer details all land correctly.
8. Enable the flow for live data and monitor the iPaaS error log daily for the first week. Field mapping issues almost always surface in the first few days of live operation.

This approach pairs well with more complex operational setups — for example, if you're also automating your purchase order workflow or routing data to a separate warehouse management system. Think of the iPaaS layer as a central hub rather than a point-to-point pipe.

Method 3: Direct API (custom build)

This is the highest-effort option and, honestly, most SME brands don't need it. But if you have genuinely bespoke requirements — custom fulfilment logic, non-standard data models, or compliance-driven data handling — a direct API build gives you complete control.

1. Review the Shopify Admin API documentation at shopify.dev/docs/api/admin-rest or the GraphQL equivalent. Decide whether to use REST or GraphQL — GraphQL is where Shopify is heading, and newer endpoints (like Markets and B2B) are GraphQL-only.
2. Review the Business Central API documentation at learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference. BC exposes standard entity APIs (sales orders, items, customers) and supports custom APIs built via AL extensions if you need non-standard entities.
3. Create API credentials for both platforms as described in Method 2, steps 2–3. For BC, OAuth 2.0 via Azure AD is the standard auth flow for production integrations.
4. Design your data model before writing a line of code. Map every Shopify field you need to its BC equivalent. Decide which system is the master record for each entity type (products, customers, inventory). Document this — future-you will be grateful.
5. Build the integration layer — typically a middleware service (Node.js, Python, Azure Functions, etc.) that listens to Shopify webhooks for new events and writes to BC via API calls. Use Shopify webhooks rather than polling where possible; they're more reliable and lower latency.
6. Implement error handling and retry logic from day one. Both APIs rate-limit. Shopify's REST API allows a certain number of requests per second depending on your plan tier; BC has its own throttling. Your middleware needs to handle 429 responses gracefully.
7. Test with a staging environment — both Shopify and Business Central support sandbox/development environments. Don't test against live data.
8. Deploy and monitor. Build an alerting mechanism (email, Slack, whatever you use) for failed sync events. A silent failure in a custom integration can cause significant data drift before anyone notices.

If you're managing a sophisticated multi-channel operation — perhaps alongside a full DTC operations stack — the custom route gives you the flexibility to handle edge cases that break pre-built connectors. Just go in clear-eyed about the ongoing maintenance cost.

Common errors and how to fix them

Native connector not available — "Business Central on-premises" error

The official Microsoft Shopify Connector only works with Business Central in the cloud (SaaS). It isn't supported for on-premises or private cloud deployments. If you're on on-premises BC, your options are a third-party iPaaS connector or a custom API build. There's no workaround — it's an architectural constraint, not a configuration issue.

Custom field mapping mismatches causing data discrepancies

Shopify's metafields and Business Central's custom item attributes don't map automatically. If you use metafields for things like product certifications, material codes, or country-of-origin data, you'll need to configure that mapping explicitly — either in the native connector's metafield settings (expanded in the 2026 API update) or in your iPaaS field mapping. Audit your Shopify metafields before setup and build a mapping document. Fixing data discrepancies after the fact is significantly more painful than getting it right upfront.

Historical data not migrating automatically

This catches a lot of teams off guard. Integration connectors — native or third-party — handle ongoing data flows. They don't retroactively import historical orders, customers, or inventory movements from Shopify into Business Central. If you need historical order data in BC (for reporting, customer history, or financial reconciliation), that's a separate data migration project. Plan for it separately, and factor in data cleaning time — Shopify export formats don't map neatly to BC import templates without transformation.

Sync errors and duplicate records appearing in Business Central

Sync failures typically show up in Business Central's Job Queue Log or the Shopify connector's error log (accessible via the Shopify Shop Card). Common causes: API timeouts during high-traffic periods, conflicting edits to the same record in both systems simultaneously, or an item in Shopify that has no matching SKU in BC. Check the error log first — the messages are usually specific enough to act on. For duplicate customer records specifically, review your customer mapping settings; the native connector lets you match incoming Shopify customers to existing BC customers by email, which prevents most duplicates.

Frequently asked questions

Does Shopify integrate with Microsoft Dynamics 365?

Yes. Microsoft and Shopify partnered to build a native connector directly into Dynamics 365 Business Central. It synchronises orders, inventory, customers, and product data between the two platforms. Third-party and custom API approaches are also available for more complex requirements.

How do I sync inventory from Shopify to Dynamics 365?

Using the native connector, go to Shopify Inventory in Business Central and run Sync Inventory to Shopify for an immediate push, or configure the background job queue to run on a schedule. Business Central acts as the inventory master and pushes current stock levels to Shopify, which prevents overselling. You can map specific BC locations to specific Shopify locations for multi-warehouse setups.

What is the best app to connect Shopify and Dynamics 365 Business Central?

For most Business Central SaaS users, the Microsoft native Shopify Connector is the right starting point — it's first-party, maintained by Microsoft, and covers the majority of sync requirements. If you need more flexibility, custom field mapping, or you're on Business Central on-premises, a third-party iPaaS connector is the next step. A custom API build is only worth it for genuinely bespoke workflows.

Can I connect multiple Shopify stores to one Dynamics 365 environment?

Yes. Business Central supports multiple Shopify shop configurations in a single environment, each with its own setup for locations, pricing, and customer mapping. This is useful if you run separate regional storefronts — a UK store and an EU store, for example — and want to manage inventory and orders centrally. Each shop is configured independently via its own Shopify Shop Card in Business Central.

Which method should you use?

Start with the native connector if you're on Business Central SaaS and your data model is relatively standard — it's genuinely good, it's kept current (the 2026 Wave 1 update added real capability), and the maintenance burden is low. Move to an iPaaS connector if you're on on-premises BC, need bidirectional custom field sync, or want to route data to additional platforms without custom code. Reserve the direct API build for situations where the pre-built options have real gaps your business can't work around — and go in knowing you're taking on ongoing engineering responsibility.

Whatever you build: test with real order data before go-live, set up error alerting from day one, and plan your historical data migration separately. It's the step most teams skip and almost everyone regrets.

For broader operational context, the guides on choosing shipping software, ASN receiving workflows, and batch picking processes are worth reading once your ERP sync is stable — because fixing your data flow often exposes the next bottleneck downstream.