Elbuz connects to your OTTO Market (otto.de) shop with your own OTTO Partner Connect app: it imports products, orders and returns, and sends back listings, prices, stock and shipments.
When you need this:
- Your catalog lives in Elbuz — new products go to OTTO as full listings with category, brand and required attributes.
- You ship from your warehouse — your status sends OTTO the tracking number, plus the return number for parcels.
- Customers return items — a return arrives as a document; you send your decision as a status.
Where to start: create an app in OTTO Partner Connect and paste its keys into an “OTTO” import template.
What the OTTO connection can do
- Connection with your own app — Client ID and Client Secret, no intermediaries.
- Product import — name, brand, description, barcode, price, stock, category and photos.
- Orders — with the address, delivery and discounted prices.
- Prices and stock — back to OTTO, with the result in the log.
- New listings — with an OTTO category, brand, mandatory attributes and GPSR data.
- Shipments and cancellations — through your order status.
- Returns — as a “Customer return” document; acceptance or rejection is sent as a status.
What to get in OTTO Partner Connect
Elbuz works with OTTO through your own app. Create it in OTTO Partner Connect, in the API-Zugriff section, and give it these scopes:
| Scope | What Elbuz uses it for |
|---|---|
products | products, prices, new listings, categories and brands |
orders | orders and cancellations |
shipments | shipments with a tracking number |
availability | stock, shipping profile and processing time of new listings |
returns | customer returns |
shipping-profiles | the product's delivery type: parcel or freight |
An app without returns or shipping-profiles still works, but returns aren't imported and parcel shipments aren't sent.
1
App Client ID2
App Client Secret3
Sandbox4
Shipping profile ID5
Order processing time- App Client ID — from OTTO Partner Connect, the API-Zugriff section.
- App Client Secret — the secret of the same app.
- Sandbox — 1 for the OTTO test environment, empty for the live account.
- Shipping profile ID — without it new listings cannot be ordered.
- Order processing time — 1 to 99 days; empty — as in the profile.
| Template field | What to enter |
|---|---|
| App Client ID, App Client Secret | The app keys from API-Zugriff. Required |
| Sandbox | 1 — work with the OTTO test environment; empty — with your live account |
| Shipping profile ID (for new listings) | A shipping profile from your OTTO account. Without it, new listings can't be ordered |
| Order processing time, days | From 1 to 99. Empty — as in the shipping profile |
After pasting the keys, wait for “All changes saved” and click “Test connection”. The reply “Connection works. OTTO Market” (marked “sandbox” for the sandbox) means the keys are correct.
“Active” and “Orders” are already on in a new template: within 5 minutes of saving the keys, Elbuz starts pulling orders for the last 30 days. Elbuz maps marketplace statuses to yours by name; what arrived and how it was mapped is shown in the template's “Order statuses” window. Want to check first? Clear “Orders”.
Description of the interfaces Elbuz uses: OTTO Market API.
What goes into the product card
Elbuz imports your products on OTTO together with stock and brand names, and puts each variation into the base catalog as a product card.
| OTTO data | Product field in Elbuz |
|---|---|
| name (productLine), otherwise the SKU | Name |
| description | Description |
| brand | Manufacturer |
| variation SKU | SKU |
| EAN | Barcode |
| price | Price |
| stock | Quantity |
| OTTO category | Category — found by name or created |
| photos | Photos |
A repeat import finds the card by its SKU link. To keep a run from touching the card at all, turn on the “Do not update” toggle in it (“Import protection” section); to protect only prices, use “Fixed Price”.
How orders arrive
An order lands as a “Customer order” document, unposted. The first import takes orders from the last 30 days, later ones take orders changed since the last import, with a 12-hour margin. An existing order is recognized by its number and updated.
You don't need to accept orders on OTTO: the marketplace hands them to the seller ready for processing. For roughly the first half hour, a new order is in the “announced” state with no address — Elbuz skips it and picks it up on a later run, once the address appears.
- Items. OTTO counts each unit as a separate item; Elbuz merges identical products with the same price into one line with a quantity.
- Price — including VAT, already discounted.
- Delivery — the order's delivery charge; the document total is items plus delivery.
- Canceled items don't go into the document if the order has other items.
Order statuses
Elbuz maps the marketplace status to yours by itself, by code or name; an unrecognized one comes in as “New”. To fine-tune, use the “Order statuses” button in the “Related settings” card of the import template: enter the OTTO code in the “Code (name) on site (API)” column next to your status.
| OTTO code | What it means |
|---|---|
PROCESSABLE | Ready for processing — needs to be shipped |
SENT | Shipped |
RETURNED | Returned |
CANCELLED_BY_PARTNER | Canceled by you |
CANCELLED_BY_MARKETPLACE | Canceled by the marketplace |
A status mapped to SENT or CANCELLED_BY_PARTNER is sent to OTTO by the export (shipments). What happens to a posted order and its reservation is covered in importing orders via API.
How prices and stock go back to OTTO
Large volumes go in batches: up to 500 variations per price and data batch, up to 200 products per stock batch. Elbuz renews access on its own. A new listing's description is cut to 5,000 characters. The product's marketplace state is saved in the product link: PENDING, ONLINE, RESTRICTED, REJECTED, INACTIVE.
The reverse direction is a separate export template of the “OTTO” type. It has three fields:
- App Client ID and App Client Secret — the same as in the import template. The export takes the sandbox, shipping profile and processing time from there.
- API version (marketplace parameters) — the address you ship from:
country|postcode|city, for exampleDE|10115|Berlin. Without it, shipments aren't sent.
1
App Client ID2
App Client Secret3
Shipping address- App Client ID — the same as in the import template.
- App Client Secret — the same secret.
- API version (marketplace parameters) — the shipping address: country|postcode|city.
Products linked to OTTO listings are updated. The price goes in euros including VAT — Elbuz doesn't convert currency, so prices in the filtered set must be in euros. Stock is the product quantity, no less than zero.
Why the price doesn't update right away
OTTO accepts prices and new listings as a task and processes it on its side. Elbuz waits about a minute for the result. If it doesn't arrive, the log shows “OTTO: task ‹number› is still being processed, result — on the next run”, and the next run picks up the result. Stock is accepted immediately.
| What the log says | What it means |
|---|---|
| “OTTO: prices — succeeded: N, errors: M” | Run summary |
| “OTTO: “‹name›” (‹SKU›) rejected: ‹reason›” | The marketplace didn't accept the price or listing |
| “OTTO: product ‹SKU› rejected by the marketplace: ‹reason›” | The product is already on OTTO, but the marketplace took it off sale (REJECTED status) |
| “OTTO: ‹field› — ‹error›” | The marketplace didn't accept the stock of a specific product |
Schedule and request limit
OTTO doesn't send instant notifications, so Elbuz pulls orders and returns by itself every 5 minutes if “Orders” is selected in the template and the keys are filled in. This is done by the shared “Marketplace orders” task in the “Job schedule” window, where you can also change the interval. This pass doesn't load the catalog, and orders also picked up by the template's schedule aren't duplicated.
The catalog is updated by the template's own schedule: the “Schedule setup” button in the “Related settings” card. Run it rarely, at night for example: while the catalog is loading, the orders pass is skipped until the next one. Prices and stock go to OTTO with the export template on its own schedule, from several times a day to hourly.
OTTO limits request frequency. Elbuz keeps its pace below the limit, and when refused because of it, waits and retries. If that doesn't help, the log shows “OTTO: request limit exceeded, try again later”. A broken-off run is safe to repeat: if a run broke off.
New listings on OTTO
OTTO doesn't let you put an offer on someone else's listing: each seller describes the product themselves. So with the “Publish new products” checkbox, an unlinked product goes to OTTO as a full listing. Before sending, Elbuz checks that everything is there:
| What's needed | Where Elbuz takes it from |
|---|---|
| Barcode of 8 digits or more | the product's “Barcode” field |
| OTTO category | the product category, mapped to an OTTO category (the OTTO tab in the mapping window) |
| Brand from the OTTO list | the product manufacturer; the name must match a brand available to you on OTTO |
| At least one photo | product photos, up to 20 |
| Mandatory category attributes | product attributes with exactly the same name as on OTTO — usually in German |
The name (up to 100 characters) and description use the export template's “Description language” — choose German for OTTO. VAT comes from the product's tax class: up to 10% — reduced (7%), otherwise or with no class — standard (19%). The listing code is the product SKU; if it's missing or over 50 characters, the Elbuz product ID.
If something is missing, the listing isn't sent, and the log lists what: “OTTO: listing “‹name›” not sent — no images; mandatory OTTO category attributes are empty: ‹attributes›”. Elbuz doesn't invent values the product lacks: add attributes with the names from the list.
GPSR data
EU product safety rules require manufacturer data and an EU responsible person in the listing. Elbuz takes them from the “Product safety (GPSR) — eMAG, OTTO” window (a button in the OTTO or eMAG import template; shared details). The EU responsible person is the minimum. Without the data, the listing goes as is and OTTO decides — usually rejecting it.
What happens after sending
- The log shows “OTTO: listings sent: N, task ‹number›”. While OTTO processes the task, later runs skip these products: “OTTO: new listings are still being processed: N”.
- An accepted listing — “OTTO: listing “‹name›” (‹SKU›) accepted”, and the product is linked. Elbuz immediately sends its shipping profile and processing time from the import template.
- A rejected one — “OTTO: “‹name›” (‹SKU›) rejected: ‹reason›”, the link is removed, and the next run tries again.
If “Shipping profile ID” is empty in the import template, the listing appears on OTTO but can't be ordered. The log warns: “OTTO: the import template has no shipping profile ID — new listings will not be orderable”.
Shipments, return tracking number and cancellation
The “Orders” checkbox in the export template sends two events from your orders to OTTO:
| Your status is mapped to | What Elbuz sends |
|---|---|
SENT | Shipment of all items ready to ship, with the carrier and tracking number |
CANCELLED_BY_PARTNER | Order cancellation |
OTTO requires three things for a shipment; without any of them, the event isn't sent:
- Tracking number — the “Delivery service: number” field in the document's “Delivery” card (expand “More fields”).
- Carrier from the OTTO list — DHL, DPD, GLS, HERMES, UPS and others. Elbuz takes the code from the “Delivery types” button of the import template, or without mapping, the delivery service name from the document.
- Ship-from address — from the export template's “API version (marketplace parameters)” field.
Return tracking number for parcels
For products shipped as a parcel (a PARCEL shipping profile), OTTO accepts the shipment only with the number of the parcel the customer will use to return the item. Enter it in the “Return tracking number” field in the document's “Delivery” card, under “More fields”:
number— the return carrier is the same as for the shipment;GLS:number,DHL:numberorHERMES:number— a different return carrier.
OTTO accepts returns only via DHL, GLS and Hermes. For freight delivery, the field isn't needed.
1
Delivery service: number2
Return tracking number- Delivery service: number — the shipment tracking number.
- Return tracking number — the parcel number for a return; another carrier — with a prefix, e.g. GLS:…
Each event is sent once: after sending, Elbuz remembers the new marketplace status. The log shows lines “OTTO: order ‹number› → SENT” and the summary “OTTO: order statuses sent: N, errors: M”. A refusal shows as “OTTO: order ‹number› → SENT not sent — ‹reason›”.
Customer returns
Returns announced by the customer and returns delivered to the OTTO warehouse by mistake arrive with orders — as a “Customer return” document based on the order. Each returned item is a separate document: OTTO counts units separately.
The document has the product, price and customer from the order, plus the tracking number and carrier of the returned parcel. The document number is the order number with a -R… suffix. A repeat import updates the same document instead of creating a new one.
How to accept or reject a return
The decision is sent as the return document status, mapped in the “Order statuses” window of the import template. The export with the “Orders” checkbox sends it.
| What to enter in “Code (name) on site (API)” | What OTTO receives |
|---|---|
ACCEPTED | Return accepted |
ACCEPTED:reason or ACCEPTED:reason:condition | Accepted with a reason and item condition using OTTO codes |
REJECTED:reason | Return rejected, for example REJECTED:ITEM_DAMAGED or REJECTED:WRONG_ITEM |
A rejection reason is required. A status with a bare REJECTED isn't sent: the log shows “OTTO: return ‹number› not rejected — add a reason in the status mapping, e.g. REJECTED:ITEM_DAMAGED”. For returns, it's handy to create separate statuses “Return accepted” and “Return rejected (damaged)”.
Scenarios
List the catalog you manage in Elbuz on OTTO
What to turn on. Map your categories to OTTO categories (OTTO tab, “Load marketplace dictionary” button), fill in the GPSR data, and set the shipping profile ID in the import template. Add attributes named like the mandatory OTTO attributes to products. In the export template — German as the “Description language”, the “Products” and “Publish new products” checkboxes.
What you get. Products that have everything needed go to OTTO as listings; the rest get a list of what's missing in the log. Published listings then update price and stock on every run.
Ship OTTO orders from Elbuz
What to turn on. In the import template — the “Orders” checkbox, status mapping for sending to OTTO (SENT, CANCELLED_BY_PARTNER) and carrier codes via the “Delivery types” button. Orders need no schedule: they arrive by themselves every 5 minutes. In the export template — the ship-from address and the “Orders” checkbox.
What you get. A manager enters the tracking number and, for a parcel, the return tracking number, then sets the status mapped to SENT — the next export sends the shipment to OTTO.
What to do when OTTO rejects data
| What you see | Why | What to do |
|---|---|---|
| “OTTO: enter the app Client ID and Client Secret” | The keys in the template are empty | Paste the app keys (what to get in OTTO Partner Connect) |
| “…brand “‹name›” is not among the usable OTTO brands” | The product manufacturer doesn't match a brand available to you on OTTO | Fix the manufacturer name or request the brand in your OTTO account |
| “…mandatory OTTO category attributes are empty: …” | The product has no attributes with these names | Add attributes with the names from the list, exactly as on OTTO (new listings) |
| “…category is not mapped to an OTTO category” | The product category has no link to OTTO | Map it on the OTTO tab of the category mapping window |
| “…no tracking number (required)” | “Delivery service: number” is empty | Enter the tracking number in the document (shipments) |
| “…carrier “‹name›” is not in the OTTO list…” | The document's delivery service doesn't match an OTTO carrier code | Map the delivery service to an OTTO code with the “Delivery types” button of the import template |
| “…marketplace parameters lack the ship-from address “country|postcode|city”” | The address field in the export template is empty | Enter the address, for example DE|10115|Berlin (export) |
| “…OTTO requires a return tracking number for parcels (PARCEL)…” | The product ships as a parcel, but “Return tracking number” is empty | Fill in “Return tracking number” in the document delivery (return tracking number) |
| “…OTTO does not accept return carrier “‹name›”…” | OTTO accepts returns only via DHL, GLS and Hermes | Enter the number with a prefix: DHL:…, GLS:… or HERMES:… |
| “…no positions on the marketplace are ready to ship” | All items have already been shipped or canceled | Check the order in your OTTO account |
FAQ
Can I sell on someone else's OTTO listing, like on Amazon?
No, OTTO doesn't allow it: each seller describes the product themselves, so Elbuz sends a full listing (new listings).
An order is in my OTTO account but not in Elbuz — why?
For the first half hour, a new order has no address, and Elbuz skips it. The next import picks it up (orders).
My attributes are in Ukrainian — will they work for OTTO?
No, the attribute name must exactly match the OTTO attribute name, usually in German. Add attributes with those names (new listings).
How can I test everything first without real orders?
Enter 1 in the “Sandbox” field of the import template — Elbuz will work with the OTTO test environment (template fields).
A return arrived as several documents — is that a mistake?
No, OTTO counts each unit as a separate item, so each returned item gets its own document (returns).
Where to find it and who has access
- Menu
- Directories → Operations → Data import → new template of type “OTTO”
- Other entry points
- Directories → Operations → Data export — a template of the same type; categories — the marketplace category mapping window
- Access right
- the “Import” window in “Group permissions”
- Have ready
- an app in OTTO Partner Connect, a shipping profile ID
Related topics
- If products don't go to OTTO because of the category: mapping categories to marketplaces.
- If a manager handles orders in Elbuz and it matters what a run overwrites: importing orders via API.
- If you also sell on Kaufland or ManoMano: connecting Kaufland, connecting ManoMano.
