ERPNext Cdiscount Connector

Key Features

`Cdiscount Settings` single DocType holding API credentials in Frappe's encrypted site config, environment (sandbox/production) toggle, and per-flow sync switches

Scheduler events in `hooks.py` poll the Cdiscount / Octopia Marketplace API for new and updated orders and stage them as `Cdiscount Order` records

Automatic Sales Order creation from staged orders against a mapped customer, price list, and warehouse, with optional Delivery Note and Sales Invoice generation

`Cdiscount Offer` DocType mapping ERPNext Items to Cdiscount offers by SKU and EAN, with publish and edit (update price, stock, description) actions

Two-way inventory sync: `doc_events` hooks on Bin/Stock Ledger changes push available quantity to Cdiscount so offers reflect real ERPNext stock

Two-way price sync: Item Price updates push to the matching Cdiscount offer, and incoming offer prices can update ERPNext, with a configurable source-of-truth per field

Cdiscount Fulfilment (CDAV) support — fulfilment-mode orders are detected, tagged, and routed so they are not shipped twice

`Cdiscount Settlement` DocType that imports statement lines and reconciles marketplace commissions, refunds, and payouts against ERPNext accounting

Whitelisted Frappe REST API methods for manual resync, single-offer publish, and on-demand order pull, callable from client-script buttons or external systems

Client scripts adding action buttons (Publish Offer, Resync Order, Fetch Settlement) directly on the relevant DocType forms

Dedicated role profile (e.g. `Cdiscount Manager`) plus DocType permissions so marketplace controls are isolated from general ERPNext users

Idempotent sync keyed on Cdiscount order/offer identifiers to prevent duplicate Sales Orders on repeated polls or retries

Full API call and error logging via a log DocType and Frappe's Error Log, with ret/backoff on transient Cdiscount API failures

Built and tested against ERPNext / Frappe v15 and v16, installed into your existing bench as a versioned app

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2–4 weeks 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.

What you get

Installable source code for the exact version we build for you, as a standard Frappe app on your bench

Installation and configuration on your staging and production sites, including Cdiscount API credential setup and Item/warehouse mapping

Technical documentation: DocType reference, hooks and scheduler map, whitelisted API methods, and configuration guide

End-user guide plus a live training session for your operations and catalogue team

UAT on a staging bench using your own catalogue, with a documented rollback plan before production cut-over

A post-go-live support window for bug fixes and adjustments after launch

Handover of the private git repository with full commit history for the version we deliver

Who this is for

French Cdiscount seller running ERPNext

A France-based retailer or brand selling on Cdiscount that has standardised operations on ERPNext and needs orders, stock, and pricing to flow automatically instead of being re-keyed from the Octopia seller back office.

Multi-channel e-commerce operations manager

Runs Cdiscount alongside other channels and warehouses, and needs reliable two-way inventory and price sync so a sale on one channel does not oversell another, all reconciled inside ERPNext.

Finance / accounting lead

Owns the monthly close and needs Cdiscount settlement statements, commissions, and refunds reconciled against ERPNext accounting rather than hand-matched in spreadsheets.

ERPNext partner or internal IT team

Maintains the client's bench and wants a clean, versioned Frappe app with proper DocTypes, hooks, role profiles, and a handed-over git repo they can maintain, not opaque middleware.

How ERPNext Cdiscount Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor
Cdiscount order sync	Scheduled pull creates Sales Orders automatically, idempotent by order ID	Possible, but you design and maintain the polling and dedup logic	Often present, but tied to the vendor's own schema and mappings
Two-way stock & price sync	`doc_events` + scheduler push both ways with per-field source of truth	Build it yourself, including conflict handling	Usually one-way or limited, varies by vendor
Offer publish & edit	`Cdiscount Offer` DocType mapped to Items with publish/edit actions	Hand-rolled against the Cdiscount offer feed	Sometimes, if the vendor covers the French market
Settlement reconciliation	`Cdiscount Settlement` DocType reconciled to ERPNext accounting	Bespoke work, often skipped due to effort	Rarely covered in depth
Cdiscount Fulfilment (CDAV)	Detected, tagged, and routed to avoid double shipping	Extra logic you must specify and build	Depends on vendor scope
Fit to your ERPNext setup	Built to your Items, warehouses, tax and pricing during scoping	Fully bespoke by definition	Generic; you adapt your data to its model
Code ownership	Full source and git repo handed over for your version	You own it, and you own all the maintenance	Closed source; locked to the vendor
Support & maintenance	Post-go-live support window plus optional ongoing agreement	Entirely on your team	Subscription-based vendor support

Frequently Asked Questions about ERPNext Cdiscount Connector

Is this a ready-made app I can download and install today?

No. It is build-to-order. ECOSIRE scopes your Cdiscount setup and ERPNext configuration, then builds, installs, and supports the connector for you. There is no instant download — you receive a version built and tested against your own catalogue and requirements.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on which flows you need (orders only versus full offer, price, fulfilment, and settlement) and how clean your Item and warehouse mapping is. We confirm dates after the scoping call and UAT sign-off precedes go-live.

Which ERPNext and Frappe versions are supported?

We build and test against ERPNext / Frappe v15 and v16. The connector is a standard Frappe app installed into your existing bench. If you are on an older version, we will flag it during scoping and discuss an upgrade or backport.

How does support and updates work after go-live?

Every build includes a post-go-live support window for bug fixes and adjustments. Because you receive the full source and git repository, your team or ECOSIRE can maintain and extend it. Ongoing support or Cdiscount API-change maintenance beyond the initial window can be arranged as a separate agreement.

Do you need our Cdiscount API access, and is it secure?

Yes — you provide Cdiscount / Octopia Marketplace API credentials. They are stored server-side in Frappe's encrypted site config, never exposed in client-side code, and all outbound calls are logged. We can build and validate against the Cdiscount sandbox environment first where available.

How does the two-way inventory and price sync avoid conflicts?

Sync is driven by `doc_events` hooks and scheduler events, and is idempotent — keyed on Cdiscount order and offer identifiers so repeated polls never create duplicate Sales Orders. You configure the source of truth per field (for example, ERPNext owns stock and price), so there is a clear, deterministic winner rather than a race.

Can it handle Cdiscount Fulfilment (fulfilled-by-Cdiscount) orders?

Yes. Cdiscount Fulfilment (CDAV) orders are detected and tagged so they are routed correctly and not shipped from your own warehouse by mistake, while self-fulfilled orders continue through your normal ERPNext Delivery Note flow.