Platform · Rohlik

Rohlik Data Scraping

Q: How do you handle variable-weight fresh items?

Per-kilo price is the primary value, with is_variable_weight flagged and the estimated pack price captured separately and marked as an estimate. Where a listing gives only an estimate and no per-kilo rate, we do not derive one from an assumed weight — that would put a calculated number in a field that looks observed.

Scheduled online grocery, not ten-minute delivery. That single difference changes what availability means.

Rohlik data scraping collects product listings, pricing, promotions and slot availability from Rohlik's Central European operations, including its German and Austrian brands. The structural difference from quick commerce: Rohlik delivers into scheduled slots, not minutes, so slot availability is a state distinct from stock and the two must not be collapsed.

An operator that has expanded into space vacated by exiting rapid-delivery players, on a model that survived when theirs did not. Which makes its pricing a useful benchmark rather than a curiosity.

Get a free sample See sample data

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

rohlik.jsonl LIVE FEED

{"country":"CZ","brand":"rohlik", "ean":"85941*** redacted", "name_local":"Example testoviny 500g", "price":42.90,"currency":"CZK", "in_stock":true,"slot_available":true, "serviceable":true,"earliest_slot":"2026-08-26T08:00"} {"product_id":"rh-8812", "in_stock":true,"slot_available":false, "earliest_slot":"2026-08-30T18:00", "note":"stocked, no slot for 4 days — NOT a stockout"} {"product_id":"rh-9902","is_variable_weight":true, "price_per_kg":189.00, "price":94.50,"price_is_estimate":true, "caution":"charged on actual weight — listed price is not what is paid"}

3 of 1,204,110 product rows · 4 countriesthree availability states · EAN fill 78.1% · schema v1.0

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

Rohlik at a glance

How we handle Rohlik specifically

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

Platform: Rohlik and its regional brands, Central Europe
The model: Scheduled slots, not minutes. Full grocery baskets, not fill-in
Consequence: Slot availability is separate from stock. Both can be true or false independently
Assortment: Deep — a full grocery catalogue, not a convenience range
Fresh: Significant, including variable-weight items priced per kilo
Country: A dimension. Assortment and brand differ per market
Deposits: Where a market operates them, kept separate from shelf price
Refresh: Daily is usually right. Scheduled grocery moves slower than q-commerce

Platform specifics

What separates scheduled grocery from quick commerce

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

Three availability states, not one

On a ten-minute service, availability is close to binary. On a scheduled service it is not.

In stock — the item is held.
Slot available — there is delivery capacity in a usable window.
Serviceable — the service reaches this address at all.

All three are independent. An item can be in stock with no slot for four days, which is a very different situation from a stockout and a completely different competitive signal.

We deliver all three plus earliest_slot, because during peak periods stock typically holds while slot capacity does not, and a single "available" field hides exactly that.

This is the same structure our BigBasket work uses, where slot and stock diverge routinely.

Variable-weight fresh items break naive price fields

Rohlik carries a deep fresh range, and fresh is where most grocery feeds go wrong.

Variable-weight items are priced per kilo, and the displayed item price is an estimate for an approximate weight.
The customer is charged on actual weight, so the listed price is not what is paid.
Comparing a per-kilo item to a fixed-pack item on headline price is meaningless.

We record price_per_kg as the primary value for variable-weight lines, flag is_variable_weight, and capture the estimated pack price separately with price_is_estimate: true. Where a listing gives only an estimate and no per-kilo rate, we do not derive one from the assumed weight.

Deposits

Where a market operates a container deposit, it is captured as its own field and never folded into the shelf price — the same discipline our Flink page applies to German Pfand.

Deep assortment, private label and the honest matching limit

A full grocery catalogue rather than a convenience range means assortment depth is a competitive dimension in its own right, and it also means private label is significant.

Private label has no shared identifier and no equivalent at another retailer.
We match it within a retailer and flag it as unmatched across retailers.
We do not pair it on name similarity, which would produce a comparison that is quietly wrong.

Branded lines match on EAN where published. We report the EAN fill rate per category before quoting, because that number decides whether a cross-retailer programme is viable in your categories — the same figure our Lulu work leads with.

Country as a dimension

Rohlik operates under different brands per market with different assortments and pricing. country and brand are on every record, and cross-country comparison is a deliberate join with FX where currencies differ.

Scope

What we collect on Rohlik, 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 with country and local brand on every record
In stock, slot available and serviceable as three independent states
Earliest delivery slot where one is offered
price_per_kg primary for variable-weight items, with is_variable_weight flagged
Estimated pack price captured separately, marked as an estimate
Container deposit as its own field where a market operates one
EAN where published, with fill rate reported per category
Private label flagged and marked unmatched across retailers
Promotional mechanics as displayed, separate from base price

❌ What we do not, and why

A single availability field collapsing stock and slot
A per-kilo rate derived from an assumed weight
Private label matched across retailers on name similarity
A deposit folded into the shelf price
Sales, order volumes or warehouse quantities

Core Rohlik fields

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

Field	What it is on this platform
country / brand / city	Market, local brand and geography
product_id / ean / ean_missing_reason	Identifiers, with nulls reasoned
name_local	Retained exactly as published
price / currency	Displayed price
is_variable_weight / price_per_kg / price_is_estimate	Fresh handled properly
deposit_amount / deposit_type	Where a market operates deposits
in_stock / slot_available / serviceable	Three independent states
earliest_slot	Where one is offered
pack_size / pack_unit / price_per_unit	Parsed, with the basis named
is_private_label / cross_retailer_matched	Flagged, and unmatched where it cannot pair
observed_at	Timestamp

Use cases

What teams do with Rohlik data

Central European grocery price benchmarking

Country and brand on every record with EAN matching where published, so a Czech price and a German one are compared on the same product rather than on a name that looked similar.

Slot capacity as a service signal

Slot availability tracked separately from stock, which is where service degradation actually appears during peak periods and where a quick-commerce schema sees nothing.

Fresh category comparison done correctly

Per-kilo pricing primary for variable-weight lines, so a fresh comparison is not distorted by estimated pack prices that customers never actually pay.

Assortment depth benchmarking

A full grocery catalogue rather than a convenience range, so range breadth is measurable as a competitive dimension against traditional supermarkets.

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

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

Rohlik is usually collected alongside its competitors

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

Rohlik data scraping: frequently asked questions

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

Because on a scheduled service they are independent. An item can be in stock with no delivery slot for four days, which is a completely different situation from a stockout and a different competitive signal.

During peak periods stock typically holds while slot capacity does not, and a single 'available' field hides exactly that.

Per-kilo price is the primary value, with is_variable_weight flagged and the estimated pack price captured separately and marked as an estimate.

Where a listing gives only an estimate and no per-kilo rate, we do not derive one from an assumed weight — that would put a calculated number in a field that looks observed.

No, and the difference matters for the schema. Rohlik delivers into scheduled slots with a full grocery catalogue, rather than minutes with a convenience range.

Applying a quick-commerce schema loses the slot dimension entirely, which is one of the more useful signals the model produces.

Yes, on EAN where it is published, and we report the fill rate per category before quoting so the programme is scoped on real matchability.

Private label is the honest limit — it has no equivalent at another retailer, so we flag it as unmatched rather than pairing it on name similarity.

Yes, as their own field where a market operates them, never folded into the shelf price. A deposit is refundable and it differs by container type, so combining them produces a systematic error on the affected categories.

We quote individually. Drivers are country count, catalogue breadth and refresh frequency. Daily is usually right — scheduled grocery moves considerably slower than quick commerce, and higher frequency costs more for the same answer.

One scoping call, a free pilot within 24 hours including the EAN fill rate, then a fixed monthly quote. Request a quote.

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