MAGENTO INTEGRATION
Magento Dynamics 365 Business Central Integration: Connectors, Cost and Timeline
Business Central has a documented REST and OData API, so Magento orders can post as sales orders while stock, prices and shipment status flow back. The hard parts are item variants, location mapping and a request limit that applies per user.
✦ WHAT SYNCS
What moves between Microsoft Dynamics 365 Business Central and Magento.
| DATA | DIRECTION | NOTES |
|---|---|---|
| Orders | Out of Magento | Magento orders post as Business Central sales orders, with line items, tax and shipping mapped (scandiweb, ECOSIRE). |
| Inventory | Into Magento | Availability by location. Business Central warehouses or locations map to Magento sources (scandiweb, ECOSIRE). |
| Products and prices | Into Magento | The item master (SKU, units of measure, status) and price lists come from Business Central. Price lists and customer groups map to Magento price rules (scandiweb). |
| Customers | Both ways | Magento customers and addresses map to Business Central customers and ship-to or bill-to records (ECOSIRE). You need de-duplication rules. |
| B2B accounts and price lists | Into Magento | Customer-specific prices and company accounts need a single owner. The ERP is normally the source for contracted prices. |
| Invoices | Into Magento | Invoices created in Business Central write back to Magento to close the order. Paid status writes back only where the payment flow supports it (scandiweb). |
| Shipments | Into Magento | Posted shipments and tracking numbers write back to Magento (scandiweb). ECOSIRE writes back fulfilment and invoiced status. |
| Credit memos and refunds | Both ways | Refund handling differs by vendor. eOne's template lists Magento Credit Memos to BC and BC Credit Memos to Magento (eOne). scandiweb names refunds in its end-to-end test scope but does not describe a refund flow (scandiweb). The Celigo and ECOSIRE pages do not mention refunds, so ask each vendor. Business Central webhooks cover sales credit memos (Microsoft). |
✦ THE API
The Microsoft Dynamics 365 Business Central API.
| ASPECT | DETAIL |
|---|---|
| API type | REST API v2.0 on OData v4, with webhook subscriptions and OData $batch. SOAP endpoints exist but are being de-emphasized. |
| Authentication | OAuth 2.0 through Microsoft Entra ID. Service-to-service calls use the client credentials flow with the API.ReadWrite.All application permission and an Entra application registered inside Business Central. |
| Rate limits | Business Central online, per user: 6,000 requests in a 5-minute sliding window and 5 concurrent requests (extras queue for up to 8 minutes, then return 503). Also 100 simultaneous connections, a 20,000-entity maximum page size, 100 operations per $batch, an 8-minute operation timeout and 200 webhook subscriptions. Going over returns HTTP 429. Microsoft states the same limits apply to service principals. |
| Documentation | Microsoft Dynamics 365 Business Central API docs (opens in a new tab) |
✦ CONNECTOR OPTIONS
Connector options.
| NAME | TYPE | NOTES | LINK |
|---|---|---|---|
| Celigo Magento to Business Central integration | iPaaS | Celigo lists a pre-built Magento and Business Central integration that syncs orders. Its page does not detail other flows, so confirm scope with Celigo. It runs on Celigo's platform. | Vendor page (opens in a new tab) |
| scandiweb Business Central integration | Custom | Agency-built sync of orders, item master, inventory by location, price lists, shipments and invoices, with delta sync, retries and error logs. scandiweb also offers middleware the client can own. | Vendor page (opens in a new tab) |
| ECOSIRE Business Central connector | Extension | Build-to-order AL extension installed per tenant, not an AppSource download. Covers catalog, orders, inventory (including MSI), customers and multi-store or multi-currency mapping. You receive the AL source and permission sets. | Vendor page (opens in a new tab) |
| MuleSoft Adobe Commerce Connector (Mule 4) | iPaaS | Third-party Mule 4 connector for the Magento REST API, developed by TA Digital and listed on MuleSoft Exchange. The listing says it requires an additional fee. It covers the Magento side only; the Business Central side is built in Mule flows. | Vendor page (opens in a new tab) |
| Custom build on Business Central API v2.0 | Custom | Direct integration between the Magento REST API and Business Central OData. Microsoft's guidance is to use webhooks, lastModifiedDateTime filters and $batch to stay inside the limits. | Vendor page (opens in a new tab) |
| eOne SmartConnect Magento to Business Central template | iPaaS | Template on eOne's SmartConnect platform. It lists customers, products, inventory, orders and credit memos, each with a bulk map for the first load and an ongoing map meant to be scheduled. It needs a SmartConnect.com subscription and the SmartConnect eCommerce Extension in Business Central. The page shows no prices. | Vendor page (opens in a new tab) |
| Tinx Adobe Commerce connector for Business Central | Extension | Pre-built connector listed by Intelegain. It imports orders, creates customers and sends tracking to Adobe Commerce. Intelegain says stock changes in Business Central reach the webshop within one minute. Pricing is "Contact for Pricing". Its page does not mention refunds. | Vendor page (opens in a new tab) |
✦ COST AND TIMELINE
Cost and timeline.
| LEVEL | SCOPE | TYPICAL RANGE | TIMELINE |
|---|---|---|---|
| Level 1 | Connector set up and configured | $3,000-8,000 | 2-4 weeks |
| Level 2 (this integration) | Custom API integration (orders, inventory, customers) | $10,000-25,000 | 4-8 weeks |
| Level 3 | Complex ERP sync (B2B pricing, multiple warehouses, middleware) | $25,000-75,000+ | 8-16 weeks |
Typical range, quoted after a scoping call.
A standard order, stock and price sync against the documented API sits at level 2. Heavy B2B price lists, multi-company or multi-currency setups push it toward level 3. Microsoft says the standard API cannot be extended with extra fields, so any custom field means a custom API copy. No connector published by Microsoft or Adobe turned up. Searches of Microsoft Learn, AppSource and the Adobe Commerce Marketplace returned only third-party vendors, so treat every option here as vendor-supported. Sync timing varies. Business Central webhooks wait 30 seconds after the first change to a record, and if more than 1,000 records change in that window they send one collection notification instead (Microsoft). Subscriptions expire after three days unless renewed. ECOSIRE's extension uses Job Queue entries for scheduled polling of new orders and inventory deltas, with intervals set in its setup page and no figures published. scandiweb combines scheduled sync with event-based updates and sends only changed records. eOne's ongoing maps are meant to be scheduled. Intelegain says stock changes arrive within one minute. Celigo's page gives no timing.
✦ WHERE THESE PROJECTS GO WRONG
Where these projects go wrong.
- Variants. Magento configurable products and their children must map to Business Central items and item variants. A mismatch shows up as missing-SKU errors on orders.
- Tax. Orders carry tax into Business Central, and scandiweb maps tax classes per store view and tests tax-inclusive prices before go-live. A tax-group or rounding mismatch shows up as totals that do not match, so test both.
- Locations and overselling. Business Central location stock has to map to Magento sources, with safety stock and reservation rules, or the storefront sells what a warehouse does not have.
- Contract pricing. Price lists and customer groups need one owner and a mapping to Magento price rules or shared catalogs.
- Per-user throttling. Six thousand requests per five minutes and five concurrent calls will slow a bulk catalog or stock load. Spread the work with webhooks, $filter and $batch, or use more than one service principal.
- Status loops. A shipment or invoice written back to Magento must not trigger the order sync again.
- Custom fields. The standard API cannot carry extra fields (Microsoft), so plan a custom API page early.
✦ QUESTIONS MERCHANTS ASK
Microsoft Dynamics 365 Business Central integration FAQ.
Does Business Central have a REST API I can use with Magento?+–
Yes. Microsoft documents a standard API (v2.0) built on REST and OData, enabled by default for Business Central online. Authentication is OAuth 2.0 through Microsoft Entra ID.
Which data usually syncs between Magento and Business Central?+–
Orders go into Business Central. Item data, stock by location, prices, shipments and invoice status come back to Magento, and customers usually move both ways. The exact scope depends on how your warehouse and finance teams work.
Will API rate limits cause problems?+–
They can on a large catalog or frequent stock updates. Business Central documents per-user limits and returns HTTP 429 when you exceed them. The integration needs retry logic and narrow queries, for example filtering on lastModifiedDateTime.
Do I need middleware like Celigo or MuleSoft?+–
Not always. You can run a packaged connector, an iPaaS template or a direct custom build. Volume, how much custom logic you need and who will maintain it decide which fits.
Can the standard Business Central API carry my custom fields?+–
Microsoft states that extending the standard APIs with extra fields is not currently possible. You copy the AL code and build a custom API instead, which adds scope to the project.
How long does an integration take?+–
It depends on scope. The table above shows typical timelines for each level, and a standard order, stock and price sync usually lands at level 2. Final price and timeline come after a scoping call.
✦ KEEP EXPLORING
Related integrations.
Magento Dynamics AX Integration: Connectors, Cost and Timeline
Microsoft ended mainstream support for Dynamics AX 2012 R3 on October 13, 2021 and extended support on January 11, 2023. A Magento integration here means a choice: buy a vendor connector, build on AX's older SOAP services, or wait for the move to its successor.
Magento QuickBooks Integration: Connectors, Cost and Timeline
QuickBooks Online and QuickBooks Desktop need two different integrations. Online talks REST and OAuth 2.0. Desktop talks qbXML through the Web Connector. Find out which one you run before anyone quotes you a price.
SOURCES
- Microsoft Learn: API (v2.0) for Dynamics 365 Business Central (opens in a new tab)
- Microsoft Learn: Operation limits in Business Central online (opens in a new tab)
- Microsoft Learn: Working with API limits in Business Central (opens in a new tab)
- Microsoft Learn: Business Central service-to-service authentication (opens in a new tab)
- Celigo: Magento integrations (opens in a new tab)
- scandiweb: Magento integration with Business Central (opens in a new tab)
- ECOSIRE: Business Central Magento connector (opens in a new tab)
- MuleSoft Exchange: Adobe Commerce Connector for Mule 4 (opens in a new tab)
- eOne: Adobe Commerce to Business Central template (opens in a new tab)
- Microsoft Learn: Working with webhooks in Business Central (opens in a new tab)
- Intelegain: Adobe Commerce connector for Business Central (opens in a new tab)