iPaaS Value

Magento and Centric ERP integration

Move the data transformation and logic to Alumio, creating flexibility for future ambitions.
An iPaaS makes all your connections visible and understandable on its user-friendly graphical interface, makes it easy for system integrators or agencies to quite literally be on the same page with project managers and C-level, when planning tweaks, improvements or budget allocations on their system integrations.

Magento and Centric ERP integration

“Move the data transformation and logic to Alumio, creating flexibility for future ambitions.”

AGU, a leading bicycling brand from The Netherlands sells reliable, functional and stylish cycling clothing and accessories to cyclists and mountain bikers at all levels. Founded in 1966, AGU has gained much experience since and evolved to a significant B2B player within the BeNeLux. Over the last decade, digital commerce has become an increasing and extensive part of their strategy. With Centric as ERP backoffice and Magento as commerce platform, an integration was required to optimize their current workflow and to make preparations for future ambitions.

Alumio was chosen to process AGU’s Magento Orders to Centric Tradeworld and to process stock data from Centric to Magento. Centric Tradeworld is a modular build all-in-one solution that supports wholesalers with activities as trade, production, services, warehouse, transport and personnel. Solutions like Business Intelligence, Document Management, e-Business and Workflow Management are part of Centric Tradeworld.

With AGU’s successful Magento site, orders needed to be seamlessly exported into Centric Tradeworld. Alumio temporarily stores data from Magento and transforms the order data to meet the data structure needed for Centric Tradeworld.

Next to that, Alumio subscribes all stock data from Centric. Alumio stores the data and detect changes in stock. The changes are being published to Magento. In order to keep both systems accurately, Magento pushes all product SKU’s to Alumio.

The great thing about Connector Templates in Alumio is that they can be reused for different endpoints. So if your e-commerce is not Magento but for example Shopware 6 or WooCommerce, you can easily apply this connector to connect Centric.

AGU’s e-commerce managers and solution partner MediaCT collaborated on this project, delivering a smooth and stable data route between the IT systems. This integration delivers an optimization within the current process of AGU. Next to that the integration serves as a preparation within AGU's IT ecosystem for future growth.

1) Let the API Datapoints be created via SAP Consultants

Risk of low quality & performance errors
If your team will create the data points in the API’s for a fully blown SAP B2B portal, for the first time, the risk of forgetting data fields, the wrong type / logic of creating webservices in a way they will not perform is enormous.    

Let's give you 1 example and insight:   In order to create a customer or so-called self-service portal in your B2B eCommerce, where customers can have a look to their current stats of orders and deliveries, or the history of orders, you need to create 2 separate webservice to make sure you are not over requesting the SAP API. You need to create a separate web service which only requests the header information (invoice number,  for only the latest 10 items, etc and 1 separate which request the detailed information of an invoice. rserd customer will look for a list of first and only will have a look to 1 order/ delivery. The API call of the headers is exceptionally light, and the request of detailed information is a bit heavier. By using 2 APIs call for this feature, you are preventing to request all the detailed information for every user, which will visit the self-service portal. This way if building the API’s is 98% lighter than requesting all detailed information for all orders by all users!

The risk of configuring your webservice in a way which will get a big load to your SAP is enormous. When requesting all products, B2B Prices, Orders or Invoices to your SAP using real-time calls via a wrong logic, it may cause serious  performance problems. It is  therefore extremely important to configure the webservice with the right logic, using a smart caching  mechanism, to not request data in real-time by using “call” requests to your  API webservices, however  use a push mechanism to prevent big load and performance issues

2) Use an off the shelf certified and proven SAP API Plugin

Learn More
No items found.
iPaaS Value

Magento and Centric ERP integration

Move the data transformation and logic to Alumio, creating flexibility for future ambitions.
Magento and Centric ERP integration

“Move the data transformation and logic to Alumio, creating flexibility for future ambitions.”

AGU, a leading bicycling brand from The Netherlands sells reliable, functional and stylish cycling clothing and accessories to cyclists and mountain bikers at all levels. Founded in 1966, AGU has gained much experience since and evolved to a significant B2B player within the BeNeLux. Over the last decade, digital commerce has become an increasing and extensive part of their strategy. With Centric as ERP backoffice and Magento as commerce platform, an integration was required to optimize their current workflow and to make preparations for future ambitions.

Alumio was chosen to process AGU’s Magento Orders to Centric Tradeworld and to process stock data from Centric to Magento. Centric Tradeworld is a modular build all-in-one solution that supports wholesalers with activities as trade, production, services, warehouse, transport and personnel. Solutions like Business Intelligence, Document Management, e-Business and Workflow Management are part of Centric Tradeworld.

With AGU’s successful Magento site, orders needed to be seamlessly exported into Centric Tradeworld. Alumio temporarily stores data from Magento and transforms the order data to meet the data structure needed for Centric Tradeworld.

Next to that, Alumio subscribes all stock data from Centric. Alumio stores the data and detect changes in stock. The changes are being published to Magento. In order to keep both systems accurately, Magento pushes all product SKU’s to Alumio.

The great thing about Connector Templates in Alumio is that they can be reused for different endpoints. So if your e-commerce is not Magento but for example Shopware 6 or WooCommerce, you can easily apply this connector to connect Centric.

AGU’s e-commerce managers and solution partner MediaCT collaborated on this project, delivering a smooth and stable data route between the IT systems. This integration delivers an optimization within the current process of AGU. Next to that the integration serves as a preparation within AGU's IT ecosystem for future growth.

Connect your eCommerce platform to your ERP

Ready to dive in?

Get your demo today.

Let's build an IT-landscape for tomorrow, together!