datawebotCdiscount product data: catalog products and seller offers
How Cdiscount separates catalog products from seller offers, and how to keep item price, delivery cost, condition and variants apart.
Updated · datawebot team
A product sheet and a Cdiscount offer describe different things
Cdiscount product research crosses two records that are easy to confuse: the catalog description of an item and a seller’s offer for it. For a useful comparison, add a third layer: the condition, destination and time at which an offer was observed.
Scroll to compare →
| Record | Fields to preserve | Why the distinction matters |
|---|---|---|
| Catalog product | Product reference, GTIN/EAN when present, title, brand, category and relevant attributes. | A title match alone can join different pack sizes, models or variants. |
| Seller offer | Seller name, condition, item price and delivery terms when available. | One product can have separate seller offers with different conditions and delivery. |
| Observation | Destination or delivery context, source URL and timestamp. | Offers and displayed values can vary with context and change over time. |
Keep the Cdiscount identifiers in their own fields
Keep seller references distinct from catalog identifiers so that cross-seller analysis does not silently merge unrelated records.
Scroll to compare →
| Field | What it identifies | Matching guidance |
|---|---|---|
| GTIN / EAN | A product or variant when the source provides one. | Preserve as text, including leading zeroes; do not substitute a title when it is absent. |
| Catalog product reference | Cdiscount’s reference for the catalog product. | Use it to align offers on the same catalog item, not to identify a seller’s offer. |
| Seller reference | A seller’s own reference for its product or offer, when shown. | Keep the seller identity alongside it; another seller may use a different reference. |
| Condition | The offer’s stated condition. | Condition describes offer context; it does not identify the underlying catalog item. |
Compare displayed price with delivery and condition attached
Delivery should remain a separate amount and option from the item price. Keep seller, condition, destination and observation time beside the displayed price.
Scroll to compare →
| Value | Example or field | How to use it |
|---|---|---|
| Displayed item price | €20.00 in a fictional example. | Attribute to the observed page and retain its timestamp. |
| Delivery | A fictional delivery offer of €4.00 to one selected destination. | Keep separate from item price; do not call €24.00 a final checkout total. |
| Offer context | Same fictional item, seller, new condition and observation time. | Match condition and delivery context before comparing values; do not mix a used offer with a new one. |
Keep French variants and delivery modes in their own context
Product attributes depend on category: some categories use size or color, while others use storage, material or different properties. Category requirements should be read per category rather than copied across the whole catalog. Variant groups can help relate choices, but each child item still needs its own identity and offer context.
Scroll to compare →
| Cdiscount detail | Record when available | Avoid this assumption |
|---|---|---|
| Category attributes | Category, language and the product properties shown. | The same fields apply to every category. |
| Variant family | The variant group plus each child’s GTIN, product reference and variant attributes. | A shared group reference makes child items interchangeable. |
| Delivery offer | Delivery mode, preparation time and destination context where shown. | Delivery details are part of the product identity or a timeless property. |
| Fulfillment | The seller/fulfillment wording and offer details shown for the specific offer. | Octopia Fulfillment and Express Seller mean the same thing or guarantee an ETA, eligibility or free shipping. |
Content reviewed 2026-10-24.