Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Web orders and enquiries from WordPress reach Microsoft Dynamics 365 Business Central already coded to the right customer and dimensions, so finance posts them instead of rebuilding them by hand.
Business Central posts nothing until it knows who a transaction belongs to and which dimensions it carries. A WordPress order arrives with none of that: an email address, a basket, a payment reference. Finance then invents the customer and posts days later, which is why web revenue reconciles last. Connecting WordPress and Microsoft Dynamics 365 Business Central through Alumio moves that decision upstream. Customers are matched or created, dimension values are applied by rule as the order is built, and items are checked against real availability. Web trade posts on the same terms as everything else.
DATA THAT FLOWS BETWEEN THEM
Customers
Sales orders
Items
Item availability
Dimension values
Posted invoices
Payments
Orders reach Business Central complete enough to post, so online trade closes with the rest of the ledger instead of waiting for someone to code it after the fact.
Alumio applies Business Central dimension values as each WordPress order is created, so reporting by channel or brand is reliable without anyone tagging transactions by hand.
Repeat buyers are matched to their existing Business Central customer rather than created again, which keeps credit position, payment terms and history in one place.
Item availability from Business Central drives what WordPress offers, so the site stops accepting orders for stock that finance and the warehouse already committed elsewhere.
A WordPress checkout creates a Business Central sales order with the customer matched, dimensions applied and items validated, so the document moves through picking and invoicing without a clerk retyping any part of it.
When a first-time buyer completes a WordPress purchase, Alumio creates the Business Central customer with the correct posting group and payment terms, so their second order lands against a proper account rather than a duplicate.
Item availability changes in Business Central are pushed to the matching WordPress products, so a line that has just been committed to a wholesale order stops being sellable online before a customer can buy it twice.
Alumio sits between sales channels and fulfillment systems as a governed integration backbone. Orders are routed, transformed, and validated, while status updates return to every channel.
Authenticate your systems using Alumio's pre-built connectors. Choose from 200+ connector packages in the marketplace, plus unlimited custom integrations.
Define how data fields map between systems in a visual interface. Adjust formats, enrich records, and apply business logic, no custom code required.
Configure flows to run in real time on events, on a schedule, or both. Reduce manual data entry and let Alumio handle movement and transformation between systems.
.svg){kind=icon}
Once your first integration is live, adding your ERP, PIM, WMS, or CRM connects to the same hub. Existing flows keep running. No rebuilding from scratch.
No, and the third system is usually a payment provider. Business Central wants a settled amount it can reconcile, while the provider holds the authorization and fee detail, so teams connect it alongside WordPress rather than after. Alumio runs all three flows on one platform, which means the payment reference travels with the order into Business Central instead of being matched by hand at bank reconciliation.
Yes. Each completed WordPress order becomes a Business Central sales order as it happens, with customer matching, dimension coding and item validation applied on the way through. Where a rule cannot be satisfied, for example an item that no longer exists in Business Central, the order is held and surfaced rather than posted wrong, so finance reviews an exception instead of unpicking a bad document.
The mapping is configured in Alumio, which replaces the export-and-import routine most teams run between a WordPress plugin and Business Central. Dimension rules, customer matching logic and item validation are all set up in the interface. Business Central implementations differ in how dimensions are structured, and if your coding rule is genuinely unusual, custom JavaScript can be added through the Code Transformer at that step rather than reshaping the whole flow around it.
That is the point of doing it this way. Alumio resolves the customer, applies the dimension values and validates the item lines before the Business Central sales order is created, so what lands is postable rather than a draft someone has to finish. Orders that cannot be completed correctly are held and flagged with the reason, which keeps the ledger clean and gives finance one queue to work instead of a monthly surprise.
Nothing posts twice and nothing disappears quietly. Every message between WordPress and Business Central is logged with its content, monitored live, and raised as an alert the moment it is rejected, with the failing field and the reason shown together. Automatic retries handle transient Business Central locks, and orders that still cannot post stay in an exception queue with full context until someone resolves them.
Talk to an Alumio integration specialist. We'll map the right architecture for your systems, at the right scale, so your operations stay reliable through every change.
.svg)
