Platform · Albert Heijn

Albert Heijn Data Scraping

Two things complicate a simple price field here: the Bonus mechanic, and the fact that not every AH store is run by AH.

Albert Heijn data scraping collects product listings, pricing, Bonus promotions and availability across Albert Heijn's Dutch and Belgian operations. Two structures complicate the price field: Bonus pricing, which is a promotional mechanic rather than a member tier, and a franchise element within the banner, meaning not every store is company-operated.

The Dutch market is concentrated and comparatively transparent, which makes the two complications here worth getting right rather than smoothing over.

Get a free sample See sample data

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

albertheijn_2026-08-25.jsonl LIVE FEED

{"country":"NL","store_id":"ah-1180", "ean":"87180*** redacted", "price":2.49,"currency":"EUR", "deposit_amount":0.15,"deposit_type":"statiegeld_blik", "bonus_mechanic":"2e halve prijs", "bonus_conditions":"requires 2 units", "bonus_cycle_week":35, "effective_price":"null", "effective_basis":"quantity_conditional_basket_unknown"} {"store_id":"ah-9021","ean":"87180*** redacted", "price":2.65,"bonus_mechanic":"null", "store_operating_model":"not_published", "note":"different price, no Bonus — franchise element. we do NOT assert which stores are franchised"} {"bonus_mechanic":"25% korting","bonus_conditions":"unconditional", "effective_price":1.87,"effective_basis":"unconditional discount applied"}

3 of 884,220 product-store rows · NL + BEBonus kept separate from base price · cycle-aligned · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Albert Heijn or its owners. Albert Heijn 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

Albert Heijn at a glance

How we handle Albert Heijn specifically

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

Retailer: Albert Heijn — Netherlands and Belgium
Bonus: A promotional mechanic, captured as displayed, not folded into price
Franchise: Part of the estate is franchised, which can affect price and range
The unit: Store, with banner as a computed rollup
Two countries: Separate markets with different ranges and pricing
Deposit: Dutch statiegeld kept separate from shelf price
Own label: Significant, and does not cross-match to other retailers
Refresh: Weekly for base price; Bonus cycles need matching to their calendar

Platform specifics

What complicates the price field at AH

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

Bonus is a mechanic, not a member price, and the distinction matters

It is easy to treat Bonus as a member-gated price and handle it the way we handle Prime pricing at Whole Foods. That would be wrong, and the difference changes what the data means.

Bonus offers are promotional mechanics — multibuys, percentage discounts, bundles — running on a published cycle.
They are displayed publicly, so there is no gated-share problem of the kind Whole Foods has.
Many are conditional on quantity or basket, so an effective unit price depends on a basket we cannot see.

We capture bonus_mechanic and its conditions as structured fields, keep them separate from the base price, and compute an effective price only where it is unconditional, with the basis recorded. Where a mechanic is basket-conditional, effective price is null with a reason rather than a number resting on an assumption.

The cycle matters for scheduling

Bonus runs on a published weekly cycle. A collection schedule that does not align to it will sample some weeks mid-cycle and some at the boundary, producing promotional-intensity numbers that measure the schedule. We align observation to the cycle and record bonus_cycle_week.

Franchise stores inside the banner

Part of the Albert Heijn estate is franchised rather than company-operated. That is a milder version of the Edeka cooperative structure, and it has the same consequence in kind if not in degree.

Price and range can differ between company-operated and franchised stores.
A banner-level figure blends the two, which is fine for a headline and wrong for anything precise.
Promotional participation is not necessarily identical across the estate.

store_id is on every record and banner figures are computed rollups with the store detail retained. Where a store's operating model is published we record it; where it is not, we do not assert it — the same position as on our Edeka page, and for the same reason.

Two countries

The Dutch and Belgian operations are separate markets with different ranges and pricing. country is a dimension and they are never pooled.

Dutch market mechanics

Statiegeld

The Netherlands operates a container deposit scheme covering bottles and cans. As with German Pfand, the deposit is refundable and separate from the shelf price, and it differs by container type.

Captured as its own field, never folded in. A comparison to a non-deposit market that ignores it is systematically wrong across the affected categories.

Own label

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

Unit pricing

Displayed unit pricing is standard in Dutch grocery. We capture it and compute our own from parsed pack data, then flag disagreement — which is usually a listing error and, on a franchised estate, worth knowing which stores are producing them.

Scope

What we collect on Albert Heijn, 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 on every record
Bonus mechanic and conditions as structured fields, separate from base price
Effective price only where a mechanic is unconditional, with the basis recorded
bonus_cycle_week, with observation aligned to the published cycle
Store operating model where published, not asserted where not
Statiegeld deposit amount and type as separate fields
Displayed unit price captured, with our computed value and disagreement flagged
Own label flagged and marked unmatched across retailers
country as a dimension — Netherlands and Belgium never pooled

❌ What we do not, and why

Bonus treated as a member-gated price
An effective price computed from a basket-conditional mechanic
A store's operating model asserted where it is not published
A deposit folded into the shelf price
Own label matched across retailers on name similarity

Core Albert Heijn fields

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

Field	What it is on this platform
country / store_id / city	Two markets, and store as the unit
store_operating_model	Where published. Not asserted where not
product_id / ean / ean_missing_reason	Identifiers, with nulls reasoned
name_local	Dutch retained exactly as published
price / currency	Base shelf price, without deposit
bonus_mechanic / bonus_conditions / bonus_cycle_week	The mechanic, its conditions, and where in the cycle
effective_price / effective_basis	Only where unconditional, with the basis named
deposit_amount / deposit_type	Statiegeld as its own fields
unit_price_computed / unit_price_displayed / unit_price_matches	Ours, theirs, and agreement
is_own_label / cross_retailer_matched	Flagged, unmatched where it cannot pair
in_stock / observed_at	Availability and timestamp

Use cases

What teams do with Albert Heijn data

Bonus promotional intensity, measured on the cycle

Observation aligned to the published Bonus cycle with the cycle week recorded, so promotional intensity is measured rather than sampled at arbitrary points in it.

Company-operated versus franchise price variation

Store-level records with the operating model where published, showing whether franchise autonomy is exercised and where.

Dutch market benchmarking with deposits separated

Statiegeld as its own field, so a comparison to a non-deposit market is not systematically wrong across beverages.

Listing accuracy monitoring

Our computed unit price against the displayed one, with disagreements flagged — and on a franchised estate, attributable to stores.

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

Send us a Albert Heijn 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.

Albert Heijn is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Albert Heijn 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 Albert Heijn-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

Albert Heijn data scraping: frequently asked questions

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

No, and the difference changes what the data means. Bonus offers are promotional mechanics — multibuys, percentage discounts, bundles — running on a published cycle, and they are displayed publicly.

So there is no gated-share problem here. What there is instead is conditionality: many mechanics depend on quantity or basket, so an effective price rests on a basket we cannot see.

Only where a mechanic is unconditional, and with the basis recorded. Where it is basket-conditional, effective price is null with a reason.

A three-for-two effective price depends on whether the shopper buys three, and that is an assumption rather than an observation.

Because a schedule not aligned to it samples some weeks mid-cycle and some at the boundary, producing promotional-intensity numbers that measure the schedule rather than the market.

We align observation to the published cycle and record bonus_cycle_week so the position within the cycle is always known.

No — part of the estate is franchised, and price, range and promotional participation can differ. It is a milder version of the Edeka cooperative structure with the same consequence in kind.

We record the operating model where published and do not assert it where it is not. Banner figures are computed rollups with store detail retained.

As its own field, never folded into the shelf price. The deposit is refundable and differs by container type, so a comparison to a non-deposit market that ignores it is systematically wrong across the affected categories.

We quote individually. Drivers are store panel size, country count and whether Bonus-cycle-aligned observation is in scope, which raises the observation count relative to a flat weekly schedule.

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

See real Albert Heijn 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