JTL-Wawi is a widely used inventory management system for online retailers, but orders, stock levels and product data have to flow reliably between Wawi and your sales channels. I develop custom integrations that connect JTL automatically with your shop, your marketplaces and other systems, without anyone retyping data or maintaining stock twice.
What I build for JTL
- Creating orders in JTL: New orders from the shop or a marketplace arrive in JTL as a sales order, including addresses, line items and shipping method.
- Syncing stock: Stock levels from JTL are transferred to your sales channels continuously, so you never sell more than you can deliver.
- Retrieving product data: Items and changes are taken over from JTL instead of being maintained separately in every system.
- Fetching fulfillment data: Once an order has shipped in JTL, shipping and tracking information is collected and passed to the shop or marketplace.
- Setting up API access: Access to the JTL API is set up on the JTL side so that the integration runs cleanly and permanently.
- Connecting shipping carriers: With JTL as the leading system, carriers can be automated as well, see Logistics and fulfillment integration.
Excerpt from my JTL projects
- plentyONE and JTL: An integration in which plentyONE hands orders over to JTL. I set up the API access on the JTL side; product data and stock are retrieved from JTL, orders are created in JTL and fulfillment data is fetched back from JTL.
This is an excerpt from my completed projects, not a complete list of my services. JTL offers its own interface for items, stock and orders, and whatever else you need, I build individually. If your project does not appear here, just get in touch.
Ready-made connector or custom integration?
For common shop systems and marketplaces there are ready-made JTL connectors and plugins. They cover the standard case. Whether that is enough for you, the comparison shows:
| Ready-made connector | Custom integration | |
|---|---|---|
| Fits if | Your process follows the standard | Your process deviates or several systems are involved |
| Customization | Limited to none | Fully adaptable |
| Counterpart | Only systems supported by the connector | Any system with an API or file interface |
| Data sources | Usually one | Several sources can be combined |
| Costs | Ongoing license or subscription fees | One-time development, running costs usually lower |
Technology: how I work with JTL
I access items, stock, orders and shipping data via the JTL API. Access is set up and secured on the JTL side. Data is exchanged with the counterpart via REST, JSON, XML, CSV or FTP, depending on the system. We agree together, per data flow, which data leads in JTL and which in the shop.
Process
- Clarify data flows: Which data goes in which direction, which system leads, which special cases are there?
- Build and test: I build the integration and test it with real orders before it goes live.
- Go-live and operation: The integration runs in the background, runs are logged, and I implement process changes afterwards.
Every project is different, so you receive an individual quote after we have agreed the details.
Frequently asked questions
Which systems do you connect to JTL?
Shop systems such as plentyONE, Shopify or Shopware, and marketplaces, via Tradebyte or directly. I have already connected JTL with plentyONE.
Can JTL be the leading system?
Yes. Which system acts as the leading system is decided individually per data flow.
Do I need a plugin in JTL for the integration?
The integration uses the JTL API. Which prerequisites or approvals your JTL installation needs for it, we clarify in an initial call.
Can shipping carriers be connected too?
Yes. Shipping and tracking data can be taken over automatically, see Logistics and fulfillment integration.
You use JTL and need a shop or marketplace connection? Tell me briefly about your project.
Go to contact pageManufacturer: JTL-Software GmbH — more information: https://www.jtl-software.de (opens the manufacturer's website)