Connect Shopware to JTL-Wawi

For Shopware 6 and JTL-Wawi, there is the JTL-Connector. It sends items, prices and stock to the shop and brings orders and customers into the Wawi. For most merchants, it is the first choice. A custom integration makes sense if Shopware should stay the lead system for content, if custom fields or B2B prices are missing, or if individual data flows need to run faster.

Which data flows between Shopware and JTL-Wawi

1. Order becomes an order in the Wawi, with payment method and shipping method every few minutes
2. Customer becomes a customer in the Wawi, with customer group with the order
3. Items and variants come from the Wawi, texts and images from Shopware if you wish on change
4. Stock is written from the Wawi to the shop per warehouse with every posting
5. Shipping status and tracking number go from the Wawi to the order in the shop on shipment
6. Incoming payment is reconciled between shop and Wawi daily

What already exists for Shopware and JTL-Wawi

JTL describes the JTL-Connector as an interface for exchanging items, categories and customer data between JTL-Wawi and a shop system. Shopware 6 is one of the supported solutions. According to a practical guide from February 2026, the Shopware 6 connector is already included in the free JTL Start edition, with orders billed through quotas. JTL-Wawi is the lead system here: you maintain items, prices and stock in the Wawi, and changes made in the shop can be overwritten at the next sync.

If you maintain your items in the Wawi anyway and use standard prices, start with the connector. Custom code is then often not needed at all.

Where the standard stops

• Payment plugins block the sync

  In the Shopware forum in 2024, a merchant described how the Klarna plugin rejected address changes from JTL. The connector's queue then backed up, and shipping status, tracking numbers, prices and stock no longer reached the shop. The way out was to deactivate the plugin briefly.

• Duplicate properties

  Another user reported in 2021 that after each sync, more duplicate properties with differing values were created. He suspected a faulty migration from Shopware 5 as the cause.

• Variant images multiply

  In 2023, a merchant described in the forum that during sync from JTL to Shopware 6, every variant receives all product images. For items with hundreds of variants, this multiplies the stored images. He left open whether the cause lies with the connector or the data model.

• New Shopware versions

  For Shopware 6.7, there is a community package meant to fix incompatibilities of the connector. A Shopware update can therefore stop the sync until the connector catches up.

• Custom fields and B2B prices

  Free fields and variant attributes from JTL do not always fit Shopware properties. According to the guide, customer-specific prices often need their own mappings.

How we build the integration

We do not necessarily replace the connector. Often our integration takes over only the part that causes trouble, such as B2B prices or stock from several warehouses, and the connector does the rest. Beforehand, we define which system leads for which field.

JTL side: We use the JTL-Wawi API for the local installation or the cloud. The application is registered with an app ID and API key. We create orders through the API, so workflows in the Wawi work as usual. Where needed, we read from the SQL database, but never write to it.

Shopware side: We write items, prices and stock in bundles through the Sync API of the Admin API. This saves calls when a thousand stock levels change at once. A signed webhook reports new orders. So that payment plugins such as Klarna do not block address changes from the Wawi, we write addresses only when explicitly wanted.

Operation: Every record that cannot be transferred lands individually in an error list. The rest keeps running, with no backlog for everyone. More on monitoring under Operation and monitoring, and on shop and ERP under shop-ERP integration.

Process and price range

In the free integration check (30 minutes), we clarify which system leads which data and whether the connector stays. A fixed price follows in 3 working days. If the integration only adds one data flow, the range starts at €1,900 net. More under Process and pricing.

Updated: 10/20/2026