Custom scraper

Douglas Scraper

We do not have a dedicated Douglas data API. What we do have is an AI scraper that reads a douglas.de page you point it at, turns it into the columns you asked for and hands them back by REST, CSV or Excel — on a schedule, priced per page.

  • douglas.de
  • douglas.at
  • douglas.ch
Three stages of a Douglas run: paste a douglas.de URL billed from the render price of EUR 0.75 per 1,000 pages; declare columns such as brand and product_title; and the 12 columns it returns.

How to scrape Douglas

Douglas publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface. Douglas is the DACH beauty price reference and the main offline-online hybrid in European beauty. The way to get the data is to read the page the way a customer sees it. Beauty prices are set per size and per shade, and a gift-with-purchase or a sampling offer can be worth more than a discount without touching the price at all.

How douglas.de is laid out

What a run needs to know about Douglas before you pick the URLs.

  • Sizes are separate offers

    Perfume and cosmetics come in several sizes (for example 30, 50 and 100 ml), each with its own price. Always record the size with the price.

  • Unit price per 100 ml

    German shops must show a base price (Grundpreis) per volume. Capture it; it is the fair way to compare sizes and retailers.

  • Beauty Card offers

    Many promotions are only for Douglas Beauty Card members, or need a code in the basket. Keep the public price as your main column and the offer text next to it.

  • Own brand

    Douglas Collection is Douglas's own brand and has no direct competitor price. Filter it out of brand-level comparisons.

  • Country shops

    douglas.de, .at and .ch are separate shops with their own prices, and Switzerland prices in CHF. List each market on its own.

What the AI scraper does with a douglas.de link

The same three steps as any other page you point it at. Nothing about Douglas is pre-built, which is exactly why it works on pages nobody wrote a connector for.

  1. Paste the link

    Give it a douglas.de product or listing URL. Market, currency and assortment all come from the page itself, so there is no region setting to get wrong — the URL decides.

  2. Declare the columns

    Name each field, give it a type and write a line telling the AI what to look for. “brand” and “product_title” are the two most people start with. The schema is yours and you can change it between runs.

  3. Schedule it and collect

    Run it daily, weekly or on demand. Every run returns the same columns in the same order with a timestamp on each row, so the history builds itself.

Set it up once. The data keeps coming.

Save your search once and it runs by itself. Every run lands in your own Scrapewise database, and you pick how to read it.

  1. Set it up once

    Add your ASINs, keywords, places or apps to a scraper in the web app. New accounts get 5 free requests.

  2. Runs on your schedule

    Pick daily, weekly on the days you choose, every few days, or the first or last day of the month. Scheduled runs start at night, European time. Need it more often? Start runs from your own code.

  3. Saved in your database

    Each run adds dated rows, so this week sits next to last week. Rows are kept for 90 days.

  4. Use it your way

    Open the table in the web app and download the latest run as an Excel file. Ask your own AI assistant about it. Or pull the rows into your code with an API key.

Ask your AI assistant about your own data

Connect Claude Desktop or Claude Code with a read-only key. The assistant reads the rows you've already collected, at no extra cost on Scrapewise. With a full-access key it can start a run for you too.

  • Which of my ASINs lost the Buy Box this week?
  • Which competitor cut prices the most since Monday?
  • Show the keywords where I dropped out of the top 10.

What you send and what you get

You send a link and a column list. Everything else — market, currency, which products are on the page — comes from the page, so there is nothing to configure twice.

You give
  • Link to a Douglas pagerequired

    Open the product or category page in your browser and copy the address. Any Douglas country domain works the same way.

    https://www.douglas.de/
  • Your column listrequired
    brand, product_title, variant, size
  • How often it runsoptional
    Daily at 06:00 UTC
You get

One row per product on the page, 7 columns each

  • product_title
  • price
  • currency
  • availability
  • brand
  • sku
  • source_url

REST API, CSV or Excel. The column set stays the same between runs, so downstream jobs do not re-map fields.

What a run on Douglas actually returned

This is real output, not a mock-up. 2 rows, collected on 3 October 2026 from live douglas.de product pages through our own engine, the same way one of your runs would. Prices move, so treat the numbers as a sample of shape rather than a current price list.

All 7 columns

  • product_title
  • price
  • currency
  • availability
  • brand
  • sku
  • source_url

2 sample rows, all 7 columns seen across sample calls.

2 sample rows, all 7 columns seen across sample calls.
product_titleproduct_titleProduct title as the retailer writes itpricepricePrice the page is charging todaycurrencycurrencyCurrency the page quotedavailabilityavailabilityStock state the page publishedbrandbrandBrand as the retailer labels itskuskuThe retailer's own product codesource_urlsource_urlThe exact page this row was read from
30 ml14EURInStockGuess1067289https://www.douglas.de/de/p/5010868118
100 ml - Mini73.6EURSoldOutCHANEL1077857https://www.douglas.de/de/p/5010980006

Column names are ones we chose when declaring the schema for this run. Yours can be named whatever your downstream job already expects. We pointed the run at 8 Douglas product pages and 2 came back with a readable price. The rest returned something other than a product page, which is ordinary on this storefront and the reason the tier named above is what it is. We publish what we measured, not what we expect.

What a Douglas page costs

Pay-as-you-go from your wallet. No plan, no monthly fee, no seat count. The price shown is the starting price: €0.75 per 1,000 pages with a browser render. If a run also needs a residential proxy it costs €3.75 per 1,000 pages.

€0.75per 1,000 pagespay-as-you-go, no plan

Measured on 3 October 2026, not assumed. A plain request for a douglas.de page comes back HTTP 400 rather than a page, so the run goes through a browser.

Worked example

500 Douglas pages checked once a day for a month is 15,000 pages.

about EUR 11.25 for the month at the render price, about EUR 56.25 if the pages also need a residential proxy

You are charged for what a run actually used, not what it was expected to need, and your balance never expires.

See the full price list →

Typical fields the AI scraper extracts from a Douglas page

Treat this as a starting point rather than a fixed schema. What comes back is whatever the page actually shows on the day of the run.

Size and shade set the price

Beauty is the category where one product page is many prices, and where a size scrape without a size column is unusable.

  • Price for the size the page is showing
  • Size exactly as printed
  • Price per 100 ml or 100 g where printed
  • Shade or formulation the page is showing
  • Which sizes and shades are listed at all

Offers that are not discounts

A gift with purchase, a sampling offer or a bundle moves perceived value without moving the price, and it is text on the page.

  • Gift-with-purchase or offer wording as printed
  • Strike-through or was-price where shown
  • Bundle or set composition, where the page lists it
  • Loyalty or member price where shown
  • Promotion end date, where printed

Product identity

Beauty catalogues are brand-dense, so brand and variant are the join keys rather than a part number.

  • Brand as labelled
  • Site's own product code
  • EAN or GTIN, where published
  • Category breadcrumb
  • Ingredient list, where rendered
  • Rating and review count, where shown

The column list is one you write: name each field, give it a type and a line telling the AI what to look for. The schema belongs to your run, not to us. How Custom Schema works →

What it cannot give you If a field is not visible on the page, the scraper cannot invent it. Identifiers such as EAN or GTIN only come back when Douglas publishes them.

What people use Douglas data for

01

Price per 100 ml comparison

The only honest comparison in beauty, because the same product in two sizes is two different value propositions. Size as a column makes it computable.

02

Gift-with-purchase tracking

Beauty competes on offers more than on discounts, and the offer is text on the page. Capturing that wording daily reconstructs a competitor's promotional calendar.

03

Brand price-floor checks

If you own a beauty brand, this is how you see what your products are actually listed at across the retailers that carry them, per size, with the date attached.

04

Shade and range availability

Which shades a retailer actually stocks, and which have quietly gone out of stock, is a range signal that price data alone misses.

05

Assortment research before a launch

What a category carries, at what price points and sizes, from which brands, rather than what a category report says it carries.

What makes Douglas harder than an ordinary storefront

Here is what the scraper is actually up against on douglas.de, measured rather than assumed.

Access

  • Plain HTTP requests are answered, but the answer is the shell of the page rather than the priced version of it
  • No named protection vendor on the response, which is why this one lands on a cheaper tier than most of the cohort
  • No usable sitemap directive in robots.txt, so the URL list comes from your own category pages

Sizes and shades multiply the page

  • Each size usually carries its own price, so a single price column is ambiguous without a size column
  • Shades are frequently separate variants with their own stock state and sometimes their own price
  • Offers are free text rather than a percentage, so they have to be captured as written rather than parsed into a number
  • Brand and category pages are lazily loaded, so a sweep is a list of URLs rather than one request

What the page publishes

  • No product-level structured data is published, so every field is read off the rendered page
  • Each size is published as a nested product with its own price, so a naive run returns rows titled '30 ml' rather than the product name.
  • Price is one of the last things the page settles on, so a read taken too early records the placeholder rather than the number

What to watch on douglas.de

The one thing specific to this site. The general limits — public pages only, no field the page does not show, your URLs rather than a full crawl — are in the custom scrapers FAQ.

  • Douglas has one specific trap

    Each size is published as a nested product with its own price, so a naive run returns rows titled '30 ml' rather than the product name.

FAQ

Douglas scraping — questions

What people ask before pointing the scraper at douglas.de.

Douglas publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface.

Questions that apply to every site — scheduling, exports, what it will not do — are answered in the custom scrapers FAQ.

Ready to pull Douglas data into your stack?

Start free — or talk to our team about your exact fields, refresh cadence and volume.