Integration combo
Magento to Microsoft Dynamics Business Central integration
Magento (Adobe Commerce) handles the storefront. Microsoft Dynamics 365 Business Central is the financial and operational system of record. Connecting them properly means orders flow into BC as proper sales documents, customers post against the right ledgers, and finance has a clean audit trail from checkout to general ledger. We design, build and support Magento-to-Business Central integrations as a Patchworks Partner Agency, with the same team carrying delivery into ongoing SLA cover.
Flow shape
Order sync: Magento to Business Central
Magento orders land in Business Central as posted sales documents with the right dimensions, posting groups and customer ledger entries.
- Trigger Magento Order placed sales_order_place
- Extract Patchworks Ingest order queue, dedupe
- Decision Patchworks Customer card exists? lookup by email / external ID
- Transform Patchworks Map order items, dimensions, VAT groups
- Action BC Create sales order via API endpoint
- Writeback Magento Tag order store BC document number
Illustrative only. The diagram above shows how an integration of this shape works in concept. It is not a screenshot or export of the actual Patchworks process flow; the production flow has more nodes, more branches and more error handling than a marketing page can usefully render.
What we sync
6 synchronisations between Magento and Microsoft Dynamics Business Central.
Only the data flows that both platforms actually support. Each section below describes what’s in scope, the gotchas we watch for, and how the flow is shaped inside Patchworks.
- 01
Order sync
Magento Microsoft Dynamics Business Central
Orders raised in Magento flow into Microsoft Dynamics Business Central on creation, status change and edit. The flow normalises Magento's order schema into the record shape Microsoft Dynamics Business Central expects, including line-level discounts, taxes, gift cards, shipping methods and multi-currency. Partial cancellations and post-capture edits are handled with idempotent updates so Microsoft Dynamics Business Central stays the system of record without double-counting. Edge cases that come up most often on this pair: backorders, pre-orders, subscription rebills and orders placed through guest checkout with no matching customer record on the destination side.
- 02
Inventory sync
Microsoft Dynamics Business Central Magento
Stock levels in Microsoft Dynamics Business Central push to Magento on a schedule, on movement events, or both. The flow handles multi-location and multi-warehouse split, safety stock buffers, in-transit and committed quantities, and channel-specific availability rules. Where Magento has its own location model we map Microsoft Dynamics Business Central's locations onto it explicitly rather than relying on default behaviour. Throttling protects both sides during bulk recalculations; deltas only during normal operation. The goal is one source of truth for sellable inventory across the estate, with Microsoft Dynamics Business Central retaining authority.
- 03
Product sync
Microsoft Dynamics Business Central Magento
Product master data syncs from Microsoft Dynamics Business Central to Magento on publish, with channel-aware enrichment so Magento only receives the attributes it can act on. Variants, option sets, media, locale-specific copy, category mappings and metafield or extension data are handled explicitly. New SKUs flow in; deprecated SKUs are flagged rather than hard-deleted so historical orders stay intact. Where Magento has channel-specific requirements that Microsoft Dynamics Business Central does not natively model (typing rules, required attributes, image dimensions), the integration enforces them at the boundary rather than asking the merchandising team to.
- 04
Pricing sync
Microsoft Dynamics Business Central Magento
Price lists in Microsoft Dynamics Business Central push to Magento with currency, tax-class and customer-group awareness intact. Promotional pricing, contract pricing and tiered B2B pricing are handled as first-class concepts rather than overrides applied at the storefront. Where Microsoft Dynamics Business Central runs effective-dated pricing, the flow coordinates the cutover so Magento's catalogue switches at the same instant as the finance side rather than drifting by hours. Currency rounding and display-tax rules are reconciled at the integration boundary to avoid the classic 1p / 1c off-by-one that haunts multi-currency rollouts.
- 05
Customer sync
Magento Microsoft Dynamics Business Central
Customers created or updated in Magento flow into Microsoft Dynamics Business Central with a stable cross-system identifier so the same shopper isn't fragmented into duplicates across the estate. Addresses, marketing preferences, B2B account hierarchies, tax exemption flags and channel attribution are mapped explicitly rather than left to Microsoft Dynamics Business Central's defaults. Where Microsoft Dynamics Business Central is the customer system of record (CRM or ERP) we publish back into Magento so storefront personalisation and segmentation reflect the canonical state. GDPR deletion and rectification are propagated across the integration in both directions.
- 06
Tax sync
Microsoft Dynamics Business Central Magento
Tax codes, tax classes and jurisdiction rules in Microsoft Dynamics Business Central push to Magento so the storefront or marketplace charges what finance will actually post. VAT groups, reverse-charge B2B handling, marketplace-of-record tax (where the channel collects on the seller's behalf) and US sales-tax nexus are each modelled explicitly. The integration validates that Magento's tax calculation matches Microsoft Dynamics Business Central's before publishing a price; mismatches are flagged loudly rather than left to surface at month-end on a VAT return.
Typical delivery
8 to 12 weeks for a standard delivery.
Up to 5× faster using PatchBuddy- Week 1 Discovery: chart of accounts, posting groups, dimension model, VAT setup.
- Weeks 2 to 5 Build: customers, items, orders, inventory, invoices, fulfilment writeback.
- Weeks 6 to 8 Integration testing against Magento and BC sandbox; finance review.
- Weeks 9 to 10 UAT with finance and operations.
- Weeks 11 to 12 Cutover and hyper-care into retainer.
Patchworks delivery
How Patchworks shapes Magento to Microsoft Dynamics Business Central.
Business Central has its own opinions about how transactional data lands: customer card requirements, posting groups, dimension codes, VAT business and product groups. The Magento side has its own structures (EAV catalogue, customer groups, configurable products) that don't always have a one-to-one BC mapping. We build the translation in Patchworks, document the mappings explicitly and hand over runbooks the BC consultant can act on without calling us.
Got more connectors that need to live in this flow? A 3PL, a marketplace, returns, a PIM, anything. We can do it. Most live integrations end up larger than a pair, all built and supported as one estate. More on multi-platform estates →
Our Patchworks practiceQuestions
Common questions.
-
01 Do you handle BC dimensions on every transaction?
Yes. Dimensions are mapped explicitly at scoping (typically channel, region, brand, where they exist) and applied to every posted line. Finance reporting works out of the box because the dimension data is right at source. -
02 What about VAT business / product posting groups?
Magento tax classes map onto BC VAT business and product posting groups. We define the matrix at scoping so VAT calculations match between the storefront and BC's tax engine without exception lists. -
03 Do you handle BC's posting cadence (queued vs immediate)?
Either pattern. The integration can post to BC immediately on order creation or batch into a posting queue your operations team controls. We pick the pattern at discovery based on how your finance side runs end-of-day. -
04 Do you support this under SLA after go-live?
Yes. The same team that builds the integration runs it under retainer. Monitoring on every shipped flow, on-call cover, monthly health checks and tiered response SLAs from £750/month.
Get in touch
Tell us what you’re trying to connect.
And what’s in the way. We will tell you whether we are the right people to do it. Drop us a line below, or open the chat in the corner of the screen.
Direct: contact@ecirql.com
Message sent
Thanks. We’ll be in touch.
Your message is in our inbox. A human will read it and reply within a working day. For anything urgent, drop us a line at contact@ecirql.com or open the chat in the corner of the screen.