↑↓ selectEnter openEsc close

    1. Elbuz
    2. European marketplaces

    How to connect Kaufland to Elbuz: offers, orders and prices in cents

    23 min readUpdated

    Elbuz connects to your Kaufland Marketplace seller account (Germany, Austria, Czechia, Slovakia, Poland) with a key pair: it imports offers into the base catalog, receives orders and sends back prices and stock.

    When you need this:

    • You sell on Kaufland and elsewhere — one catalog for all channels' stock and orders.
    • Several Kaufland countries — each gets its own template.
    • A manager handles orders in Elbuz — repeat runs don't overwrite their statuses or posted documents.
    • You price in Elbuz — the export sends them to Kaufland, publishing new offers by EAN.

    Where to start: take both keys from your seller account and paste them into a “Kaufland” template.

    What the Kaufland connection can do

    • Connection with two keys — no app to link.
    • Offer import — with the name, description, manufacturer, , price, stock, category and photos of the Kaufland product page.
    • Orders — the full history on the first run, then only changes; a run doesn't overwrite your manager's work.
    • Reservation for orders — once the document is posted.
    • Prices and stock back to Kaufland — in batches, with new offers published by EAN.

    What you need from Kaufland

    The connection works without linking an app: you paste two keys from your seller account. The “Connection” card has five fields, and the first two are required:

    Template fieldWhat it is
    Client key (Shop-Client-Key)The public half of the key pair. Required
    Secret keyThe secret half: every request is signed with it. Required
    StorefrontCountry code: de, at, cz, sk, pl and other storefronts open to your account. The “Pick from list” button under the field shows them and fills in the one you choose. If left empty, de is used
    Shipping group The import doesn't use it. For publishing new offers, it's set in the export template (export)
    VAT indicator (vat_indicator)Same here: it doesn't affect the import, and for publishing it's set in the export template

    Once the keys are in, click “Test connection”: Elbuz sends one lightweight signed request and replies with the storefront name. This confirms the keys were copied in full and the right country is selected.

    “Active” and “Orders” are already on in a new template: within 5 minutes of saving the keys, Elbuz starts fetching the entire order history. Elbuz maps marketplace statuses to yours automatically, by name; the template's “Order statuses” window shows what came in and how it was mapped. Want to check first? Clear “Orders”.

    Marketplace documentation for sellers: Kaufland Seller API. The keys are issued in your seller account, in the settings section.

    What goes into the product card

    Kaufland has a shared product page (maintained by the marketplace) and your offer on it — price, stock, condition. Elbuz takes the list of your offers and fetches the product page for each one, so the catalog gets a complete product, not just a line with a price.

    Kaufland dataProduct field in Elbuz
    product page nameName
    page description and short descriptionDescription, short description
    manufacturerManufacturer
    id_offer — your offer codeSKU
    page EANBarcode
    offer price (in cents)Price (converted to currency)
    offer stockQuantity
    offer conditionStatus: available — product enabled
    page categoryCategory
    main photo and other imagesPhotos (if the matching checkbox is on)

    The marketplace sends and accepts money in cents: 5999 means 59.99. Elbuz converts it both ways on its own, and the catalog shows a regular price. A four-digit number in Kaufland data where you expected two digits is cents.

    Specifications and categories

    Product specifications don't come from Kaufland: the marketplace doesn't share page attributes through this channel. If Elbuz is your main catalog, fill in specifications yourself or pull them from another source, such as a supplier price list.

    The category comes as a single name, not a full path: the marketplace's category tree won't appear in the catalog. Kaufland service categories:

    • “Products - kaufland” — for offers whose page has no category;
    • “Products - kaufland - ‹template name›” — for products from orders that weren't in the catalog.

    Both are created disabled and excluded from exports, so these products go nowhere until you sort them into your own categories. A repeat run doesn't move a product in the tree. How to remove a service category safely: service categories and brands.

    What a repeat run overwrites

    A repeat import finds its card by the name Kaufland returned: the marketplace doesn't pass the manufacturer's part number or a product link. Here's how a run changes a card it finds:

    What the run doesFields
    Overwrites with Kaufland dataname, description and short description, manufacturer, SKU (offer code), barcode, price, quantity, the “enabled” flag
    Clears every timeold price and tags — Kaufland doesn't pass them
    Leaves aloneposition in the category tree, photos of an existing card, specifications

    If you fix a name in Elbuz, the next run brings back the Kaufland page name without warning. If you set the old price by hand, the Kaufland template will wipe it on every run.

    To lock a whole card, use the “Do not update” toggle in the product card, “Import protection” section. To keep a run from overwriting the price with the marketplace's, turn on “Fixed price” in the card: other fields still update, but the price stays yours.

    The “Import protection” group in the product card, Statuses and flags section
    1Do not update
    2Fixed Price
    1. Do not update: closes the whole product card from an import run.
    2. Fixed Price: protects the card's prices from being overwritten by an import run.

    An offer disappeared from the marketplace or changed condition

    The import doesn't touch an offer that wasn't in the run: the product keeps its last price and stock, isn't disabled or deleted, and the log says nothing about it. Remove discontinued items by hand, or they'll go out with old numbers in exports to other channels.

    An offer that still comes in but has changed condition:

    • condition AVAILABLE — the product in Elbuz is enabled;
    • another condition and zero stock — the product is disabled;
    • another condition but stock above zero — the product stays enabled.

    If Kaufland isn't the only source for a product

    Kaufland finds a card by its name. A card created by another source with a manufacturer part number or a product link won't be recognized: Kaufland will create a second one with the same name. A card that the other source also identified only by name will be written to by both templates.

    A shared card keeps the value from the run that finished last (two templates on the same product). With Kaufland, you'll notice it on stock: if a supplier price list also feeds the card, the quantity will jump between two values. The “Do not update” toggle keeps the sources apart.

    How orders arrive

    Kaufland sends orders as lines — separate “order unit” records. Elbuz groups them into a document by order number: it takes the header from the first line, adds the rest as items and totals the amount. Three identical products become three lines of one piece each, not one line with a quantity of three.

    The document gets:

    • the order number, creation and change dates, external status;
    • the recipient's first and last name, phone, the buyer's email, comment;
    • the shipping address — street, house number, city, postcode, country;
    • the currency.

    The status comes as a marketplace code, and Elbuz maps it to yours by itself: need_to_be_sent — “Processing”, sent — “Shipped”, cancelled — “Canceled”. You can adjust this with the “Order statuses” button in the “Related settings” card of the template form. An unrecognized status gives a new order “New” and leaves an existing document unchanged.

    The first import brings in the entire history — slow for a large account. After that, Elbuz takes only what changed since the last run, with a twelve-hour margin for lines changed after a page was read. Existing orders are recognized by number and updated, not duplicated.

    What a repeat run does to an order

    A document is recognized by the order number together with the source code. A run overwrites little:

    • Your processing status changes only when the status on the marketplace has actually changed since last time.
    • The external status and its name are overwritten with marketplace data.
    • Address, phone, email, contact, comment and amount are filled in once, when the document is created.
    • Items go only into a newly created document: new lines aren't added to an existing one, and a line deleted by a manager won't come back.
    What a repeat run does to an order already in Elbuz. Your status changes only at the bottom of the right branch, when both conditions are met
    YesNoNoYesNoYesAn order with this numberis already in ElbuzIs the document posted?No field changesHas the marketplace status changedsince the last run?Your status staysIs this status mappedwith the “Order statuses” button?The document getsyour status from the mappingExternal status, delivery serviceand payment service are overwrittenwith marketplace dataItems, address, contacts,comment and amount stay as theywere
    • Action or result
    • Decision: the path depends on the answer

    A repeat import doesn't change a single field in a posted document. Once it's posted, the marketplace no longer writes to it.

    Kaufland passes neither the delivery service nor the payment service, so a run writes an empty value to the “Delivery service” and “Payment service” fields, and whatever a manager entered disappears. This doesn't apply to posted documents.

    Orders, stock and reservations

    An order arrives as a “Customer order” document, unposted. While it's unposted, neither stock nor reservations move.

    • You post the document — a reservation appears for its items. Stock isn't written off; part of it is marked as taken.
    • You move it to a final status — completed, delivered, cancelled, rejected, returned and the like — the reservation is released.
    • You post a sales invoice based on the order — it writes off the goods, and the order's reservation drops by that quantity.

    Reservations work when inventory tracking is on and at least one warehouse exists.

    A cancellation on Kaufland arrives with a regular run and changes the document status — only if the document isn't posted. A posted order keeps its previous status and holds the reservation until you change the status yourself. Look for mismatches between your Kaufland account and Elbuz among cancellations.

    Related settings card with schedule and order status buttons
    1Order statuses
    2Schedule setup
    1. Order statuses — map Kaufland status codes to your own statuses.
    2. Schedule setup — configure how often orders are fetched.

    How prices and stock go back to Kaufland

    The reverse direction is a separate export template of the same type: Elbuz sends prices and stock in batches of up to 150 items; the marketplace answers for each, and the log shows how many passed and how many were rejected. The offer key is saved on catalog import, so import the Kaufland catalog once before the export.

    Instead of a zero price, Elbuz sends 1 cent. A product with an empty or zero price will appear on the marketplace at 0.01 and sell for that. Before the first export, make sure the template's filtered set has no products without a price.

    Elbuz can't deactivate or delete offers: a product that drops out of the export's filtered set simply stops getting updates. To stop selling, set stock to zero and wait for the export, or deactivate the offer in your Kaufland account.

    Publishing new offers

    With the “Publish new products” checkbox on, Elbuz publishes an offer for a product that doesn't have one on the marketplace yet. The offer attaches to an existing page by EAN, so you need a barcode (at least 8 digits) and a shipping group ID — without it, publishing won't start.

    The shipping group ID, VAT indicator and storefront are set in the export template's “API version (marketplace parameters)” field: storefront|id_shipping_group|vat_indicator, for example de|3457|standard_rate. An empty storefront means de, an empty VAT indicator means standard_rate.

    If the product page doesn't exist in the Kaufland catalog yet (you're the manufacturer or the first seller), Elbuz sends the name, description, manufacturer, photos, product condition and the mapped Kaufland category for marketplace review. The offer for the page is created on one of the next runs, once Kaufland approves it.

    The name and description are taken in the language set in the export template's “Description language” field — for the German storefront, pick German; without a translation, the main language is sent. Map Kaufland category attributes in the category matching window, “Kaufland attribute” column: without required attributes the page isn't sent, and the log lists what's missing.

    The log shows each published offer as a line “Kaufland: product ‘…’ published (unit …)”.

    What has to line up for a new offer to go to Kaufland. A yellow diamond is a decision point, and publishing can stop at any of them
    NoYesNoYesNoYesYesNoThe product is in Elbuz,no offer on the marketplaceIs the “Publish new products”checkbox on?The offer isn't publishedDoes the product have an EANbarcodeof at least 8 digits?Publishing won't start —log entryIs the shipping group IDset in the export template?Publishing won't start —log entryIs there already a page with thisEANin the Kaufland catalog?The offer attachesto the existing pageThe page data goesfor marketplace reviewReview is asynchronous: the offer iscreatedon one of the next runs
    • Action or result
    • Decision: the path depends on the answer

    Scheduled updates

    Kaufland doesn't send instant notifications, so Elbuz fetches orders by itself every 5 minutes if “Orders” is checked and the keys are filled in. The shared “Marketplace orders” task in the “Job schedule” window does this; the interval is set there. This pass skips the catalog, and orders also picked up by the template schedule aren't duplicated.

    The catalog is updated by the template's own schedule — the “Schedule setup” button in the template form. Set it to run rarely, for example at night: while the catalog is running, the orders pass is skipped until the next one.

    The “Active” / “Disabled” badge takes the template off the schedule and out of automatic order fetching, as with other sources (disable a template). The price export is a separate template with its own switch: if you disable the import, prices will still go to the marketplace.

    If a run breaks off

    • The catalog is written in batches of 500 offers: whatever was saved is updated, the rest keeps old data. With fewer than five hundred offers there's one batch, and nothing gets saved.
    • Orders are all or nothing: Elbuz reads every page and saves in one go. The date from which the next portion is taken moves only after saving, so a retry picks up the same interval.
    • The export breaks off in batches of 150: whatever went out is changed on the marketplace.
    One order run. The left branch is the first run, the right one is every run after it. Note the error in the middle: it breaks off the run before saving, so the date doesn't move and the next run picks up the same interval
    No — first runYesYesNoYesNoNoYesOrder runIs there a date in the“Import ordersfrom date” field?All order lines are takenLines changed since that dateminus twelve hours are takenPages of 100 lines —lines are grouped into documents bynumberDid the marketplace return an error?The run stops — no orderis saved, the date doesn't moveAre there more pages and“Stop” wasn't clicked?Was at least oneorder collected?Nothing is saved,the date doesn't moveAll collected ordersare saved togetherThe date in the field movesto the latest change read
    • Action or result
    • Decision: the path depends on the answer

    A retry is safe: an order is found by number, a product by name. General rules: if a run breaks off.

    How much Elbuz takes in one run

    There's no cap on the number of offers or orders. The catalog takes longest: besides the offer pages, Elbuz requests each product page and each Kaufland category separately. To see how long it takes for you, check the “Time spent” column in the template list and “Run history” in the template card header.

    WhatHow much
    Page of offers and page of order lines100 per request
    Writing to the base catalogin batches of 500 offers
    Batch when updating prices and stock150 items — a hard Kaufland limit
    Waiting for one response120 seconds, 30 for the connection
    Retries after a rate-limit rejectionup to three, with a growing pause
    Photos when sending a new page for reviewup to 12
    EAN barcode for publishing an offerat least 8 digits

    Scenarios

    Data selection card with Products, Photo and Orders checkboxes
    1Products
    2Photo
    3Orders
    1. Products — import the product catalog.
    2. Photo — import product photos.
    3. Orders — import marketplace orders.

    Move your Kaufland catalog into Elbuz

    What to turn on. Fill in “Client key (Shop-Client-Key)”, “Secret key” and “Storefront”; in the “Select data to import” card, select “Products”, and for images also “Photo”.

    What you get. Each offer lands as a card with the name, description, manufacturer, barcode, price converted from cents, stock and a single-name category. There will be no specifications or old price — Kaufland doesn't pass them.

    Receive orders without losing your manager's work

    What to turn on. The “Orders” checkbox; Elbuz maps the statuses by itself, and the “Order statuses” button in the “Related settings” card is for adjustments. The template needs no schedule: orders arrive by themselves every 5 minutes.

    What you get. The first run picks up the history, later ones the changes since the date in the “Import orders from date (YYYY-MM-DD)” field in the “Advanced” block, with a twelve-hour margin. Your status changes only when the Kaufland status has changed and is mapped; a posted document doesn't change.

    Kaufland as a sales channel for a catalog you manage in Elbuz

    What to turn on. Run the import once with the “Products” checkbox — it links cards to offers. Then keep only “Orders”, otherwise the catalog run will overwrite price and stock with Kaufland figures. Prices are sent by an export template of the same type.

    What you get. Linked products go to the marketplace in batches of 150 items, with a price of at least one cent and stock of at least zero. Without the “Publish new products” checkbox, products not linked to an offer are skipped with no log line.

    What to do when Kaufland won't send or accept data

    Troubleshooting common problems
    What you seeWhyWhat to do
    “Test connection” doesn't reply with the storefront name A key was copied incompletely or the wrong country is selected Paste both keys and the country code again (what you need from Kaufland)
    “Kaufland: API error - HTTP 429: rate limit” The request limit was still exhausted after three retries Run the template later — a retry is safe (if a run breaks off)
    “Kaufland: ‘…’ - no EAN barcode, publishing to Kaufland is not possible” An offer attaches to a marketplace page by EAN Fill in a barcode of 8 digits or more in the product (publishing new offers)
    “Kaufland: shipping group ID (id_shipping_group) is missing - publishing is not possible. Fill it in the template” An offer can't be created without a shipping group Enter it in the export template's “API version (marketplace parameters)” field, for example de|3457|standard_rate
    “Kaufland: prices and stock updated, offers: N (errors: M)” with a non-zero M The marketplace rejected some items Fix the prices and stock in the catalog and run the export again — the offer updates under the same key
    The catalog run overwrote the wrong data There's no bulk undo, and old values aren't kept Affected cards — the “Date updated” column, created ones — “Source: name”; the price is visible in “Product price history” (if you imported the wrong data)
    An offer was published by mistake Elbuz can't deactivate offers, and the link stays Deactivate the offer in your Kaufland account and remove the product from the export template's filtered set
    Products in the “Products - kaufland” category aren't exported The service category is created disabled Move the products to your own categories (categories)
    The “Delivery service” entered by a manager is gone Kaufland doesn't pass it, so the run writes an empty value Post the document — a run doesn't write to posted ones (repeat order run)

    FAQ

    What goes in the “Storefront” field?

    The storefront's country code: the “Pick from list” button under the field shows the ones open to your account. An empty field means Germany. For several countries, create a template for each (template fields).

    Why do products have no specifications?

    Kaufland doesn't pass page attributes through this channel. Fill them in Elbuz or pull them from another source (specifications).

    Why does an order have three lines of one piece instead of one line of three?

    The Kaufland API sends orders as separate units. The order total and contents are correct, there are just more lines (orders).

    Why does the old price I set by hand disappear?

    Kaufland doesn't pass an old price, and every run writes an empty value. Lock the card with the “Do not update” flag (repeat run).

    An order was cancelled on Kaufland — what happens in Elbuz?

    An unposted document gets your status from the mapping. A posted one stays as it was and holds the reservation (reservation).

    A product disappeared from Kaufland — will Elbuz delete it?

    No. The item keeps its last price and stock; remove it by hand (disappeared offer).

    Where it is and who has access

    Menu
    Directories → Operations → Data import → new template of type “Kaufland”
    Other entry points
    Directories → Operations → Data export — a template for prices and stock
    Access right
    the “Import” window in “Group permissions”
    Have ready
    the client key and secret key from your Kaufland seller account

    One template covers one storefront: if you sell in both Germany and Poland, create two templates with different values in the “Storefront” field.

    Kaufland connection card with key and storefront fields
    1Client key
    2Secret key
    3Storefront
    1. Client key — the public half of the key pair.
    2. Secret key — the secret half of the pair.
    3. Storefront — the Kaufland country code.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free