Autodoc Scraper — Car Parts with OEM Numbers & EAN

Scrape car parts from Autodoc, Europe's largest online car-parts retailer: names, brands, prices, OEM cross-reference numbers, EAN barcodes, manufacturer part numbers, technical specs, ratings, and vehicle compatibility.

What is Autodoc Scraper?

Autodoc sells millions of car parts across roughly 27 European storefronts (autodoc.de, autodoc.co.uk, autodoc.fr, autodoc.es, autodoc.it, autodoc.nl, and more) that all run on the same platform. Its product pages carry the data that matters in the automotive aftermarket: the OEM cross-reference numbers that map an aftermarket part to the original equipment numbers of VW, BMW, Mercedes and every other vehicle maker, plus EAN barcodes, manufacturer part numbers, and full spec tables.

This actor crawls Autodoc's category tree, harvests product links, and extracts the complete data set from each product page. One domain input switches the same actor between country storefronts.

• Part cross-referencing — Map aftermarket parts (Bosch, Brembo, ATE, Febi, ...) to OEM numbers per vehicle manufacturer
• Price monitoring — Track aftermarket part prices across European markets and against your own catalog
• Catalog enrichment — Pull EAN codes, part numbers, and spec tables to enrich a parts database or marketplace listing
• Assortment analysis — See which brands and product lines Autodoc pushes per category
• Cross-country comparison — Run the same category on .de, .fr, and .co.uk to compare pricing per market

What data does Autodoc Scraper extract?

• Product name — Full title including brand and part number
• Brand — Parts manufacturer (BOSCH, BREMBO, ATE, ZIMMERMANN, TEXTAR, ...)
• Price & currency — Current price in the storefront's currency
• OEM cross-reference numbers — Original equipment numbers with vehicle-manufacturer attribution (the flagship field)
• EAN barcode — For matching against other catalogs
• SKU & MPN — Manufacturer part number, with and without separators
• Vehicle compatibility — Common vehicle models the part fits (up to 50 per product)
• Technical specs — Full attribute table (diameter, thickness, fitting position, surface, ...)
• Availability — InStock / OutOfStock status
• Ratings & reviews — Customer rating value and rating count
• Product image — Main image URL
• Category & URL — Category the product was found under and its canonical product URL

How to scrape Autodoc data

1. Get a Bright Data API key with a Web Unlocker zone (Autodoc runs a Cloudflare challenge on every request; regular proxies do not get through).
2. Pick one or more category URLs from the /autoteile/ tree, for example https://www.autodoc.de/autoteile/bremsscheibe-10132 (brake discs).
3. Set maxResults and run. The actor walks subcategories automatically when a single category page does not carry enough products.
4. Export the dataset as JSON, CSV, or Excel from the Apify Console or via API.

Keyword search URLs (/search) are not supported — drive the scraper with category URLs instead. Every category on the site has one, and the actor discovers subcategories on its own.

Input

Field	Type	Description
categoryUrls	Array	Category pages from the /autoteile/ tree to scrape
domain	String	Storefront to scrape (default www.autodoc.de; also .co.uk, .fr, .es, .it, .nl, ...)
fetchDetails	Boolean	Fetch each product page for OEM/EAN/specs/compatibility (default true). Set false for fast listing-only data
maxResults	Integer	Maximum products to return (default: 100)
brightDataApiKey	String	Your Bright Data Web Unlocker API key (required)
proxyConfiguration	Object	Not used — all requests go through Bright Data

Example input

{
    "categoryUrls": [
        { "url": "https://www.autodoc.de/autoteile/bremsscheibe-10132" }
    ],
    "maxResults": 100,
    "fetchDetails": true
}

Example output

{
    "name": "BREMBO Prime 09.9772.11 Bremsscheibe",
    "brand": "BREMBO",
    "price": 47.49,
    "currency": "EUR",
    "sku": "09977211",
    "mpn": "09.9772.11",
    "ean": "8020584018286",
    "oemNumbers": [
        { "oemNumber": "5Q0615301F", "manufacturer": "VW / AUDI / SKODA / SEAT / CUPRA" },
        { "oemNumber": "1K0615301AA", "manufacturer": "VW / AUDI / SKODA / SEAT" },
        { "oemNumber": "JZW615301H", "manufacturer": "VW / SKODA / SEAT" }
    ],
    "compatibility": [
        "Golf 7 Bremsscheiben",
        "Golf 5 Bremsscheiben",
        "Audi A3 8P Bremsscheiben",
        "Tiguan 5N Bremsscheiben"
    ],
    "availability": "InStock",
    "inStock": true,
    "rating": 4,
    "reviewCount": 115,
    "imageUrl": "https://media.autodoc.de/360_photos/1657592/h-preview.jpg",
    "specs": {
        "Einbauposition": "Vorderachse",
        "Durchmesser": "312",
        "Bremsscheibenart": "innenbelüftet",
        "Oberfläche": "beschichtet"
    },
    "articleId": "1657592",
    "category": "Auto Bremsscheiben hinten und vorne",
    "url": "https://www.autodoc.de/brembo/1657592",
    "scrapedAt": "2026-07-11T10:32:18.512Z"
}

How many results per run?

Each product's detail page is fetched individually (that is where the OEM and EAN data lives), at roughly 2–5 seconds per product with light concurrency. A 100-product run finishes in a few minutes; catalogue-scale runs take hours. The actor persists its crawl state, so long runs survive platform migrations and never push the same product twice.

With fetchDetails: false you get about 20 products per category page fetch — much faster and cheaper, but without OEM numbers, EAN, specs, or compatibility.

Multi-country support

All Autodoc storefronts share one platform. To scrape another country, set domain and use category URLs from that domain:

{
    "domain": "www.autodoc.co.uk",
    "categoryUrls": [{ "url": "https://www.autodoc.co.uk/car-parts/brake-disc-10132" }]
}

Prices come back in the local currency (EUR, GBP, ...).

Limitations

• Bright Data API key required. Autodoc's Cloudflare protection blocks direct requests and datacenter proxies. A Web Unlocker zone handles it reliably; you pay Bright Data per request (typically well under a cent).
• No keyword search. The site's /search endpoint is not crawlable — use category URLs. The category tree covers the full catalog.
• Category pages show top products only. Each category page lists around 20 products; the actor compensates by walking subcategories. For full-catalogue coverage, seed multiple deep categories.
• Compatibility list is capped at 50 vehicles per product to keep items compact.

Related Scrapers

• Leroy Merlin Scraper — French DIY & home improvement products
• ManoMano Scraper — European DIY marketplace
• Idealo Scraper — German price comparison across categories
• AutoTrader UK Scraper — UK used-car listings

FAQ

Do I need an Autodoc account or cookies? No. Everything comes from public product pages.

Can I scrape a single product? Seed the category the product sits in and set a low maxResults, or run with fetchDetails: true and filter the output by articleId.

Is scraping Autodoc legal? This actor extracts publicly available product-page data (prices, part numbers, availability). You are responsible for how you use the data; check the terms that apply to your use case.

Why do a few products come back without OEM numbers? Universal parts and accessories have no OEM cross-references on their pages. The field is populated whenever the site shows it.