Managed integrations after go-live: an SLA that follows your data routes
Going live with an integration feels like the end of a project. In reality it is where the longest part begins. From that moment your routes run every day, with real orders, real stock and real customers. And from that moment everything around them starts changing too: an ERP gets an update, a supplier adjusts its API, a channel is added.
Managing integrations means someone knows what is running, sees when something goes wrong, and fixes it before your customer or your sales team notices. With standalone scripts that is often one person with the knowledge in their head. In an integration layer like Alumio, that knowledge is captured in routes and logs, and you can make agreements about it.
We do not make those agreements with a standard package. The SLA we agree with you follows the data routes in your environment, because not every route carries the same weight.
.png)
Why the SLA follows your data routes
An SLA with one response time for everything sounds tidy, but it rarely matches how an integration landscape is put together. The question is not how fast we respond, but to which outage.
An order route into the ERP. If webshop orders do not reach your ERP, nothing gets picked, invoiced or shipped. Within a few hours you have customers on the phone. A route like that needs short response times.
A nightly product sync. If product data from your PIM does not come through one night, slightly older descriptions are online tomorrow morning. Annoying, but it can wait until the morning, and a new attempt often fixes it by itself.
Everything in between. Stock to a marketplace, returns from the WMS, prices for business customers: each route has its own answer to what an outage costs and how quickly it must be fixed. That answer depends on your business, not on the technology.
That is why we start management with the same question as a new project: which routes affect your revenue, and which can wait a while? The SLA follows from that, with short response times on the routes that matter and a calmer regime on the rest. How those routes are built on the ERP side is covered on ERP integration for your webshop.
Seven parts of good management after go-live
Overview of your routes
Which routes run, what they do and which systems depend on them, recorded in one place.
Priority per route
Routes that affect revenue get a different regime from routes running quietly overnight.
Monitoring
Health, performance and errors of your integrations kept in view, so deviations stand out before they become problems.
Alerts to the right person
An outage lands with whoever can act on it, not in a shared inbox.
Recovery without data loss
Messages are held, retried and resubmitted where needed.
A tailored SLA
Short response times where it counts, agreed on the basis of your routes rather than a standard table.
Ongoing development
When a system changes, such as with an ERP update, we adapt the routes with it.
What Alumio does itself, and what Memo adds
Part of the management is already in the platform. Alumio records per route which message was processed when and what failed. Failed messages are retried according to the rules you set, and a message that stays stuck can be resubmitted without guessing whether it was already processed. Alumio also monitors the health, performance and errors of the integrations on the platform itself. Each edition, Essential, Growth and Custom, comes with its own SLA for the platform, with priority support in Growth.
That SLA is about Alumio. It says nothing about your routes: whether the order flow into your ERP takes priority over the nightly sync, who gets called when Exact Online starts delivering a field differently, and who adjusts the mapping when your ERP is updated. That is the part we add.
A tailored SLA. Tuned to the routes in your environment, with short response times where an outage hits revenue.
Routes set up by priority. We configure retries, thresholds and alerts per route, so a critical route raises the alarm sooner than one that recovers by itself.
Alerts to the right person. An error in the order route comes to us and, if you want, to someone on your team. A data error only the source can fix goes to whoever manages that source.
Ongoing development. Systems change. An ERP update, a new API version at a marketplace, an extra field in the PIM: we adjust the routes before it becomes an outage, and we extend them as your landscape grows.
If you want to handle part of that work yourself, such as small changes and resubmitting messages, that works too. Enablement and training explains how we train your team for it, with a mix in which we watch the critical routes and you manage the rest. Management appears in a quote as its own layer next to the licence and the implementation; see What an integration costs.
.png)
Management in practice
XXL Nutrition: an extension of their own team. At XXL Nutrition we brought the routes between Magento, Pimcore, Exact Online and the new WMS Ceyenne by Diract IT together in Alumio: sales orders, purchase orders, product and stock updates, fulfilment, returns and receipt of purchase orders. The goal was overview and scalability, not more automation. XXL Nutrition's product owner described Memo as an extension of their own team, reachable almost day and night during the project. That short line is exactly what you need after go-live. Read the XXL Nutrition case.
LifeGoods: seven brands, one integration layer. LifeGoods manages seven brands on a single Shopware installation, with Alumio as the integration layer. That means many routes that must keep running at the same time, and an outage in a shared route hits not one webshop but several brands at once. In a landscape like that, priority per route makes the difference. Read the LifeGoods case.
Memo has been an Alumio partner since 2020 and has built more than 100 integrations with it. We are a team in Emmen, with short lines and no account manager between you and the integrator who knows your routes. More about who we are on Alumio partner in the Netherlands.
Which route must never stop?
Tell us which systems you have connected and which flows affect your revenue. In half an hour we will know where the risks are and what an SLA that fits your routes looks like.
Frequently asked questions
What does managing integrations involve?
Management is everything that happens after go-live to keep your routes working: monitoring, resolving outages, resubmitting messages that got stuck, and adjusting routes when your systems change. We agree an SLA with you for it that matches your data routes.
What is your response time for an outage?
It depends on the route. An outage in the order route into your ERP needs a short response time, a failing nightly product sync can wait until the morning. That is why we do not quote a standard time, but agree per environment which routes get which response time.
What is the difference between Alumio's SLA and Memo's?
Alumio's SLA covers the platform: each edition has its own SLA, and Alumio monitors the health, performance and errors of the integrations on the platform. Our SLA covers your routes: which ones take priority, who gets alerted and who adjusts the mapping when something changes.
What happens when my ERP gets an update?
We look in advance at what changes in fields, endpoints or behaviour, and adjust the routes accordingly. That falls under ongoing development. If you know an update is coming, let us know as early as possible, so we can test before it goes live.
Can you also manage integrations you did not build?
Yes. We start by mapping what is running: which routes exist, which system owns which data and where the risks are. At Boomlab, for example, we took over an Alumio project halfway through from a previous partner. Only after that inventory do we agree an SLA.