How to Sync Dolibarr with Cdiscount: A Complete Integration Guide

The pain: double data entry on Cdiscount

You sell on Cdiscount. Your ERP is Dolibarr. Between the two, the same ritual repeats every day: you change a price in Dolibarr, then open the Cdiscount seller back office to copy the change offer by offer. An order comes in on Cdiscount, you re-key it into Dolibarr. You create the invoice by hand. You go back to Cdiscount to mark the order shipped and enter the tracking number.

Cdiscount adds a wrinkle the other marketplaces don't have: a mandatory eco-tax. Every offer must carry an eco-participation contribution (EcoTax) and, for electrical and electronic goods, a WEEE levy (DeaTax). Managing those amounts offer by offer, on top of price and stock, multiplies the chances of a mistake.

This process eats hours every week. Errors pile up: a mistyped price, a forgotten eco-tax, an order never imported, a transposed tracking number. The bigger your catalog gets, the worse it scales. At 50 products it's tedious. At 500 it's a full-time job.

The real cost isn't just the lost time — it's the risk. A wrong price on Cdiscount for 24 hours can generate loss-making orders. A bad eco-tax value can get your offer rejected. A forgotten invoice throws off your accounting. ERPkit removes this double entry: Dolibarr becomes the single source of truth, and the sync runs itself.

What makes Cdiscount different from the other marketplaces

If you've already integrated Shopify, WooCommerce or PrestaShop with Dolibarr, three things set Cdiscount apart:

Cdiscount runs on the Octopia platform. Cdiscount is operated technically by the Octopia platform, so ERPkit talks to Octopia's Seller API. On ERPkit's side the authentication is distinctive: ERPkit uses its own platform credentials (a Client ID and Secret held on its infrastructure, shared across all sellers), and it acts on your behalf using your Octopia Seller ID. In practice you enter no API key and no secret — just your Seller ID, in the Dolibarr module. That's different from eBay (which uses an OAuth sign-in) and from Shopify/WooCommerce (which ask for your own API key).

Eco-tax is mandatory on every offer. This is the only ERPkit marketplace where every offer carries two tax lines on top of VAT: EcoTax (eco-participation, packaging and recycling) and DeaTax (the French WEEE levy for electrical and electronic equipment). ERPkit reads those amounts from two dedicated extrafields on the Dolibarr product — erpkit_ecotax_fr and erpkit_deatax_fr — and sends them on every sync. The key thing to watch: an empty field syncs as 0, and 0 overwrites the Cdiscount value. ERPkit keeps a reminder about this on the sync page, which you can collapse but never lose. Set these fields before you sync. If you already track eco-tax in your own Dolibarr field, you can map it from the Pricing > Eco-tax fields tab.

Offer writes are asynchronous. Unlike the marketplaces that apply each update at once, Cdiscount works through offer packages. On each cycle, ERPkit creates a package, uploads your changed offers into it (price, VAT, EcoTax, DeaTax, stock), submits the package, then polls Octopia until the package reaches the Integrated state. ERPkit then reads the per-offer results. It's a little slower than those, but the progress bar shows you where it is, and if a package doesn't integrate within the bound, the affected offers are simply retried next cycle, so no data is lost.

The sync key is your product reference. For Cdiscount, ERPkit matches your Dolibarr product reference (ref) to Octopia's sellerProductId. Keep them identical: that's what lets ERPkit reconcile offer results (Phase 1) and link imported order lines to your products (Phase 2). The offer link itself goes in the cdiscount_variant_id field.

Setting up ERPkit in 6 steps

Step 1: Authorize ERPkit against your Octopia seller account

Cdiscount/Octopia uses a platform model: ERPkit authenticates with its own Octopia credentials and acts on your behalf via your Seller ID. You don't create any key: you give ERPkit's app access to your seller account, once. Open Octopia's API Credentials Management page and sign in, choose I'm using a feed aggregator, then My aggregator is not on this list and My aggregator provided me its clientId. Paste ERPkit's client ID, ERPkit-Octopia, accept the Terms & Conditions and confirm with your Octopia login. Note the Seller ID shown on the confirmation screen: you need it in Step 3. Details: Setting up Cdiscount.

Step 2: Create a free ERPkit account

Head to app.erpkit.app and create your account. In the ERPkit plugin catalog, open the Cdiscount France card and subscribe to the plan you need. The free Solo plan is available for Cdiscount too.

Step 3: Install the free Dolibarr module and enter your Seller ID

On the ERPkit Marketplace Sync page, click Download Dolibarr Module (free, open source GPL v3). In Dolibarr, go to Home > Setup > Modules/Applications, upload the ZIP and enable the ERPkit module (install guide).

Open the ERPkit setup page, pick Cdiscount in + Add Marketplace, enter your Seller ID and click Save. The module then creates the fields on your product forms: cdiscount_variant_id, cdiscount_price, cdiscount_compare_price, plus the two eco-tax fields erpkit_ecotax_fr and erpkit_deatax_fr. On the Dolibarr side you store only your Seller ID — no secret.

Step 4: Create the Cdiscount sync config

Back in ERPkit, click Create Sync Config and enter your Dolibarr base URL and API key (on ERPkit's side this is exactly the same process as the other marketplaces). There's no Connect button: Cdiscount uses platform credentials plus your Seller ID (entered in Step 3), so once the Dolibarr connection tests green, you're connected.

Step 5: Link your products and set the eco-tax

On each Dolibarr product you want to sync, fill in the cdiscount_variant_id field (the Octopia offer identifier) and the cdiscount_price field (the price to publish). Make sure the Dolibarr reference (ref) matches Octopia's sellerProductId. Finally — the step unique to Cdiscount — set the eco-tax: erpkit_ecotax_fr (EcoTax) and, where applicable, erpkit_deatax_fr (DeaTax). Remember an empty field means 0 and overwrites the Cdiscount value.

Step 6: Run your first sync

You're ready. From your sync config detail page, run the sync. ERPkit creates an offer package, uploads your changed products (price, VAT, EcoTax, DeaTax, stock), submits the package and polls Octopia until it integrates. Only changed products are sent thanks to smart delta sync. The progress bar shows you where it is, and the sync log sorts each result into three buckets: offer integrated (success), offer rejected for a product-fixable reason (a warning, for example eco-tax codes 1008/1031), or a system error (retried automatically).

What's next?

Once product sync is in place, ERPkit also handles:

• Cdiscount order import — Paid Cdiscount orders flow automatically into Dolibarr, with customer matching by email and product linking by reference. You choose, from the Order Statuses tab, which Octopia statuses (Accepted, InPreparation, Shipped, Delivered, etc.) get imported.
• Invoice generation — Dolibarr invoices are created, validated, and marked paid automatically from the imported orders.
• Fulfillment — When you validate a shipment in Dolibarr, ERPkit sends the status and tracking number to Cdiscount. A carrier suggestion list (Colissimo, Chronopost, Mondial Relay, etc.) is offered in the Carrier Mapping tab.
• Factur-X — Generate compliant electronic invoices (PDF/A-3 with embedded CII XML) to get ahead of the EU e-invoicing rules.

Important: ERPkit only sends price, VAT, eco-tax (EcoTax/DeaTax) and stock to Cdiscount. The titles, descriptions, photos, attributes and categories of your offers are never modified. ERPkit doesn't create offers: they must already exist on Cdiscount, and you link them via the cdiscount_variant_id field.