Commerce & ERP integration
Customer prices, stock, orders and invoices directly from your systems, such as SAP, Microsoft Dynamics, PIM etc. We build the shop and interface together with your ERP consultancy and run both for years.
Data flows
With an integration, the interface takes over what the sales back office often does by hand today. We check these five data flows first in every project.
ERPShop: data flow from ERP to shop
Without integrationThe shop shows list prices. The customer expects their contract price and calls.
With integrationEvery customer sees their own price, calculated from the terms in the ERP.
ERPShop: data flow from ERP to shop
Without integrationStock levels come from the last export. Customers order items that are no longer in stock.
With integrationStock and delivery date are pulled from the ERP when the page is opened.
ERPShop: data flow from ERP to shop
Without integrationDiscounts, payment terms and product ranges per customer are maintained twice.
With integrationThe ERP remains the leading system. The shop takes over customer master data, terms and product range.
ShopERP: data flow from shop to ERP
Without integrationOrders arrive by email and are retyped into the ERP.
With integrationEvery order is created as a sales order in the ERP, and the status flows back into the shop.
ERPPortal: data flow from ERP to portal
Without integrationCustomers phone to ask for copies of invoices and delivery notes.
With integrationInvoices, delivery notes and order status are available in the customer portal.
Proof points from Switzerland
Both shops are connected to SAP and were built together with Swiss SAP consultancies. The consultants were responsible for the ERP, and we were responsible for the shop and interface.
AISymfony shop with SAP integration
Müller + Krempel AG supplies primary packaging for pharma, food and cosmetics. Business customers were to order online, with data directly from SAP.
An online shop based on Symfony, connected to SAP.
Business customers order online. REEA looks after the shop on an ongoing maintenance basis.
AI2customer groups in one shop: business and private customers
ALBIRO AG supplies workwear, protective clothing and safety clothing. One shop was to serve both business and private customers, connected to the SAP backend.
Shop on Magento with Symfony and a web app, connected to SAP.
Both customer groups buy in the same shop. REEA maintains it on an ongoing basis and now also supports a sister company within the group.
Collaboration
Your ERP consultancy, for example for SAP or Microsoft Dynamics, knows your ERP; we know shop, portal and interface. A clear division of tasks prevents two parties building the same thing, or nobody closing the gap in between.
| Task | Your ERP consultancy | REEA |
|---|---|---|
| Customising, pricing and terms in the ERP | yes | no |
| Provide and approve interfaces in the ERP | yes | no |
| Define data fields, directions and error casestogether | yes | yes |
| Middleware, data synchronisation and error handling | no | yes |
| Shop, customer portal and UX/UI design | no | yes |
| Tests with real data from the ERP test systemtogether | yes | yes |
| Operation, updates and monitoring of the interface | no | yes |
A typical split. In the project we agree it with everyone involved.
Interface
Choose a system. The connection behind it always follows the same principle: prices, stock and customer data come from ERP, CRM or PIM, such as SAP, Microsoft Dynamics, etc. Orders go back.
Strong in B2B with customer groups, approvals and individual prices. A common target when an older Magento shop is being replaced.
For large product ranges and several shops on one installation. We take over existing shops, carry out version upgrades and rebuild the interfaces when the ERP changes.
For shops closely tied to a WordPress website. We build the ERP integration as a custom interface that we document and maintain.
For shops that need to launch quickly. The connection to ERP and PIM runs via middleware so that logic and data are not locked into the shop.
When business customers need more than a shopping basket: invoices, delivery notes, order status and reorders behind a login. Often together with the shop, on the same interfaces.
Also in use: PrestaShop · Sylius · custom ordering portals on Symfony
Process
Integration does not start in the code. The data from the ERP belongs in the very first draft, otherwise the user interface will not fit the data interface later on.
AI
AIWe map the ordering process, pricing logic and data flows with the business department, IT and the people responsible for the ERP. This results in a target picture, a list of interfaces and a stage plan.
We design the shop and customer portal up to a clickable prototype. Customer prices, availability and order status are in the draft from the start, not only in the code.
The shop and interfaces are built in parallel. We test in stages against the ERP test system, with real items, customers and terms.
After go-live, we monitor the interfaces, install security updates and develop the shop further.
Operation for years
Hosting in Switzerland possible, e.g. with Infomaniak, or in the EU.
Development takes place in our development centre, certified to ISO 27001 for information security and to ISO 9001, 14001 and 45001.
We also take over shops from other service providers and review the code and interfaces first.
If the ERP changes, we adapt the interface in good time, coordinated with the people responsible for your ERP.
Diagram: what comes up in the years after go-live
Systems
We work with what you already run and only recommend a switch if it pays off.
All systems at a glanceand many more
FAQ
In principle, all the common ones. We work mainly with Shopware, Magento and Adobe Commerce, WooCommerce and Shopify, as well as PrestaShop and Sylius. Which system fits depends on your product range, pricing logic, customer groups and your ERP.
Either the shop queries the price directly in the ERP when the page is opened, for example in SAP or Microsoft Dynamics, or the terms are transferred regularly and calculated in the shop. Which fits better depends on the number of customers and items, and on how often prices change. We clarify this in the concept.
Yes, that is our preferred model. Your ERP consultancy is responsible for customising and the interfaces on the ERP side; we handle the shop, portal, middleware and operation. We define data fields and error cases together.
Regular maintenance of SAP ERP 6.0 ends at the end of 2027 and can be extended at extra cost until the end of 2030. When you move to a new SAP system, the interfaces between shop and ERP have to be adapted or rebuilt. We plan them together with your SAP migration so that the shop is ready on the changeover date.
That depends on your Magento version, the extensions and your product range. We compare the effort and benefit of upgrading versus switching and recommend the route that is cheaper to run in the long term. If you switch, we carry over customer accounts, data and redirects.
Often, yes. Business customers do not just want to order, but also to see invoices, delivery notes and order status. The shop and portal can run on the same interfaces, with a shared login.
Yes. We take over shops from other service providers, first review the code and interfaces, and then take care of security updates, version upgrades and further development.
Your system, our connection
In the Integration Check we spend around 60 minutes mapping shop, ERP and PIM, show the most important starting points and then send you a written result with a cost estimate. The check is free of charge.
What you bring: a list of your systems and two questions on your mind.
