Seller guide / Cdiscount
Cdiscount repricing: from a price rule to a verified marketplace result
Cdiscount Offer updates use the Octopia API workflow. A reliable repricer needs the correct OAuth and SellerId context, valid Offer identity, bounded calculations, package feedback and a later marketplace read-back.
See Cdiscount repricingNeed the product workflow first? Review the Cdiscount repricer page for supported capabilities and limits.
The Octopia Offer update model
Octopia provides JSON Offer-management APIs for marketplace updates, including the Cdiscount channel identified as CDISFR. Updates are submitted as packages and move through processing states before item feedback is available.
That asynchronous model means a successful request is the beginning of the verification path. Store the package identifier and inspect its result rather than marking every item successful immediately.
Identity and authorization
The connected store needs valid OAuth context and the correct SellerId. Every action must target the exact seller Offer and marketplace channel. A similar product record does not prove ownership of the Offer being changed.
Authorization failures, inactive Offers and mismatched identifiers should stop the update with a visible error. They should never trigger a fallback guess.
Price boundaries and management rules
Octopia documents Offer management rules and validation, including price-floor-related controls. Autopricy adds seller-defined minimum and maximum values to the calculation before an eligible change enters a package.
If an existing Cdiscount or third-party pricing tool manages the same Offers, overlapping actions can conflict. Audit current automation and choose a clear owner for the scope.
Package feedback and read-back
Track package creation, processing status and item-level feedback. A processed package can still contain rejected rows. After successful feedback, retrieve the marketplace Offer again when possible to compare the later stored value.
These checkpoints support honest states: submitted, processing, rejected, accepted and confirmed by read-back. Each proves a different part of the workflow.
A controlled example
An Offer has a €18.50 minimum and €24.00 maximum. The rule calculates €19.80 and creates a JSON update package. Autopricy retains the package ID, checks item feedback and then reads the Offer again. Only the later evidence supports describing the marketplace value as confirmed.
Begin with a small SKU group and review every error category. Expand after authorization, package feedback and read-back are stable.
Primary sources
Cdiscount repricing FAQ
What is an Offer update package?
It is an asynchronous group of Offer changes. Keep its identifier and inspect processing and item feedback.
Does a processed package prove the storefront price?
Not by itself. Item feedback and a later Offer read-back provide additional evidence.
Can Autopricy run beside another repricer?
Overlapping automation can conflict, so the current pricing owner should be reviewed before activation.
Does Autopricy guarantee the featured Offer?
No. It controls eligible price actions, while marketplace placement can depend on other signals.
Related resources
Continue from guide to implementation
Test the workflow on a real store
Start with one supported store, a controlled product scope and visible platform results.