Dynamics 365 Ecommerce Integration: Setup Guide

Not sure which route fits? Book a discovery call and tell us which Dynamics 365 app and which store you run.

Key takeaways

• “Dynamics 365” is a family of products, and the one you run decides how a store connects.
• Business Central and Shopify stores should try Microsoft’s own Shopify Connector before paying for anything else.
• Decide which system owns each field before you switch any sync on.
• Both Business Central and the finance and operations apps answer overload with a 429 error, so build in retries.
• Test in a sandbox, then watch the first live orders in both systems.

Table of contents

• What is a Dynamics 365 ecommerce integration?
• Which Dynamics 365 do you actually run?
• How can you connect your store to Dynamics 365?
• What do Dynamics 365’s API limits mean for your plan?
• How do you set up a Dynamics 365 ecommerce integration in 8 steps?
• What can you learn from a similar ERP sync?
• What mistakes break the sync?
• Who should build a Dynamics 365 ecommerce integration?
• FAQ

If you run Microsoft Dynamics 365 and sell online, you’ll want orders, stock, prices and customers to move between the two without anyone retyping them. This guide shows how to pick the right route, what Microsoft’s own documentation says about limits and what to test before real orders flow.

What is a Dynamics 365 ecommerce integration?

A Dynamics 365 ecommerce integration is a link that moves orders, customers, items, prices and stock between your online store and Dynamics 365, so nobody retypes them. An ERP is the system a company runs its stock, orders and accounts from. Dynamics 365 is Microsoft’s family of business software that includes ERP products.

Orders and customers usually travel from the store into Dynamics 365. Items, prices and stock levels usually travel the other way, when the ERP owns them. You decide which way each field moves.

Refunds and returns need their own path too. Our payment gateway API integration guide covers the payment side of that.

Which Dynamics 365 do you actually run?

Ask whoever administers it, or look at the product name inside the app. Three products matter for ecommerce, and each one connects differently.

Product	What it is	Built-in store link	Main APIs	Typical route for a small store
Dynamics 365 Business Central	The Business Central ERP app	Shopify Connector, preinstalled for new sign-ups and trials	API v2.0, OData and webhooks	Microsoft’s Shopify Connector, or a marketplace connector for other stores
Dynamics 365 Finance and Supply Chain Management	The finance and operations apps	None for online stores	OData, batch data API and custom services	Connect through the APIs
Dynamics 365 Commerce	Microsoft’s omnichannel commerce product, on the platform it shares with Finance and Supply Chain Management	Its own e-commerce storefront and site builder	Headless commerce engine in the Commerce Scale Unit	Only if you move the store onto it

Dynamics 365 Commerce is a product, not a connector. Microsoft’s architecture overview lists its parts: Commerce headquarters, a Commerce Scale Unit that hosts the headless commerce engine, a React-based e-commerce storefront, site builder and the Store Commerce app. If you searched for “dynamics 365 commerce” hoping to link an existing store, you want one of the other two rows.

How can you connect your store to Dynamics 365?

There are four routes, cheapest first. Start at the top and stop at the first one that fits your store, your Dynamics 365 app and your process.

• Microsoft’s Shopify Connector (Business Central and Shopify). Microsoft’s getting started guide says the app is preinstalled for all new sign-ups and trials. You connect each shop from a Shopify Shop card in Business Central. This is the Business Central Shopify integration to look at first. On the Shopify side, the guide points to the Dynamics 365 Business Central app in the Shopify App Store, which is optional if you already have Business Central.
• A marketplace connector. For WooCommerce, Adobe Commerce, BigCommerce or another platform, look for a ready-made connector in an app marketplace. We don’t name or rank any, so check each vendor’s own pricing page and which Dynamics 365 app it supports.
• A custom integration. When your process is unusual, you build against the Business Central API v2.0, or against OData and the batch data API in the finance and operations apps. Our guide to custom API integration services explains the general method.
• Moving the store onto Dynamics 365 Commerce. This only makes sense if you already run Finance and Supply Chain Management and want one platform for stores and web.

Another ERP follows the same pattern. Our Shopify NetSuite integration guide and our NetSuite WooCommerce integration guide show the same store-and-ERP questions with NetSuite behind the shop.

What do Dynamics 365’s API limits mean for your plan?

They mean your integration has to expect being told to slow down. Both Business Central and the finance and operations apps answer an overloaded moment with HTTP 429, Too Many Requests, so your sync needs a retry with a pause, not a crash or a flood of repeat calls.

For Business Central online, Microsoft’s operation limits page lists these OData limits. The first two apply to each user, the last two to the whole environment:

• 6,000 requests in a 5-minute sliding window, and a 429 when you go over.
• 5 requests processed at the same time, with extra ones waiting in a queue.
• A page size of 20,000 records and 100 operations in one $batch request.
• An 8-minute timeout per request, and up to 200 webhook subscriptions.

Microsoft’s API limits guide says to retry after a cool-off period, using regular intervals, growing intervals, exponential back-off or randomization. It also says to use webhooks instead of polling, and to filter, expand, batch and deep insert to cut the number of calls. The limits page says you get more throughput by spreading the work across several users, and that service principals get the same limits as any other user.

The finance and operations apps work differently. Resource-based limits throttle requests with a “Too Many Requests” answer when web server resources run high, and Microsoft’s older per-user limits are switched off from version 10.0.36, with no way to turn them back on. You can give each integration a Low, Medium or High priority on the Throttling priority mapping page, so a critical sync is throttled last.

For volume, Microsoft’s integration overview gives a rule of thumb. Above a few hundred thousand records, use the batch data API instead of OData.

How do you set up a Dynamics 365 ecommerce integration in 8 steps?

To set up a Dynamics 365 ecommerce integration, confirm which Dynamics 365 app and store you have, choose a route, decide who owns each field, map the keys, set up access, test in a sandbox, plan retries and renewals, then go live with a watch period.

Step 1: Confirm the app, the store and the route

Use the table and the decision tree above. Write down which Dynamics 365 product you run, which store platform you sell on and which of the four routes fits.

Step 2: Pick the system of record for each field

Microsoft’s item sync guide says to decide which system owns product data before you configure item sync. If you manage names, descriptions and pricing in Business Central, choose the To Shopify direction. If your merchandising team maintains content in Shopify, choose From Shopify.

Step 3: Map the keys

The connector offers several SKU Mapping options, such as Item No., Item No. plus Variant Code, Vendor Item No. and Bar Code. Pick one early and put that value on every Shopify variant. Also line up locations, shipping methods, payment terms and the accounts that shipping and refunds post to.

Step 4: Set up access

For the Shopify Connector, the user needs the Shopify Admin (SHPFY – ADMIN) permission set. For custom API work, register an application in Microsoft Entra ID and give it its own credentials. Never share a personal login with an integration.

Step 5: Run it in a sandbox first

Connect a test shop to a non-production environment and run real-looking orders through it. Microsoft lists a known issue here: connecting from a sandbox needs HTTP requests to be allowed in that nonproduction environment.

Step 6: Decide how orders become documents

Microsoft’s order sync guide describes the switches. Auto Create Sales Documents builds a sales order when an imported Shopify order needs fulfillment. Auto Release Sales Order releases it, and Use Shopify Order No. reuses the Shopify number if the number series allows manual numbers. Refunds can become a credit memo or a return order.

Step 7: Build in retries and renewals

Handle 429 with a back-off, and alert someone when a sync fails. If you use webhooks, remember that Business Central subscriptions expire after three days unless you renew them with a PATCH request, and the renewal needs the same validation handshake as creating the subscription. The Shopify Connector’s refresh token stays valid for up to 90 days without a successful refresh, after which you reconnect the shop.

Step 8: Go live and watch

Compare the first orders, stock levels and payments in both systems. Keep Shopify’s “Automatically archive the order” setting off, because Microsoft says archived orders can’t be imported. Then keep watching until a few days of orders match.

Microsoft Learn pages and the Shopify App Store listing were checked in October 2026.

What can you learn from a similar ERP sync?

Web25 hasn’t delivered a Dynamics 365 project, so we won’t tell you a Dynamics story. The closest public work is our Mirael3D POHODA case study, a WooCommerce store linked to the POHODA accounting system.

That project exchanged stock and orders in both directions through validated XML. It matched 129 products individually, found 0 stock discrepancies at the full audit and went live one day ahead of the agreed deadline. The cancellation step runs behind an off, log-only or live switch.

Three habits carry over to any ERP, Dynamics 365 included: match on a stable key, do a dry run before live writes, and put destructive steps behind a switch.

What mistakes break the sync?

Beyond the settings in the steps above, these four traps come from Microsoft’s own documentation, and each is cheap to avoid.

• Importing a refund before its original order became a sales document, so Business Central records an error and skips the sales document.
• Using a multi-option variant matrix in Shopify, where the connector can’t create variants for you.
• Exporting units of measure as variants, which can show wrong availability until the next stock sync.
• Skipping the time zone on the company’s post code, which causes date conversion errors.

Who should build a Dynamics 365 ecommerce integration?

For Business Central with Shopify and standard processes, set up Microsoft’s connector yourself or with your Dynamics partner. For another platform with a ready-made connector, ask the connector’s vendor. Custom work only makes sense when no connector covers your process.

Web25 is our agency. This guide covers it alongside alternatives.

Web25 builds custom API and ERP integrations between online stores and business systems as part of its backend and API work. That fits the last group, such as a custom site, a web app or a Microsoft Dynamics website integration that no connector handles.

Whoever you hire, ask three questions:

• Which Dynamics 365 app have you connected before?
• How do you handle 429 errors and webhook renewals?
• What happens to a refund for an order that never synced?

FAQ

What to do next

Write down your Dynamics 365 product, your store and which system owns each field, then work through the eight steps above. If you want a second opinion, book a discovery call and describe your setup.

---

Written by Adam Khaled, Founder, Web25. Last updated October 19, 2026.