kaufda.de Circulars & Offers Scraper — Germany Prospekte

Scrape German retail circulars (Prospekte) and the offers inside them from kaufda.de (the Bonial brochure portal). Paste the homepage, a retailer page, a city page or any category page and get clean, flat records: one row per product offer (title, brand, price in EUR, category, retailer, validity window, image) and one row per circular (publisher, page count, validity, cover image) — each tagged with a recordType and a machine-readable parse_confidence score.

This kaufda.de Circulars & Offers Scraper is built for price-monitoring tools, retail and CPG market-research teams, deal aggregators and lead-generation pipelines that need structured German weekly-flyer data without maintaining a fragile in-house scraper.

What kaufda data you get

Offer rows (recordType: "offer"):

• title — the product / offer headline as listed
• brand — the brand of the advertised product (e.g. DJI, SONY)
• mainPrice — the price parsed to a number, plus priceFormatted as displayed ("339,00 €")
• currency — always EUR
• category / categories — kaufda's own category labels for the offer
• publisherName / publisherId — the retailer running the circular (e.g. MediaMarkt Saturn)
• validFrom / validUntil — the offer's validity window
• imageUrl — the offer image
• brochureId / brochurePage — the circular and page this offer sits on

Brochure rows (recordType: "brochure"):

• title — the circular's title (e.g. Dein Markt)
• publisherName / publisherType — the retailer and its type (e.g. RETAILER)
• pageCount — number of pages in the flyer
• publishedFrom / publishedUntil / validFrom / validUntil — schedule
• coverImage — the flyer cover
• publisherLogo — the retailer logo

How to scrape kaufda.de

1. Paste one or more kaufda.de URLs — the homepage (https://www.kaufda.de/) returns the current top offers and brochures; a retailer, city or category page returns that page's circulars and offers.
2. Toggle Include brochures off if you only want product offers.
3. Set Max results to cap cost. Run. Results stream into the dataset.

The actor reads the catalog from kaufda's own embedded data layer and de-duplicates offers by id and brochures by content id.

How much does it cost?

Pay per result — there is no subscription. You are billed per record returned, so a small trial run costs cents. The actor runs on Apify's RESIDENTIAL proxy (country: Germany) billed to your own Apify account — there is no extra proxy fee from us and no key to supply.

Example output

{
  "recordType": "offer",
  "id": "7b5af2bb-b282-43cf-a2d3-90eb0806628f",
  "title": "Osmo 360 Standard Combo Action Cam , WLAN, Touchscreen",
  "brand": "DJI",
  "mainPrice": 339,
  "priceFormatted": "339,00 €",
  "currency": "EUR",
  "category": "Flachbildfernseher",
  "publisherName": "MediaMarkt Saturn",
  "validFrom": "2026-06-22T07:00:00.000+0000",
  "validUntil": "2026-06-29T06:59:00.000+0000",
  "imageUrl": "https://content-media.bonial.biz/7b5af2bb-b282-43cf-a2d3-90eb0806628f/27a89860-0dd8-3c7c-a529-ff30876d9a7a.jpeg",
  "brochureId": "2d9fc5c7-0889-45e3-99bc-eae0d842ec2c",
  "brochurePage": 1,
  "parse_confidence": 1.0
}

Why this kaufda.de Circulars & Offers Scraper

• Reads the catalog from kaufda's own data layer — the parser walks kaufda's embedded JSON state and picks offers and brochures by their fields, not brittle CSS class names, so it keeps working across the homepage, retailer, city and category page layouts and through redesigns.
• Normalized prices — mainPrice is a number ready for filtering, sorting and discount math; priceFormatted keeps the exact German display string.
• Reliable access built in — every request is routed through Apify's RESIDENTIAL proxy for a stable German egress; no key to supply.
• Quality signal built in — parse_confidence lets you trust the data and drop incomplete rows automatically.
• Offers and circulars in one run — get both the product-level deals and the flyer-level metadata, tagged by recordType.

FAQ

Do I need a kaufda login or API key? No. The actor reads public kaufda.de pages.

Which data does it cover? German retail circulars (Prospekte) and the offers inside them as published on kaufda.de.

In what language is the data? Offer titles, descriptions, brands and categories are returned in German exactly as kaufda lists them; prices are normalized to a number in EUR.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.