PlentyONE Expert Partner
ERP integration for your online shop: one data source for every channel
An online shop that is not connected to your ERP system creates work instead of taking it away. We connect your ERP to your shop and sales channels so that products, stock levels, prices and orders move automatically. Error logging, monitoring and a single contact who understands both worlds are part of the package.
- PlentyONE, JTL-Wawi, SAP, Microsoft Dynamics and in-house systems
- Stock synchronised every few minutes instead of once a day
- The analysis phase is bookable on its own; the concept is yours
This page describes the work no pure shop project covers: the connection between the system that holds your stock and the channels you sell through. Where it sits in the bigger picture is shown on the services hub.
What is an ERP integration?
An ERP integration connects your ERP system to your shop and sales channels so that products, stock, prices and orders move between them automatically. It defines not only the technology but also which system is the leading source for which field. Without that decision the systems overwrite each other, and nobody can say which stock figure is correct.
When an ERP integration is worth it
This service is aimed at IT management, managing directors and e-commerce leads in companies whose system landscape has grown over the years. The effort pays off when at least one of these applies:
- Your stock sits in the ERP system but is maintained a second time in the shop or on marketplaces.
- You sell through more than one channel and reconcile stock once a day or by export today.
- Orders from the shop are transferred into the ERP system by hand, and invoices and delivery notes are created twice.
- An existing interface breaks regularly, and nobody can say reliably when.
An integration is less worthwhile for a small, stable catalogue on a single sales channel. In that case we say so in the first consultation and recommend the cheaper route instead of selling a project.
How the data moves between ERP, shop and channels
An integration is four data flows running in two directions. Outbound go product master data, stock and prices: out of the ERP system into the interface layer, transformed there for each destination and completed with the mandatory fields that channel demands, and on into shop and marketplaces. Inbound come orders, payment status and returns, so that invoice, delivery note and stock correction are created where your accounting expects them.
ERP system
- Product master data
- Stock
- Prices
- Documents
Interface or middleware
- Field mapping
- Queue
- Retry
- Log
Shop and marketplaces
- Online shop
- Amazon
- OTTO
- Kaufland
The way backOrders · Payment status · Returns · Tracking numbers
What decides the outcome is less the frequency than the direction: for every field it is settled which system owns it and which only reads it. The price comes from the ERP system, the channel margin from the pricing profile, the order number from the channel. Where that assignment is missing, two systems overwrite each other until somebody intervenes by hand — and abolishing that intervention is the point of the integration.
Where ERP integrations usually go wrong
Over the past few years we have taken over a number of integrations that were started elsewhere. Five patterns repeat themselves:
Data quality is checked too late
Attributes are named differently in every system, variants are poorly structured, mandatory fields are missing. The interface works technically, and the marketplaces still reject the products. That is why the data model comes before the technology with us. Where thousands of products need reworking, AI automation does the classifying and the filling in while your team approves.
There is no system of record
Prices are changed once in the ERP system and once in the shop. As long as it is not defined which system owns which piece of information, the systems overwrite each other's data.
Errors stay invisible
The sync breaks, nobody notices, and three days later you are selling stock that ran out long ago. Every integration therefore needs logging and active alerting.
The integration cannot be maintained
A script, written by a single developer, without documentation and without tests. After the next ERP update nothing works at all.
Nobody owns both sides
The ERP consultant points to the shop agency, the shop agency points back to the ERP consultant. And you mediate instead of working.
What we do
Analysis and data model
We map your product structure, clean up attributes and variants, and define the mandatory fields for each target channel. Without this step, integrations regularly fail the data quality checks the platforms run.
Interface development
We connect via REST, SOAP, GraphQL, EDI or file exchange — whichever your system offers. Where that is not enough, we build a dedicated middleware layer with a queue, retry logic and state management. If an application is needed behind it, that is software development; the interface itself is covered under API development.
Stock and price synchronisation
Stock moves every few minutes instead of once a day. Channel-specific price profiles and safety stock levels protect you from overselling on marketplaces.
Orders and documents back into the ERP
Orders from every channel run through one process. Invoices, delivery notes and returns are created in the ERP system instead of being entered by hand afterwards.
Monitoring and alerting
A dashboard shows the status of every connection. When a sync breaks, data fails validation or figures look unusual, you and we are notified automatically.
Documentation and handover
Every interface is documented: data flows, field mapping, error handling, operating instructions. That way you do not depend on one individual — not even on us.
Connecting a shop to an ERP system: three methods compared
There are three ways to connect your ERP system and your shop. Which one fits depends on your system landscape, your data quality and the number of channels you run:
| Criterion | Native connector | Middleware | Custom interface |
|---|---|---|---|
| Suits | standard processes, common system pairs | several channels, diverging data models | in-house systems, two clearly defined systems |
| Typical duration | 2–6 weeks | 3–6 months | 6–14 weeks |
| Maintenance | vendor updates, little influence | centralised in the middle layer | full control, documented |
| Limits | standard field mapping, little room for special logic | one more component to operate | highest effort when channels change later |
Native connector
Ready-made connection modules from the vendors, for example from JTL-Wawi to common shop platforms or from PlentyONE to the major marketplaces. Fast and inexpensive when both systems are widely used and your processes follow the standard. When a provider promises two to six weeks across the board, this is almost always the route they mean — and it assumes clean master data.
A typical case: JTL-Wawi as the system of record, one online shop as the only channel, standard shipping. The connector moves products, stock and orders; the field mapping is adjusted and nothing else. As soon as a second channel with mandatory attributes of its own arrives, the standard runs out. The connector is then a sensible step, but not a target architecture.
Middleware
A dedicated layer between the ERP system and the channels, with a queue, field mapping, retry logic and monitoring. It makes sense as soon as several channels, diverging data models or high availability requirements come together. The middleware survives a platform change: replace the shop and only a new adapter is needed.
A typical case: SAP as the system of record, a shop as the front end and three marketplaces, each with its own mandatory attributes and pricing rules. The layer reads from SAP once, transforms per destination and logs every transfer. If one channel goes down, its queue waits without blocking the others, and the backlog is worked off rather than typed in again.
Custom interface
A direct connection through the interfaces of both systems — REST, SOAP, GraphQL, EDI or file exchange. The right route for in-house systems and clearly defined data flows between two systems. Documentation and tests are what decide whether the interface survives the next ERP update.
Where the ERP's own scope runs out at this point, the missing piece is built as custom software — a dealer portal with customer-specific prices in front of the interface, for instance.
A typical case: an in-house system that grew over years as the system of record, and one shop as the only channel. Two systems, one manageable data flow — a middleware layer here would be extra machinery to operate for no return. The cost of this route shows up later: add a third channel and the logic sits in the wrong place, and the way forward leads through a middleware layer after all.
PlentyONE as the ERP core or as middleware
PlentyONE holds a special position because it can fill both roles. For merchants without a legacy ERP system, PlentyONE is the system of record: ERP, shop and marketplace connections come from one platform, and separate interface projects largely disappear.
For companies with an existing ERP system — SAP or Microsoft Dynamics, for example — PlentyONE works as multi-channel middleware: the ERP system stays in charge of products, prices and accounting, while PlentyONE distributes to shop and marketplaces and feeds the orders back. Which role is more economical depends on your system landscape and processes; we operate both variants for clients today. The platform itself is covered on the PlentyONE agency page.
Systems we work with
ERP and inventory management: PlentyONE, JTL-Wawi, SAP, Microsoft Dynamics, Lexware and in-house systems
Shop platforms: Shopify and Shopify Plus, Adobe Commerce, WooCommerce, plentyShop — platform selection itself is covered by the e-commerce agency
Marketplaces: Amazon, OTTO, Zalando, Kaufland, eBay, Decathlon and industry portals; how these channels are connected is described under marketplace integration
PIM and data storage: Akeneo and custom databases
If your system is not on this list, that does not mean it cannot be done. It only means we read the documentation first, before we promise anything.
How an integration project runs
- System review (free, 30 minutes) — which systems, which data flows, where does it hurt?
- Analysis phase — product structure, data quality, the interface capabilities of every system involved. The result is a documented concept with an effort estimate.
- Data model and mapping — field mapping, mandatory fields per channel, rules for conflicts.
- Development and testing — built in a test environment with real data, reviewed by our own testers. The scope of that review is described on the QA and software testing page.
- Parallel operation — the new and the old process run side by side until the data matches.
- Cut-over and monitoring — go-live with a rollback option, followed by continuous monitoring.
What decides the cost of an ERP integration
Four things set the effort of an integration: how many systems and channels are involved, whether those systems offer stable interfaces, what state the product master data is in, and how high the requirements for availability and monitoring are. A native connector between two common systems is therefore a different project from a middleware layer serving three marketplaces.
The analysis phase is deliberately bookable on its own. You receive a concept that you could also have implemented by another provider. What the implementation costs is set out in an offer after the first consultation; licence and hosting costs for your own systems and marketplace channel fees are stated separately in it.
Covered by an integration project
- System review and data analysis
- A documented integration concept
- Field mapping per system and channel
- Error handling and retry logic
- Monitoring with active alerting
- Testing with real data and parallel operation
- Operating instructions and handover
- A supervised cut-over with a rollback option
You can commission ongoing operations separately from the project — those services are listed under maintenance and support.
References and evidence
We have brought ERP systems, shops and several sales channels onto one shared data basis for multi-channel merchants, including retailers who grew from a single channel into marketplace selling. The measured figures appear in the case studies once the client has approved them; in the first consultation we show references from your industry before that, under NDA if you prefer.
Online retail
Layba
From manual order handling to a fixed Pick&Pack routine — with barcode scanning, automatic status changes and credit notes
Multi-channel retail
First Austria
One import per category instead of one overloaded structure — product data in the right format for every marketplace
Trade
GSM Shop
Price lists and DPD labels run on the client's own infrastructure — automated and fully documented
Frequently asked questions
What decides the cost of connecting an ERP system to an online shop?
The number of systems and channels involved, the quality of their interfaces and master data, and the requirements for availability and monitoring. Where systems are bespoke or requirements are high, a dedicated middleware layer may be needed. What your integration costs is set out in an offer after the first consultation.
How long does an ERP integration take?
Six to fourteen weeks for a standard integration. Before that comes the analysis phase, two to four weeks — the part that decides whether the project runs smoothly later on.
Which ERP system suits our online shop?
That depends on your catalogue, your processes and the size of your team. For merchants without a legacy system, PlentyONE is often the most economical basis, because ERP and channels come from one platform. We connect existing systems such as SAP, Microsoft Dynamics or JTL-Wawi rather than replacing them. We only make a recommendation after the system review.
Our ERP system was built in-house. Can it still be connected?
Usually yes. What matters is whether the system offers an interface or whether we can access the database directly. We establish that in the analysis phase, before any development effort is incurred.
How often is stock synchronised?
Typically every 5 to 15 minutes, and for critical product ranges event-driven in real time. A daily sync is not enough in multi-channel retail.
What happens if the interface fails?
Orders and data changes are held in a queue and processed automatically once the connection is restored. You and we are alerted immediately.
Can you take over an existing integration?
Yes. We start with a technical audit: code quality, documentation, error handling, monitoring. After that you know whether a rework is enough or whether rebuilding is the more economical route.
The next step
Bring along which systems you run today, which of them holds your stock and where the existing transfer breaks down. You do not need a requirements document. Where the integration sits in the bigger picture is shown on the services hub.
Let us talk about your system landscape
Thirty minutes with a developer. Afterwards you know where your system stands and which steps give you the most leverage.
- A reply within 24 hours on working days
- PlentyONE Expert Partner, in-house QA
- NDA before the first conversation on request