E-commerce ERP, PIM and WMS integration that stays in sync
We connect your store with the systems your company runs on: ERP, PIM, WMS, payment, shipping and marketplace systems. We design the data flow so stock, prices and orders match without retyping, and sync errors surface before a customer notices them.
We start with the flow that costs your team the most manual work today.
When you need an integration
Stock levels do not match
A customer buys a product that is already gone, or the store shows it as sold out while it sits in the warehouse.
Orders are retyped by hand
Your team copies orders from the store into the ERP, and statuses back to the customer.
Price lists live in the ERP
B2B prices and discounts sit in the accounting system, and the store keeps its own outdated copy.
Product data in several places
Descriptions, attributes and images live in the PIM, spreadsheets and the store at the same time.
What you get
A data flow map
Which data, in which direction, how often and which system is its source.
Integration via API or middleware
Direct, through middleware or a connector tool, depending on the systems and volume.
Sync of the key data
Products, prices, stock, orders, statuses and documents, following the map.
Error handling and monitoring
Queues, retries, logs and alerts for your team.
Tests and documentation
Tests on test data and documentation that lets you maintain the integration without us too.
How we design an integration
An integration lasts for years only when it is clear from day one who owns the data and what happens when something goes wrong.
A source of truth for every data type
We decide which system owns products, prices, stock, customers and orders. Without that, every sync eventually drifts.
Sync mode that fits the data
Not everything has to be real time. Stock and orders usually are, while the catalogue is often synced in batches.
Error handling
Queues, retries and operations that are safe to repeat: a short ERP outage neither loses an order nor creates a duplicate.
Monitoring
You can see what synced and what did not, and you get an alert before an error reaches a customer.
| Data | Direction | Typical mode |
|---|---|---|
| Products and attributes | PIM or ERP → store | On change or in batches |
| Prices and customer price lists | ERP → store | When a price list changes |
| Stock levels | ERP or WMS → store | As close to real time as possible |
| Orders | Store → ERP or WMS | Immediately after checkout |
| Statuses, documents, shipments | ERP or WMS → store | On status change |
| B2B customers and terms | ERP ↔ store | When terms change |
How we work
Conversation
Which systems, which data and where the manual steps are today.
Data map and fixed price
We design the flows and quote the integration at a fixed price.
Build on test data
The integration runs first in a test environment with your real data structure.
Go-live
Cutover, close watch over the first days and adjustments.
Maintenance
Updates when the ERP or store changes, and extension to further systems.
Systems
Examples of systems a store is commonly connected to: SAP Business One, Microsoft Dynamics, NetSuite, Comarch ERP, Akeneo, Pimcore, WMS platforms, and payment and shipping providers. Not a closed list: what matters is an available API or a way to exchange data.
- Comarch
- Base
Engagement model: fixed price
We quote the integration at a fixed price for an agreed scope.
The price depends on the number of systems, the availability and quality of their APIs, the number of data flows and the volume. When the integration is part of a larger implementation, we price it within that stage.
When the scope is still unclear, we start with the implementation plan: 5 working days, €2,500 net, credited against an implementation worth more than €15,000 net.
See the implementation planQuestions about e-commerce integrations
What is ecommerce ERP integration?
It connects your store and ERP so both work on the same data: stock and prices stay current, orders reach the ERP automatically, and statuses and documents flow back to the customer. Manual retyping and the errors that come with it disappear.
Which systems should be integrated with a store?
Most often the ERP (stock, prices, orders, documents), a PIM (product data), a WMS (warehouse and shipping) and payment and shipping providers. We start with the flow that costs your team the most manual work.
Ready-made connector or a custom integration?
A connector is enough when it handles your data and process without workarounds. A custom integration makes sense with non-standard pricing, several warehouses, B2B or high volume, where connectors start losing data.
How much does ERP integration cost?
It depends on the number of systems, the quality of their APIs and the number of data flows. Once the data is mapped, we quote the integration at a fixed price.
How do you keep stock levels in sync?
One system, usually the ERP or WMS, should own stock. We send changes as close to real time as possible, and the store also reserves stock at checkout so two purchases never land on the same last item.
Do you only build integrations for Medusa stores?
We build integrations as part of Medusa implementations and migrations, where they become part of the store’s logic rather than a separate plugin. If your store runs on another platform, we will work out in the first conversation whether an integration makes sense without migrating.
Show us where your data drifts today.
In 20 minutes, we will decide which flow to start with and which systems need connecting.