What a Microsoft Dynamics 365 Business Central integration gives you.
Oversell drops sharply because stock levels refresh on schedule and a calculated buffer protects high-velocity lines. Customer trust in availability statements rises because the data is governed, not guessed.
Orders flow into Business Central cleanly, invoicing kicks off on schedule, and dispatch confirmations reach customers without manual intervention. Cash receipt matching becomes routine, not a month-end scramble.
Credit limits, account holds and pricing rules from Business Central apply at web checkout. Bad credit or held accounts cannot proceed, preventing bad debt and returns disputes at dispatch.
Order audit trail, payment status, invoice timing and stock movement align. Finance teams close the month with confidence because ecommerce orders reconcile cleanly against the ERP ledger.
Late orders, unmatched invoices and stuck payments surface in named queues with clear ownership. Issues resolve before customers notice, not after support escalations.
Where a Microsoft Dynamics 365 Business Central integration earns its place.
If two or more of these are true, the integration usually pays for itself quickly.
Where off-the-shelf connectors fall short.
Vendor connectors are fine for simple cases. Here's where the real ones need more.
Business Central stock changes on a schedule, not in real time. Between sync windows, the storefront cannot see the latest pick activity, returns or stock adjustments. High-velocity or low-stock lines can oversell if the buffer is not tuned carefully.
Orders may not enter Business Central immediately. Network latency, validation failures or ERP downtime can hold orders in queues. Without named exception owners and clear fallback rules, orders can sit acknowledged to the customer but unprocessed in the ERP.
Business Central can hold customer-specific prices, but the storefront cannot always apply all contract rules (e.g. volume discounts, time-based pricing). Manual overrides or bespoke development may be needed to honour complex pricing logic at checkout.
Invoices and credit notes move from Business Central on a batch or event-driven schedule. If dispatch and invoicing are not tightly coupled, the customer may see conflicting messages about invoice date versus dispatch date.
Business Central can track stock across locations, but the storefront does not always know which location will fulfil an order. Split shipments, branch fulfilment and cross-location transfers require clear ownership and orchestration outside the core ERP sync.
If Business Central is offline, the storefront has no fresh stock or pricing. Without a cached policy and fallback rules, checkout can grind to a halt. The decision to block orders or allow cached data needs to be explicit.
Many commerce teams assume the ERP is always available and pricing is always fresh; when either assumption breaks, orders slip into gaps and month-end reconciliation becomes manual detective work.
Where this integration sits in your estate.
Microsoft Dynamics 365 Business Central holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.
One integration architecture, any storefront. Microsoft Dynamics 365 Business Central connects through the same governed layer whatever commerce core you run.
- Stock availability and allocation
- Base and customer-specific pricing
- Customer credit limits and account holds
- Sales order creation and invoicing
- Cash receipt matching and reconciliation
- Product catalogue and merchandising display
- Checkout and cart
- Customer login and account portal
- Order confirmation to customer
- Promotions and channel-specific pricing
Systems this integration usually sits next to.
Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.
- Adobe Commerce
- Magento Open Source
- Shopify Plus
- BigCommerce
- Other storefronts
- PIM
- OMS / order management
- WMS / fulfilment
- Payment processor
- Marketplace connectors
- Customer data platform / CRM
- Tax engine
- BI / reporting platform
Not sure if this works with your stack?
Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.
The data flows we wire.
Each flow has a direction and an owner. We agree both before a line of code is written.
How iWeb configures the integration around your business.
Same method on every integration. The decisions come before the code.
- 01Design order-to-cash flows
We map how orders flow into Business Central, where they wait, how they are acknowledged, when they are invoiced and how returns tie back. We define the ERP document types, numbering and field mapping upfront so the ledger stays clean.
- 02Build governed pricing and customer rules
We extract contract pricing, customer-specific rates and credit limits from Business Central and publish them to the storefront in a format checkout can consume. We handle tiered pricing, time-based rates and account holds without breaking promotions.
- 03Implement stock buffers and safety logic
We calculate and maintain safety-stock buffers for each product based on lead time, demand volatility and ERP reorder-point rules. The storefront applies the buffer at checkout to prevent oversell between sync windows.
- 04Set up exception handling and observability
We create named queues for late orders, unmatched payments, stuck invoices and stock variance. Alerts surface immediately so operations can resolve issues before they cascade, and dashboards show order lag, invoice timing and cash reconciliation status.
- 05Plan ERP downtime and fallback policy
We work with you to decide how the storefront behaves when Business Central is offline - whether to reject orders, allow them on cached data or queue them. We build the fallback path and test rollback to ensure customers do not experience silent failures.
Who owns what.
The single most important table in any integration. One system owns each field; everything else reads it.
Built this before
iWeb has integrated Business Central with ecommerce storefronts across retail, trade, manufacturing and foodservice sectors. We understand how stock, pricing and order-to-cash workflows sit in the middle of your operating model and where governance and exception handling matter most.
What we test before launch.
Every one of these is rehearsed before a customer ever sees the integration.
Common risks and where they bite.
We name these on day one. A risk written down is a risk you can plan around.
Orders picked or cancelled in Business Central do not sync to the storefront on time. The storefront sells products that are already out of stock, or shows unavailable stock as in-stock. Over time, physical stock and ecommerce inventory fall out of step.
Business Central rejects an order because of a customer-account issue, pricing mismatch or stock allocation failure. The order sits acknowledged to the customer but unprocessed in the ERP. If no one monitors the exception queue, the customer never receives the goods or invoice.
Customer-specific pricing from Business Central does not refresh to the storefront, or a contract expires and old prices linger. Customers receive unexpected invoices at variance to checkout prices, or unprofitable orders ship because the list price was wrong.
A customer is on credit hold in Business Central, but the storefront does not know. The order goes through checkout, ships and invoices, then bounces back from finance because the customer is not creditworthy. Returns and disputes follow.
The invoice date in Business Central does not match the dispatch date from the warehouse. Customers see conflicting timelines on their account, or invoicing happens before dispatch, creating cash-flow and compliance confusion.
Business Central goes offline for maintenance or an outage. The storefront cannot read stock or pricing, so checkout freezes. If no cached-data fallback policy is in place, revenue stops until the ERP comes back up.
Relevant services and sectors.
Common questions about Microsoft Dynamics 365 Business Central integrations.
How does stock availability sync from Business Central to the storefront?
Stock levels refresh on a regular schedule - typically hourly or every few hours - from Business Central to the storefront. A safety-stock buffer is applied to the published figure to protect against demand between sync windows. The storefront uses this buffered number for checkout availability checks. If the ERP is offline, the storefront falls back to the last-known figure until the sync resumes.
What happens if Business Central is offline?
Depending on your downtime policy, the storefront can either reject new orders with a maintenance message, or accept them into a queue and process them once Business Central comes back online. We set the fallback behaviour upfront so you do not lose revenue unexpectedly. Cached stock and pricing can support a brief outage if you choose.
How are customer-specific prices and contracts handled at checkout?
Customer-specific pricing is extracted from Business Central and published to the storefront so that when a known customer logs in, they see their contract prices or volume discounts. Complex tiered pricing and time-based rates can be honoured if they are modelled in the ERP. Promotions and channel-specific discounts are applied on top without breaking the contract base.
How do web orders flow into Business Central, and what if validation fails?
Orders flow from the storefront into Business Central as sales documents. If validation fails - for example, the customer is on credit hold or stock cannot be allocated - the order sits in an exception queue with a clear reason code. Operations reviews and resolves the exception, or the order is rejected back to the customer with an explanation. No orders are silently lost.
How are invoices and credit notes reconciled with ecommerce orders?
Once an order is picked and dispatched, Business Central generates the invoice and sends it to the storefront and the customer. Returns and credit notes flow back to Business Central from the warehouse or customer service. Finance teams reconcile invoices against orders and payments to close the month. The audit trail stays clean because every transaction has a source document number.
What happens if a customer's credit limit is exceeded at checkout?
Credit limits from Business Central are synced to the storefront. At checkout, the order is validated against the customer's current credit usage and limit. If the order would exceed the limit, checkout is blocked and the customer is told to contact sales. Operations can manually override in the ERP or increase the limit if warranted.
How does payment reconciliation work between the payment processor and Business Central?
Payment status flows from the payment processor (e.g. Stripe, PayPal, Square) into Business Central via an integration. Finance teams match payments against invoices to confirm cash receipt. If a payment fails or is disputed, the exception is flagged so follow-up action can happen before the invoice is marked fully paid.
What if an order is cancelled or returns happen after dispatch?
If a customer or operations cancels an order before dispatch, the stock is returned to available inventory in Business Central and the order is voided in the ERP. If a return happens after the invoice, a credit note is issued in Business Central, stock is received back, and the customer account is credited. The full audit trail stays visible in both systems.
How are multi-location stock and split shipments handled?
Business Central can track stock across locations. If your storefront needs to know where stock will be fulfilled from, or if an order will be split across locations, that logic lives in your OMS or a custom fulfillment rule. The ERP provides the location-level stock; the orchestration layer decides how it ships. We integrate both flows so dispatch confirmations and stock movements reconcile back to Business Central.
How is exception handling and monitoring set up so issues do not slip through?
We create named exception queues for late orders, unmatched payments, stuck invoices and stock variance. Alerts are sent to named owners when items land in these queues. Dashboards show order lag, invoice timing and cash reconciliation status in real time. Weekly or daily reviews ensure no exception goes unowned.
What happens if there is a mismatch between the order in the storefront and the invoice in Business Central?
Mismatches are caught at the validation and reconciliation layers. If an order in commerce does not match the sales document in Business Central - for example, a line item is missing or a price is wrong - the exception is flagged. Finance and operations work together to reissue the invoice or correct the order before the customer is charged twice or under-charged.
How do we manage the transition to this integration without breaking existing orders?
We run the new integration in parallel with your existing process for a period, comparing order counts, stock figures and invoice totals. Once we confirm parity, we cut over to the new flow. Any orders in flight during the cutover are tracked so they do not fall between systems. We keep a rollback plan in place for the first few days in case an issue surfaces.
Can the integration handle promotions and discounts that are not in Business Central?
Yes. Business Central provides the base price and contract pricing; the storefront layer applies promotions, bundle discounts and time-limited offers. The invoice issued from Business Central reflects the discount applied at checkout, so the customer sees a consistent price from checkout through to the invoice.
What level of stock detail is published to the storefront - SKU-level or category-level?
Stock is published at SKU level from Business Central so the storefront can show accurate availability for each variant. We also sync safety-stock buffers and reorder thresholds so the storefront knows which products are low-stock and should trigger alerts or restrict customer-tier access.
Other erp · finance integrations.
Adjacent integrations in the same category. Same shape of work, different vendor.
Projects with a similar shape.
A home department store replatform built around catalogue depth, product data and connected ERP fulfilment.
Home retail trading supported by Adobe Commerce, Akeneo PIM and Microsoft Dynamics ERP integration.
A sports equipment PIM project built around product data, launch speed and catalogue accuracy.
Product launches supported by cleaner data, better completeness and less manual product work.
A car care commerce platform rebuilt around product discovery, seasonal demand and checkout flow.
Car care retail supported by stronger seasonal sales, checkout activity and reduced returns.