Platform · Edeka

Edeka Data Scraping

Not a chain. A cooperative of independently run stores, many of which set their own prices — which makes a banner-level Edeka price a number nobody charges.

Edeka data scraping collects product listings, pricing and availability across Edeka's German store network. The structural fact that shapes everything: Edeka is a cooperative rather than a conventional chain, with a large number of independently operated stores that set some of their own pricing and assortment. A single Edeka price does not exist, and a feed that reports one is averaging stores that genuinely charge different amounts.

Most German grocery data treats Edeka like Rewe or Kaufland. The ownership structure is different and it shows up directly in the data.

Get a free sample See sample data

Free pilot on your own Edeka list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

edeka_2026-08-25.jsonl LIVE FEED

{"store_id":"ed-4471","city":"Hamburg", "ean":"40123*** redacted", "price":2.49,"currency":"EUR", "deposit_amount":0.25,"deposit_type":"einweg", "grundpreis_displayed":3.32,"grundpreis_matches":true, "promo_running":true} {"store_id":"ed-9902","city":"Hamburg", "ean":"40123*** redacted", "price":2.79,"promo_running":false, "note":"same product, same city, different store — independently operated"} {"banner_rollup_price":2.61, "observable_store_count":412, "caution":"a computed rollup. no store charges this"}

3 of 2,204,110 product-store rows · Germanystore_id mandatory · banner figure is a computed rollup · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Edeka or its owners. Edeka and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

Edeka at a glance

How we handle Edeka specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Retailer: Edeka — a cooperative, Germany
The structural fact: Many stores are independently operated
Consequence: Stores set some of their own prices and assortment
So: A banner-level Edeka price is a number nobody charges
The unit: Store. Rollup to banner only as a computed view
Pfand: German deposits kept separate from shelf price
Grundpreis: Displayed unit price captured, and ours computed alongside
Own label: Significant, and does not cross-match to other retailers

Platform specifics

Why the cooperative structure changes the data

These are the reasons a Edeka dataset needs its own handling rather than a shared retail schema.

Independently operated stores are not branches

A conventional chain sets prices centrally and its stores execute them. Edeka's structure includes a large number of independently run stores operating under the banner.

That produces variation a chain schema is not built for:

Prices differ between stores on the same product, and not only for regional-cost reasons.
Assortment differs, because an independent operator makes range decisions a branch manager would not.
Promotional participation differs — a national campaign is not necessarily running everywhere.

store_id is mandatory on every record, and any banner-level figure is a computed rollup with the store detail retained underneath, so it can always be decomposed.

Where a store's operating model is exposed we record it, but we do not assert whether a given store is independently operated where that is not published. It is a structural fact about the network, not a claim we make store by store.

German market mechanics, which apply here as elsewhere

Pfand

Container deposits are separate from the shelf price and refundable. A beverage at €4.99 plus €1.50 Pfand is not a €6.49 product, and deposit amounts differ by container type so it is not a flat adjustment. Captured as its own field, never folded in — the same discipline our Flink page applies.

Grundpreis

German law requires a displayed unit price. We capture it and compute our own from parsed pack data, then flag grundpreis_matches where they disagree.

A disagreement is usually a listing error rather than a parsing failure, and on a cooperative with independent stores it is worth knowing which stores are producing them.

Own label

Edeka's own-label range is significant and has no equivalent at another retailer. Flagged, matched within the banner, and marked unmatched across retailers rather than paired on name similarity.

What a store-level cooperative feed is unusually good for

The structure that makes Edeka awkward for a chain schema makes it informative for a specific question: how much price autonomy actually gets exercised.

Price dispersion within a banner is measurable at store level, and it is not measurable at all on a centrally priced chain.
Promotional participation rate — what share of stores are running a given national campaign — is observable where the campaign is identifiable.
Assortment divergence between stores shows where independent operators are making different range calls.

For a supplier negotiating with the cooperative, that dispersion is the thing worth knowing and it is not available from any published source.

The honest limit

Not every Edeka store has an online presence, and the online range does not match the store range. We collect what is published online and we do not infer store-level assortment from it. A dispersion figure is therefore a figure across the observable stores, and we state how many that is.

Scope

What we collect on Edeka, and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

Store-level price and availability, with store_id mandatory
Banner-level figures as computed rollups, with store detail retained
Pfand deposit amount and type as separate fields from shelf price
Displayed Grundpreis captured, with our computed unit price alongside
grundpreis_matches flagged where the two disagree
Own label flagged and marked unmatched across retailers
Promotional mechanics as displayed, with participation observable per store
Observable store count stated on every dispersion figure
German product names retained exactly as published

❌ What we do not, and why

A single banner-level Edeka price presented as the price
A store's operating model asserted where it is not published
Store-level assortment inferred from the online range
A deposit folded into the shelf price
Own label matched across retailers on name similarity

Core Edeka fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	What it is on this platform
store_id / city / region	Mandatory. The unit of analysis
product_id / ean / ean_missing_reason	Identifiers, with nulls reasoned
name_de	Retained exactly as published
price / currency	Shelf price, without deposit
deposit_amount / deposit_type	Pfand as its own fields
pack_size / pack_unit / price_per_unit / unit_basis	Parsed by us
grundpreis_displayed / grundpreis_matches	Theirs, and whether it agrees with ours
is_own_label / cross_retailer_matched	Flagged, unmatched where it cannot pair
promo_mechanic / promo_running	Mechanics, and whether this store is running it
observable_store_count	Stated on any dispersion figure, per batch
in_stock / observed_at	Online range only, with a timestamp

Use cases

What teams do with Edeka data

Price dispersion within a banner

Store-level records across a cooperative, which makes intra-banner price variation measurable — something a centrally priced chain simply does not produce.

Promotional participation rate

What share of observable stores are running a given national campaign, which for a supplier negotiating with the cooperative is the number that is not published anywhere.

Assortment divergence between stores

Where independently operated stores are making different range decisions, visible as a pattern rather than as noise in a banner average.

German market price benchmarking

Against Rewe, Kaufland and the discounters on EAN where published, with Pfand separated so beverage comparisons are not systematically wrong.

The 24-hour sample — run on your sources, not ours

Send us a Edeka item or category list. We run real collection against it and return the output within 24 hours, with the platform-specific fields populated so you can check them yourself rather than take our word for it.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.

Edeka is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Edeka data becomes useful when it sits next to the competitor set on one schema, refreshed on one schedule, so a price index or availability comparison is genuinely like-for-like.

That is what grocery data scraping covers, and a Edeka-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

Edeka data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

Because Edeka is a cooperative rather than a conventional chain, and a large number of stores are independently operated with their own pricing and assortment decisions.

A banner-level figure averages stores that genuinely charge different amounts. We deliver store-level records and compute a banner rollup on request, with the detail retained so it can be decomposed.

Where a store's operating model is published we record it. Where it is not, we do not assert it.

The cooperative structure is a fact about the network; whether a specific store is independently run is not something we would claim from a listing page.

It is the thing this structure produces that a centrally priced chain cannot. For a supplier negotiating with the cooperative, knowing how much price autonomy actually gets exercised — and where — is not available from any published source.

Every dispersion figure carries the observable store count, so you know what it is a dispersion across.

As its own field, never folded into the shelf price. A beverage at €4.99 plus €1.50 deposit is not a €6.49 product, and deposit amounts differ by container type so it is not a flat adjustment.

Folding it in produces a systematic error across the whole beverage category and makes German prices incomparable to non-deposit markets.

Both. We capture the displayed unit price German law requires and compute our own from parsed pack data, then flag where they disagree.

A disagreement is usually a listing error rather than a parsing failure — and on a cooperative it is worth knowing which stores are producing them.

We quote individually. Store panel size is the dominant driver here rather than SKU count, because the value of the dataset is in the dispersion across stores.

One scoping call, a free pilot within 24 hours, then a fixed monthly quote. Request a quote.

See real Edeka data before you commit to anything

Send us an item or category list. We return the output within 24 hours with the platform-specific fields populated.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner