Business Central, Sales or Finance: how each changes a WooCommerce integration

The closest fit to a store. It has a resource for each thing you need, and the actions that finish a document, such as shipAndInvoice on an order and post on an invoice. Our mapping guide uses it for that reason.

Three things to plan for. Webhook notifications expire after three days unless renewed, and a wrong error response can delete the subscription. Standard API pages can’t take extra fields, so a custom field means a custom API page written in AL. And limits apply per user, including service principals, which Microsoft says can reach them fairly quickly when one identity does all the work.

Sales holds customers, leads and opportunities. It has order and invoice tables, but check whether your finance team really treats them as the record. If accounting happens elsewhere, the store’s order may only need to appear on the customer’s timeline, while the financial document goes to the ERP.

Dataverse has useful tools here. Alternate keys let you upsert using your own identifier, such as the Woo customer ID, so a repeated message updates and doesn’t duplicate. Change tracking gives you a delta link for what has changed, but changes are only available within a retention window, seven days by default. A sync that stops for longer has to start again from a full read.

A webhook step has a 60-second timeout and one further attempt on 502, 503 or 504, so don’t rely on it alone. A webhook registered as synchronous also blocks the user’s save in Dynamics if your endpoint is down, so asynchronous is the safer default.

For enquiries rather than orders, this is usually the product in question. See WordPress forms into Dynamics.

Finance and operations apps expose public data entities over OData, with a maximum page size of 10,000 and batches where a changeset succeeds or fails as a unit, which is useful for an order with its lines. Records belong to a legal entity, and by default a call returns data only from the user’s default company, so multi-company setups need care.

Throttling is based on server resources, with a 429 and a Retry-After to respect. Microsoft lists the Data Import/Export Framework and recurring integrations as exempt, so batched imports are a real option for a store that doesn’t need each order in Finance straight away.

You will also hear about dual-write. It links finance and operations apps with Dataverse in near real time. It isn’t a store connector, but if you already use it, a customer written to Dataverse can reach Finance through it, which may change where your store should connect.

In practice, a project at this level runs through the company’s implementation partner, and our part would be the store and the integration layer, working to the partner’s data model.

1. Which product and version do we run, and is it online or on-premises?
2. Which system is the financial record for orders and invoices?
3. Which fields have been customised or made mandatory beyond the standard ones?
4. Can we have a sandbox, and a dedicated application user for the integration?

With those answers, the choice between a plugin, connector or custom build gets much clearer. Our integration service starts from the same questions.