Credentials and SellerId must stay aligned
Autopricy scopes authorisation and actions to the actual Cdiscount seller account.
Cdiscount repricer / Octopia workflow
Cdiscount repricing with rules, package feedback and read-back
Autopricy connects a Cdiscount seller through the current OAuth and SellerId workflow, synchronises Product and Offer data, applies bounded item-price rules, and records package feedback and later read-back. It complements the marketplace’s native tools when a seller needs multi-store control and a visible operations history.
Cdiscount price operations
A rule needs package feedback and a later marketplace state
Cdiscount already offers native floor-price functionality. External repricing earns its place by coordinating multiple stores, explicit rules, bulk operations and verifiable execution history.
Package acceptance is an intermediate state
Feedback can report processing or errors; it should not be reduced to a generic success message.
Native and external automation can conflict
The current store strategy must be reviewed so two pricing systems do not issue competing actions.
Marketplace mechanics
How Cdiscount repricing is verified
| Connect | Use the current OAuth and SellerId path for the seller account. |
|---|---|
| Import rules | Associate exact items with valid minimum, maximum and repricing settings. |
| Submit package | Send eligible Offer updates and retain package and item-level feedback. |
| Read back | Compare the later marketplace state with the requested target before calling it confirmed. |
Reference: Cdiscount seller guidance on native floor pricing
External repricing should not fight native automation
Cdiscount’s own price-floor mechanism may already operate on an Offer. Before enabling Autopricy, confirm which system owns the price decision and avoid overlapping automation.
Workflow
Introduce Cdiscount repricing with one owner
Authorise the store
Confirm OAuth, SellerId and the current store context.
Review existing automation
Identify native price-floor settings or other tools that may already change prices.
Import bounded rules
Validate item identity, minimum, maximum and eligible products.
Track package and read-back
Review feedback, errors and later marketplace state before scaling.
Illustrative workflow
Package feedback is not the final price
Example: a €19.80 target is inside a €18.50–€24.00 range and enters an Offer package. Autopricy records package and item feedback first, then checks the later marketplace value. A processed package alone is not described as a guaranteed winning Offer.
Related resources
Continue with the relevant workflow
FAQ
Cdiscount repricing with rules, package feedback and read-back: common questions
How is Autopricy different from Cdiscount native repricing?
Autopricy focuses on explicit multi-store rules, bulk operations, package feedback and shared execution history. The appropriate owner depends on the seller’s current setup.
Can native and external repricing run together?
Overlapping tools can issue conflicting actions. Review the current store automation and choose a clear owner before activation.
Does package success prove the storefront price?
Not by itself. Package feedback and a later marketplace read-back are separate pieces of evidence.
Does Autopricy guarantee the featured Offer?
No. Price can affect competition, but marketplace placement can also depend on stock, delivery, seller performance and platform rules.
Test the workflow on a real store
Start with one supported store, a controlled product scope, explicit boundaries and visible platform results.
yuanyongvia@gmail.com