Elbuz connects to your Cdiscount (France) seller account with three Octopia values: it imports offers, accepts orders, and returns prices and stock.
When you need this:
- You sell on Cdiscount and elsewhere: all channels' stock and orders in one catalog.
- Orders must be accepted in time: Elbuz accepts them during the import.
- You set prices in Elbuz: the export sends them in packages, logging each rejection's reason.
- You list new products: an EAN product becomes an offer on an existing or new product page.
Where to start: create a Client ID and Client secret in the Seller Portal and paste them with the Seller ID into a “Cdiscount” template.
What the Cdiscount connection can do
- Connects with seller keys: no app registration and no review by Octopia.
- Imports offers with the name, description, brand, , price, stock, category, and photos from the Cdiscount product page.
- Orders: 30 days of history on the first run, then only changes; Elbuz accepts orders that are waiting for acceptance on its own.
- Prices and stock back to Cdiscount: in Octopia packages, with the reason for each rejection in the log.
- Publishing new products: an offer by EAN on an existing product page, or a new product page under the mapped category.
Where to get the keys in the Seller Portal
Cdiscount's technical side is run by Octopia: the seller account, the , and the documentation are all on its side. You don't need to register an app: sellers create the keys themselves.
- Sign in to the Octopia Seller Portal and open the API Credentials Management page.
- Click “Create my clientId and clientSecret”.
- Copy the clientId, clientSecret, and sellerId shown.
The key pair gives access to all data of the seller account. Don't send it as plain text and don't paste it into other people's templates.
The import template has five fields; the first three are required:
| Template field | What to enter |
|---|---|
| Client ID | clientId from the Seller Portal |
| Client secret | clientSecret; after saving, the field appears empty |
| Seller ID (Octopia seller identifier) | sellerId; without it, Octopia doesn't know whose data to return |
| Sales channel | An empty field means CDISFR, Cdiscount France. Enter another code only if you're connected to a different Octopia channel |
| Delivery modes for new offers | code:price, comma separated, for example THD:4.99,EHD:9.99. Needed only for publishing; prices and stock update without them |
Delivery codes come from the Octopia reference list: THD is tracked, EHD express, SHD signed for, NTHD untracked, PPMR and PPLP are Mondial Relay and La Poste pickup points. A third number after a colon is the surcharge for each additional item: THD:4.99:1.
Once the keys are in, save the template and click “Test connection”. Elbuz gets a token and requests the seller details; the response shows the shop name and channel, for example “Cdiscount — ‹shop› (CDISFR)”. This confirms that the keys were copied in full and that the Seller ID belongs to these keys.
“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 and accepting those awaiting acceptance. 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”.
1
Client ID2
Client secret3
Seller ID4
Delivery modes for new offers- Client ID — the public half of the API key from Seller Portal.
- Client secret — the secret half; it is not shown again after saving.
- Seller ID — your seller account number, sent with every request.
- Delivery modes for new offers — without them new offers are not published.
Octopia's instructions for sellers: Getting started and API key management.
What goes into the product card
On Cdiscount, the marketplace manages the product page, and the seller lists their offer on it: a price and stock. Elbuz pulls the list of your offers on the channel and requests the product page for each one by EAN, so a full product lands in the catalog, not just a line with a price.
| Cdiscount data | Product field in Elbuz |
|---|---|
| product page name | Name (in French, the marketplace language) |
| product page description | Description |
| brand | Manufacturer |
| your offer reference (sellerExternalReference) | SKU |
| product page EAN | Barcode |
| offer price | Price |
| price before discount, if higher than the current one | Old price |
| total stock across all delivery modes | Quantity |
| offer state: active means yes, anything else means no | The “enabled” flag |
| product page category | Category (as a single name) |
| product page photos | Photos, if the “Photo” checkbox is selected |
Specifications don't come from Cdiscount. If the marketplace product page couldn't be retrieved and the offer is new, the product is saved with the name #‹EAN›: rename it or run the import again later.
The category arrives as a name, without a tree. If you don't have such a category, Elbuz creates it. Offers without a category go into the service category “Products - cdiscount”: it's created disabled and excluded from exports. How to handle it: service categories and brands.
What a repeat run overwrites
A repeat import looks for your product first by the offer link: the reference stored by any Cdiscount template, including the export template that published the offer. If nothing is found, it searches by name. So renaming a product page on the marketplace doesn't create a duplicate.
| What the run does | Fields |
|---|---|
| Overwrites with Cdiscount data | name, description, manufacturer, SKU, barcode, price, old price |
| Always overwrites, even with zero | quantity and the “enabled” flag |
| Doesn't overwrite with blanks | a field Cdiscount sent nothing for keeps your value |
The Cdiscount template has no separate “don't update the name” switch. If you don't need the marketplace's French names, import the catalog once to set up the links, then leave only “Orders” in the template (scenario). You can lock individual cards in the product card itself, in the “Import protection” section:
- “Do not update”: the run doesn't touch the card at all;
- “Fixed Price”: the run doesn't rewrite prices but updates the other fields.
The import doesn't touch an offer that wasn't in the run: the product keeps its last price and stock. Remove discontinued items manually. More: two templates for the same product.
How orders arrive and get accepted
With the “Orders” checkbox, every 5 minutes Elbuz pulls the channel's orders changed since the last time (schedule). The first run takes 30 days of history; later runs start from the date in the “Import orders from date (YYYY-MM-DD)” field of the “Advanced” block, with a twelve-hour margin. Existing orders are recognized by number and updated, not duplicated.
Automatic acceptance
Orders with the status “awaiting acceptance” (WaitingAcceptance) are accepted on Cdiscount by Elbuz itself, before they're saved to the catalog. The marketplace cancels orders that aren't accepted in time, so this way you won't lose one. The document is saved straight away with the status “accepted” (Accepted).
If Octopia didn't accept the request, a red line “Cdiscount: API error — … (approval-status ‹number›)” appears in the log, and the order is imported with the status “awaiting acceptance”. Accept it in the Seller Portal before the marketplace cancels it.
The seller is obliged to fulfill an accepted order. If the product isn't actually available, cancel the order in the Seller Portal and make sure your Cdiscount stock matches the real stock (export).
What goes into the document
- order number, purchase and last change dates, Cdiscount status;
- recipient's first name, last name, phone, and email, delivery address;
- payer and their address, payment method, delivery method, and delivery cost;
- line items: SKU (your offer reference), EAN, name, price, quantity; currency.
The status arrives as a Cdiscount code, and Elbuz maps it to yours by name; to fine-tune, use the “Order statuses” button in the “Related settings” card. How a repeat run treats a document a manager is already working on, and why a posted document doesn't change: who overwrites an order.
Shipments with a tracking number are sent by the export with the “Orders” checkbox: see shipments.
How prices and stock go back to Cdiscount
The reverse direction is a separate export template of type “Cdiscount”. It uses the same Client ID and Client secret, and the “API version (marketplace parameters)” field contains Seller ID|channel|delivery modes, for example 98979|CDISFR|THD:4.99,EHD:9.99. Elbuz takes any empty parts from the Cdiscount import template with the same Client ID.
1
Client ID2
Client secret3
API version (marketplace parameters)- Client ID — the same key as in the import template.
- Client secret — the secret half of the API key.
- API version (marketplace parameters) — Seller ID, channel and delivery modes separated by “|”.
Only products linked to offers are updated, so import the catalog from Cdiscount once first. What goes to the marketplace:
- Price: the number from the catalog, with no currency conversion. The marketplace expects euros including VAT (channel CDISFR). If your catalog is in hryvnias, UAH 1,200 goes to Cdiscount as €1,200, so before the first export make sure the prices in the template's filtered set are in euros.
- Stock: the product quantity, no less than zero; shared across all sales channels of your Octopia account.
- Which products: set by the export template's filter, as for other channels.
Why the result doesn't come right away
Octopia accepts changes not one offer at a time but in a package: Elbuz creates a package, fills it, sends it, and waits about a minute for processing. The marketplace processes a package in anything from a few seconds to tens of minutes.
| What the log says | What it means |
|---|---|
| “Cdiscount: package ‹id› submitted for processing, requests: N” | The package went to the marketplace |
| “Cdiscount: package ‹id› is still processing (state …), the result will be fetched on the next run” | A minute wasn't enough. The next run first fetches this package's result |
| “Cdiscount: package ‹id› processed, accepted: N (rejected: M)” | The result of a package from the previous run |
| “Cdiscount: “name” (reference) — rejected: reason” | Octopia rejected a specific offer; the reason is the marketplace's text |
| “Cdiscount: package ‹id› is no longer available (6-hour lifetime expired)…” | The package lived on the marketplace for 6 hours and is gone. The data will go with the next package |
The summary line “Cdiscount: prices and stock updated, offers: N (errors: M)” counts only offers whose result has already arrived. A zero there right after a package is sent isn't a failure, just waiting.
Elbuz can't remove offers: a product that drops out of the export's filtered set simply stops being updated. To stop selling, export zero stock or remove the offer in the Seller Portal.
Publishing new products
With the “Publish new products” checkbox in the export template, Elbuz lists products that don't have an offer on Cdiscount yet. For each one, it looks for a marketplace product page by EAN:
| Situation | What Elbuz does |
|---|---|
| A product page with this EAN exists in the Cdiscount catalog | Creates your offer on it: price including VAT, stock, delivery modes, 2 days of preparation |
| No product page, Cdiscount category mapped | Submits a new product page for Octopia review; the offer appears once it's approved |
| No product page, category not mapped | Skips the product with a line in the log |
| No EAN of 8 digits or more | Skips the product with a line in the log |
The offer takes the VAT rate from the product's tax class; without a class, 20%. The condition (new, used, refurbished) comes from the product condition field; if it's empty, “new”. The offer reference is the product SKU, or the product ID in Elbuz if there's no SKU.
New product page: what's sent and what's missing
Choose a Cdiscount category for your categories in the “Marketplace Category and Attribute Mapping” window, “Cdiscount” toggle. The category list is loaded by the “Load marketplace dictionary” button using the Cdiscount import template's keys. More: mapping categories to marketplaces.
1
Cdiscount chip2
Load marketplace dictionary3
Cdiscount category column- Cdiscount chip — shows this marketplace's columns in the table.
- Load marketplace dictionary — pulls the Cdiscount category tree using the import template keys.
- Cdiscount category column — pick the category for new product cards here.
A new product page gets the name (up to 132 characters), the description without markup (up to 5,000), the manufacturer as the brand, up to 6 photos, and the mapped category code. Each product is a separate product page: Elbuz doesn't combine variants into one page.
The name and description are taken in the language set in the export template's “Description language” field; for Cdiscount, choose French. Without a translation, the main language is used.
Map the category properties (color, size, material, etc.) in the same window: on the Cdiscount tab, click the category row, and in the “Cdiscount attribute” column below choose marketplace properties for your specifications (required attributes). Values come from your specifications; a property with a list of values accepts only an option Cdiscount offers.
If a required property isn't mapped, the product page isn't sent: the log shows “Cdiscount: “‹name›” — mandatory category properties are empty: ‹list›”. Octopia may still reject the page; then the log shows “Cdiscount: product card “…” (EAN …) refused: ‹field›: ‹reason›”.
An approved page shows in the log as “Cdiscount: product card “…” (EAN …) added to the catalog, publishing the offer”, and in the same run Elbuz sends the offer to it. A published offer is marked by the line “Cdiscount: product “…” published (reference …)”.
How to send shipments to Cdiscount
The “Orders” checkbox in the export template marks an order as shipped on Cdiscount. It works when the document has both:
- your status mapped to the code
Shippedin the “Order statuses” window of the import template; - a tracking number in the “Delivery service: number” field of the “Delivery” card (expand “More fields”).
Carrier: a name from the Cdiscount carrier list, mapped to a delivery service with the “Delivery types” button of the import template. Without a mapping, Elbuz sends the delivery service name from the document.
The event is sent once; orders already shipped, delivered, cancelled, or refused on Cdiscount aren't sent. The log shows “Cdiscount: order ‹number› shipped, parcel ‹tracking number›” and the summary “Cdiscount: shipments sent: N, errors: M”. No tracking number means a red line “Cdiscount: order ‹number› has no tracking number, shipment not sent”.
Scheduled updates and the request quota
Cdiscount sends no instant notifications, so Elbuz pulls and accepts orders 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 template form. Run it rarely, at night for example: while the catalog is loading, the orders pass is skipped until the next one. Export packages need time, so exporting more often than every 15–20 minutes is pointless.
1
Order statuses2
Schedule setup- Order statuses — maps Cdiscount statuses to your own.
- Schedule setup — how often the import runs.
Octopia limits requests per hour. At the limit, Elbuz waits and retries up to three times. If that fails, the log shows “Cdiscount: Octopia request quota exceeded, try again later”. It's not a key error: the run just waits for the next hour. The catalog import uses the most requests: one per offer's product page.
The “Active” / “Disabled” badge takes the template off the schedule and out of automatic order pulling (disable a template). The price export is a separate template with its own switch.
If a run breaks off
- Catalog: written in batches of 500 offers; whatever was saved is updated, the rest keeps the old data.
- Orders: saved in one go after all pages are read; the date for the next portion moves only after saving, so a retry pulls the same period. Orders already accepted on the marketplace aren't accepted again: they're no longer awaiting acceptance.
- Export: Octopia processes a sent package without Elbuz, and the next run fetches the result.
A retry is safe. General rules: if a run breaks off.
Scenarios
1
Products2
Photos3
Orders- Products — the catalog of Cdiscount offers.
- Photos — the images of product cards.
- Orders — orders from the marketplace.
Move your Cdiscount catalog into Elbuz
What to turn on. Fill in “Client ID”, “Client secret”, and “Seller ID”; in the “Select data to import” card, select “Products”, and also “Photo” for images.
What you get. Each offer on the channel becomes a card with a French name, description, brand, barcode, price, stock, and a single-name category. Your offer reference becomes the SKU, and the export later matches by it.
Accept orders and never miss a deadline
What to turn on. The “Orders” checkbox; Elbuz maps the statuses itself, and the “Order statuses” button is there for fine-tuning. Orders don't need a template schedule: they arrive by themselves every 5 minutes.
What you get. New orders are accepted on the marketplace automatically and saved as documents with the status “accepted”. An acceptance error line in the log is your signal to accept the order manually in the Seller Portal.
Cdiscount as a channel for a catalog you manage in Elbuz
What to turn on. Run the import once with the “Products” checkbox to link cards to offers. After that, leave only “Orders”, or the catalog run will overwrite names, prices, and stock with Cdiscount data. Prices are sent by the export template, in euros, with no conversion.
What you get. Linked products get their price and stock in packages; with “Publish new products”, the rest of the products with an EAN are listed on existing product pages, or as new product pages for mapped categories.
What to do when Cdiscount won't send or accept data
| What you see | Why | What to do |
|---|---|---|
| “Cdiscount: enter Client ID, Client secret and Seller ID from the Octopia seller account” | One of the three fields is empty | Fill in all three and save the template (keys) |
| “Cdiscount: API error — auth HTTP …” | Octopia didn't issue a token: the key wasn't copied in full or was revoked | Create the keys again in API Credentials Management and paste both in again |
| “Cdiscount: API error — HTTP 403: …” with no mention of a limit | The Seller ID doesn't belong to these keys, or the keys have no access to the channel | Check the Seller ID and sales channel against the Seller Portal, then click “Test connection” |
| “Cdiscount: Octopia request quota exceeded, try again later” | The hourly quota is used up and retries didn't help | The quota recovers within an hour. In the orders pass, increase the interval of the “Marketplace orders” task; for the catalog, run it less often (quota) |
| “Cdiscount: package … is still processing” | Octopia didn't manage to process the package within a minute | Wait for the next run: it will fetch the result (packages) |
| “Cdiscount: “…” (…) — rejected: …”, a summary with non-zero errors | The marketplace rejected some offers; the reason follows the colon | Fix the price or stock in the catalog and wait for the next export |
| “Cdiscount: delivery modes for new offers are not set — publishing is impossible” | An offer can't be created without delivery modes | Enter them in the import template or as the third part of “API version”, for example THD:4.99 |
| “Cdiscount: “…” — no EAN barcode, cannot publish on Cdiscount” | An offer attaches to a product page by EAN | Fill in a barcode of 8 digits or more in the product |
| “…no product with EAN … in the Cdiscount catalog, and the Cdiscount category is not mapped” | A new product page needs a marketplace category | Map the category in the mapping window, “Cdiscount” toggle (new product page) |
| “Cdiscount: product card “…” (EAN …) refused: …” | A category property isn't mapped, or its value doesn't suit Cdiscount | Map the properties on the Cdiscount tab (required attributes) or create the product page in the Seller Portal; Elbuz links the offer by EAN on its own |
| “Cdiscount: API error — … (approval-status …)” | The marketplace didn't accept the order acceptance request | Accept the order manually in the Seller Portal before it's cancelled |
| Products in the “Products - cdiscount” category aren't exported | The service category is created disabled | Move the products to your own categories (catalog) |
FAQ
My catalog prices are in hryvnias. What goes to Cdiscount?
The same number, with no conversion: UAH 1,200 becomes €1,200. Product prices for Cdiscount must be in euros (export).
Why are product names in French?
Elbuz takes the name from the Cdiscount product page, and the marketplace keeps its pages in French. After the first import, leave only “Orders” or lock the cards with “Do not update” (repeat run).
Can I turn off automatic order acceptance?
No, the Cdiscount order import always accepts orders that are awaiting acceptance. If you don't want that, clear the “Orders” checkbox and accept orders in the Seller Portal (acceptance).
Does Elbuz send the tracking number to Cdiscount?
Yes: the export with the “Orders” checkbox sends the status mapped to Shipped and the tracking number from the document (shipments).
Why does Octopia reject new product pages?
Most often because a category property isn't mapped or is filled in incorrectly. The reason is in the export log; properties are mapped on the Cdiscount tab of the category mapping window (new product page).
I changed the price, but Cdiscount still shows the old one. Why?
The package is still being processed or is waiting for the next run. Check the log line about the package state (packages).
Where to find it and who has access
- Menu
- Directories → Operations → Data import → new template of type “Cdiscount”
- Other entry points
- Directories → Operations → Data export: a template for prices, stock, and publishing
- Access right
- the “Import” window in “Group permissions”
- Have ready
- Client ID, Client secret, and Seller ID from the Octopia Seller Portal
Only legal entities with a French SIRET or a European VAT number can sell on Cdiscount. One template = one seller account and one sales channel.
Related topics
- If you need the general import mechanics (schedule, breaks, service categories), see the data import overview.
- If a manager works on orders in Elbuz and it matters what a run overwrites, see importing orders via API.
- If new product pages are missing marketplace categories, see mapping categories to marketplaces.
- If you also sell on Kaufland, see connecting Kaufland.
