WooCommerce and Dynamics
WooCommerce and Microsoft Dynamics: plugin, connector or custom build?
Most of what you will find on this is written by someone selling one option. Here are all three, with the point where each one stops being the right choice, including our own.
By itmarkerz Technologies. Updated 30 October 2026.
The three options
| WordPress plugin | Connector or automation platform | Custom build | |
|---|---|---|---|
| What it is | Software installed in your store, usually licensed per year. | A hosted service between the two systems, configured rather than coded. | Code written for your flows, running in the store or beside it. |
| Suits | Standard flows, one Dynamics product, little customisation on either side. | Several systems to connect, or a team already using that platform. | Heavy customisation, unusual rules, or volume where failures are expensive. |
| Mapping | What the screens allow. | Flexible, within what its connectors expose. | Anything the APIs allow. |
| When it fails | Depends on the vendor. Test it. Runs on your store’s server. | Usually a good run history. Check how it recovers from long outages. | Whatever you specify, which also means you have to specify it. |
| Who you call | Vendor support, often separate from Woo and Microsoft support. | Platform support, plus whoever configured it. | Whoever built it, so check that documentation and access are in the contract. |
| Ongoing costs | Licence and updates. | Subscription, sometimes priced on volume. | Maintenance, which rises whenever either side changes. |
| Biggest risk | It almost fits, and you bend your process around the gap. | Costs grow with volume, and logic is scattered across flows. | You pay for something a product already does. |
How the choice changes by Dynamics product
“Dynamics” isn’t one product, so check this first. A plugin that supports Business Central may do nothing for Finance. We go deeper in Business Central, Sales or Finance.
| Product | Connects through | What this means for the choice |
|---|---|---|
| Business Central | REST API v2.0, with webhooks | The most likely place to find a product that fits. Check customised fields and tax setup. |
| Dynamics 365 Sales | Dataverse Web API | Good for customers and enquiries. Ask how a product models orders and invoices, because they may live in your ERP instead. |
| Finance, Supply Chain | OData data entities and batch data import | Fewer off-the-shelf fits, more configuration. A custom route or a platform is more common here. |
| Older on-premises versions | Depends on version | Get the exact version first, and check it is still supported. |
Sync direction and order volume
One-way, a small number of orders each day: almost any option works. Start with the cheapest, and don’t commission a custom build for this unless your rules are unusual.
Two-way: conflict handling becomes the real product. Ask each vendor exactly what happens when a customer’s address changes on both sides. If the answer is that the latest change wins, see the conflict rules in our mapping guide and decide whether you can live with it.
High volume: what matters is what happens during your busiest hour. A plugin working inside each checkout request can slow the checkout, and the APIs have documented limits that a burst of orders can reach. Look for background processing and retries that respect a 429. Our high-volume guide has the detail.
Five failure tests to run before you pay
Demos show the working case. Run these in your Dynamics sandbox, whichever option you are looking at, and hold us to them too.
- Turn Dynamics off for an hour and place ten orders. Does the store keep selling? Do all ten arrive afterwards, once each?
- Send the same order twice. Do you get one sales order or two?
- Use an unknown SKU. Is someone told, and how soon, or does the order disappear quietly?
- Check a multi-line order with a coupon and shipping against the Dynamics total, to the cent.
- Ask for a reconciliation report. Can you see, for yesterday, every order and whether it arrived? If nobody can show you that, you will find out about gaps from your accountant.
When custom is the wrong answer
If your flows are standard and a product passes those tests, buy the product. A custom integration has to be maintained whenever WooCommerce or Dynamics changes, and that cost doesn’t end. It becomes worth it when the gap between a product and your process is costing someone time every day, or when a failed sync costs real money.
We built custom on a WordPress site for a water-treatment supplier, sending enquiries into Dynamics with mapping, validation and retry, and on a high-volume store whose orders and customers sync to Dynamics. If you want to talk about that route, see the integration service. For the store in general, see WooCommerce development.
The two custom integrations mentioned above
Three years keeping a high-volume Belgian WooCommerce store up, fast and in sync with Microsoft Dynamics: PHP 7.4 to current, two-hourly backups to S3-compatible storage, monitoring, and every change request handled.
- Sector
- E-commerce & retail
- Region
- Belgium
- Stack
- WordPress, WooCommerce, Microsoft Dynamics
- Engagement
- Maintenance, three years and ongoing
WordPress website plus an integration that sends enquiries and customer data straight into Microsoft Dynamics for a Belgian supplier of water-treatment systems to businesses. Fixed-scope project.
- Sector
- Industrial & B2B
- Region
- Belgium
- Stack
- WordPress, Microsoft Dynamics
- Engagement
- Fixed-scope project
Questions
Why don't you name the plugins and connectors?
Listings, prices and supported products change, and we would rather you checked them on the day you buy. The questions on this page are the ones to ask each vendor, whoever they are.
You build custom integrations. Isn't this biased?
We do, so weigh that. We say plainly when a plugin is enough: if a product does what you need and passes the failure tests below, buy it. A custom build you don't need is a cost you keep paying to maintain.
Can we start with a plugin and move to custom later?
Yes, and it is a reasonable way to learn what you actually need. Keep your field mapping written down outside the plugin, and keep the shared keys clean, so you can move without untangling the data.
More on WooCommerce and Dynamics
- WooCommerce to Microsoft Dynamics: field mapping and sync guideOrders, customers, products and invoices, field by field, with conflict rules.
- Business Central, Sales or Finance: how each changes a WooCommerce integrationDifferent APIs, limits and change notifications for each product.
- Syncing WooCommerce orders to Dynamics at high volumeQueues, duplicate protection, throttling and daily reconciliation.
- WordPress forms into Dynamics, without a plugin that almost fitsMapping, validation and retry for enquiries that must not go missing.
- Moving a live WooCommerce store from PHP 7.4 to currentThe order of work on a store that has to keep selling.
- What WooCommerce maintenance should include for a store that can’t go downThe questions to ask any provider, with our own plans compared.
- How often should a WooCommerce store back up?Working out a schedule from your own orders, and testing the restore.
Not sure which of the three you need?
Tell us which Dynamics product you run, what should sync and how many orders you handle. If a plugin will do, we will say so.
We reply within one business day (IST).