Microsoft Dynamics 365 Business Central integrations for ecommerce.

Business Central can connect to Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce, commercetools and custom commerce platforms. The right approach depends on pricing, stock, accounts, orders, fulfilment and how much logic needs to sit in the ERP, middleware or storefront. iWeb has direct project experience on Adobe Commerce and Magento and works with the wider set where the architecture and connectors support it.

Customer-specific pricing and discounts, stock by location, account ordering and credit limits, orders, dispatch confirmations, invoices and credit notes, and customer and address records. Exact scope depends on how the business runs Business Central.

It is usually a mix. Stock and pricing are read on demand and cached at storefront read time. Orders post asynchronously through monitored queues. Reference data (accounts, catalogues, price lists) refreshes on a defined schedule. The right cadence depends on volume, ERP load and how quickly the business needs each flow to settle.

In Business Central, where the operation already runs contracts, discounts and account terms. The storefront reads pricing through a governed boundary and caches it at read time, so account customers see live prices without each page view calling the ERP. We usually look at price-list volume and refresh tolerance to decide cache windows.

Business Central holds the authoritative stock position, often alongside a WMS for branch or warehouse-level detail. The storefront reads availability through a governed boundary and respects fulfilment rules per location. Where the logic should live depends on how stock is allocated, whether multiple locations are in play and how often the position changes.

Yes. Business Central typically owns pricing, stock and accounts; a PIM such as Akeneo owns enriched product attributes, media and channel rules. Both feed the commerce platform through their own connectors so each system stays responsible for its own data.

When more than one system sits either side of the boundary, when transformation, retries or routing need to be observable, or when the storefront should not own ERP semantics. Simpler estates can run on a direct connector. The right approach depends on data volume, transformation complexity and how integration errors will be supported.

Integration is treated as a first-class part of the platform: queues, retries, dead-letter handling, alerts and a written runbook the on-call team can act on. Failures are tracked across storefront, middleware and Business Central rather than blamed on one side.

Yes. We help decide what to keep, stabilise or replace by reading the existing integration code, message contracts and incident history first, then writing down what to fix first and what is safe to defer. The first month on support is deliberately conservative on change.

iWeb is an ecommerce agency, not a Business Central reseller. iWeb works alongside the client's Business Central partner or in-house team on the integration boundary.

Queues, retries, dead-letter handling, alerts and reconciliation reports across storefront, middleware and Business Central, with a written runbook the on-call team can act on.

Yes. Multi-company and multi-currency estates are wired against the actual Business Central ledger rather than approximated, with the integration contract written down per company.