We integrate Dynamics 365 with commerce and web via APIs and webhooks for a single source of truth.
Where Business Central is the source of truth for stock, pricing and finance, we integrate rather than duplicate — so the storefront reflects the ERP and finance teams stop reconciling spreadsheets.
When the ERP is the source of truth
For most of our commerce and wholesale clients, Microsoft Dynamics 365 Business Central owns the numbers that matter: stock, cost, pricing, customer accounts, invoices. The website is a sales channel, not the system of record — and treating it as one creates permanent reconciliation work for someone in finance.
So our default position is that the ERP stays authoritative and the storefront reflects it. That single decision eliminates most of the data disputes that otherwise consume monthly reporting.
How we integrate it
APIs and webhook orchestration in both directions: product, pricing and inventory flowing out to commerce; orders, customers and payment status flowing back. Idempotency so a repeated message cannot duplicate an order. Retry with backoff for transient failures, and dead-letter queues so a permanent failure reaches a human rather than disappearing.
Field mapping is agreed explicitly, including the awkward cases — how customer-specific pricing is expressed, how backorders and partial fulfilment behave, what happens when a product exists in one system and not the other. These are the details that determine whether an integration is trusted after month three.
What it changes operationally
Staff stop re-entering orders. Finance stops reconciling two sets of figures. Customers see accurate availability. And reporting becomes possible across the whole business rather than per system, which is usually where the Power BI layer follows. For Wafex and Tile Empire this integration is the quiet foundation under the commercial results, and it is the work least visible from the outside.