Platform · Colruyt

Colruyt Data Scraping

A retailer that publicly commits to matching competitors' prices. So a price movement here may be somebody else's decision arriving late.

Colruyt data scraping collects product listings, pricing and availability across Colruyt's Belgian operation. What makes it analytically distinct is its stated price-matching policy: Colruyt publicly positions on matching competitors' prices, which means a price change in this feed may be a reaction rather than an initiative — and a series that cannot tell the difference will attribute a competitor's move to Colruyt.

Almost every price feed implicitly assumes a retailer sets its own prices. Where a retailer has publicly committed to matching, that assumption stops holding and the analysis has to change with it.

Get a free sample See sample data

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

colruyt_2026-08-25.jsonl LIVE FEED

{"product_id":"col-4471","ean":"54120*** redacted", "name_nl":"Example product 500g","name_fr":"Produit exemple 500g", "price":2.19,"currency":"EUR", "price_changed_since_last":true, "observed_at":"2026-08-25T09:14:22+02:00", "observation_window_seconds":300, "competitor_set_synchronised":true, "price_change_attribution":"not_determined"} {"retailer":"competitor-a","ean":"54120*** redacted", "price_changed_since_last":true, "observed_at":"2026-08-25T09:09:41+02:00", "note":"moved 5 min earlier. the SEQUENCE is the evidence — we do not label it"} {"product_id":"col-9902","is_own_label":true, "cross_retailer_matched":false, "caution":"own label — no competitor equivalent to match against"}

3 of 304,110 product rows · competitor set synchronisedprice_change_attribution: not_determined · schema v1.0

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

Colruyt at a glance

How we handle Colruyt specifically

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

Retailer: Colruyt — Belgium
The distinguishing fact: A stated policy of matching competitors' prices
Consequence: A price change may be a reaction, not an initiative
What that breaks: Any analysis treating a movement as this retailer's decision
What we do: Record the change, never attribute the cause
What makes it tractable: Collect the competitor set alongside, on one schedule
Belgium: Bilingual — Dutch and French. Both retained as published
Refresh: Higher than a typical grocer, because reaction timing is the signal

Platform specifics

What a price-matching policy does to a price series

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

A movement you cannot attribute is worse than no movement

Standard grocery price analysis treats a change as a decision: the retailer moved, and the question is why.

Where a retailer has publicly committed to matching competitors, some proportion of its movements are responses to someone else's decision. Those look identical in the data.

A price drop may be Colruyt competing, or it may be Colruyt matching a competitor who dropped first.
The two mean opposite things for a supplier or a rival reading the series.
Nothing in a single-retailer feed distinguishes them.

What we do and do not do

We record the change with a precise timestamp and we do not attribute a cause. There is no reason_for_change field, because we would be guessing at one.

price_change_attribution is a constant not_determined, stated so that nothing downstream treats a movement as an initiative.

What makes it analysable

Collecting the competitor set on the same schedule. If a competitor moved first and Colruyt followed within the observation window, the sequence is visible — and the sequence is the evidence, not our label on it.

That is why a Colruyt engagement is usually scoped with two or three Belgian competitors rather than alone. Colruyt data by itself is the least informative version of this dataset.

Which means observation frequency is the design decision

On most grocers, refresh frequency is a cost trade-off: prices move slowly, so a lower cadence loses little.

Here the timing is the analysis. If you want to see whether Colruyt led or followed, your observation window has to be shorter than the reaction time.

A weekly cadence tells you prices differ. It cannot tell you who moved first.
A daily cadence across the competitor set resolves most sequences.
The competitor schedule must match, or the comparison is between two different observation times.

We record observed_at to the second and hold the schedule identical across the retailers in scope. This is one of the few grocery cases where we would recommend a higher refresh than a client's instinct.

Compare that to our DMart page, where we recommend lower. The right cadence is a property of the retailer's pricing behaviour, not a default.

Belgian specifics: two languages and a deposit scheme

Dutch and French

Belgium is bilingual and product listings appear in Dutch and French, sometimes both on one listing. We retain both as published, record the dominant language, and do not machine-translate into the name field.

Matching runs on identifiers, normalised attributes and image hashes rather than title similarity, which performs badly across two languages describing the same product differently.

Deposit

Belgium operates a container deposit on part of the beverage range. As with German Pfand and Dutch statiegeld, it is refundable, differs by container, and is captured as its own field rather than folded into the shelf price.

Own label

Significant, and it does not cross-match to other retailers. Flagged, matched within the banner, marked unmatched across — the same position as everywhere else, and it matters here because own-label lines are not covered by a price-matching policy in the same way branded lines are.

Scope

What we collect on Colruyt, 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

Product listings, price and availability with precise timestamps
price_change_attribution constant not_determined, stated explicitly
Competitor set collected on an identical schedule where in scope
Change events with the observation window recorded
Dutch and French names retained as published, dominant language recorded
Deposit amount and type as separate fields from shelf price
Own label flagged and marked unmatched across retailers
Pack parsed, with unit price on a stated basis
Higher refresh recommended, with the reasoning stated

❌ What we do not, and why

A cause attributed to any price movement
A lead-or-follow conclusion drawn by us from the data
Machine translation written into product name fields
A deposit folded into the shelf price
Own label matched across retailers on name similarity

Core Colruyt fields

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

Field	What it is on this platform
product_id / ean / ean_missing_reason	Identifiers, with nulls reasoned
name_nl / name_fr / language_dominant	Both languages retained as published
price / currency	Shelf price, without deposit
price_changed_since_last / observed_at	The change, and when we saw it — to the second
price_change_attribution	Constant: not_determined. We record, we do not explain
observation_window_seconds	How tight the window was, which bounds any sequence claim
competitor_set_synchronised	Whether competitors were observed on the same schedule
deposit_amount / deposit_type	Belgian deposit as its own fields
is_own_label / cross_retailer_matched	Flagged, unmatched where it cannot pair
pack_size / pack_unit / price_per_unit	Parsed, with the basis named
in_stock	Availability

Use cases

What teams do with Colruyt data

Lead-or-follow sequence analysis

Colruyt and its competitor set observed on one synchronised schedule with second-level timestamps, so the sequence of movements is visible as evidence rather than as our interpretation.

Reaction-time measurement

How quickly a competitor's move appears in Colruyt's pricing, which is measurable only where both are observed on the same tight schedule.

Branded versus own-label movement patterns

Own-label lines are not subject to matching in the way branded lines are, so the difference in movement behaviour between the two is itself a finding.

Belgian market price benchmarking

Against other Belgian grocers on EAN where published, with deposit separated so beverage comparisons are not systematically wrong.

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

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

Colruyt is usually collected alongside its competitors

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

Colruyt data scraping: frequently asked questions

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

Because on a retailer with a stated price-matching policy, a movement may be its own decision or a reaction to a competitor's, and the two look identical in a single-retailer feed.

price_change_attribution is a constant not_determined. Putting a guessed cause in a field would make an inference indistinguishable from an observation.

By collecting the competitor set on the same schedule. If a competitor moved first and Colruyt followed within the observation window, the sequence is visible — and the sequence is the evidence.

That is why we usually scope this with two or three Belgian competitors rather than Colruyt alone. Colruyt on its own is the least informative version of this dataset.

Yes, and this is one of the few grocery cases where we recommend a higher refresh than a client's instinct. Timing is the analysis — a weekly cadence tells you prices differ but cannot tell you who moved first.

Compare our DMart page, where we recommend lower. The right cadence is a property of the retailer's pricing behaviour, not a default.

Not in the way it covers branded lines, since an own-label product has no competitor equivalent to match against. That difference in movement behaviour between branded and own-label lines is itself worth measuring.

We flag own label and mark it unmatched across retailers as usual.

Both retained as published with the dominant language recorded. We do not machine-translate into the name field.

Matching runs on identifiers, attributes and image hashes rather than title similarity, which performs badly when two languages describe the same product differently.

We quote individually, and it sits above a typical Belgian grocery engagement because the useful version includes a synchronised competitor set at a higher cadence.

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

See real Colruyt 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