Shopware ERP Integration with Microsoft Dynamics 365: How It Works
How to connect Shopware 6 with Microsoft Dynamics 365 Business Central: which data flows where, integration options, project steps and common pitfalls.
A Shopware–Dynamics 365 integration connects your online store with your ERP so that products, prices and stock come from Dynamics, and orders and customers flow back from Shopware automatically. There are three ways to build it: a ready-made connector, an integration platform (middleware) or a custom integration using the Shopware Admin API and the Dynamics 365 Business Central API. Most projects start by deciding which system is the leading system for each type of data.
Which data flows where
| Data | Leading system | Direction |
|---|---|---|
| Products, variants, attributes | Dynamics 365 | Dynamics → Shopware |
| Prices, price lists, customer-specific prices | Dynamics 365 | Dynamics → Shopware |
| Stock levels | Dynamics 365 | Dynamics → Shopware (frequent or near real-time) |
| Orders | Shopware | Shopware → Dynamics (as sales orders) |
| Customers and addresses | Depends on the project | One-way or two-way |
| Invoices, delivery status, tracking | Dynamics 365 | Dynamics → Shopware |
Rule of thumb: the ERP owns master data and finance; the shop owns the checkout.
Three integration options
| Option | Best for | Trade-offs |
|---|---|---|
| Ready-made connector (e.g. the Shopware Business Central extension for Shopware 6 Cloud) | Standard processes, quick start | Limited to the fields and flows the connector supports |
| Integration platform / middleware (e.g. Shopware Nexus or an iPaaS) | Several systems (ERP, PIM, marketplaces) | Extra licence; mappings must still be designed |
| Custom API integration | Custom pricing, B2B rules, special workflows | More development and maintenance, but full control |
Project steps
- Data audit: list every entity, field and rule in Dynamics and Shopware.
- Define the leading system for each data type and the sync frequency.
- Field mapping: item numbers, variants, units, tax rates, price groups and customer numbers.
- Build and test on a Dynamics sandbox and a Shopware staging store.
- Error handling: logging, retries and alerts when a sync fails.
- Go-live and monitoring: watch the first orders, stock updates and invoices closely.
An indicative timeline is 4–6 weeks with a ready-made connector and 8–16 weeks for a custom integration with B2B pricing. An audit gives a reliable estimate.
Common pitfalls
- No clear leading system, so data is overwritten in both directions.
- Variants and units of measure that do not match between ERP and shop.
- Stock synced too rarely, which leads to overselling.
- No monitoring, so failed orders are noticed days later.
- Tax and rounding differences between the shop and the ERP.
SolutionThinker is a Shopware Extension Partner and Microsoft certified for Azure, .NET, SharePoint and Microsoft Dynamics. See our Shopware services and Shopware for B2B.
FAQ
Does Shopware have a standard connector for Dynamics 365 Business Central?
Yes. Shopware offers a Business Central integration extension for Shopware 6 Cloud, and several partners offer connectors. Check whether it supports all the data and rules you need before you decide.
Can I connect Shopware to Dynamics 365 Finance and Operations?
Yes, usually through middleware or a custom API integration, because Finance and Operations projects tend to have more complex data and processes.
How often should stock be synced?
As often as your sales volume requires, from every few minutes to near real-time. Fast-moving stock should never be synced only once a day.
Does the same approach work for other ERP systems?
Yes. The steps – leading system, field mapping, testing and monitoring – are the same for other ERP systems; only the connector or API changes.