When the E-Commerce Storefront Confirms What Dynamics 365 Business Central Hasn’t Authorized

Most ERP-commerce integrations on Microsoft Dynamics pass data correctly. Fields sync, orders flow, and the monitoring dashboard reports no errors. The failures that matter most in B2B distribution don't show up until a buyer acts on what the storefront told him and the ERP disagrees.

One Transaction, Two Silent Failures

A purchasing manager at a regional industrial contractor logs into his distributor’s eCommerce site to place a job-critical order. The distributor runs on Dynamics 365 Business Central. The product page shows 95 units in stock. The purchasing manager’s account shows Net 30 as an available payment option. He selects 80 units, chooses Net 30, submits, and forwards the confirmation to his project manager. The crew schedule is now built around what the storefront just told him.

From his perspective, nothing went wrong. The transaction processed without error. The order went through.

From the distributor’s side, two failures began the moment he clicked to confirm. One belongs to operations. The other belongs to finance. They are separate in consequence and identical in cause.

What “In Stock” Means in Dynamics vs. What It Means at Checkout

Inventory in Dynamics 365 Business Central is not a single number. It is a set of operational states maintained across warehouses, each with its own significance to fulfillment. On-hand quantity sits alongside several other tracked states: reservations against open sales orders and work orders, safety stock thresholds configured to absorb demand variability, and inbound quantity tied to purchase orders and transfers not yet received. These states exist because every commitment the business makes to a customer depends on them being accurate.

When the distributor’s integration mapped inventory to the storefront, it passed one of those states: total on hand, likely summed across locations. The eCommerce platform received a number. It had no mechanism to interpret what that number included or excluded. It stored the value as an attribute of the SKU and rendered it as a buying signal.

The buyer read “95 in stock” as a shipping commitment. Dynamics held a different number entirely. Of the 95 units on hand, 30 were reserved against existing sales orders, 15 were held as safety stock, and roughly 50 were actually available to promise. The warehouse team discovered the gap when they pulled the order.