Can I keep my existing ERP when using Shopware 6?
A new store does not automatically require a new ERP. How we assess compatibility, data ownership and reliable order transfers.
AI-generated image- 1Quick answer
- 2Key takeaways
- 3When can I keep my existing ERP?
- 4What integration options does Shopware 6 provide?
- 5What should I ask the connector provider to demonstrate?
- 6Which system should control prices and stock?
- 7How do I avoid duplicate orders after a transfer failure?
- 8Does the connection need unrestricted access to my store?
- 9When should I consider Odoo or another ERP instead?
- 10How can sjmedia help me decide?
- 11Sources & further reading
- 12Cite this article
- 13Authors & technical review
Quick answer
Yes, if your ERP still supports the required workflows and a maintainable connection to Shopware 6 is possible. Check the exact versions, data mapping, error handling and responsibilities. An API or a connector name alone does not prove that orders and changes will be processed reliably.
Your store is moving to Shopware 6, but your existing inventory and ERP system has worked reliably for years. Does it have to be replaced? At sjmedia, we would not treat that as an automatic consequence of the store project. We would first establish whether the existing system can provide the required data and receive orders safely. Keeping an ERP can make sense, provided its connection to the new store does more than a one-off product export.
Key takeaways
- A Shopware project does not automatically require an ERP replacement.
- Verify compatibility and data ownership for each workflow.
- Test interrupted transfers and retries before launch.
When can I keep my existing ERP?
If the system still meets your operational requirements and a maintainable integration is possible, Shopware 6 alone is not a reason to replace it. The actual software version, available interfaces, vendor support and required workflows determine the decision. Saying that an ERP “has an API” is not sufficient evidence.
We would start with everyday tasks: maintaining products, providing stock information, receiving orders and returning processing updates. Your exceptions matter too. A system that reliably handles standard parcels may not automatically support partial deliveries, customer-specific prices or multiple warehouses in the required way.
Our separate guide covers choosing an ERP for an online store. This article focuses on establishing whether your existing solution can stay.
What integration options does Shopware 6 provide?
Shopware distinguishes its Store API for customer-facing interactions from the Admin API for administrative and system-level operations. The Admin API is therefore particularly relevant to ERP data exchange. It is not, by itself, a ready-made connection to every inventory system. Source: Shopware API concept.
A connector or custom integration needs to reconcile both systems' data models. The suitable approach also depends on the Shopware deployment model. An extension intended for a self-hosted installation should not be assumed to work in a SaaS project. Shopware documents a separate extension model for SaaS. Source: Shopware SaaS extensions.
We would therefore record the proposed Shopware version and deployment model, together with the ERP version, early in the project. Only then can compatibility be assessed meaningfully.
- Identify data
- Define ownership
- Test transfers
- Check consistency
What should I ask the connector provider to demonstrate?
Request evidence for your workflow, not merely a list of supported systems. We would agree six points for the initial assessment:
- The exact combination of Shopware version, deployment model and ERP version.
- Mapping products, variants, customers and existing identifiers.
- Transferring an order with shipping and payment information.
- Handling changes, cancellations and partial deliveries where required.
- Detecting failed transfers and providing a controlled retry process.
- Responsibility for updates, troubleshooting and ongoing operating costs.
Use representative sample data for the test. “Bidirectional” is too vague without a field and process description. It may mean orders flow one way and dispatch updates return the other. That does not mean every field should be edited independently in both systems.
Which system should control prices and stock?
We assign responsibility for each piece of information. If the ERP supplies prices, a store-side change should not be silently overwritten by the next import. If editorial product descriptions are maintained in Shopware, ERP imports need to respect those fields. Ownership should follow your working process rather than a blanket rule for all merchants.
A hypothetical example: a wholesaler manages item numbers, purchasing and stock in its existing ERP. The store team adds product guidance and images in Shopware. We would define the import so a stock update cannot replace editorial content. Replacing the ERP is not necessarily required. This describes a possible setup, not a documented customer case study.
For stock, we also distinguish available quantities from quantities already reserved. The figure that the store should use is a business decision. Our guide to synchronising stock levels explores that question further.
How do I avoid duplicate orders after a transfer failure?
A connection can fail after the ERP has created an order but before the integration receives confirmation. Blindly creating the same order again can produce a duplicate. We would therefore make an unambiguous link between the store order and ERP order an acceptance requirement.
A controlled retry should recognise whether the order already exists. The implementation depends on the systems involved. Traceable identifiers, transfer logs and an agreed error-handling process are important. This is a requirement for the connection, not a feature automatically guaranteed by every Shopware integration.
Before launch, we test such interruptions in a suitable test environment. A successful standard order only proves that the straightforward route works. It says little about what your team must do after a failure.
Does the connection need unrestricted access to my store?
Shopware supports dedicated integration credentials and assigned roles or permissions. We would establish the rights required for the actual data flow rather than granting full administrator access without assessment. Source: Shopware integrations.
Ownership of those credentials and the process for changing them also need to be clear. This belongs in the handover to your team. An integration whose access details are known only to a former service provider is difficult to support reliably when something goes wrong.
When should I consider Odoo or another ERP instead?
Replacing the ERP becomes relevant when the existing system itself no longer meets important requirements or the necessary connection cannot be operated sensibly. Missing support for required workflows or consistently disproportionate maintenance effort can justify a review. A store migration alone is not sufficient reason.
As an Odoo Partner, we give Odoo particular consideration where the requirements fit. The connector, version and data scope still need to be demonstrated. We do not promise a universal standard connection. Our guide to changing the store and ERP together discusses the order in which these projects should proceed.
How can sjmedia help me decide?
Through our Shopware services, we would document the existing workflow, prepare a limited integration assessment and agree the critical test cases with you. The result should clearly distinguish tasks that already work, required changes and unresolved limitations. That provides a basis for deciding whether the ERP can remain and what effort to budget for.
If the store platform is also undecided, we continue to consider PrestaShop for individual workflows. If Shopware is already a sensible choice, we focus on a sustainable connection. For us, a platform preference cannot replace evidence that your orders will be processed reliably in everyday operation.
Sources & further reading
- Shopware: API concept ↗accessed
- Shopware: Integrations ↗accessed
- Shopware: SaaS extensions ↗accessed
Cite this article
Ewelina Schmid (sjmedia GmbH, Kuppenheim): Can I keep my existing ERP when using Shopware 6?. 16 Nov 2026. https://www.sjmedia-consulting.de/en/wissen/schnittstellen/shopware-bestehende-warenwirtschaft
Author & technical review
Related to this topic.
Questions about this topic? Let’s talk about it.
I’ll listen to your situation and discuss which next steps suit your store.




