Skip to content
Kaufland

JTL-Wawi Kaufland Integration: Anbindung Guide

How to connect Kaufland to JTL-Wawi: JTL-eazyAuction setup, EAN listing, GPSR fields, orders and carrier codes, common errors, and when to build a custom integration.

Written by
Md AshikSenior Software Engineer, Artisan Dojo
Published
Reading time
8 min read
Quick summary30-second read
  • JTL-eazyAuction lists Kaufland Global Marketplace as a native sales channel in JTL-Wawi, set up under Plattformen > Verkaufskanäle.
  • If an EAN already exists on Kaufland, JTL sends only offer data; new EANs create products that stay "In Prüfung" until approved.
  • Every Kaufland offer needs a shipping group and warehouse, defined in the Kaufland Seller Portal and synced into JTL-Wawi.
  • GPSR contact data comes from the article's manufacturer or responsible person, mapped in JTL-Wawi 2.0 with DotLiquid variables.
  • A custom integration via the Kaufland Seller API and JTL-Wawi API fits bundles, special stock or pricing logic, and failing connectors.

The standard way to connect Kaufland to JTL-Wawi is JTL's own marketplace module, JTL-eazyAuction, which lists Kaufland Global Marketplace as a sales channel: you add it under Plattformen > Verkaufskanäle, and it syncs offers, stock, prices, orders, shipping confirmations and returns. The alternatives are a third-party connector or middleware, or a custom integration built on the Kaufland Seller API and the JTL-Wawi API. For most sellers the native JTL-Wawi Kaufland integration is the starting point, and custom work only makes sense where it stops fitting.

Our general Kaufland ERP guide explains the Kaufland side: EAN matching, units, storefronts and order units. This post covers the JTL side, what the native connection does, where sellers usually get stuck, and when to build something yourself.

What are the options for a JTL-Wawi Kaufland Anbindung?

RouteHow it worksGood fitWatch out for
JTL-eazyAuction (native)Kaufland Global Marketplace added as a sales channel in JTL-WawiMost JTL sellers with standard products and processesNeeds an eazyAuction license for the channel and an order package; each order counts as a transaction
Third-party connector or middlewareA partner tool talks to Kaufland and syncs with JTL-WawiSellers who already run several marketplaces through one toolOne more system to map, monitor and pay for
Custom integrationYour own service between the Kaufland Seller API and JTL-WawiBundles, special stock logic, Fulfillment by Kaufland flows, or data the standard fields cannot carryYou own maintenance, including Kaufland API changes

A few things about the native route, from JTL's own guide:

  • Requirements. A Kaufland seller account, JTL-Wawi 1.8.3 or later, an edition that includes an order package, and an active JTL-eazyAuction license for the channel. JTL says additional channel licenses can be booked free of charge in the JTL customer center, but every order on the channel is billed as a transaction against your order package, whether you import it or not.
  • Countries. JTL's Kaufland page lists Kaufland.de, .at, .cz, .sk, .pl, .fr and .it as active. Additional countries on the same seller account are added as separate sales channels, without a new account.
  • B2C only. JTL's FAQ notes that Kaufland offers only B2C trade.

You will also see "JTL-SCX" in forums and on partner sites. It is JTL's sales channel interface for JTL-Wawi, and third-party developers use it to sell their own connectors for marketplaces JTL does not cover itself. For Kaufland, check first whether the native channel already does what you need.

How does listing work ("JTL Kaufland Artikel listen")?

Everything starts with the EAN. JTL sends either product data or offer data, depending on whether the EAN already exists in Kaufland's catalog:

  • EAN exists on Kaufland. Only the offer is sent: price, stock, shipping group. You can force this per article or per category with the field "Nur Angebotsdaten senden" set to Ja, under Verkaufskanalspezifische Felder.
  • EAN is new to Kaufland. JTL sends product data and Kaufland creates the product. JTL's guide says approving new products takes several hours, sometimes several days, and offers stay "In Prüfung" until then.
  • Required offer fields. Each offer needs a shipping group (Versandgruppe) and a warehouse (id_warehouse), both defined in the Kaufland Seller Portal and then synced into JTL-Wawi as metadata. If the warehouse is empty and no default exists, Kaufland rejects the offer.
  • Category attributes. For new products, you map JTL data to Kaufland's category-specific fields under Plattformen > Weitere Marktplätze > Verkaufskanalfelder zuordnen. Set them on the top-level category for all articles, or per category where requirements differ.
  • Variations. Kaufland receives the parent's variation names and values automatically. JTL warns that filling variation-forming marketplace fields yourself can get the offer rejected.

Prices come from a JTL-Wawi customer group assigned to the channel's price types. If you want different prices per storefront, create a separate customer group per Kaufland channel. JTL enters prices in your default currency and converts them at sync, so Polish and Czech prices move with the exchange rate.

How do you send GPSR data from JTL to Kaufland?

Since the EU General Product Safety Regulation (GPSR), Kaufland needs manufacturer or responsible-person contact data per product. In JTL-Wawi this lives on the manufacturer (Hersteller) and the responsible person (verantwortliche Person) assigned to the article. JTL's guide names five Kaufland fields: name, address, email, and either phone or website URL.

For JTL-Wawi 2.0, JTL provides DotLiquid variables for these fields, mapped under Verkaufskanalfelder zuordnen in the "Produktsicherheit" fields, and recommends replacing older SQL-based mappings with them. Two rules from the guide matter:

  • Use one contact type per article. Either the manufacturer or the responsible person, not a mix across fields.
  • Non-EU manufacturers need a responsible person. JTL recommends storing one for every manufacturer so the mapping stays consistent.

Top tip

Before a large listing run, filter your JTL articles for missing EANs, missing manufacturers and missing responsible persons. Each of those turns into a rejected offer later, and those rejections are much slower to find on Kaufland than in JTL.

How do orders, shipping and returns flow?

With the native channel, Kaufland orders are imported into JTL-Wawi, invoices can be uploaded, shipping confirmations go back automatically, and returns are handled in JTL-Wawi. Some details worth knowing:

  • No back-import. Only orders placed after the connection are imported.
  • Carrier codes. Map each JTL shipping method to a Kaufland carrier code in the Versand tab. JTL's FAQ lists "Validation Failed (Code 400)" on shipping confirmations as an invalid carrier code.
  • Errors. Rejected shipping confirmations appear under Plattformen > Weitere Verkaufskanäle > Wichtige Ereignisse (F10). If an order stays "Unversendet", look there first.
  • Sync timing. With JTL-Worker, sync runs automatically on intervals you set. After adding a channel, JTL says to restart the Worker once.

On the Kaufland side, every item in an order is its own order unit, shipped, cancelled and returned on its own.

How to set up the JTL-Wawi Kaufland integration, step by step

Step 1: Check version and licenses

Confirm your JTL-Wawi version, that you have an order package, and that the JTL-Wawi tenant is linked to the JTL customer center with a JTL-eazyAuction license for the channel.

Step 2: Prepare the Kaufland Seller Portal

Create shipping groups and warehouses there first. Turn off any other stock or price feed, such as Kaufland's automatic CSV upload. JTL's FAQ says several feeds overwrite each other's prices and stock.

Step 3: Add the sales channel

Under Plattformen > Verkaufskanäle, click Anlegen, pick Kaufland, add it and sign in with your access data. In the Anbindung tab, set a returns warehouse and enable "Bestand senden".

Step 4: Sync metadata and configure prices and shipping

Enable the metadata import, run a sync, assign a customer group to the price types, and map shipping methods to carrier codes. Then sync again.

Step 5: Map category fields and GPSR

Fill in the required fields under Verkaufskanalfelder zuordnen, including shipping group, warehouse and the product safety fields.

Step 6: List a small batch first

Activate a few articles with existing EANs and a few new ones. Check what Kaufland accepts, what stays "In Prüfung", and what shows up as an error, before listing the full catalog.

Common mistakes with JTL and Kaufland

  • Two feeds for one account. An old CSV upload or another tool still updates offers, and prices or stock flip back after each JTL sync.
  • Missing carrier mapping. Orders ship in the warehouse but stay unshipped on Kaufland, which hurts your seller metrics.
  • No stock buffer for prepayment. JTL's FAQ points out that prepaid orders only reach JTL-Wawi after payment, so the same stock can sell twice in between.
  • Expecting Kaufland to keep your category. Kaufland may move offers into a category it considers better. JTL says turning this off goes through Kaufland support.
  • Ignoring "Aktueller Wert". Kaufland sometimes changes or partly accepts product data. If customers see something different from what you sent, compare "Ihr Wert" and "Aktueller Wert" and raise it with Kaufland.

Our marketplace ERP integration checklist covers more go-live checks.

When does a custom integration make sense?

A custom integration is worth it when your process does not fit the native channel's standard flows, for example:

  • Stock logic JTL does not model the way you need, such as bundles from several warehouses or per-channel allocation rules.
  • Pricing rules per storefront that go beyond one customer group and a currency conversion.
  • Data JTL cannot map, or workflows around returns, cancellations or Fulfillment by Kaufland that need more control.
  • An existing JTL-SCX or third-party connector that keeps failing and nobody maintains.

Technically, a custom integration talks to Kaufland through the Seller API (https://sellerapi.kaufland.com/v2/, HMAC-signed requests) and to JTL-Wawi through the JTL-Wawi API, a REST API JTL documents on developer.jtl-software.com in on-premise and cloud variants. An app first has to be registered in JTL-Wawi under Admin before it can call the API, and which variant applies depends on your Wawi version. Writing straight into the JTL-Wawi SQL Server database bypasses JTL's own logic, and we avoid it.

If you are planning one, our post on the Kaufland API v2 migration covers the current API, and custom integration vs. connector compares the trade-offs. For Odoo instead of JTL, see the Kaufland Odoo integration guide.

FAQ

Does JTL-Wawi support Kaufland natively?

Yes. JTL-eazyAuction lists Kaufland Global Marketplace as a sales channel, with offer sync, order import, invoice upload, shipping confirmations and returns. It needs a JTL-eazyAuction license for the channel and an order package.

Can I sell on several Kaufland countries with one JTL setup?

Yes. Each additional Kaufland country on the same seller account is added as its own sales channel in JTL-Wawi. Use a separate customer group if prices should differ.

Why do my Kaufland offers stay "In Prüfung"?

New products need Kaufland's approval. JTL's FAQ says processing normally takes up to 24 hours, and new sellers go through a manual review that can take longer.

What is "jtl kaufland gpsr" about?

Sending manufacturer or responsible-person contact data to Kaufland. In JTL-Wawi 2.0 you map it with DotLiquid variables under Verkaufskanalfelder zuordnen.

Do I need JTL-SCX for Kaufland?

Not necessarily. JTL-SCX is the interface third-party developers use to connect other marketplaces to JTL-Wawi. Kaufland is available through JTL-eazyAuction, so check the native channel first.

Need help with your JTL Kaufland connection?

We build and maintain Kaufland integrations for JTL-Wawi and other ERPs, from fixing an existing setup to custom stock and pricing logic. See our Kaufland API integration service and marketplace ERP integration service, or book a free 30-minute call by describing your JTL setup below.

Need help with this?

Describe your project. Get a reply from an engineer.

Which marketplaces or platforms are involved?
What do you need?
How should we get back to you?

We use your details only to reply to this inquiry. See our privacy policy.

Keep reading

Related guides

All guides
MessageFree 30-min call