JTL-Wawi integration: connecting JTL-Wawi
JTL-Wawi can be connected in three ways: through the Wawi API with REST and GraphQL, through the JTL-Connector for common shop systems, and through file imports with JTL-Ameise. The Wawi API is available locally and through JTL Cloud. A custom integration pays off when your target system has no ready-made connector or the standard sync is not enough.
What JTL-Wawi is and who uses it
JTL-Wawi is the inventory management system (Warenwirtschaft) from JTL-Software. Merchants manage products, stock, orders, deliveries and invoices in it. It is set up through a desktop client. It is typically used as the hub between shop, marketplaces, shipping and accounting.
Which interfaces JTL-Wawi offers
| Path | What applies according to the JTL documentation |
|---|---|
| Wawi API, on-premises | REST and GraphQL on the merchant's computer or network (port 64110). The app registers itself, the merchant approves it under "Admin > App-Registrierung" and receives an API key that is shown only once. Calls carry the header Authorization: Wawi <key>. |
| Wawi API, cloud | Same API through api.jtl-cloud.com when the Wawi is connected to JTL Cloud. Sign-in uses OAuth 2.0 client credentials through the JTL Partner Portal; the token is valid for one hour, and the tenant ID goes in the header X-Tenant-ID. |
| JTL-Connector | Exchanges products, categories and customer data in both directions with shop systems. Available ready-made for Shopware 6, WooCommerce, Shopify and PrestaShop. |
| JTL-Ameise | Import and export through files, for example CSV with product data or stock levels. |
For planning, the place of operation matters most. The on-premises variant runs where the Wawi runs. A service on the internet can reach it only through the cloud variant or through your own secured route into the company network. The overview page does not describe webhooks for the Wawi API. We therefore plan with short polling intervals until an event path is documented.
Typical connections and data objects
- Order is taken over from the shop, status is reported back every 15 minutes
- Stock is reported to the shop and marketplaces every 15 minutes
- Items and prices go to the shop hourly
- Invoice and credit note are handed over as postings daily
- Delivery with tracking number is reported to the shop on dispatch
Common connections are Shopware with JTL-Wawi and JTL-Wawi with DATEV. The intervals are examples and are set for each project.
Where standard connectors reach their limits
Systems without a connector
For shops, industry software or accounting systems without a ready-made connector, only the Wawi API or the file route remains.
Custom fields
Additional fields, custom product attributes or special pricing logic are often not transferred completely by standard connectors.
Availability
If the Wawi sits in the office, the connection has to restart cleanly after reboots and network outages.
File imports
Imports through Ameise are practical, but without checks and a log, faulty rows are noticed late.
How we connect JTL-Wawi
First we check whether a JTL-Connector covers your case. If not, we build the connection on the Wawi API: in the cloud variant if the Wawi is connected to JTL Cloud, otherwise with a small service inside the company network. The app requests only the permissions it needs. Every run is logged, errors are retried and reported. Where no API fits, we use the file route with validation, see integration without an API.
Frequently asked questions
Does JTL-Wawi have an API?
Yes, the Wawi API with REST and GraphQL. It runs locally at the merchant or is reached through JTL Cloud.
Do I need the JTL-Connector or a custom integration?
Ready-made connectors exist for Shopware 6, WooCommerce, Shopify and PrestaShop. If their fields and workflows are enough, that is often the cheaper choice. A custom integration pays off for other systems or special rules.
Can the Wawi be connected to DATEV?
Yes. Invoices and credit notes from the Wawi can be handed to DATEV as a posting batch (Buchungsstapel). Details are on the page JTL-Wawi with DATEV.
Sources
- JTL Developer: ERP Integration Overview (Wawi API on-premises and cloud), retrieved on 20 Oct 2026
- JTL Guide: JTL-Connector, retrieved on 20 Oct 2026
- JTL Guide: FAQ on installation and setup (CSV import with JTL-Ameise), retrieved on 20 Oct 2026
Connections with JTL-Wawi
JTL-Wawi → DATEV
JTL-Wawi and DATEV after the end of Rechnungsdatenservice 2.0: what the Buchungsdatenservice covers, where customer accounts fail and when custom code helps.
Shopware → JTL-Wawi
Shopware 6 and JTL-Wawi: what the JTL-Connector syncs, why the sync gets stuck and when custom code makes sense for parts of it.
Related
JTL-Wawi → DATEV
JTL-Wawi and DATEV after the end of Rechnungsdatenservice 2.0: what the Buchungsdatenservice covers, where customer accounts fail and when custom code helps.
Shopware → JTL-Wawi
Shopware 6 and JTL-Wawi: what the JTL-Connector syncs, why the sync gets stuck and when custom code makes sense for parts of it.
Shop-ERP connection
Products, stock levels, prices and orders synced automatically between shop and ERP.
