Upload customer invoices on Cdiscount

🛍️ Summer Sales 2026 are coming

France’s official Summer Sales period is approaching, and sale pricing can be prepared up to 3 days before the start date.

Please keep in mind that French “Omnibus” rules rely on the lowest public price in the last 30 days: this reference price is used to compute the displayed discount during the sales period.
So, when planning your updates, be careful not to push your price too low right before the event — otherwise you may lower the reference price and reduce (or cancel) the perceived discount.

🧾 E-invoicing in France: the countdown has started

France is moving to mandatory electronic invoicing for B2B transactions between VAT-registered companies established in France, with a progressive rollout starting September 1st, 2026.

From that date, all companies must be able to receive e-invoices. Issuing becomes mandatory from Sept 1st, 2026 for large companies and mid-caps (ETI), and from Sept 1st, 2027 for SMEs and micro-businesses.
In practice, invoices must be exchanged through an approved platform (directly or via a compatible solution), and the same timeline also applies to upcoming e-reporting obligations.

Technical news RSS

🚚 Cdiscount now supports shipping CancelRequest lines

Good news for Cdiscount sellers: you can now declare shipments for order lines in CancelRequest status in specific cases.

This is allowed when the order header is InPreparation, the supplyMode is Seller, and the cancellation request was initiated by the customer. You still use the same endpoint POST /orders/{orderId}/shipments (payload unchanged).

This update prevents blocking situations when a customer requests cancellation after the parcel has already entered the shipping process — while keeping clear eligibility rules (seller-initiated or sales-channel-initiated cancellations are still rejected).

🔐 Token generation quotas will be enforced (June 30, 2026)

We will soon enforce limits on token generation: 500 requests per hour per IP address.

Tokens are valid for approximately 2 hours. The authentication response includes the token and its validity duration in the expires_in property. To avoid unnecessary renewals (and prevent being rate-limited), request a new token only when the current one is close to expiring — ideally a few minutes before expiration.

Please review your current implementation to ensure compliance before June 30, 2026.