REWE [Just 💰$0.90] — German Grocery Prices avatar

REWE [Just 💰$0.90] — German Grocery Prices

Pricing

from $0.90 / 1,000 results

Go to Apify Store
REWE [Just 💰$0.90] — German Grocery Prices

REWE [Just 💰$0.90] — German Grocery Prices

💰 $0.90 per 1,000 products. Scrape shop.rewe.de for real prices from your local REWE store — a postal code in and priced products out · unit price per kg and litre · ingredients and nutrition · GTIN and Pfand · Bio and category filters.

Pricing

from $0.90 / 1,000 results

Rating

0.0

(0)

Developer

Black Falcon Data

Black Falcon Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

What does REWE do?

REWE extracts structured product data from shop.rewe.de — including current shelf price and campaign flags and multi-resolution product images. It supports keyword search and controllable result limits, so you can run the same query consistently over time. The actor also offers detail enrichment (extra per-record fields the search results omit).

New to Apify? Sign up free and use the included $5 monthly platform credit to test this actor.

Key features

  • 📍 Real prices from a real store — REWE prices and product range differ from store to store. Give a postal code or town — zipCode: "50667" — and the nearest priceable store is picked for you, so every row carries that store's actual price and its actual assortment. Leave it empty to browse the whole national catalogue instead (names, brands, GTINs, categories, images) — without prices, because nationally there are none.
  • ⚖️ Price per kilo and litre — every product carries comparePrice and compareUnit normalised to €/kg, €/l or €/piece alongside the shelf price, so a 500 g pack and a 1 kg pack are directly comparable. A multipack whose size cannot be read unambiguously returns null rather than a misleading number.
  • 🥫 Ingredients, nutrition and allergens — beyond price: the ingredient statement, REWE's own nutrition table, the allergen statement, the manufacturer or responsible party, the GTIN barcode, pack size, deposit (Pfand) and any age restriction — the fields that make a grocery row usable for matching, compliance and analysis.
  • 🎛️ The store's own filters — browse a whole category (categorySlug: ["h-milch"]) with or without a keyword, narrow to a brand, or use REWE's own quick filters — Bio, vegan, regional, chilled, frozen, new. campaignsOnly returns just what is currently on offer. Sort by price, name or best sellers.
  • 🧺 Price a shopping list — pass productIds with matching quantities and each product is fetched and priced directly, with a lineTotal per row — a basket costed against one specific store, rather than a search you hope contains the items.
  • ♻️ Incremental mode — daily runs emit only products whose price, campaign flag, or validity window changed since the prior run — the rest stay UNCHANGED and are filtered out by default. Perfect for price-tracking apps and tilbud-alert pipelines. Saves 80–95% on recurring monitoring.
  • 📦 Compact mode — drop the heavy fields (ingredients text, full nutrition table, image variants, manufacturer block, label objects, price history) and keep shopping essentials: identity, current price, per-unit price, campaign flags + discount %, parsed unit size + brand, and basket line totals. Cuts each row by ~77% — ideal for AI agents, MCP servers, and LLM context windows where allergen text is noise.
  • 🧹 Empty-field stripping — drop null, empty-string, and empty-array fields from each record before push. Smaller payloads for AI agents and dashboards that already handle missing fields gracefully.
  • 📤 Export anywhere — Download the dataset as JSON, CSV, or Excel from the Apify Console, or stream live via the Apify API and integrations (Make, Zapier, Google Sheets, n8n, …).
  • 🔌 MCP connectors — export your results into Notion via Apify's MCP connectors — a clean run-summary page, no glue code. Opt-in via the App connector field; deterministic field-mapping, no AI. Built on Apify's connector framework, so more destinations open up as their catalog grows.

What data can you extract from shop.rewe.de?

Each result includes Core product fields (listingId, productId, gtin, name, brand, tags, grammage, and category, and more) and detail fields when enrichment is enabled (description and detailFetched). In standard mode, all fields are always present — unavailable data points are returned as null, never omitted. In compact mode, only core fields are returned.

Enable detail enrichment in the input to fetch each record's detail page — extra fields the search results omit.

Input

The main inputs are a search keyword and a result limit. Additional filters and options are available in the input schema.

Key parameters:

  • query — Product search keywords, e.g. "milch", "bio kaffee", "nutella". German terms match best. Use a JSON array for several searches in one run, e.g. ["milch","butter"]. Required if no Start URLs are provided.
  • zipCode — German postal code, town, street or store name — e.g. "50667" or "Köln". The nearest REWE store that can be priced is picked automatically, and every product then comes back with that store’s real price and range. Leave empty to browse the whole national catalogue instead — you still get names, brands, GTINs, categories and images, but no prices, because REWE prices are per-store.
  • marketId — Advanced: an exact REWE market ID, if you already know it. Overrides the postal code above.
  • categorySlug — Browse whole REWE categories instead of (or alongside) a keyword — pass a list, e.g. ["h-milch"] or ["milch", "kaese-eier-molkerei"]. Each category is browsed in full; add a keyword to search inside them instead.
  • brand — Only products from this brand, spelled as REWE spells it, e.g. "REWE Beste Wahl".
  • attribute — Narrow to one of REWE’s own quick filters. (default: "")
  • campaignsOnly — Return only products currently on offer. (default: false)
  • inStockOnly — Drop products the selected market cannot currently sell. Products whose availability cannot be determined are kept. (default: false)
  • sortBy — Order the results. (default: "RELEVANCE_DESC")
  • productIds — Price an exact list of products instead of searching, e.g. "1042422". Each one is fetched and priced directly.
  • quantities — How many of each product above, in the same order. Defaults to 1. Each result then carries its line total.
  • startUrls — Paste REWE search URLs, e.g. https://shop.rewe.de/productList?search=milch. Each URL becomes its own search; results are merged and deduped by product across all URLs. URLs without a search keyword (category browse pages, single product pages) are skipped. (default: [])
  • ...and 24 more parameters

Input examples

Basic search — Keyword-driven search with a result cap.

→ Full payload per result — all standard fields populated where the source provides them.

{
"query": "milch",
"maxResults": 50
}

Incremental tracking — Only emit products that changed since the previous run with this stateKey.

→ First run builds the baseline state. Subsequent runs emit only records that are new or whose tracked content changed. Set emitUnchanged: true to include unchanged records as well.

{
"query": "milch",
"maxResults": 200,
"incrementalMode": true,
"stateKey": "milch-tracker"
}

Compact output for AI agents — Return only core fields for AI-agent and MCP workflows.

→ Small payload with the most important fields — ideal for piping into LLMs without token overhead.

{
"query": "milch",
"maxResults": 50,
"compact": true
}

Output

Each run produces a dataset of structured product records. Results can be downloaded as JSON, CSV, or Excel from the Dataset tab in Apify Console.

Example product record

{
"listingId": "a58fa5a29afe7741736d0206d392be17db09a591df28c741680d02556a3310ee",
"productId": "1042422",
"gtin": "1042422",
"name": "Hemme Milch Frische Vollmilch 3,7% 1l",
"brand": "Hemme Milch",
"tags": [
"Gekühlt",
"Regional"
],
"grammage": "1l",
"category": "Frischmilch",
"categoryPath": [
"Käse, Eier & Molkerei",
"Milch",
"Frischmilch"
],
"image": "https://img.rewe-static.de/1042422/8646730_digital-image.png",
"images": [
"https://img.rewe-static.de/1042422/8646730_digital-image.png"
],
"price": 1.59,
"currency": "EUR",
"isOnSpecial": false,
"available": false,
"hasVariants": false,
"freeShipping": false,
"merchant": "REWE",
"url": "https://shop.rewe.de/p/hemme-milch-frische-vollmilch-3-7-1l/1042422",
"portalUrl": "https://shop.rewe.de/p/hemme-milch-frische-vollmilch-3-7-1l/1042422",
"searchQuery": "milch",
"contentQuality": "full",
"detailFetched": true,
"scrapedAt": "2026-08-02T16:35:46.897Z",
"source": "shop.rewe.de",
"contentHash": "3a4db8814352e2b027449407b99dcebc3ace640cad25471f0cbd515b09567d77"
}

Incremental fields

When incremental mode is on, each record also carries:

  • changeType — one of NEW, UPDATED, UNCHANGED, REAPPEARED, EXPIRED. Default output covers NEW / UPDATED / REAPPEARED; set emitUnchanged: true or emitExpired: true to opt into the others.
  • isRepost, repostOfId, repostDetectedAt — populated when a new listing matches the tracked content of a previously expired one. Set skipReposts: true to drop detected reposts from the output.

How to scrape shop.rewe.de

  1. Go to REWE in Apify Console.
  2. Enter a search keyword.
  3. Set maxResults to control how many results you need.
  4. Enable includeDetails if you need the extra detail-page fields.
  5. Click Start and wait for the run to finish.
  6. Export the dataset as JSON, CSV, or Excel.

Use cases

  • Extract product data from shop.rewe.de for market research and competitive analysis.
  • Track pricing trends across regions and categories over time.
  • Monitor new and changed products on scheduled runs without processing the full dataset every time.
  • Feed structured data into AI agents, MCP tools, and automated pipelines using compact mode.
  • Export clean, structured data to dashboards, spreadsheets, or data warehouses.

How much does it cost to scrape shop.rewe.de?

REWE uses pay-per-event pricing. You pay a small fee when the run starts and then for each result that is actually produced.

  • Run start: $0.01 per run
  • Per result: $0.0009 per product record

Example costs:

  • 10 results: $0.019
  • 25 results: $0.033
  • 100 results: $0.1
  • 200 results: $0.19
  • 500 results: $0.46

Example: recurring monitoring savings

These examples compare full re-scrapes with incremental runs at different churn rates. Churn is the share of products that are new or whose tracked content changed since the previous run. Actual churn depends on your query breadth, source activity, and polling frequency — the scenarios below are examples, not predictions.

Example setup: 100 products per run, daily polling (30 runs/month). Costs scale linearly with the number of products.

Churn rateFull re-scrape run costIncremental run costSavings vs full re-scrapeMonthly cost after baseline
5% — stable niche query$0.10$0.01$0.09 (86%)$0.43
15% — moderate broad query$0.10$0.02$0.08 (76%)$0.70
30% — high-volume aggregator$0.10$0.04$0.06 (63%)$1.11

Full re-scrape monthly cost at the same cadence: $3.00. First month with incremental costs $0.52 / $0.78 / $1.17 for the 5% / 15% / 30% scenarios because the first run builds baseline state at full cost before incremental savings apply.

Platform usage is included in the per-result fee shown above.

FAQ

How many results can I get from shop.rewe.de?

The number of results depends on the search query and available products on shop.rewe.de. Use the maxResults parameter to control how many results are returned per run.

Does REWE support recurring monitoring?

Yes. Enable incremental mode to only receive new or changed products on subsequent runs. This is ideal for scheduled monitoring where you want to track changes over time without re-processing the full dataset.

Can I integrate REWE with other apps?

Yes. REWE works with Apify's integrations to connect with tools like Zapier, Make, Google Sheets, Slack, and more. You can also use webhooks to trigger actions when a run completes.

Can I use REWE with the Apify API?

Yes. You can start runs, manage inputs, and retrieve results programmatically through the Apify API. Client libraries are available for JavaScript, Python, and other languages.

Can I use REWE through an MCP Server?

Yes. Apify provides an MCP Server that lets AI assistants and agents call this actor directly. Use compact mode, descriptionMaxLength, a single descriptionFormat, and excludeEmptyFields to keep payloads manageable for LLM context windows.

This actor extracts publicly available data from shop.rewe.de. Web scraping of public information is generally considered legal, but you should always review the target site's terms of service and ensure your use case complies with applicable laws and regulations, including GDPR where relevant.

Your feedback

If you have questions, need a feature, or found a bug, please open an issue on the actor's page in Apify Console. Your feedback helps us improve.

You might also like

Getting started with Apify

New to Apify? Create a free account with $5 credit — no credit card required.

  1. Sign up — $5 platform credit included
  2. Open this actor and configure your input
  3. Click Start — export results as JSON, CSV, or Excel

Need more later? See Apify pricing.

Disclaimer

This actor accesses only publicly available data on shop.rewe.de. You are responsible for how you use the extracted data — in particular any personal information such as names, phone numbers, or email addresses — and for complying with REWE's terms of use, applicable data-protection law (including the GDPR where it applies), and the anti-spam rules of your jurisdiction.

This actor is not affiliated with, endorsed by, or connected to REWE.

Search keywords

rewe scraper, rewe api, apify rewe, rewe data extraction, shop.rewe.de scraper, shop.rewe.de data, shop.rewe.de api, rewe preise, german grocery prices, supermarket prices germany, rewe angebote, lebensmittel preise, grocery price monitoring germany, rewe produkte.