↑↓ selectEnter openEsc close

    1. Elbuz
    2. European marketplaces

    How to connect Zalando to Elbuz: prices by country, orders and new products

    6 min readUpdated

    Elbuz connects to your Zalando partner account (zDirect, 15 EU countries) with application keys: it imports prices and stock by EAN, receives orders and returns prices and stock for each sales country.

    When you need this:

    • You sell on Zalando and elsewhere — all channels' stock and orders in one catalog.
    • Several Zalando countries — one template updates price and stock in all.
    • The product is already on Zalando — Elbuz adds your offer to it by EAN.
    • You're a manufacturer — Elbuz submits a new product by the mapped outline.

    Where to start: get your zDirect application's Client ID and Client secret and paste them into a “Zalando” template.

    What the Zalando connection can do

    • Connection with two application keys — no link code and no Elbuz gateway.
    • Catalog import — the price, stock and status of each for the template's first country.
    • Orders — the history on the first run, then only changes.
    • Prices and stock back to Zalando — to each listed country, in that country's currency.
    • Publishing — an offer on an existing product by EAN, or a new product submitted for Zalando review.

    What you need from Zalando

    Zalando accepts sellers by invitation only. First you pass selection for the Zalando partner program and sign the partner agreement — only then do you get access to the zDirect Partner Portal and its API.

    The keys are issued by an application created in the zDirect Partner Portal:

    1. The seller invites their technical partner to zDirect.
    2. The technical partner creates an API application specifically for this seller. One application account serves one seller.
    3. The portal shows the two halves of the key — Client ID and Client secret. Paste them into the Elbuz template.
    Zalando import template: the Connection card with API key fields
    1Client ID
    2Client secret
    3Sales countries
    4Merchant ID
    1. Client ID — the public half of the zDirect app keys.
    2. Client secret — the secret half; stored hidden.
    3. Sales countries — country codes separated by commas; the first one gives the catalog price and stock.
    4. Merchant ID — needed only when the keys cover several sellers.
    Template fieldWhat it is
    Client IDThe public half of the application key. Required
    Client secretThe secret half of the key. Required
    Sales countries: comma-separated codes (de,at,pl...)Two-letter country codes. The first country is the source of price and stock when importing the catalog. If left empty, de is used
    Merchant ID (optional - detected from the keys)The Zalando merchant code. Fill it in only when the keys serve several merchants — otherwise Elbuz detects it on its own

    Once the keys are in, click “Test connection”. Elbuz asks Zalando who owns the keys and replies with a “Zalando” line showing the country codes and Merchant ID. This confirms the keys were copied in full.

    “Active” and “Orders” are already on in a new template: within 5 minutes of saving the keys, Elbuz starts fetching all orders Zalando keeps. 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”.

    Zalando documentation for partners: zDirect API authorization, rate limits.

    What comes in from the Zalando catalog

    Through the API, Zalando returns only the offer figures: EAN, price, stock and status. The response has no name, description, brand, photos or specifications. So each EAN becomes a separate Elbuz product that looks like this:

    Zalando dataProduct field in Elbuz
    size EANBarcode and SKU
    —Name “Zalando ‹EAN›”
    price in the template's first countryPrice
    stock in the first countryQuantity
    offer online or stock above zeroStatus: product enabled
    —Category “Zalando”

    The “Photo” checkbox has no effect on the Zalando import: the marketplace doesn't return images through this channel. Fill in names, descriptions and photos in Elbuz yourself or pull them from a supplier price list.

    Zalando import template: the Select data to import card with checkboxes
    1Products
    2Orders
    1. Products — the catalog: prices, stock and statuses by EAN.
    2. Orders — Zalando orders are fetched automatically.

    What a repeat run changes

    For a product already in the catalog, a run updates only the price, quantity and status. It doesn't touch the name, description, category, photos or other fields — even if the name is still “Zalando ‹EAN›”. So rename the card, and the run won't bring that name back.

    A run finds its card by the EAN link set by the first import or by publishing from Elbuz. To lock out the remaining updates, use the toggles in the product card, “Import protection” section:

    • “Do not update” — the Zalando run doesn't change the card at all;
    • “Fixed Price” — the run doesn't overwrite the price, but still updates quantity and status.

    A card created from a supplier price list or by hand isn't recognized by the Zalando catalog import: it has no EAN link yet. The run creates a second card, “Zalando ‹EAN›”. If you maintain the catalog in Elbuz, don't turn on “Products” — link your products through the export (scenario).

    A run doesn't disable or delete a product that disappeared from Zalando: the item stays with its last price and stock. General rules: a product disappeared from the source.

    How orders arrive

    Each Zalando order arrives as a “Customer order” document with the order number. The document gets:

    • the number, creation date and modification date, and the Zalando status code;
    • the recipient's first and last name, the buyer's email and customer number;
    • the shipping address — address lines, city, postcode, country;
    • items with price and quantity, and the currency.

    An item's quantity is the ordered amount minus what was canceled on Zalando. Zalando doesn't pass the buyer's phone, carrier or payment method, so these fields stay empty.

    The first import brings over all orders Zalando keeps. After that, Elbuz takes only what changed since the last run, with a twelve-hour margin. An existing order is recognized by its number and updated, not duplicated. How a repeat run treats the status, items and a posted document works as for Kaufland: repeat order run.

    The status comes as a Zalando code, and Elbuz maps it to yours by itself, by name; you can adjust this with the “Order statuses” button in the “Related settings” card of the template form.

    Zalando import template: the Related settings card with Order statuses and Schedule setup buttons
    1Order statuses
    2Schedule setup
    1. Order statuses — maps Zalando status codes to your own statuses.
    2. Schedule setup — sets how often the import runs.

    Elbuz doesn't confirm anything on Zalando by itself: tracking numbers and shipments aren't sent back. Mark shipments in zDirect, and Elbuz picks up the new status on the next run.

    How prices and stock go back to Zalando

    The reverse direction is a separate export template of type “Zalando”. It has the same Client ID and Client secret, and the “API version (marketplace parameters)” field sets the countries: de,at. If the keys serve several merchants, add the Merchant ID after a pipe: de,at|your-merchant-id.

    On Zalando, the price is set separately for each country. Elbuz sends the product's price and stock to each country in the field, in batches of up to 1000 items. The currency depends on the country:

    CountryCurrency Zalando reads the price in
    plPLN
    czCZK
    chCHF
    se, dk, noSEK, DKK, NOK
    gb, hu, roGBP, HUF, RON
    others (de, at, fr, nl…)EUR

    Elbuz sends the number from the export template as is. A price of 1200 in hryvnias goes to Zalando Germany as 1200 euros. If your catalog isn't in euros, set a price formula with the exchange rate and your markup in the export template (price in the export). Countries with different currencies need different export templates.

    The export updates only products linked to a Zalando EAN. The link is set by the catalog import or by publishing. Without the “Publish new products” checkbox, the export skips all other products without a log line.

    Code 104 isn't an error

    The log shows the run summary as “Zalando: prices and stock sent, accepted: N, waiting for EAN onboarding: K (errors: M)”. K is the products with code 104: the EAN hasn't completed onboarding on Zalando yet. Zalando applies the price once the product is approved, and Elbuz keeps sending it on every run.

    Errors count only rejected items. Each one is a separate red line “Zalando: prices - ‘name’ rejected, code …: reason” (for stock — “stocks”).

    Publishing products on Zalando

    With the “Publish new products” checkbox in the export template, Elbuz publishes products not yet linked to Zalando. Each needs an EAN barcode of at least 8 digits. Then there are two paths:

    What's on ZalandoWhat Elbuz doesLog line
    A product with this EAN already existsAdds your offer to the existing product and immediately sends price and stock“Zalando: offer ‘…’ attached to the Zalando product (EAN …)”
    No product, outline mappedSubmits a new product for Zalando review“Zalando: ‘…’ - new product submitted to Zalando review”
    No product, outline not mappedSkips the product“Zalando: ‘…’ - there is no Zalando product with this EAN and no Zalando outline is mapped for the category”

    New product: the outline and what goes into it

    An outline (silhouette) is the product type on Zalando: dress, sneakers, bag. You map it to your category in the “Marketplace mapping” window: select the “Zalando” chip, click “Load marketplace dictionary” to pull your account's list of outlines, and fill in the “Zalando silhouette” column. Details: mapping categories to marketplaces.

    Marketplace category matching window with the Zalando chip selected and the Zalando silhouette columns in the category table
    1Zalando chip
    2Zalando silhouette column
    1. The Zalando chip switches the table columns to this marketplace.
    2. The Zalando silhouette column holds the silhouette under which Elbuz submits a new product card.

    Elbuz puts the product name, the manufacturer as the brand, the full description and up to 12 photos into the new product. Limits of a new product:

    • No variants. One Elbuz product is one Zalando product with one color and one size. Sizes of the same style become separate products.
    • Required outline attributes — size chart, size code, color, season, target audience — are mapped in the category mapping window. Color and season are matched by name in the Zalando dictionary; size chart and size code are sent as you entered them. Without a required attribute the product isn't submitted: “Zalando: "…" (outline …) — required attributes are empty: …”. “Publish readiness” shows unmapped attributes.
    • The brand is matched by the manufacturer name in the Zalando dictionary. No such brand — the product isn't submitted, and the log names the missing brand.

    A “sent” response means only the initial check passed. Zalando gives its final verdict within minutes or hours. Later exports check the result themselves and, until approval, send price and stock with code 104.

    The log shows a rejected product as “Zalando: ‘…’ - the new product was rejected by Zalando: reason”. The export skips that product from then on. Fix it in Elbuz: after any change to the product card, the next export submits it again.

    Scheduled updates

    Zalando 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.

    Zalando limits request frequency: orders — 40 per minute, prices — 30, stock — 60. When refused because of the limit, Elbuz waits as long as the marketplace says (up to a minute) and retries up to four times.

    General rules for break-offs and retries: if a run breaks off. The catalog is written in batches of 500 products, and orders in one pass after all pages are read, so a retry is safe.

    Scenarios

    You sell only on Zalando and want to see stock in Elbuz

    What to turn on. Fill in “Client ID”, “Client secret” and “Sales countries”; in the “Select data to import” card, check “Products” and “Orders”.

    What you get. Each EAN becomes a “Zalando ‹EAN›” card with the first country's price and stock in the “Zalando” category. Add names, photos and descriptions yourself — later runs won't erase them.

    You maintain the catalog in Elbuz, and Zalando is one of your channels

    What to turn on. In the import template — only “Orders”. In the export template — the countries in the “API version (marketplace parameters)” field, a price formula in euros and the “Publish new products” checkbox.

    What you get. Products that already exist on Zalando get your offer and an EAN link, with no duplicates in the catalog. The rest go for review as new products, provided their category has a mapped outline.

    You sell in Germany and Poland

    What to turn on. Two export templates with the same keys: the first with de,at and a price in euros, the second with pl and a price in zlotys.

    What you get. Each country gets the price in its own currency; stock is the same, from the catalog.

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

    Troubleshooting common problems
    What you seeWhyWhat to do
    “Zalando: API error - HTTP 401 (auth): …”, or “Test connection” doesn't show the Merchant ID The key wasn't copied in full, or the application was revoked in zDirect Paste the Client ID and Client secret again (what you need from Zalando)
    “Zalando: provide the Client ID and Client secret of the zDirect application” The key fields in the template are empty Fill in both fields and save the template
    “… HTTP 429: rate limit” The request limit is still exhausted after four retries For the orders pass, increase the interval of the “Marketplace orders” task; for the catalog, run it less often; a retry is safe (schedule)
    “Zalando: the merchant has no sales channels for countries … - check the country codes in the marketplace parameters” The countries field has a code where you don't sell on Zalando, or a typo in a code Correct “API version (marketplace parameters)”, for example de,at
    “waiting for EAN onboarding: K” with K above zero The product isn't approved by Zalando yet — this isn't an error Nothing: the price applies after approval (code 104)
    Red lines “Zalando: prices - ‘…’ rejected, code …” Zalando didn't accept some items; the reason is at the end of the line Fix the price or stock in the catalog and run the export again
    “Zalando: ‘…’ - no EAN barcode, publishing to Zalando is not possible” Offers and products on Zalando are tied to the EAN Fill in a barcode of 8 or more digits in the product
    “… no Zalando outline is mapped for the category” There's no Zalando product with this EAN, and nothing to submit a new one with Map an outline to the category (new product)
    “Zalando: publish error [name] HTTP 400: …” on every run Zalando rejected the product for a reason other than empty required attributes; the reason is in the error text Fix what the error says, or create the product in zDirect — the next export finds it by EAN and adds your offer
    “Zalando 4006…” cards appeared in the catalog next to your own The catalog import didn't recognize products without an EAN link Turn off “Products”, delete the extra cards, and link your own through the export (scenario)

    FAQ

    Can I sign up on Zalando myself?

    No. Zalando accepts partners by invitation only. API keys become available after you sign the agreement (what you need from Zalando).

    Why are products from Zalando named “Zalando 4006…”?

    The Zalando API doesn't return names, only the EAN and offer figures. Rename the cards in Elbuz — a repeat run won't change the name (repeat run).

    Can I publish a dress in several sizes as one product?

    No. Elbuz submits one product as a Zalando product with one size. Create a product with a size chart in zDirect, and Elbuz will add offers to it by EAN (new product).

    What does code 104 mean?

    The EAN is still going through onboarding on Zalando. This isn't an error: the price applies once the product is approved (code 104).

    Does Elbuz send the tracking number to Zalando?

    No. Mark shipments in zDirect, and Elbuz picks up the new order status on the next run (orders).

    Why is the price on Zalando dozens of times higher?

    The price went out in hryvnias, and Zalando read it in euros: Elbuz doesn't convert currencies. Set a price formula in the export template (export).

    Where it is and who has access

    Menu
    Directories → Operations → Data import → new template of type “Zalando”
    Other entry points
    Directories → Operations → Data export — a template for prices, stock and publishing
    Access right
    the “Import” window in “Group permissions”
    Have ready
    the Client ID and Client secret of an application from the zDirect Partner Portal

    One template covers one Zalando merchant, but any number of countries: list them in the “Sales countries” field.

    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