Connecting Shopware to Your ERP: How to Get the Integration Right

When your Shopware shop grows, so does the busywork behind it: updating stock levels, creating new items, adjusting prices, typing orders into your ERP system. An ERP integration does exactly that automatically. Through an interface, Shopware and your inventory management or ERP system exchange data in both directions – products, stock, prices, orders, and customers stay in sync without anyone lifting a finger. You can do this with a ready-made connector or a custom integration built on the Shopware API. Which route fits you depends on your system and your workflows – and that's exactly what we'll look at here.

Why double data entry is the most expensive process in your shop

As long as you have a handful of orders a day, doing it "quickly by hand" still works. But double data entry doesn't scale – the effort grows with every order and every product. And it costs more than just time:

• Overselling: The shop still shows three in stock, the warehouse ran out long ago. The customer orders, you have to cancel – bad experience, refund process, lost trust.
• Outdated prices: You raise purchase and sales prices in the ERP, but the shop keeps selling at the old price for days. Every order eats into your margin.
• Typos when transferring orders: Every order someone copies from the shop into the ERP is a potential source of error – wrong quantity, swapped address, forgotten line item.
• No reliable source of truth: Which number is correct right now – the one in the shop or the one in the warehouse? If nobody knows for sure, you're making decisions on shaky ground.

In our projects we often hear "one of our colleagues takes care of that in the mornings." That's exactly the expensive part: a person spends hours every day shoveling data from one system into the next – work an integration handles invisibly in the background.

What an ERP integration actually syncs

"Connecting Shopware to the ERP" sounds like a big deal. At its core, though, it comes down to five concrete data flows between your shop and your inventory management system – usually in a clearly defined direction:

1. Products & master data: New products, descriptions, categories, EANs, and properties are maintained centrally in the ERP and automatically created or updated in Shopware. You maintain them once, not twice.
2. Stock levels: Inventory from the ERP is continuously pushed into the shop. If an item runs out, it disappears from sale or is set to "unavailable" – no overselling.
3. Prices: Sales prices, tiered prices, and customer group prices come from the ERP and take effect in the shop immediately. Promotions run under clean control too.
4. Orders: Every order flows from Shopware into the ERP – with line items, payment method, shipping method, and customer data. From there it's processed, picked, and invoiced.
5. Customers: New customers and address changes get handed over so no duplicates pile up in the ERP and accounting receives clean records.

The key question is direction: in most integrations, the ERP is the "leading" source for products, stock, and prices, while orders travel from the shop into the ERP. Which system has the final word on which field is something we clarify at the start of every project – the reliability of the whole integration hangs on it.

Ready-made connector or custom integration?

There are broadly two ways to connect Shopware and your ERP. Both have their place – the choice depends on your system and your edge cases.

Option 1: Ready-made connector / middleware

For common systems there are prebuilt connectors or middleware that sit between shop and ERP as a translator. The upside: the standard case is set up quickly, and the vendor handles ongoing maintenance. The downside: you often pay a monthly fee, you're tied to their roadmap, and as soon as your workflows deviate from the standard, the connector hits its limits. You might know this already from subscription plugins that can do ninety percent – just not the one thing you actually need.

Option 2: Custom integration via the Shopware API

Shopware 6 ships with a capable API (the Admin API) that lets you cleanly read and write products, stock, prices, orders, and customers. On top of that we build a tailored integration – either as a dedicated Shopware plugin or as a standalone service in between. The upside: it maps your workflows exactly, including the edge cases, and it belongs to you. The downside: the initial setup costs more than "install a connector." In return there are no recurring license fees, and you don't depend on a third party.

Technically, this kind of integration is familiar ground for us. How a clean connection between two systems works in principle is something we've written up in detail in our post on API integrations – the principles there apply one-to-one to an ERP connection.

JTL, Sage, SAP Business One & co.: what differs per ERP

"Integrating the ERP" means something different with every system. The three questions that determine the effort are always the same, though: what kind of interface exists? In which direction does the sync run? And who triggers it – the shop or the ERP?

A neutral overview of the systems we run into most often among mid-sized companies:

Two things almost always come on top, whichever system you run: the handover to your tax advisor (not an ERP, but part of the picture – plan it in cleanly as an export step) and the question of whether your ERP vendor maintains the integration themselves or you need a third party for it.

Which system you're running strongly determines the effort: a well-documented ERP with a clean REST API is integrated far faster than a homegrown specialty solution where we have to work out the interface first. If your system isn't in the table above, that's not a deal-breaker. As long as it offers some kind of interface – API, file export, direct database access – it can be integrated. We check that upfront so you don't get any surprises.

Stock sync: the three errors that cause overselling

Stock is the data flow integrations fail on most often – and the only one whose errors cost money directly. We keep seeing these three patterns:

1. The sync runs on a clock, not on events. The ERP pushes stock into the shop every 15 minutes. During those 15 minutes the shop happily keeps selling – with two units left and a promotion running, that's enough for three orders. The fix isn't "sync every 30 seconds" (that kills performance), it's a combination: a scheduled full sync plus an immediate stock update as soon as an order comes in. For scarce items, a safety buffer that the shop never puts up for sale helps on top.

2. Absolute values overwrite what the shop has already sold. The ERP writes "product X: 5 units" – based on a figure from ten minutes ago. In the meantime the shop sold two and counted itself down to 3. The sync resets it to 5, and suddenly the stock is back although it's gone. That's a classic race condition. It gets clean when orders travel into the ERP before the ERP writes stock back – or when the shop keeps its own reserved stock that the sync respects.

3. Stock hangs on the wrong object. In Shopware every variant carries its own stock – size M in blue is a different record from size L in blue. If the ERP only supplies one figure per parent product, the integration either distributes it wrongly or not at all. The same problem, one size up, applies to bundles and bills of materials: in the ERP a bundle often has no stock of its own, it results from its components. The integration has to calculate that – if it doesn't, you're selling sets that don't exist.

Related but separate: tiered prices and customer group prices. An ERP often knows price lists per customer, while Shopware works with customer groups and tiered prices. Mapping those two models onto each other cleanly is regularly more work than the entire product sync – and it's where standard connectors most often hit their limit in B2B.

The typical pitfalls

An integration is quickly "plugged together" – and just as quickly becomes a new source of errors if you overlook the traps. These are the points that matter:

Data ownership. The most common conflict: the same piece of information exists in both systems and both "want to be right." If it isn't clearly settled which system leads on which field, shop and ERP overwrite each other – sometimes the price is gone, sometimes the description. That's why we define per data field who owns the truth.

Sync conflicts and outages. What happens when the ERP doesn't respond, or an order gets changed in two places at once? A good integration doesn't lose data, it retries later. We solve this with queues that safely buffer every task until it's done – so no order is lost just because a system was briefly down.

Performance. If stock is pulled live from the ERP on every page view, your shop gets slow – and with cloud ERPs you run into the API limit on top. The load belongs away from the frontend: a scheduled sync in the background, complemented by event-based updates where it counts (see stock above). Every data flow gets its own frequency.

Error transparency. You don't want to find out from the quarterly numbers that no order has reached the ERP for weeks. A proper integration logs what happens and actively speaks up when something is stuck.

How an integration project runs with us

We work in a deliberately structured way so you know where you stand from the start:

1. Assessment: We look at your ERP, your Shopware version, and your workflows. Which data flows where, and what edge cases exist (tiered prices, customer groups, batches, bundles)?
2. Define the data model & directions: For every field we clarify which system leads and how often it syncs. This is the most important half hour of the project.
3. Build the integration: We develop the connection – fail-safe via queues, with clean logging and automated tests, so it doesn't quietly break with the next update.
4. Test run with real data: Before anything goes live, we run real products and orders through it and check whether both systems see the same thing.
5. Go-live & support: We switch over step by step and keep an eye on the first few days. After that the integration runs in the background – and if you want to extend it, the code is clean and easy to follow.

What does a Shopware ERP integration cost?

Honest answer: it depends on how good your ERP's API is and how many edge cases are in play. As a rough guide:

• Full ERP or inventory management integration: from €2,900 – syncing products, stock, prices, orders and customers between Shopware and your system.
• Focused integration plugin: from €2,390 – when only one data flow needs to run, for example handing orders over to one specific system. That's made up of the compact plugin (€990) and the integration building block (€1,400).
• Anything beyond that by effort: €79/h – for edge cases like batches, bills of materials, or pricing logic that exists nowhere else.

The step from €2,390 to €2,900 is deliberately small. As soon as more than one data flow is supposed to run, the full integration is almost always the better deal – which is why, when someone says "just the orders for now," we often suggest taking stock and prices along right away.

The honest counter-calculation: two hours of reconciliation a week is 100 hours a year – per person, and every one of them error-prone. On top of that come overselling, margin lost to stale prices, and the complaint handling caused by typos. Measured against those running costs, a clean integration often pays for itself faster than you'd think. If you're only just considering a shop, our post on what an online shop costs covers the bigger cost picture – the ERP integration is one building block within it.

Sometimes we also advise against it: if you have twenty orders a month and your ERP ships a solid standard integration, custom development isn't worth it. That's exactly the honesty you rightly expect.

Conclusion: connect it properly once instead of typing every day

A Shopware shop only unfolds its value once it works seamlessly with your inventory management. Whether ready-made connector or custom integration via the Shopware API – what matters is that stock, prices, and orders stay reliably in sync and no order gets lost. We build exactly that connection: clean, fail-safe, and tailored to your workflows.

Still typing orders into the ERP by hand, or frustrated by overselling because shop and warehouse don't match? Tell us about your systems and your process – in a free initial call we'll tell you honestly which route fits you and what effort to expect. No obligation, no sales pressure.

Frequently asked questions