Quick answer

A dedicated Business Central WooCommerce connector is the best fit for most stores that need two-way inventory, order, price and invoice sync with little in-house development. Power Automate suits simple, low-volume flows. An iPaaS such as Azure Logic Apps suits companies integrating many systems. A custom build suits unusual processes, if you can maintain it.

Four ways to connect WooCommerce and Business Central

There are four realistic ways to build a WooCommerce Business Central integration, and I get asked to compare them almost every week. Store owners usually arrive with one of two ideas: "we already pay for Microsoft 365, so Power Automate must be free", or "our developer can build it in a month".

Both can be true. Both can also go badly. The right answer depends on how much data you sync, how often it changes, and who will look after the integration once it is live.

This guide compares a dedicated Business Central WooCommerce connector with Power Automate, an iPaaS platform and a custom build, using the limits Microsoft publishes and the problems I see after go-live. If you are thinking about the wider picture first, our piece on ecommerce automation with Business Central explains what a fully automated WooCommerce backend looks like. Whichever option you pick, it has to support a reliable order management system, and it has to respect one rule: Business Central is the ERP as the master record for WooCommerce stock and prices.

What are the four options?

Each option moves the same data: inventory, orders, products, customers, prices and invoices. They differ in who builds the logic, who maintains it and how it scales.

1. Dedicated Business Central WooCommerce connector. A ready-made app built only for this pairing. The vendor owns the sync logic, the mapping screens and the updates.
2. Power Automate. Microsoft's low-code automation tool. You build flows yourself using the Business Central connector and a WooCommerce connector.
3. iPaaS (integration platform as a service). A general integration platform, such as Azure Logic Apps or a commercial middleware product, used to connect many systems at once.
4. Custom build. A developer writes an AL extension inside Business Central, or an external service, that calls the WooCommerce REST API and the Business Central APIs directly.

Business Central WooCommerce connector vs alternatives: side by side

Here is how the four options compare on the points that matter after launch. The ratings are my view, based on what each approach includes out of the box.

The pattern is simple. The more a tool is built for general automation, the more of the WooCommerce Business Central logic you have to build and maintain yourself. A Business Central WooCommerce connector trades flexibility for logic that already exists.

Option 1: a dedicated Business Central WooCommerce connector

A dedicated Business Central WooCommerce connector is purpose-built software that already knows how WooCommerce orders map to Business Central sales orders, how SKUs map to items, and how price lists map to WooCommerce prices. You configure it rather than build it.

What you usually get:

• Two-way sync for orders, inventory, products, customers, prices, shipments and invoices.
• Mapping screens for locations, payment methods, tax, customers and discounts.
• Error logs and retries, so a failed sync does not disappear.
• Support and compatibility updates when Business Central or WooCommerce release new versions.

For B2B sellers, a Business Central WooCommerce connector also tends to handle the hard parts that are painful to build yourself: customer price groups, payment terms and customer-specific catalogs in WooCommerce.

What setup involves. Setting up a Business Central WooCommerce connector is configuration rather than development. You generate WooCommerce REST API keys, authorize the Business Central connection, map locations, payment methods, tax and customers, then run test orders in a sandbox. The technical connection takes hours; most of the project time goes into checking the mapping against real orders before go-live.

Where it falls short. A Business Central WooCommerce connector covers the standard flows. If your business runs a genuinely unusual process, for example a custom manufacturing step triggered by web orders, you may need the vendor to customize it or add a small side flow. Ask about customization before you buy.

My view. For most WooCommerce stores on Business Central, a dedicated Business Central WooCommerce connector is the lowest-risk path. The logic is tested across many stores, and when Microsoft ships a release wave, fixing compatibility is the vendor's job, not yours.

Option 2: Power Automate

Power Automate lets you build flows that react to events in Business Central or WooCommerce. Microsoft's Business Central connector for Power Automate includes triggers such as "When a record is created (V3)" and "When a record is modified (V3)", and actions to find, create and update records.

It is a capable tool. I would use it without hesitation for small jobs: sending a Teams message when a large web order arrives, or emailing finance when a credit memo posts. Using it as your main Business Central WooCommerce connector is a different matter, for four reasons that come straight from Microsoft's documentation:

1. It is a premium connector. The Business Central connector is classed as premium in Power Automate, so the account that runs your flows needs a paid plan.
2. It has throttling limits. Microsoft lists 300 API calls per connection per 60 seconds for the Business Central connector. A busy sale day with stock updates on many items can reach that.
3. Bulk changes can skip flows. Business Central webhooks send a single "collection" notification when more than 1,000 records change within 30 seconds, and Microsoft notes the Power Automate connector cannot process collection notifications. In practice, a large price list update or stock import may not trigger your flow at all.
4. The WooCommerce side is third-party. The WooCommerce connector in the Power Platform catalogue is published by a third party, lists a limit of 100 API calls per connection per 60 seconds, and requires a paid companion WordPress plugin.

None of these is a dealbreaker on its own. Together, they mean a Power Automate build of a full Business Central WooCommerce connector needs careful design: batching, retries, a scheduled catch-up flow for bulk changes, and someone on your team who owns every flow.

Best for: single stores with low order volume and one or two simple flows, or as a companion to a dedicated Business Central WooCommerce connector for notifications and approvals.

Option 3: an iPaaS such as Azure Logic Apps

An iPaaS is a general integration platform for connecting many systems through one hub. Azure Logic Apps is Microsoft's own example. It offers more than 1,400 prebuilt connectors and two hosting models: Consumption, billed per execution, and Standard, billed on a hosting plan. Interestingly, the Business Central connector is classed as standard rather than premium in Logic Apps.

An iPaaS makes sense when WooCommerce and Business Central are two of many systems: a 3PL, a marketplace, a CRM, a PIM, a shipping platform. Then one integration hub with shared monitoring is easier to manage than several point-to-point connectors.

There is a design detail worth knowing. Microsoft documents that Logic Apps delivers messages "at least once", so rarely a message arrives twice, and your workflows must handle duplicates safely. For a WooCommerce Business Central integration, that means every order-creation step must check whether the order already exists in Business Central before creating it. A dedicated Business Central WooCommerce connector already does this matching; on an iPaaS, you or your partner design it.

Best for: mid-size and larger companies with an integration team or partner, and many systems beyond WooCommerce and Business Central.

Option 4: a custom build

A custom build means writing your own Business Central WooCommerce connector, either as an AL extension inside Business Central or as an external service that calls both APIs. Microsoft's guide to AL extension development describes the toolset: Visual Studio Code with the AL Language extension, table and page extension objects, and compiled .app packages deployed to your tenant.

On the data side, the Business Central API v2.0 is enabled by default for Business Central online. One limit surprises developers: you cannot add fields to the standard APIs. If you need extra fields, you copy the API's AL code and publish a custom API.

Near real-time sync usually relies on webhook subscriptions in Business Central. They work well, with three details your developer has to handle:

• Subscriptions expire after three days unless renewed with a PATCH request, and each renewal needs a handshake.
• Notifications wait 30 seconds after the first change, and more than 1,000 changes in that window arrive as one collection notification.
• If your endpoint is unreachable, Business Central retries for up to 36 hours, but only for specific error codes; other responses delete the subscription.

A custom build gives you total control, which is valuable for unusual processes. It also gives you total responsibility: every release wave, every WooCommerce update, every new field is your developer's job. In my experience, the build is rarely the expensive part. Year two and three of maintenance are.

Best for: businesses with an in-house Business Central developer and a process no Business Central WooCommerce connector supports.

How each option handles the core syncs

The table below shows who builds each sync under each option. "Included" means it ships ready to configure; "Build" means someone writes and maintains it.

That column of "Build" is the real comparison. Every row is days of design and testing, plus maintenance for as long as you run the integration. A Business Central WooCommerce connector collapses all of it into configuration.

Which option should you choose?

Choose by your situation, not by the tool you already own. Here is the decision guide I use with store owners in the US, the UK and Canada.

• You run one or several WooCommerce stores and want two-way sync working within weeks: choose a dedicated Business Central WooCommerce connector.
• You only need one simple flow, such as pushing daily orders into Business Central: Power Automate can do it, provided you accept its limits and own the flow.
• WooCommerce is one of five or more systems you need to connect: consider an iPaaS, and check whether a dedicated Business Central WooCommerce connector can still handle the WooCommerce part while the iPaaS handles the rest.
• Your process is unusual and you employ a Business Central developer: a custom build may fit, but price three years of maintenance first.
• You sell B2B with customer-specific prices, payment terms and catalogs: a dedicated Business Central WooCommerce connector, because those syncs are the hardest to build and maintain yourself.

Can you combine options?

Yes, and it often works best. A common pattern is a Business Central WooCommerce connector for the core syncs, with Power Automate for side workflows: approval requests, Teams alerts for high-value orders, or a weekly report email. The Business Central WooCommerce connector keeps the data correct; Power Automate handles the notifications people want around it.

What does moving from DIY flows to a connector involve?

Moving from Power Automate flows or a custom extension to a dedicated Business Central WooCommerce connector is mostly a mapping and cut-over exercise, not a rebuild. Your Business Central data stays where it is. What changes is which tool moves it.

The steps I follow on a typical switch:

1. List what the current flows do. Write down every flow or job: what triggers it, which records it touches, and how often it runs. This list becomes the mapping brief for the new Business Central WooCommerce connector.
2. Map in a sandbox first. Connect the Business Central WooCommerce connector to a Business Central sandbox and a staging copy of the store. Match SKUs to items, customers to customer cards, and payment methods and tax to their Business Central codes.
3. Test the awkward cases. Run test orders with coupons, variants, partial refunds and multi-currency, and compare the Business Central documents with what the old flows produced.
4. Switch off the old flows before go-live. If both the old flows and the new Business Central WooCommerce connector run at once, orders get created twice.
5. Watch the first week closely. Check the error log daily and reconcile web orders against Business Central sales orders until the numbers match every day.

Most of the work is in step 1. Teams often find flows nobody remembered building, which is one more reason to move core syncs into a supported product.

How do the options handle US, UK and Canadian requirements?

Selling across the US, the UK and Canada adds three requirements to any WooCommerce Dynamics 365 integration: tax, currency and sometimes separate legal entities. Each option can handle them, but not with the same effort.

• Tax. US sales tax, UK VAT and Canadian GST/HST each map to different Business Central setups. A Business Central WooCommerce connector usually has tax mapping screens; with Power Automate, an iPaaS or a custom build, you write that logic yourself and test every rate.
• Currency. Stores that show USD, GBP and CAD prices need a price list per currency in Business Central and a rule for which store uses which list. In a dedicated Business Central WooCommerce connector this is configuration; elsewhere it is code or flow logic.
• Separate companies. Groups with a UK or Canadian entity often run a separate Business Central company per country. Check whether each option can route each store to the right company without duplicating the whole integration.

If your growth plan includes a new country, cost this in now. Adding a second market to a well-configured Dynamics 365 Business Central WooCommerce setup is a mapping task; adding it to a stack of hand-built flows is usually a rebuild.

Common mistakes when choosing an approach

These are the mistakes I see most often when businesses pick a Business Central WooCommerce connector or an alternative:

• Choosing on licence price alone. Power Automate looks cheap until you count the flows you have to build and maintain.
• Ignoring bulk changes. A price list update across 3,000 items behaves differently from a single edit. Test it on any option.
• Forgetting duplicates. Retries and at-least-once delivery can create the same order twice unless the logic checks first.
• No owner after launch. Every DIY flow and custom extension needs a named person who fixes it at month-end.
• Building before mapping. Decide which system owns each field before writing a single flow or line of code.

Questions to ask before you decide

Whichever route you lean towards, ask these questions in writing:

• Which syncs are included, and which do we build?
• How does it handle refunds, partial refunds and cancellations?
• What happens during bulk updates and API throttling?
• Who tests and fixes the integration after each Business Central release wave?
• Can we add a second WooCommerce store without rebuilding?
• Where do errors appear, and who gets alerted?

If you want a checklist of what a strong Business Central WooCommerce connector should include, our breakdown of Business Central WooCommerce connector features goes through each one.

Key takeaways

• There are four ways to connect WooCommerce and Business Central: a dedicated Business Central WooCommerce connector, Power Automate, an iPaaS, or a custom build.
• A dedicated Business Central WooCommerce connector ships the core syncs ready to configure; every other option makes you build them.
• Power Automate's Business Central connector is premium, limited to 300 calls per connection per minute, and cannot process bulk collection notifications.
• Azure Logic Apps suits multi-system integration but delivers messages at least once, so workflows must prevent duplicate orders.
• Custom builds need webhook renewals every three days, custom APIs for extra fields, and long-term developer time.
• Many stores combine a Business Central WooCommerce connector for core data with Power Automate for alerts and approvals.

Frequently asked questions

Is a dedicated Business Central WooCommerce connector better than Power Automate?

For most stores, yes. A dedicated Business Central WooCommerce connector ships inventory, order, price and invoice sync ready to configure. Power Automate needs every flow built and maintained by your team, its Business Central connector is premium, and it has throttling limits. Power Automate works best for small side workflows alongside a Business Central WooCommerce connector.

Can Power Automate sync WooCommerce orders to Business Central?

Yes, with a paid plan and a third-party WooCommerce connector that needs its companion WordPress plugin. You build the flow that creates sales orders, then add flows for stock, prices and refunds. It works for low volumes, but busy stores often reach throttling limits or miss bulk changes.

What is an iPaaS, and when does it make sense?

An iPaaS is a cloud integration platform that connects many systems through one hub, such as Azure Logic Apps or commercial middleware. It makes sense when WooCommerce and Business Central are two of several systems, like a 3PL, a CRM and marketplaces, and you have an integration team or partner to build and run it.

How long does a custom Business Central WooCommerce integration take to build?

It depends on scope, but a full two-way build covering orders, stock, products, customers, prices, refunds and invoices is a multi-week project before testing. Ongoing maintenance continues after launch, because Business Central releases major updates twice a year and WooCommerce updates often. Price both the build and the upkeep.

Do Business Central webhooks work for real-time WooCommerce sync?

Yes, with care. Webhook subscriptions push changes for entities such as items, customers and sales orders. They expire after three days unless renewed, wait 30 seconds before notifying, and bundle more than 1,000 changes into one collection notification. Your integration must renew subscriptions and handle bulk notifications properly.

Can I use a Business Central WooCommerce connector and Power Automate together?

Yes, and many stores do. The Business Central WooCommerce connector handles the core data syncs, such as inventory, orders, prices and invoices. Power Automate handles side workflows around them, such as approval requests, Teams alerts for large orders or weekly summary emails. This keeps the critical data logic in a supported product.

Which option is best for B2B wholesalers?

A dedicated Business Central WooCommerce connector is usually best for B2B. Wholesalers depend on customer price groups, quantity breaks, payment terms, credit limits and customer-specific catalogs flowing correctly from Business Central to WooCommerce. These are the hardest syncs to build yourself, and mistakes show up as wrong prices on real customer orders.

What happens to a custom integration when Business Central updates?

Someone has to test it in a sandbox and fix anything that breaks. Business Central releases major updates twice a year, and custom extensions or flows that depend on specific fields or APIs may need changes. With a dedicated Business Central WooCommerce connector, the vendor does this testing; with a custom build, your developer does.

Is Azure Logic Apps cheaper than a dedicated Business Central WooCommerce connector?

Not always. Logic Apps Consumption bills per execution and Standard bills on a hosting plan, so a busy store can generate many runs. The larger cost is designing, testing and maintaining every workflow. Compare the platform bill plus build and support time with a Business Central WooCommerce connector subscription over three years.

Can I switch from Power Automate to a Business Central WooCommerce connector later?

Yes. Most stores switch when order volume, store count or B2B pricing outgrows their flows. Plan the move by turning off overlapping flows before the Business Central WooCommerce connector goes live, so orders are not created twice, and test the new mapping in a Business Central sandbox first.

Conclusion

Every option on this list can connect WooCommerce and Business Central. The difference is how much logic you have to build and how much upkeep you inherit. Power Automate is great for small side flows, an iPaaS fits companies with many systems, and a custom build fits unusual processes with developers on staff. For most stores, a dedicated Business Central WooCommerce connector gives two-way sync of inventory, orders, prices and invoices with the least risk and the least maintenance.

If you are weighing these options for your own store, book a free demo with the BCWC team. Bring your current setup, whether that is Power Automate flows, a custom extension or manual entry, and we will show you what moving to a dedicated Business Central WooCommerce connector would look like.