Skip to main content
Store to ERP

Dynamics 365 ecommerce integration for orders, stock and customers

A Dynamics 365 ecommerce integration connects your online store to the system that holds your products, prices, stock and accounts. Orders placed on the website arrive in Dynamics 365 without re-keying, while stock levels and prices flow back to the store. Which Dynamics 365 app you run, Business Central, Finance and Operations or Sales, decides which connector options are open to you.

Shopify connector
built into Business Central by Microsoft
Dual-write
links Finance and Operations with Dataverse apps
Two directions
orders in, stock and prices out
Person packing an online order into a cardboard box at a work table

What a Dynamics 365 ecommerce integration has to move

The store and the ERP each own part of the data. Dynamics 365 should stay the master for items, prices, stock, customers with credit terms and the accounting. The store owns the shopping experience, the cart and often the payment capture. The integration carries records between them on a schedule or as events happen, and it has to cope when both sides change the same record.

Most problems in these projects come from unclear ownership, not from the connector. If staff edit prices in the store and in Dynamics 365, one side will overwrite the other. Decide the owner of each record first, then choose the tool.

Microsoft documents the main building blocks: the Shopify connector for Business Central, the Dynamics 365 Commerce storefront, and dual-write between Finance and Operations and Dataverse. Read them before you compare partner apps, because each one sets limits on what syncs and how often.

Records in a typical Dynamics 365 ecommerce integration

Record
Usual direction
Points to settle
Products and variants
Dynamics 365 to store
Which fields the store owns, such as web descriptions and images
Prices and discounts
Dynamics 365 to store
Customer-specific prices for B2B buyers, currency and tax-inclusive display
Stock levels
Dynamics 365 to store
Which locations count, safety stock and how often to update
Customers
Both ways
Matching guest checkouts to existing accounts by email
Orders
Store to Dynamics 365
Shipping lines, discounts, gift cards and tax rounding
Payments
Store to Dynamics 365
Captured or only authorised, and how payouts reconcile in the bank
Shipments and tracking
Dynamics 365 to store
Partial shipments and the notice the customer receives
Returns and refunds
Both ways
Who starts the refund and how credit memos are created

Connector options for each Dynamics 365 app

Business Central

Microsoft's Shopify connector is part of Business Central. It syncs products, prices, stock, customers and orders, and can create sales documents automatically. Adobe Commerce, WooCommerce or BigCommerce stores use partner apps or custom work against the Business Central APIs.

Dynamics 365 Commerce

Dynamics 365 Commerce includes its own e-commerce site builder on top of Finance and Supply Chain Management. Catalogs, pricing and orders then live in one Microsoft stack, which removes a separate store platform but means a larger project.

Finance and Operations

With an outside store, integrations usually run through data entities, OData or batch imports, often with Azure Logic Apps or an integration platform in between. Throughput limits and batch timing matter, so order volume is part of the design.

Dynamics 365 Sales

In a CRM-led setup, store customers and orders are written to Dataverse so sales and service teams see buying history. With Finance and Operations also in place, dual-write keeps customers and products aligned.

Mistakes that break a Dynamics 365 ecommerce integration

  • ✓Syncing stock once a night for a store that sells fast, so popular items oversell during the day.
  • ✓Letting the store create a new customer for every guest order, which floods Dynamics 365 with duplicates.
  • ✓Posting store orders straight to invoices before payment and shipping are confirmed.
  • ✓Ignoring differences between the store's tax calculation and the ERP's, which leaves small rounding gaps on every order.
  • ✓Writing custom code where a supported connector already exists, then owning every future update yourself.
  • ✓Running without an error queue, so a failed order import goes unseen until the customer calls.

How we run a store integration project

  1. 1

    Map the flows

    List each record, its owner, direction and frequency, using a sample of real orders that includes the awkward ones.

  2. 2

    Pick the tool

    Choose the standard connector, a partner app or custom APIs based on your Dynamics 365 app, store platform and order volume.

  3. 3

    Build in a sandbox

    Connect a test store to a Dynamics 365 sandbox and run orders, returns and stock changes end to end.

  4. 4

    Reconcile

    Check that totals for a test period match between the store, Dynamics 365 and the payment provider's payouts.

  5. 5

    Go live and watch

    Switch on with error alerts in place and review the error queue every day for the first weeks.

Questions about Dynamics 365 ecommerce integration

Does Dynamics 365 have a built-in online store?

Dynamics 365 Commerce does, as part of the Finance and Operations family. Business Central and Dynamics 365 Sales do not include a storefront; they connect to one such as Shopify.

How often should stock levels sync?

As often as your sales speed needs. A store taking a few orders a day can update hourly, while a busy store needs near real-time updates or reserved stock for its fast sellers.

Can B2B customers see their own prices in the store?

Yes, when the integration sends customer-specific prices and the store platform supports logged-in pricing. Settle this early, because not every connector handles it.

Talk to us about your project.

Tell us what you run today and what has to change. A senior consultant replies with a written next step.

Get started

Start with a scoping conversation.

Thirty minutes with a senior consultant, and no sales pitch. We look at how you run today, tell you plainly whether Business Central is the right fit, and give you a realistic sense of scope, cost and timeline before you commit to anything.

What happens next
1
We review your inquiry
A consultant reads it before the call. There is no discovery questionnaire to fill in.
2
30-minute scoping call
Your processes, your current systems, and the gaps that matter most.
3
Written summary & estimate
Indicative phases, license counts and next steps, in writing after the call.
A senior consultant reads every message
NDA signed before discovery on request
No obligation on the first call
Senior consultants on every call
Request your scoping call
A few short fields. A senior consultant reads and replies.
No obligation
Your details stay with our consulting team. We never share them or add them to a mailing list.

Trusted partners

Microsoft Solutions Partner · AWS Partner

View our Microsoft partner listing

Why teams pick us

Dynamics 365 consultingWhat we do
Free readiness assessment2-hour workshop
Reply in one business dayFrom a senior consultant
Scoping in 48 hoursCalls available fast
Fixed scope, fixed priceAgreed in writing
Microsoft-certified teamMB-800 and more
Live chatA real person replies
Secure HTTPSEncrypted end to end
Call now