Seamlessly connecting warehouse management and online shop - that is the promise of the JTL-Wawi connection to Shopware 6. In practice, however, the devil is in the details: Which data flows where? What happens during conflicts? And what costs should you expect? In this practical guide, we explain the technical architecture, highlight common pitfalls, and provide you with a clear roadmap for a successful integration.
Why JTL-Wawi and Shopware 6 Belong Together
For its own company, JTL-Software states more than 15,000 customers, over 500 partners and more than 460 employees (JTL-Software). This makes JTL-Wawi a widely used warehouse management system for e-commerce in the DACH region and a common choice among small and medium-sized merchants.
Shopware 6, on the other hand, is one of the most powerful open-source shop platforms in Europe. The combination of both systems enables merchants to connect the centralized data management of the warehouse system with the flexible storefront of Shopware. This creates an end-to-end process from procurement to shipping.
Centralized Data Management
Products, prices, and inventory are maintained in JTL-Wawi and automatically synchronized to Shopware.
Multichannel Capability
JTL-Wawi simultaneously supplies multiple sales channels - Shopware, marketplaces, and proprietary shops.
Process Automation
Orders automatically flow into the warehouse management system - for seamless shipping processing.
The integration saves not only manual work but also reduces error sources significantly. Instead of manually transferring orders or reconciling inventory by hand, the entire process runs automatically. For e-commerce businesses with growing order volumes, this automation is an essential foundation for scalability.
The advantages become especially apparent in multichannel sales: Merchants who sell through marketplaces like Amazon or eBay alongside Shopware benefit from centralized inventory management in JTL-Wawi. Overselling due to unsynchronized stock becomes a thing of the past. Automatic invoice generation and shipping processing can also be controlled through JTL-Wawi, significantly accelerating the entire fulfillment process.
How the Integration Works Technically
The connection between JTL-Wawi and Shopware 6 is established through the JTL-Connector - a middleware component that acts as an intermediary between both systems. JTL lists Shopware 6 among its standard connectors (JTL-Software): the integration runs through a ready-made component from the vendor rather than a custom build.
The JTL-Connector for Shopware 6 is available from the free JTL Start edition, and no license fees apply for it (JTL-Software). Transactions are billed instead: through order packages, merchants pay by order volume rather than a fixed license fee.
The connector installs a plugin in Shopware 6 and communicates via defined endpoints with JTL-Wawi. It functions as a translator between the different data models of both systems. The actual sync logic resides in JTL-Wawi - as the leading system, it controls the data flow.
For merchants who want to go beyond standard functionality, custom middleware solutions are available. These can connect additional data sources, implement transformation rules, or trigger custom workflows that the standard connector does not cover.
Understanding Data Flow - What Syncs Where
A central principle of JTL-Shopware integration: JTL-Wawi is the system of record. This means that changes in Shopware can be overwritten by Wawi. Anyone who maintains product data directly in Shopware risks data loss during the next synchronization.
| Data Type | JTL → Shopware | Shopware → JTL |
|---|---|---|
| Product Master Data | ✓ (Push) | ✗ |
| Prices & Tiered Pricing | ✓ (Push) | ✗ |
| Inventory / Stock | ✓ (Push) | ✗ |
| Categories | ✓ (Push) | ✗ |
| Product Images | ✓ (Push) | ✗ |
| Orders | ✗ | ✓ (Pull) |
| Customer Data | ✗ | ✓ (Pull) |
| Order Status | ✓ (Push) | ✗ |
The data flow follows a clear logic: Master data such as products, prices, and inventory are maintained in JTL-Wawi and pushed to Shopware. Orders and customer data flow in the opposite direction - they are pulled from Shopware to JTL. This push-pull principle ensures that the warehouse management system keeps control over product data while the shop functions as a sales channel.
In practice, this means: When a customer places an order in the Shopware shop, this order is automatically transferred to JTL-Wawi during the next sync cycle. There it is further processed - invoice, delivery note, and shipping label are generated. The current order status (shipped, delivered) is then pushed back to Shopware, so customers can see the current status in the shop at all times.
Modify product data, prices, or inventory exclusively in JTL-Wawi. Direct changes in Shopware will be overwritten during the next synchronization. This is a common source of errors that leads to data inconsistencies. If the data outgrows an inventory system, see our article on introducing a PIM system.
For B2B scenarios with customer-specific pricing or complex attribute structures, the standard data flow can be extended. Custom mappings and transformation rules come into play here, which we explain in more detail in the section on custom extensions.
Setting Up the Integration Step by Step
A successful JTL-Shopware integration can be divided into five phases. Each phase builds on the previous one and should be carried out carefully:
- Analysis and Planning: Inventory of existing data structures in JTL-Wawi and Shopware 6. Which products, attributes, categories, and customer groups should be synchronized? This is where you lay the foundation for a clean integration - professional consulting saves significant effort later.
- Connector Installation and Configuration: Installation of the JTL-Connector plugin in Shopware 6, setup of connection parameters, and configuration of synchronization intervals. The server configuration must provide sufficient resources for the sync process.
- Mapping and Data Assignment: Fields in JTL and Shopware must be correctly mapped - especially tax rates, attributes, units, and category structures. This is where most configuration errors occur.
- Initial Data Synchronization: The first complete sync of all products, categories, and customer data. Depending on data volume, this process can take several hours. Test first with a limited product selection.
- Go-Live and Monitoring: Switch to production operation with continuous monitoring of synchronization. Faulty data records should be identified and corrected promptly.
Run the initial data synchronization in a staging environment before switching to the live shop. This allows you to identify and fix mapping errors without affecting ongoing operations.
The Most Common Integration Problems and Their Solutions
Even with careful planning, typical problems arise in practice. Here are the most common pitfalls and proven solutions:
Status 500 Errors
Typically attributable to server configuration issues, not software bugs. Solution: Increase PHP memory limit, max_execution_time, and timeout values.
Image Synchronization
Images are not transferred or transferred incorrectly. Solution: Check upload limits, validate image paths, and ensure GD library availability.
Tax Rate Mapping
Incorrect tax assignments between JTL and Shopware. Solution: Precisely align tax rules in both systems.
Further common problems concern attribute display in Shopware. Free text fields and variant properties from JTL are not correctly mapped to Shopware properties. The solution lies in precise configuration of attribute assignment in the connector. Special characters in product names, missing required fields, or inconsistent category structures can also lead to synchronization errors. A systematic approach to data cleansing before the first sync typically saves considerable effort afterward.
- Increase PHP memory limit to at least 512 MB
- Set max_execution_time to 300 seconds or higher
- Set up cron jobs for regular synchronization
- Regularly check and archive error logs
- Run test orders after go-live
- Manually reconcile tax rates in both systems
For more complex problems that go beyond standard configuration, professional development support is advisable. Especially when custom plugins, individual fields, or multi-tenant setups are involved, complexity increases significantly.
Costs and Licensing Model Overview
The cost of the JTL-Shopware integration does not depend on the connector but on the JTL edition you choose. JTL-Wawi itself is permanently free to use in the JTL Start edition; transactions are billed through order packages that can be added on. The vendor's price list tiers the editions as follows (entry prices with monthly billing, prices as of September 2026):
| Edition | Monthly Costs | Target Group |
|---|---|---|
| JTL Start | from €0/month | Entry level with basic ERP and a connected shop |
| JTL Advanced | from €119/month | Growing merchants with automation needs |
| JTL Pro | from €369/month | Multichannel merchants with high order volume |
| JTL Enterprise | on request | Companies with very high order volume |
These are the vendor's entry prices without additional order packages; JTL quotes lower monthly amounts for annual billing. Orders beyond the quota included in the plan are billed individually, with the per-order rate falling as the edition rises. Additional costs may apply for initial setup, custom mappings, and ongoing maintenance. When planning your budget, also consider the costs for professional hosting, as the sync process requires additional server resources.
Compared to custom development or manual processes, a professional JTL integration typically pays for itself within a few months. The time saved on manual inventory and order reconciliation alone usually justifies the monthly connector costs quickly. For an individual cost-benefit analysis, we recommend a personal conversation.
When calculating costs, factor in setup effort and ongoing maintenance alongside connector costs. A professionally configured integration saves support effort in the long run and avoids data losses that can be significantly more expensive.
Custom Extensions and Automation
The standard connector covers the most common synchronization scenarios. In practice, however, many merchants require custom adjustments that go beyond basic functionality:
- Custom Field Mappings: Assigning custom fields from JTL-Wawi to Shopware properties or custom fields
- Automated Workflows: Automatic status updates, shipping notifications, or invoice generation upon order receipt
- Multichannel Extensions: Synchronizing additional sales channels such as marketplaces through the same infrastructure
- Custom Middleware: Custom transformation and validation layer between JTL and Shopware for complex business logic
- ERP Integration: Forwarding data to higher-level systems such as SAP or Microsoft Dynamics For the route via an ERP system, see our article on ERP integration with Shopware.
JTL names a REST API as well as ready-made interfaces and connectors as ways to integrate existing systems (JTL-Software). Requirements beyond those routes still call for deep knowledge of the JTL database structure and the connector protocol. An experienced development agency can implement tailored solutions that meaningfully complement the standard connector.
Every shop has unique requirements for JTL-Shopware integration. From simple field mappings to complex automations - we develop the solution that fits your business model. Get in touch for an individual assessment.
This article draws on information published by JTL-Software: company metrics, the documentation of the ERP interface and the price list of the editions. Figures and prices mentioned may vary over time.
JTL-Wawi is the system of record. All master data such as products, prices, and inventory should be maintained exclusively there. Changes in Shopware will be overwritten during the next synchronization.
The JTL-Connector for Shopware 6 is already included in the free JTL Start edition; costs depend on the JTL edition you choose and on the transaction volume. JTL Start begins at €0/month, JTL Advanced at €119/month and JTL Pro at €369/month (JTL-Software, prices as of September 2026, monthly billing). Additional costs for setup and custom adjustments may apply.
Status 500 errors are typically attributable to server configuration issues, not software bugs. Common causes are insufficient PHP memory limit, short execution timeouts, or missing PHP extensions. Professional hosting with adjusted configuration typically resolves these issues.
JTL names a REST API as well as ready-made interfaces and connectors as ways to integrate JTL-Wawi into existing systems (JTL-Software). For connecting Shopware 6, the JTL-Connector is the intended route; direct database access requires particular caution and expertise.
A standard integration typically takes 1-3 weeks to set up - depending on the number of products, complexity of data structures, and individual requirements. Complex setups with custom mappings and special features can take 4-8 weeks.
Yes, JTL-Wawi is designed for multichannel operation. Alongside Shopware, marketplaces such as Amazon or eBay can be connected through the same centralized inventory management. Stock is reconciled across all channels, which typically reduces overselling considerably.