Cdiscount Manufacturer Contacts Scraper - GPSR Brand Emails avatar

Cdiscount Manufacturer Contacts Scraper - GPSR Brand Emails

Pricing

from $10.00 / 1,000 manufacturer contacts

Go to Apify Store
Cdiscount Manufacturer Contacts Scraper - GPSR Brand Emails

Cdiscount Manufacturer Contacts Scraper - GPSR Brand Emails

Cdiscount manufacturer contact scraper for French product listings. Per product: company name, postal address and contact email published under EU GPSR, plus marketplace seller identity and a DNS check on the contact email. No login. For supplier discovery, brand mapping and B2B lead lists.

Pricing

from $10.00 / 1,000 manufacturer contacts

Rating

0.0

(0)

Developer

SR

SR

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

5 days ago

Last modified

Share

Cdiscount Manufacturer Contacts Scraper

Cdiscount manufacturer contacts for supplier discovery and B2B lead lists: per product you get the company name, the postal address and the contact email published under EU product-safety rules, every contact email checked over DNS.

This Actor turns a product search on France's second-largest marketplace into a list of reachable brand contacts. You give it keywords, it walks the search results, opens the product pages behind them and returns one row per manufacturer with the contact details Cdiscount publishes, plus a verification block for the email.

Manufacturer, not seller. The difference matters

Cdiscount publishes no email for its marketplace sellers. A product page carries sellerId, sellerName and a rating block, and no address of any kind. If you came here looking for seller emails, no tool can give you those from Cdiscount, because Cdiscount does not have them on the page.

What it does publish is the manufacturer's contact, because the EU General Product Safety Regulation obliges a brand placing goods on the EU market to be reachable, and the marketplace has to surface it.

Those are genuinely different parties. On a JBL Tune 530BT listing in the baseline run for casque bluetooth, the seller block says CDISCOUNT — the marketplace's own storefront — while the manufacturer returned for that row is Harman, at sara.nait@harman.com. Each row carries both, named separately, so you always know whose address you have.

What you get

Field by field, with example values taken from real runs:

FieldExample
manufacturer_nameHarman
manufacturer_emailsara.nait@harman.com
manufacturer_address12, Rue Des Colonnes Du Trône | 75012 | Paris | France | fr
seller_nameCDISCOUNT
seller_id, seller_rating, seller_sales_count0, null, 0 (Cdiscount's own listing)
product_titleCasque bluetooth - JBL - TUNE 530BT - Supra-auriculaire sans fil - Pure Bass - Jusqu’à 76 heures d’autonomie - Noir
product_urlhttps://www.cdiscount.com/high-tech/casques-baladeur-hifi/casque-bluetooth-jbl-tune-530bt-supra-auricu/f-1065420-jbl1200130029967.html?idOffre=4289613475&sw=…
verificationformat, domain, MX, role account, free provider, disposable, business domain, status

Rows where Cdiscount published no postal address carry the company name in manufacturer_address and nothing more. That is what the page holds, not a parse failure.

Why scrape Cdiscount manufacturer contacts

Supplier discovery normally runs the wrong way round. You start from a directory of companies and hope some of them sell what you need. Starting from a product search inverts it: you search the category you actually care about, and every contact that comes back demonstrably already sells that product in France.

The second reason is that this data is only reachable per product page. There is no export, no supplier directory and no API on Cdiscount that lists manufacturers, so the alternative to this Actor is opening listings by hand and copying French postal addresses out of a compliance panel.

Third, the contacts are compliance data rather than scraped personal addresses. GPSR exists so that a regulator, a retailer or a customer can reach the responsible company. That makes it a clean basis for B2B research, and it also means the same field is present across categories rather than only where a brand chose to publish it.

Input

FieldTypeRequiredWhat it doesDefault
keywordsarrayyesProduct keywords to search. Each result page is walked and the products behind it are read.["tapis de yoga"]
products_per_keywordintegernoHow many listings to open per keyword, 1 to 60.20
max_productsintegernoHard ceiling on product pages read in one run. This is your cost ceiling.50
only_products_with_contactbooleannoReturn only rows that carry a contact, so you pay for leads rather than for pages.true
verify_emailsbooleannoCheck format and look up the domain's MX records over DNS.true

Output

One row, from the run behind the input example (

{"keywords": ["tapis de yoga"], "products_per_keyword": 2, "max_products": 2}
). Only the sw= tracking token of the URL is shortened:

{
"product_url": "https://www.cdiscount.com/le-sport/fitness-musculation-yoga/dh-fitlife-tapis-de-yoga-lige/f-12104300302-aacri83011.html?idOffre=4305465608&sw=…",
"product_title": "DH FitLife Tapis yoga liège antidérapant, caoutchouc naturel, prêt à l’emploi, Pilates fitness (Mandala Harmony)",
"seller_id": 343352,
"seller_name": "DH-FitLife",
"seller_rating": 4,
"seller_sales_count": 775,
"manufacturer_name": "DH FitLife",
"manufacturer_address": "DH FitLife",
"manufacturer_email": "en@dh-fitlife.com",
"source": "cdiscount-contacts",
"fetched_at": "2026-10-08T15:21:02.802Z",
"platform": "cdiscount",
"country": "FR",
"name": "DH FitLife",
"email": "en@dh-fitlife.com",
"address": "DH FitLife",
"verification": {
"email": "en@dh-fitlife.com",
"valid_format": true,
"domain": "dh-fitlife.com",
"has_mx": true,
"is_role_account": false,
"is_free_provider": false,
"is_disposable": false,
"is_business_domain": true,
"status": "deliverable_domain"
}
}

The row above shows two things at once: manufacturer_address holds no more than the company name, because that is all Cdiscount published for this product, and the seller DH-FitLife happens to be the manufacturer's own storefront. Both cases are normal; the Harman row in the previous section is the case where they are different companies.

One contact, one row

A single manufacturer sits behind many listings. Two product pages can publish the same manufacturer email; those collapse into one row, because a repeated contact is not an extra lead, and since a row is the billable unit, charging twice for it would be charging twice for the same fact. Some pages publish no manufacturer email at all — those are not contacts, and with only_products_with_contact left on they never reach your output.

Use cases

Supplier sourcing for a category. A buyer entering a category searches the five product terms that define it and gets the brands behind the listings that already sell in France, with a postal address to check company registration against. The seller fields stay in the row, so you can also see which marketplace accounts carry each brand.

Competitive brand mapping. Retail and pricing teams know which sellers hold a category but rarely know which manufacturers sit behind them, because the seller name on a listing is usually a reseller. Running the same keyword set weekly shows which brands enter and leave a category.

Compliance and due diligence. GPSR requires a reachable responsible party. If you operate a marketplace or import goods, this gives you the published contact for each product, plus a DNS check that says whether that address can actually receive mail.

Lead lists that survive validation. Because every row is deduplicated and MX-checked, the list you export does not need a second pass through a verification tool before a campaign.

How this compares to what already exists

A Store search for "cdiscount" returns around four thousand actors, and almost all of them answer a different question.

Product and price scrapers. Cdiscount Scraper, Cdiscount Product Search Scraper, Cdiscount Scraper: Products, Marketplace Sellers & Reviews and the rest return prices, discounts, ratings and reviews. Useful for price monitoring and assortment research; none of them returns an address, because a price page does not carry one. If you already run one of those, this Actor is the same marketplace seen from the contact side.

Generic email extractors. The Store also holds a Cdiscount Email Scraper that pulls publicly indexed emails out of Cdiscount pages, filtered by keyword, location or domain. It does not read the manufacturer panel, so a returned address carries no proof that it belongs to the company responsible for the product, and there is nothing in the row that tells you whose address it is. That is a different product: broad, unattributed addresses instead of attributed, checked contacts.

B2B email finders and lead databases. Those start from a company you already have in mind and look up its address. This Actor inverts the search: you name the category, and every contact that comes back demonstrably already sells that product in France, with the seller account that listed it still in the row.

Opening the listings by hand. The last alternative is copying contact details out of the compliance panel one product page at a time. It produces the same facts at a fraction of the speed and none of the deduplication.

Limits and gotchas

  • France only. This reads cdiscount.com, which is a French marketplace. Keywords work best in French.
  • Many of Cdiscount's own search results point at product pages that never fully arrive. A share of Cdiscount's product URLs answers 200 with an empty shell instead of the product content. That is Cdiscount's data, not a fetch problem. Those URLs are asked again a few times and then reported as a fetch error. Ask for more products than you need: a URL that never arrives still counts against max_products.
  • Some product pages publish no manufacturer email. A page without one is not a contact; with only_products_with_contact left on it never reaches your output.
  • No seller emails exist. See the section above. A row's seller_* fields identify the marketplace account, not a contact.
  • A failed DNS lookup returns has_mx: null and status: "unknown", never false. A resolver timeout is not evidence that a domain cannot receive mail.
  • No mail is sent and nothing notifies the manufacturer. Verification is format plus MX records only.
  • max_products is the cost ceiling, and it is counted in pages opened rather than rows returned, because a page that turns out to carry no contact still had to be read.

Pricing

Pay per event: you are charged per contact row delivered, not per compute unit and not per page read. With only_products_with_contact left on, that means you pay for rows that carry a manufacturer contact. There is no actor-start fee and no per-compute-unit charge.

FAQ

Can I get Cdiscount seller emails? No, and neither can any other tool. Cdiscount does not publish an email or address for marketplace sellers. It publishes the manufacturer's, which is what this Actor returns.

Why is the manufacturer different from the seller? Most listings are placed by resellers. The manufacturer is the company that put the product on the EU market and is legally reachable for it.

How do I find manufacturer contacts for a whole category? Search the four or five keywords that define the category and raise products_per_keyword. Contacts repeat across listings and are collapsed, so a wide search returns fewer rows than pages.

Are the email addresses verified? Format is checked and the domain's MX records are looked up over DNS. That proves the domain can receive mail; it does not prove the mailbox exists.

How is this different from a Cdiscount product scraper? A product scraper returns what a listing costs, how it is rated and who sells it. This Actor returns who manufactured the product and how to reach that manufacturer. The two answer different questions about the same page, and you can run both.

Is scraping manufacturer contact details from Cdiscount lawful? These details are published because EU product safety law requires it, and they identify businesses rather than private individuals. Use them for B2B research, supplier discovery, compliance and due diligence, and follow the marketing and data-protection rules that apply where you operate.