Platform · Bolt Food

Bolt Food Data Scraping

Q: Does the footprint change?

Yes, and we record markets_observed per batch rather than assuming a fixed list — so an entry or withdrawal appears as a structural change rather than as a silent drop in coverage.

The restaurant surface. And the couriers delivering it are the same ones driving rides, which makes availability move through the day.

Bolt Food data scraping collects restaurant menus, pricing, fees and availability across European and African markets. This is the restaurant surface, distinct from the platform's grocery stores. The operational feature that shapes the data: the platform runs a shared courier fleet across rides, food and grocery, so delivery availability shifts through the day for reasons outside the food business.

Our Bolt Market page covers the grocery side and makes the shared-fleet argument for stores. Here it applies to restaurants, where it moves promise times as well as availability.

Get a free sample See sample data

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

boltfood.jsonl LIVE FEED

{"platform":"bolt_food","surface":"restaurant", "price_setter":"merchant","country":"EE", "merchant_id":"bf-44120", "item_price":9.80,"currency":"EUR", "serviceable":true,"daypart":"midday", "promise_minutes":28} {"merchant_id":"bf-44120","daypart":"evening_peak", "serviceable":false,"promise_minutes":"null", "availability_cause":"not_attributed", "note":"nothing changed at the restaurant. one daily observation would see one of these"} {"surface":"bolt_market","price_setter":"platform", "courier_count":"not_collected", "markets_observed":17}

3 of 1,884,220 merchant-item-daypart rows · EU / Africarestaurant surface · cause never attributed · schema v1.0

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

Bolt Food at a glance

How we handle Bolt Food specifically

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

Platform: Bolt Food — Europe and Africa
This page: The restaurant surface
The other: Bolt Market — grocery
Operational feature: Shared courier fleet across rides, food and grocery
Consequence: Availability and promise times shift through the day
So: Multi-daypart observation is not optional
Price setter: Merchant on the restaurant surface
Markets: Many, priced independently

Platform specifics

A shared fleet, and two surfaces

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

Courier supply is not dedicated to food

The platform runs rides, food delivery and grocery on one courier and driver pool. That is efficient for the operator and it makes food-delivery availability depend on demand elsewhere.

Peak ride demand pulls capacity away from food, at exactly the hours food demand also peaks.
So a restaurant can be serviceable at one hour and not another, with nothing changing at the restaurant.
Promise times move for the same reason.
A single daily observation lands at an arbitrary point in that pattern.

We record daypart and recommend multiple observations per day rather than one — the timing argument our cadence page makes, applied to a supply constraint rather than to price movement.

And we do not attribute an availability change to fleet allocation. It is one plausible cause among several, and the allocation is not observable.

Restaurant surface, not grocery

The platform's own grocery stores are a different surface with a different price setter, covered on our Bolt Market page.

Here the merchant sets the price, frequently above dine-in to cover commission.
There the platform sets the price for its own stock.
Availability means different things — a restaurant pausing versus a store being out of an item.

surface and price_setter on every record, and where both are collected they share a schedule so any cross-surface comparison holds.

Markets

The footprint spans European and African markets that differ substantially in price level, currency and merchant mix. country is a dimension, FX is stamped per observation, and a regional average is a computed rollup rather than a primary figure.

markets_observed is recorded per batch rather than assumed, since footprints change — the discipline our foodpanda page established.

Standard mechanics, and what we do not collect

Modifier groups make the headline item price not the entry price, so min_realisable_price is the comparable figure. Fees are separate fields. Availability is address-level. All as our Uber Eats page sets out.

Languages

The footprint spans many languages. Names retained exactly, translation additive and dated, matching on structure rather than titles.

What we do not collect

Courier counts, fleet allocation or driver positions. Not published, and an availability change is not evidence of allocation.
Order volumes, merchant revenue or take rate.
Courier, customer or reviewer identity. Counts and ratings only.
Ride or grocery surface data on this scope. Separate, deliberately.

Scope

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

surface and price_setter on every record
daypart recorded, with multiple observations per day recommended
No cause attributed to an availability change
country as a dimension, with FX stamped per observation
markets_observed recorded per batch, never assumed
Modifier groups with minimum realisable price
Fees as separate fields, per market
Names retained exactly, translation additive and dated
Shared schedule where the grocery surface is also collected

❌ What we do not, and why

Restaurant and grocery surfaces blended
An availability change attributed to fleet allocation
Courier counts, positions or allocation data
A regional average presented as a price
Order volumes, revenue, courier, customer or reviewer data

Core Bolt Food fields

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

Field	What it is on this platform
platform / surface / price_setter	restaurant surface, merchant sets the price
country / markets_observed	Which market, and what the batch saw
merchant_id / merchant_name / city	A commercial entity, and where
item_name_local / language_detected	Retained exactly, with the language
item_price / currency / fx_observed_at	Price, and FX stamped at observation
modifier_groups / min_realisable_price	The number a customer can pay
delivery_fee / service_fee	Each separately
serviceable / daypart	Availability, and when it was observed
availability_cause	Constant not_attributed
promise_minutes	As displayed. Moves with fleet load
panel_schedule_id	Shared where both surfaces are collected

Use cases

What teams do with Bolt Food data

Daypart-aware availability tracking

Multiple observations per day with daypart recorded, since courier capacity is shared with rides and shifts at exactly the hours food demand peaks.

European and African menu pricing

Country as a dimension with FX per observation across markets that differ substantially in price level and merchant mix.

Cross-surface comparison

Restaurant and grocery surfaces on a shared schedule with the price setter recorded, so the difference is an observation rather than a blend.

Market presence monitoring

markets_observed per batch, so an entry or exit appears as a structural change rather than as lost coverage.

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

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

Bolt Food is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Bolt Food 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 food & restaurant data covers, and a Bolt Food-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

Bolt Food data scraping: frequently asked questions

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

Because courier capacity is pooled across rides, food and grocery. Peak ride demand pulls capacity away from food at exactly the hours food demand also peaks.

So a restaurant can be serviceable at one hour and not another with nothing changing at the restaurant, and promise times move for the same reason.

No. Fleet allocation is one plausible cause among several and it is not observable.

We record the observation with its daypart and set the cause field to not attributed.

Multiple observations per day rather than one. A single daily observation lands at an arbitrary point in a pattern that moves with fleet load.

This is the timing argument applied to a supply constraint rather than to price movement.

Different surface. Here the merchant sets the price; there the platform sets it for its own stock. Availability also means different things — a restaurant pausing versus a store being out of an item.

Where both are collected they share a schedule so a cross-surface comparison holds.

Yes, and we record markets_observed per batch rather than assuming a fixed list — so an entry or withdrawal appears as a structural change rather than as a silent drop in coverage.

We quote individually. Daypart count multiplies volume here, so it is the main variable alongside market count.

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

See real Bolt Food 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