D365ConsultantDivision of Sataware
D365ConsultantDivision of Sataware
WooCommerce and ERP

Business Central WooCommerce integration that keeps the store and the books in step.

A Business Central WooCommerce integration moves web orders into your ERP and sends stock, prices and shipment status back to the WordPress store. WooCommerce is flexible because you host it yourself and extend it with plugins. That same flexibility makes the connection harder to get right than it first looks. Below: who owns which data, three ways to build the link, the traps we see on WooCommerce sites, and how to test and watch it once it is live.

REST API
WooCommerce exposes orders, products and customers
Webhooks
can announce a new order as it is placed
Self-hosted
your hosting affects sync speed
Shopper holding a card to pay for an online order on a laptop

Who owns each record once the store is connected

Most WooCommerce stores start life as the system of record for everything. Staff type products straight into WordPress and adjust stock by hand. The bookkeeper rekeys a daily sales summary. Once Business Central arrives, that has to flip. The ERP should own the item master, costs, on-hand quantities and customer credit terms, because purchasing, receiving and the ledger all live there.

WooCommerce keeps what only a storefront can know: the order as the shopper placed it, the payment gateway reference, coupon codes, the shipping method picked at checkout, and the marketing copy and images on each product page. Decide this split field by field and write it down. Two systems that both believe they own the price will quietly overwrite each other. Sooner or later a shopper pays the wrong amount.

Direction follows ownership. Items, prices and stock levels go from Business Central out to the store. Orders, customers created at checkout and payment details come in. Shipment confirmations and tracking numbers go back out so WooCommerce can mark the order completed and email the shopper.

WooCommerce to Business Central field mapping

WooCommerce record
Business Central record
Direction
Notes
Simple product
Item
BC to store
Every product needs a unique SKU; WooCommerce treats it as optional, so audit every product before launch
Variable product and its variations
Item with item variants, or one item per variation
BC to store
Pick one pattern early: variants keep the item list short, separate items make costing and reordering simpler
Stock quantity
Available inventory from chosen locations
BC to store
Send quantity available to sell, not raw on-hand, so open sales orders keep their stock
Regular and sale price
Sales price list lines
BC to store
Scheduled WooCommerce sales need an owner, or the next price push wipes them out
Order in processing status
Sales order
Store to BC
Import at processing, not pending, so failed and abandoned payments stay out of the ERP
Registered customer or guest
Customer, or one shared web customer
Store to BC
Guests can post to a generic customer with the ship-to address carried on each order
Tax lines
Sales tax on the order
Store to BC
One system calculates, the other only records the result
Refund
Sales credit memo
Store to BC
Partial refunds need line detail, not just an amount
Shipment and tracking number
Posted sales shipment
BC to store
Moves the order to completed and triggers the shopper email

Three ways to build the WooCommerce link

Connector app

A connector app from AppSource

Connector apps on AppSource from several vendors handle the common WooCommerce objects through configuration rather than code. They are the quickest route for a standard catalog and a single store.

  • โœ“Lowest build effort
  • โœ“Vendor updates it when either API changes
  • โœ“Custom plugin fields may be out of reach
iPaaS

An integration platform in the middle

A hosted integration platform sits between the two systems, with prebuilt WooCommerce and Business Central endpoints and a visual mapping layer. It suits companies that already run other flows through the same platform.

  • โœ“Good logging and retry screens
  • โœ“One console for several integrations
  • โœ“An ongoing subscription on top of ERP licences
Custom API

A custom service against both APIs

A small service calling the WooCommerce REST API and the Business Central APIs gives full control over subscriptions, bundles, B2B pricing plugins and unusual order flows. It is the right answer only when the other two cannot model your store.

  • โœ“Reaches any plugin data stored on the order
  • โœ“You own the code and its upkeep
  • โœ“Monitoring has to be built too

WooCommerce traps that catch ERP projects

  • โœ“Caching and security plugins that block or throttle REST calls, so the sync fails quietly on your busiest days
  • โœ“Shared hosting that times out on large product updates; batch the calls and schedule heavy pushes overnight
  • โœ“Checkout plugins that add gift messages, delivery dates or PO numbers as order meta, which default mappings skip
  • โœ“WooCommerce Subscriptions renewals arriving as fresh orders every cycle, each needing a posting rule
  • โœ“Payment gateways that settle net of fees, leaving a gap between order totals and the bank deposit unless you book the fees
  • โœ“Stock held for unpaid orders drifting from Business Central when nobody cancels pending orders

Testing the link and watching it after launch

  1. 1

    Build a staging copy of the store

    Clone the WordPress site to staging and point it at a Business Central sandbox. Never test order import against production data or a live payment gateway.

  2. 2

    Run the awkward orders first

    Place orders with coupons, a mix of taxable and exempt items, a variation, a partial refund and a guest checkout. The happy path usually works; edge cases are where mappings break.

  3. 3

    Reconcile one full day

    Compare the WooCommerce orders report with posted sales in Business Central and the gateway payout for that day. All three should agree before you switch on the live sync.

  4. 4

    Set alerts, not just logs

    A failed order should raise an email or Teams message to a named person. A log nobody opens is how a store reaches month end with dozens of unposted orders.

  5. 5

    Retest after WordPress and plugin updates

    Updates to WooCommerce core or a checkout plugin can change order data. Keep a short regression script and run it after each update window.

WooCommerce and Business Central: buyer questions

Does Microsoft offer a built-in WooCommerce connector for Business Central?

No, the ecommerce connector Microsoft builds into Business Central is for Shopify, not WooCommerce. For WooCommerce you choose between connector apps on AppSource, an integration platform or a custom build against the WooCommerce REST API. Which one fits depends on how heavily plugins extend your store. A store with standard products and one payment gateway is usually well served by an app.

Should Business Central or WooCommerce calculate sales tax?

One of them should calculate and the other should only record the result. Many stores let checkout calculate tax so the shopper sees the right total, then pass the tax lines to Business Central unchanged. If you use a tax service such as Avalara, connect it at the point of calculation and stop the ERP from recalculating. Calculating in both places produces penny differences that finance ends up chasing every month.

How often should orders and stock sync?

Orders should arrive within minutes, and stock should update at least as often as it meaningfully changes. Webhooks can tell the integration about each new order, which avoids constant polling. For a large catalog, teams often push stock frequently for fast movers and less often for slow lines. The right interval is whatever stops you overselling your quickest-selling items.

More Business Central WooCommerce integration questions

Can we keep editing product descriptions in WordPress?

Yes, and usually you should. Marketing copy, images, categories and SEO fields belong in WooCommerce, where the web team works. Business Central then owns SKU, price, cost and stock, and the integration touches only those fields. Writing that boundary into the mapping stops the ERP from overwriting a carefully edited product page.

When is a WooCommerce integration not worth building?

When order volume is low enough that one person can post a daily summary in a few minutes. A handful of orders a day entered as a single sales journal can be perfectly sound accounting. The case for integration grows with order count, catalog size and how often items sell out online. If a manual process still makes more sense for you, we will say so on the scoping call.

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 - not a sales call. We look at how you run today, tell you plainly whether Business Central is the right fit, and give you an honest sense of scope, cost and timeline before you commit to anything.

What happens next
1
We review your enquiry
A consultant reads it before the call - 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, licence counts and a cost range, in writing within three days.
Reply within one business day
NDA signed before discovery on request
No obligation, no cost for the scoping call
Microsoft-certified consultants only
Request your scoping call
Four fields. A consultant replies within one business day.
No cost
Your details stay with our consulting team - never shared, never added to a mailing list.