Alumio partner: integrations between webshop, ERP and PIM that keep working
Most companies that come to us do not have an integration problem. They have an overview problem. There are scripts between the webshop and the ERP, a plugin that pushes stock to a marketplace, an export for the warehouse and an import from the PIM. Each piece works, but nobody sees the whole. When an order is missing from the ERP, it can be stuck in four places, and there is no screen that shows you which.
An integration platform solves that by putting one layer between your systems instead of wiring them directly to each other. Alumio is such a platform: cloud-native, config-first and built in Groningen. Each system only talks to Alumio, and Alumio translates, validates, keeps track of what happened and retries when something fails.
Memo has been an Alumio partner since 2020 and has built more than 100 integrations with it. This page shows what an integration layer changes, why we choose Alumio, and points you to the topic you are actually dealing with.
.png)
What an integration layer changes
Every direct connection between two systems makes sense on its own. The problem is the number of them. With three systems you have a handful of connections; with seven the count climbs fast, and each connection has its own credentials, its own field names, its own error handling and its own outages.
With Alumio in between you get three things back. You have one place where you can see which message was processed when and what failed, with logs per route. You can replace a system without rebuilding the rest, because only its connection to the layer changes. And the translation between systems is captured as configuration rather than as code in someone's script, so someone else can read it, change it and test it.
That last point matters more as code gets cheaper. A piece of mapping code is quick to write and just as quick to replace. What lasts is the agreement behind it: which ERP field becomes which webshop field, which system wins when the data disagrees, and what happens when a message does not arrive. An integration layer turns that agreement into something you can see and manage.
Why Alumio, and why Memo
Alumio uses a task-based pricing model. Every edition includes unlimited connections, users and workflows; you pay for the volume of data you process. An extra integration does not cost an extra licence, and that changes how you think about your landscape. Each edition comes with its own SLA, and Alumio itself monitors the health, performance and errors of the integrations on the platform.
What Memo adds is that we know both sides of the connection. We build the webshop ourselves: we are a Shopware Bronze Partner and a Shopware Extension Partner, and we also build on Shopify. We work with Ergonode as PIM. And we build the integration layer in between. That puts responsibility for the whole chain with one team, rather than with a webshop agency, an integrator and an ERP partner pointing at each other when something breaks.
Alumio is not tied to one webshop platform either. Our Alumio projects run on Shopware, Shopify and Magento, and the integration stays in place when you change platform. All our integrators are certified on the Alumio platform.
Alumio partner since 2020
Since 2020 we have built integrations on Alumio, the integration platform from Groningen. Alumio has no partner tiers; what counts is experience, certification and proven projects.
More than 100 integrations
More than 100 successful Alumio integrations, between webshops, ERPs, PIMs, WMSs, POS systems and marketplaces.
Certified integrators
All our integrators are certified on the Alumio platform. No account manager between you and the people who build your routes.
One team for the whole chain
We also build the webshop (Shopware Bronze and Extension Partner, Shopify) and work with Ergonode as PIM. Responsibility sits with one team.
What we help with
Each topic below has its own page, because the questions behind them are different. From ERP integration and costs to product data, marketplaces, training and management.
Who we integrate for
Broadly speaking, four kinds of client find their way to us.
Wholesalers with a business customer base and a complex data landscape. For Boomlab, a laboratory wholesaler with more than 60,000 products, we connected Microsoft Dynamics 365 Business Central, the Stibo PIM and Shopware through Alumio. The Stibo API offered no endpoint for the full category tree, so we built a webhook process in Alumio that walks the tree node by node.
Brands that are already automated but have lost the overview. At XXL Nutrition, Magento, Pimcore and Exact Online were already connected. When a new WMS arrived, Ceyenne by Diract IT, we brought the flows for sales orders, purchase orders, stock, fulfilment and returns together in Alumio.
Companies running several brands or stores on one foundation. LifeGoods manages seven brands on a single Shopware installation, with Alumio as the integration layer.
And retailers with a physical store. For Juwelier Kremer in Veendam we built a Shopify store and connected the POS system through Alumio, so stock in the shop and online stays in line.
How we work
We start with the data landscape, not the connection. In a first conversation we map which systems exist, which system owns which data, and which flows run today, including the manual ones. Only then do we choose routes, mappings and an order.
We build in iterations, route by route, so each integration is proven to work before the next one is added. After go-live we stay involved with an SLA tuned to the routes in your environment: an order flow into the ERP needs a different regime than a nightly product sync. If your team wants to build further itself, we arrange that through the Enablement Packages. We are a team in Emmen that speaks Dutch and English, with short lines and no account manager between you and the integrator.
Rebuilding the webshop as well? See Shopware webshop development or Shopify Development.
How we start
Send us which systems you are running and where it hurts, or book an introduction straight away. In half an hour you will know whether an integration layer is the right answer for your situation, and if so, which route to start with.
What clients say
“Working with Memo during the implementation of our new WMS was a great experience. They were highly responsive, proactive in finding solutions, and truly acted as an extension of our team. Thanks to their dedicated development approach, we could rely on their support almost day and night throughout the project. Together, we successfully built several integrations in Alumio, resulting in a stable and future-proof integration landscape. A reliable partner that consistently delivers on its commitments.”
“Working with Memo has transformed our online presence. The transition to Shopify has made our store more user-friendly, and the improved SEO have boosted visibility and engagement. The integration with Akeneo and our POS system has streamlined inventory management, making everything more efficient.”
“After only 10 minutes in the conversation with Memo, we knew enough. Straight to the point, friendly service, and the urge to continue. This was exactly what we needed right now.”
Frequently asked questions
What is Alumio?
Alumio is a cloud-native integration platform (iPaaS) from Groningen. You use it to connect systems such as a webshop, ERP, PIM, WMS and marketplaces without wiring them directly to each other. Integrations are configured rather than programmed, and every message can be traced in the logs. More on What is iPaaS.
How is this different from a direct connection or a plugin?
A direct connection links two systems. That works fine as long as there are only two. Once a PIM, a WMS, a marketplace or a second country is added, you end up with a web of connections, each with its own logic. An integration layer gives you one place to see, manage and rerun everything.
Does Alumio work with Shopify and Magento too?
Yes. Alumio is not tied to one webshop platform. Our Alumio projects run on Shopware, Shopify and Magento, and if you change platform later, you replace one connection instead of your entire integration landscape.
Can my team build integrations in Alumio itself?
Yes. With the Alumio Enablement Packages we teach your team to use the platform, with training and direct support from a Memo Alumio specialist. You can also choose a mix: we build the complex routes, your team manages and extends them. See Enablement and training.
What happens when an integration fails?
Alumio records every message, retries according to the rules you set and reports what does not succeed. On top of that we agree an SLA with you that matches your data routes, with short response times on the routes that affect revenue. See Managed integrations.