Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Item and price ownership is settled piece by piece between Microsoft Dynamics 365 Business Central and Inriver, so the work of describing a product stops being overwritten by a routine ERP update.
Business Central owns the item, the price and whether it can be sold, and Inriver owns everything a customer reads about it. The trouble starts when both think they own a description. An ERP update lands, overwrites a week of product content, and the product team stops trusting the integration and keeps a private copy of the catalog in a spreadsheet. That copy becomes the real problem. The Microsoft Dynamics 365 Business Central to Inriver integration works the other way round: which system owns which part of a product is decided first, so an update touches what it should and leaves the rest alone.
DATA THAT FLOWS BETWEEN THEM
Items
Item prices
Product detail
Category structure
What is still missing
Ready to publish
Only what Business Central owns is written into Inriver, so an item update corrects a price without quietly taking a week of product content down with it as well.
Which system is in charge is decided for each piece of a product rather than for the whole of it, so commercial data and content flow in opposite directions without competing.
An item created in Business Central arrives in Inriver with its commercial detail filled in, so the product team starts from something that is already right rather than nothing.
Inriver can tell Business Central which products have everything they need and which are still short, so a launch is planned against what is genuinely ready to go out.
An item is created in Business Central and Alumio creates the matching Inriver product with its code, price and category, so the product team starts adding content to something that already exists and is correct.
A price revised in Business Central updates that one figure in Inriver and nothing else, so a routine commercial change does not overwrite the descriptions, details or images somebody spent the whole week getting right.
Inriver tells Business Central which products are finished, so a launch date is set against the ones that are genuinely ready rather than against an assumption somebody made in a planning meeting several weeks earlier.
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.
A digital asset manager is a frequent addition, because images and documents have their own approval cycle and rarely arrive when the Business Central item data does. Alumio holds those connections centrally and reuses the Inriver product arrangement already configured, so an approved asset attaches to the product it belongs to rather than being uploaded twice.
Yes, and deciding ownership piece by piece, in each direction, is what makes it safe. Alumio publishes only what you nominate from Business Central into Inriver, and only the Inriver values you nominate back, so neither side can overwrite what the other is responsible for. That scoping is configured once and applies to every item afterwards.
No, this is configured rather than coded. Ownership, product detail names and where each Business Central value lands in Inriver are set up once and maintained in a form, replacing the import script that usually settles this question by accident. Where a detail has to be worked out rather than copied across, the Code Transformer handles it.
The commercial facts, and nothing about how the product is described. Item existence, price, unit and whether it can be sold are decided in Business Central and belong there. Names, product details, images and anything written for a customer belong in Inriver, where they are held and checked for anything missing. Writing that split down before the first import is what prevents the overwriting later.
A week of product content overwritten by an item update is the failure product teams remember, because a week of work disappears and nothing reports an error at all. Alumio publishes only what Business Central owns into Inriver, monitors each update live and logs what it wrote, so a refused update alerts immediately with the item and the reason. Retries run automatically where configured, and nothing else is quietly touched.
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)
