If you sell on Cdiscount, France's largest homegrown marketplace, and run ERPNext as your system of record, the two live in separate worlds. Orders sit in the Cdiscount / Octopia seller back office, while your Sales Orders, stock ledger, and accounting live in ERPNext. Someone on your team re-keys orders, watches for stock-outs across channels, edits prices in two places, and tries to make the monthly settlement statement agree with what actually reached the bank. ERPNext core has no concept of a Cdiscount offer, no OAuth client for the Cdiscount Marketplace API, and no place to reconcile marketplace commissions — so this stays manual no matter how mature your instance is.

ECOSIRE builds a proper Frappe application — erpnext_cdiscount — installed into your existing bench, not a spreadsheet macro or a middleware subscription you rent forever. The app ships its own DocTypes: Cdiscount Settings (single DocType for API credentials and sync toggles), Cdiscount Offer mapped to your ERPNext Items, Cdiscount Order as a staging record before it becomes a Sales Order, and Cdiscount Settlement for statement lines. Mapping child tables link Cdiscount SKUs and EAN codes to ERPNext Item codes and warehouses. Authentication to the Cdiscount / Octopia Marketplace API runs server-side, with tokens held in Frappe's encrypted site config and every outbound call logged for traceability.

Technically, the connector is event- and schedule-driven the way ERPNext expects. Scheduler events registered in hooks.py poll Cdiscount for new and updated orders, then create Sales Orders (and optionally Delivery Notes / Sales Invoices) against the mapped customer and warehouse. doc_events hooks fire on Item and Item Price so a stock or price change in ERPNext is pushed back to the matching Cdiscount offer through the price/stock feed, keeping the two-way sync honest. Whitelisted methods exposed over the Frappe REST API let your team trigger a manual resync or publish an offer from a client script button, and dedicated role profiles (for example Cdiscount Manager) keep marketplace controls out of the hands of general users. Cdiscount Fulfilment (CDAV / fulfilled-by-Cdiscount) flows are supported so fulfilment-mode orders are tagged and routed correctly rather than double-shipped.

Because this is build-to-order, nothing here is a stock download you install blindly. We start with a short scoping call to confirm your Cdiscount API access, your Item and warehouse structure, tax and pricing rules, and which flows you actually need (orders only, or full offer + price + fulfilment + settlement). We then build against your requirements, validate on a staging bench with your own catalogue during UAT, and install to production with a rollback plan. Typical delivery is one working week from confirmed scope, and you receive the full source code and git repository for the version we build for you. It targets ERPNext / Frappe v15 and v16.