JTL-Shop shipping integration: how shipping via JTL-Wawi works and where the limits are

The JTL-Shop shipping integration is spread across three systems: JTL-Shop only calculates shipping costs at checkout, JTL-Wawi creates shipping labels and tracking numbers via JTL-ShippingLabels or JTL Shipping 2.0, and the JTL-Worker reports the tracking number back to the shop and marketplaces with a time delay. Since June 1, 2026, the old DHL Versenden 3.0 interface has been shut down.

How does the shipping integration in JTL-Shop work?

JTL-Shop has no shipping engine of its own: the shop only calculates shipping costs at checkout, while the actual shipping processing with label and tracking number happens in JTL-Wawi. The tracking number then travels back into the shop and to marketplaces such as Amazon and eBay via the JTL-Worker. The complete path of an order looks like this:

The JTL-Guide describes this division of tasks in several documentation chapters (accessed: July 2026). Important in practice: three sets of credentials are involved, the carrier account, JTL-Wawi and JTL-Shop, and each stage can have its own sources of error.

What is the difference between shipping methods and shipping classes?

Shipping methods are what the customer selects at checkout, for example parcel shipping or freight forwarding. Shipping classes are properties of the articles: according to the JTL-Guide, each article in JTL-Shop has exactly one shipping class, which the shop uses to decide which shipping methods and costs apply to the cart.

According to the JTL-Guide, each shipping method needs at least one destination country and a linked payment method, otherwise it does not appear at checkout. In addition, special cases can be mapped, such as island surcharges or different terms per customer group. This is exactly where many support cases arise: if an assignment is missing, customers simply do not see the shipping method.

How do you set up shipping methods in JTL-Shop and JTL-Wawi?

You first create shipping methods in the JTL-Shop backend, after which they are linked to the shipping methods in JTL-Wawi. According to the JTL-Guide, after the first shop synchronization the shop shipping methods automatically appear in JTL-Wawi and are linked automatically if the names match.

If the names do not match, you have to assign them manually in JTL-Wawi under Shipping in the section Create: shipping methods. Otherwise the column Corresponds to own shipping method shows the entry none, and that is exactly when shipping notifications get stuck later. The step-by-step instructions are provided by the JTL-Guide on linking shipping methods (accessed: July 2026).

In practice, it has proven effective to name the shipping methods identically in shop and Wawi from the start and to keep the structure lean: few shipping methods, clear shipping classes, maintained article weights. The more special cases, the more points where the chain can break later.

How do DHL labels and tracking numbers get into JTL-Wawi?

You create DHL shipping labels with JTL-ShippingLabels directly from JTL-Wawi, and the tracking number automatically comes back from DHL into the ERP system. For Amazon and eBay, according to the JTL-Guide, transmission is controlled via the Amazon Carrier Code and the eBay Carrier Code respectively, and tracking URLs can be embedded in email templates.

Requirements according to the JTL-Guide (accessed: July 2026): a DHL business customer account with customer number (EKP) and billing numbers from the business customer portal, a system user with rights for shipping and returns, and a ShippingLabels license in the JTL customer center. Details can be found in the JTL-Guide on JTL-ShippingLabels for DHL.

What is JTL Shipping 2.0 and what does it cost?

According to the vendor, JTL Shipping 2.0 is a completely new, cloud-based multi-carrier platform with over 35 carriers and, per vendor information, over 50,000 shipping and return methods. It is JTL's designated successor to the previous shipping modules and runs in parallel with the migration away from JTL-Versenden 3.0. Alongside DHL, DPD, UPS, GLS, Hermes and Deutsche Post, JTL also lists international carriers.

The plans according to the JTL website (as of July 2026):

Swipe to see all columns

Depending on the terms, label prices are added; as an example, JTL lists among others DPD Parcel Shop at €3.30 to €3.60 per label. All information according to the vendor website (as of July 2026); the sole binding source is the JTL page on the shipping software.

How does the tracking number get back into the shop and marketplaces?

The tracking number is not transferred in real time, but during the next synchronization by the JTL-Worker. The Worker runs at the selected time interval, fetches new orders, reports stock changes and transfers the shipping status including tracking number to the online shop, eBay and Amazon. There is therefore always a delay between label printing and visible tracking.

For marketplaces to assign the shipment correctly, the carrier codes must be right: Amazon and eBay each expect their own identifiers for the shipping provider. If the code is wrong or the shipping method is not linked, the order arrives, but the shipping status remains open. How the Worker operates is described in the JTL-Guide on the JTL-Worker (accessed: July 2026).

Which problems frequently occur with the JTL-Shop shipping integration?

The most common disruptions concern the feedback chain and missing master data. In the JTL support forum, for example, there are discussions about tracking numbers being only partially transferred or having to be transmitted retroactively to the online shop, customers and marketplaces. You should check these points first when troubleshooting:

• Tracking numbers only partially arrive: usually an unlinked shipping method (entry none in the Wawi) or a Worker that does not synchronize or synchronizes too rarely. This is a recurring topic in the JTL support forum (accessed: July 2026).
• Wrong shipping costs at checkout: missing article weights render weight-based scales ineffective, and the calculated shipping costs do not match the actual carrier contracts.
• Label printing fails: incorrect API credentials, a wrong customer number (EKP) or missing billing numbers in the DHL business customer portal stop label creation.
• International shipping fails: missing CN22 customs data blocks shipments to non-EU countries, because the carrier will not create the label without a customs declaration.
• Tracking emails end up in spam: without correctly configured SPF and DKIM records, email providers filter out the shipping confirmations with the tracking link.

Example discussion: JTL support forum on partially transferred tracking numbers (accessed: July 2026).

When are the built-in JTL tools enough and when is an integrated solution worthwhile?

For a pure JTL setup with shop, Wawi and standard shipping, the built-in JTL tools are sufficient: JTL-ShippingLabels or JTL Shipping 2.0 cover label printing, and the Worker handles the feedback. Anyone who has configured the chain cleanly once and can live with the time-delayed synchronization does not need an additional system.

It is different when shipping runs across multiple channels and the tracking numbers need to flow back to shop and marketplaces reliably and without manual rework. This is exactly the feedback chain the DezemberHub Connector addresses: the shipping software is integrated, labels are created in the same system as the orders, and the tracking number automatically goes back to the shop and all connected marketplaces, without a separate Worker chain and without handing off to an external shipping tool.