Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Storefront · ERP
Connect Microsoft Business Central + Magento / Adobe Commerce
Automate storefront order, customer record, item / sku mapping, availability / stock, price and catalogue attributes between Microsoft Business Central and Magento / Adobe Commerce — with monitoring and managed support from APIWORX.
APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.
ERP + eCommerce Specialists
Managed & Monitored Integrations
Expert Integration Team
APIWORX Provides the Service
Yes. APIWORX connects Microsoft Business Central and Magento / Adobe Commerce.
But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.
APIWORX automates that process end to end — the objects moving between Microsoft Business Central and Magento / Adobe Commerce, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.
How it works
From requirements to a managed integration
We Design the Integration
APIWORX recommends the integration architecture, mappings and implementation approach.
We Build, Monitor & Support It
APIWORX implements the integration and provides ongoing monitoring and support as applicable.
Who this is for
This page is for eCommerce and operations teams selling through Magento or Adobe Commerce while Business Central runs orders, inventory and finance.
What needs to be in place
- Magento 2 or Adobe Commerce with API access, and the version and hosting model identified.
- Dynamics 365 Business Central (cloud, or on-premises with a connection path agreed in scoping).
- A Business Central service account permitted to create sales documents and read item availability.
- Clarity on which system owns product data, pricing and stock — that is a business decision, made before build.
When you may not need this
A small catalogue with stable stock and one fulfilment location may not need this. It earns its place when availability changes fast enough for oversell to hurt, when the catalogue is large or frequently repriced, or when order status has to be visible to customers without anyone checking the ERP by hand.
What is out of scope
- We do not build or theme your Magento storefront or maintain extensions.
- Magento hosting, upgrades and performance stay with your Magento partner.
- Adobe Commerce B2B features such as shared catalogues and company accounts are scoped explicitly where relevant.
What actually moves, and who owns it
A representative Magento-to-Business Central scope. Every object, direction and cadence is confirmed before build.
Microsoft Business CentralAPIWORX (mapping, retries, exception queue)Magento / Adobe Commerce
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Storefront order | Magento | Business Central | Magento (capture) / BC (fulfilment) | Order reaches an agreed status | Held in exception queue with the mapping error | APIWORX |
| Customer record | Magento | Business Central | Per agreed rule | At order creation | Order held rather than creating a duplicate customer | APIWORX (mapping) / you (master data) |
| Item / SKU mapping | Agreed mapping table | Business Central | Business Central | Applied per order line | Unmapped SKU raises a named exception | APIWORX (maintenance) / you (approval) |
| Availability / stock | Business Central | Magento | Business Central | Scheduled publish on an agreed cadence | Last good feed remains in force; failure alerted | APIWORX |
| Price and catalogue attributes | Business Central or agreed source | Magento | Agreed in scoping | On change, on an agreed cadence | Change held; previous values stay live | APIWORX (delivery) / you (data ownership) |
| Shipment and tracking | Business Central / WMS | Magento | Business Central | Shipment posted | Retried, then queued for review | APIWORX |
| Refund / credit memo | Magento | Business Central | Magento | Credit memo created | Queued for finance review | APIWORX |
Three decisions that make or break this integration
Who owns product, price and stock
Most Magento and Business Central problems are ownership problems rather than technical ones. If both systems can edit a price, the last writer wins and someone eventually sells at the wrong number. We fix ownership per data domain in scoping and then the integration enforces it.
- One system of record per field: item description, price, weight, tax class.
- Availability published from Business Central with location filters and optional buffers.
- Catalogue attributes that marketing needs to control stay editable in Magento by design, not by accident.
- Anything with no clear owner gets one before build starts.
Order flow into Business Central
An order becomes a Business Central sales document with the mappings, dimensions and references your team already relies on. The point is that warehouse and finance work from the ERP as normal, without a parallel storefront process.
- Order and payment references written to nominated Business Central fields for support lookups.
- Shipping method mapped to Business Central shipping agent and service codes.
- Discount, shipping income and tax components posted so the document reconciles to what the customer paid.
- Duplicate prevention keyed on the Magento order increment ID.
Fulfilment status back to the storefront
Customers judge you on whether the storefront tells them the truth after checkout. Shipment and tracking data flows back from Business Central or your WMS so Magento order status reflects reality, and support stops answering 'where is my order' from the ERP.
- Shipment confirmation with carrier and tracking written back to the Magento order.
- Partial shipments handled explicitly rather than marking an order complete early.
- Cancellations after fulfilment routed to a person instead of being reversed automatically.
- Failures retried, then queued with the reason so nothing disappears silently.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every run is logged with the source record reference so an order or document can be traced end to end.
- Failed messages are retried on a defined schedule; anything that still fails lands in an exception queue rather than being dropped silently.
- Duplicate prevention keys on the source system's own identifier (order number, PO number, document ID).
- Exceptions are worked by the APIWORX team and escalated to your named operations contacts when a business decision is needed.
- Mapping changes — new SKUs, new locations, new trading-partner requirements — are part of the ongoing engagement.
- Support windows and response commitments live in your agreement; this page does not state an SLA.
How an order is traced
Illustrative — not customer data
An illustrative trace of the references that connect a Magento order to Business Central and back.
| Magento order increment ID | Business Central sales document reference |
|---|---|
| Magento SKU | Business Central item number (mapped) |
| Business Central posted shipment | Magento shipment with tracking |
| Magento credit memo | Business Central credit document |
Scope and questions
- Does this work with Adobe Commerce as well as open-source Magento?
- Both are in scope subject to API access and version confirmation during scoping. Adobe Commerce B2B capabilities are scoped explicitly where they affect the workflow.
- Can Magento show stock from multiple warehouses?
- Availability is published from Business Central using the location filters you agree. Whether that is a single number or per-source availability depends on your Magento inventory configuration, confirmed in scoping.
- Does Business Central or Magento own pricing?
- That is your decision and we implement it. Many customers keep list pricing in Business Central and promotional pricing in Magento; the boundary is written down before build.
- What happens during a Magento upgrade?
- We coordinate with your Magento partner around the upgrade window and confirm API compatibility. Upgrade execution stays with them.
Your integration plan
Get My Integration Plan
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Ready to map your integration?
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Next step
Scope your Magento + Business Central integration
Tell us your systems and documents. A specialist confirms scope by email.