If Cdiscount is a core channel for your French store, you know the operational tax of running it beside Odoo: offers maintained by hand in the Seller Zone, prices and stock that drift the moment an order lands in another channel, and orders re-keyed into Odoo where late acknowledgements and missing tracking numbers erode your seller performance rating. Odoo's native Sales and Inventory apps manage everything downstream — confirmed sale orders, deliveries, invoicing — but they have no concept of a Cdiscount offer, no client for the Cdiscount (Octopia) Marketplace API, and no automated action to push a tracking number back to the marketplace. That gap is exactly where a purpose-built connector earns its keep.

ECOSIRE builds a dedicated Cdiscount connector as a proper Odoo module — a __manifest__.py declaring clean dependencies on sale_management, stock, and delivery, its own models extending models.Model, and no monkey-patching of core. New models such as cdiscount.account (credentials and endpoint config), cdiscount.offer (the link between your product.product and a Cdiscount SellerProductId/EAN), and cdiscount.order.import capture marketplace state, while computed fields with @api.depends derive publishable price and available quantity from your existing pricelists and stock.quant on-hand. A scheduled ir.cron job drives the API client (the Octopia/Cdiscount Marketplace REST/SOAP endpoints) in both directions: it submits offer packages, polls order queues, and confirms shipments. Every incoming order is mapped to a native sale.order and validated against your product catalogue so nothing posts to a wrong variant.

Technically, the connector is designed to fail safe and stay observable. Offer and order operations run through queued jobs with retry and idempotency keys so a marketplace timeout never double-imports an order or double-ships a line. Category and attribute mapping is data-driven — a mapping model translates your Odoo product categories and attributes into Cdiscount's required category tree and attribute schema, so publication doesn't get rejected for a missing mandatory field. Carrier confirmation reads the tracking reference from the Odoo stock.picking (and its carrier_tracking_ref) and calls the shipment-confirmation endpoint the moment the delivery is validated, keeping your dispatch SLA intact. Access is locked down with ir.model.access.csv plus record rules so only a marketplace-operations group sees credentials, and all API traffic and errors are logged to a dedicated log model you can audit from a standard Odoo list/form view. It targets Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise (Enterprise adds studio-friendly reporting; nothing here requires it).

Because this is build-to-order, we do not hand you a generic download. After a short scoping call we confirm your exact Cdiscount contract (fulfilment model, category set, carrier list, invoicing rules), fix the scope in writing, and build against it. Typical delivery is one working week from confirmed scope. You get the module installed and configured on a staging database first, run UAT with your real offers and a test order flow, then we go live with a rollback plan. You receive the full source, documentation, a training session, and a post-go-live support window — and the git repository is handed over so you own what you paid for.