Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Item master changes made in Microsoft Dynamics NAV reach Akeneo as product updates, including the moment an item stops being sold, which is the one change most catalogs quietly miss altogether.
Microsoft Dynamics NAV knows which items are still sold and Akeneo knows what a shopper reads about them, and the difficult part is not the products that exist. It is the ones that stopped. A line is discontinued in NAV, the item simply stops appearing in the export, and Akeneo keeps every attribute it had, so the product stays fully described and live on every connected channel. The Microsoft Dynamics NAV to Akeneo integration treats end of life as an event to publish rather than an absence to notice, so a withdrawn product leaves the catalog the same day it leaves the ERP.
DATA THAT FLOWS BETWEEN THEM
Item master records
Item status
Assortment flags
Unit prices
Item categories
Stock availability
An item discontinued in Microsoft Dynamics NAV is published to Akeneo as a status change, so the channels reading Akeneo stop offering it instead of carrying on.
Alumio alerts on no activity as well as on errors, so a route that quietly stops sending Microsoft Dynamics NAV items is noticed by the platform rather than by a customer.
Descriptions, media and translations built up in Akeneo stay intact when Microsoft Dynamics NAV updates an item, because only the fields the ERP owns are overwritten.
The hours spent copying new NAV items into Akeneo by hand come back, since each item arrives ready to be written up with its codes and categories already filled in.
An item is created in Microsoft Dynamics NAV and arrives in Akeneo with its code, category and unit price in place, so a product manager starts writing content rather than starting with an afternoon of data entry.
A line is discontinued in Microsoft Dynamics NAV and Akeneo receives the status change, so every channel reading the catalog stops listing it without anybody having to visit each channel in turn to confirm it has gone.
A unit price revised in Microsoft Dynamics NAV updates the Akeneo product, so the figure a shopper sees comes from the ERP rather than from whichever channel somebody on the team happened to update most recently.
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 supplier data feed is the common addition, because much of what fills a catalog arrives from the people who make the products rather than from your own ERP. Alumio holds those connections together and reuses the Akeneo attribute mapping already configured, so supplier content and NAV item data land in the same structure instead of two competing ones.
Yes, and end of life is the change worth configuring explicitly. Alumio publishes item creations and updates on a schedule you control, and treats a discontinued flag as an event to send rather than something Akeneo should infer from silence. Only relevant changes are processed, so a nightly run moves what moved rather than the whole item master.
No, this is configured rather than developed. Item status, assortment flags and the Akeneo attributes they map onto are set up once in a form and reused, which retires the spreadsheet that currently carries new items across. NAV was always reachable, whatever its reputation, and the Code Transformer remains there for a rule that mapping cannot express.
Something has to say so, because Akeneo has no notion of discontinued on its own. It holds attributes and an enabled state, and channels read those, so an item that stops arriving simply keeps its last known values and stays complete. The integration therefore publishes the NAV status as a value Akeneo can act on, rather than relying on the item's disappearance to carry the meaning.
A route that stops sending is the dangerous failure here, because the catalog looks perfectly healthy while it quietly ages. Alumio can alert on no activity as well as on errors, per route, so silence is treated as a fault rather than as good news. Each attempt is monitored live with a record of it kept, refusals alert immediately with the item and the reason, and retries run automatically where configured.
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)
