Platform · Tesco

Tesco Data Scraping Services

With Clubcard Prices captured as a separate field, because on most promoted lines that is the price people pay.

Tesco data scraping is the automated collection of publicly visible Tesco groceries data — shelf price and Clubcard Price as separate fields, own-label tier, computed unit pricing, promotional mechanics, availability and the Whoosh rapid delivery range — structured so that loyalty-gated pricing is never confused with the shelf price.

Tesco runs two prices on a large share of promoted lines: the shelf price and the Clubcard Price. Clubcard penetration is high enough that the member price is the modal transaction price. A dataset holding only the shelf price describes a market almost nobody shops in.

Get a free sample See sample data

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

tesco_prices.jsonl LIVE FEED

{"tesco_product_id":"301884412", "name":"Example Coffee Beans 1kg", "shelf_price":18.00, "clubcard_price":13.50, "effective_price":13.50, "clubcard_ends":"2026-08-18", "own_label_tier":"third_party_brand", "unit_price_computed":1.35, "unit_basis":"per_100g", "unit_price_displayed":"£1.35/100g", "promo_mechanic":"clubcard_only", "is_whoosh":false,"in_stock":true} {"tesco_product_id":"301884998", "own_label_tier":"exclusively_at_tesco", "clubcard_price":"null", "clubcard_reason":"no_clubcard_price_on_line"}

2 of 41,200 SKU rowsClubcard captured on 31.4% of lines · schema v4.1

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

Tesco at a glance

How we handle Tesco specifically

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

Platform: Tesco.com groceries, including Whoosh rapid delivery range where available
The core field: Clubcard Price captured separately from shelf price, with effective price computed
Own-label tiers: Finest, core Tesco and value tiers classified, plus Exclusively at Tesco brands
Unit pricing: Computed by us on a consistent basis per category, not taken from display
Promotions: Mechanics normalised: multibuy, meal deal, Clubcard-only, price cut
Availability: As exposed publicly, with substitutions captured where shown
Refresh: Daily standard; more frequent around promotional cycle changes
Region: United Kingdom; Republic of Ireland on request

Platform specifics

What makes Tesco data different from other grocers

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

Clubcard Prices change the answer, not just the number

This is the field that determines whether Tesco data is usable. Clubcard Prices are displayed publicly alongside the shelf price, and on promoted lines the gap is substantial.

Index direction can invert. A competitor 4% above Tesco on shelf price can be 3% below on Clubcard Price. Those are opposite competitive pictures from the same underlying data.
Promotional intensity is understated. Clubcard pricing is promotion by another name. Excluding it makes Tesco look less aggressive than it is.
Elasticity models break. A model fitted on shelf prices is fitted against a price most volume did not transact at.

We capture shelf_price and clubcard_price as separate fields with a computed effective_price, plus the Clubcard promotion end date where displayed. Where a line has no Clubcard Price, the field is null with a reason code rather than being backfilled with the shelf price.

Own-label tier is the analysis, not a label

Tesco's own-label architecture spans a value tier, the core Tesco range, Finest at the premium end, and a set of "Exclusively at Tesco" brands that do not carry the Tesco name at all.

That last group is where most datasets fail. Brand-name matching will not identify them as own-label, so private label share comes out understated and the branded-versus-own-label price index is computed against the wrong population.

We classify tier using maintained brand mappings rather than name matching, so own_label_tier is reliable across all four groups. For anyone tracking private label competition, this is usually the field the whole analysis rests on.

Unit pricing we compute ourselves, and Whoosh as a separate range

Unit prices are displayed on Tesco listings, but display conventions vary by category — per 100g, per kg, per litre, per item, per sheet. Taking the displayed figure produces a dataset where cross-category and cross-retailer comparison quietly breaks.

We compute unit price ourselves on a consistent basis per category and retain the displayed value alongside, so both are available and any discrepancy is visible rather than hidden.

Whoosh, Tesco's rapid delivery service, carries a narrower range and can price differently. We treat it as a separate range with its own records rather than merging it into the main catalogue, because merging makes Whoosh's smaller assortment look like main-range availability gaps.

Scope

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

Shelf price and Clubcard Price as separate fields, with effective price computed
Clubcard promotion end dates where displayed
Own-label tier including Exclusively at Tesco brands, via maintained mappings
Unit price computed by us on a consistent basis, with the displayed value retained
Promotional mechanics normalised, including multibuy and meal deal
Availability as publicly exposed, with substitutions where shown
Whoosh rapid delivery range as separate records
Category and search placement with sponsored slots flagged
Ratings and review text without reviewer profiles

❌ What we do not, and why

Clubcard prices visible only after signing in, if any are gated that way
Individual Clubcard account data, points balances or personalised offers
Store-level stock beyond what Tesco exposes publicly
Availability revealed only by adding items to a basket
Reviewer names, profiles or review histories

Core Tesco fields

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

Field	What it is on this platform
tesco_product_id	Tesco's own product identifier, the reliable join key here
shelf_price	The standard price, before any loyalty pricing applies
clubcard_price	The Clubcard Price where displayed, null with a reason code where absent
effective_price	Computed from the loyalty price where present, otherwise the shelf price
clubcard_ends	Clubcard promotion end date where Tesco displays it
own_label_tier	value, core, finest or exclusively_at_tesco, via maintained brand mappings
unit_price_computed	Computed by us on a consistent per-category basis
unit_price_displayed	The figure Tesco displays, retained so discrepancies are visible
promo_mechanic	Normalised mechanic: multibuy, meal_deal, clubcard_only, price_cut
is_whoosh	Whether the record is from the Whoosh rapid delivery range
in_stock / substitution_shown	Availability and whether a substitute was offered

Use cases

What teams do with Tesco data

Competitive indexing that survives loyalty pricing

Shelf and Clubcard prices are held separately with an effective price computed, so a price index reflects what shoppers actually pay rather than a shelf price most volume did not transact at.

Private label share and branded price gaps

Own-label tier including Exclusively at Tesco brands is classified via maintained mappings, so private label share and the branded-to-own-label index are computed against the right population.

Promotional intensity measurement

Clubcard-only promotions are captured with end dates alongside conventional mechanics, revealing Tesco's true promotional depth and cadence by category.

Unit-normalised range comparison

Unit prices computed on a consistent basis make pack architecture differences comparable across Tesco and other grocers, which display conventions otherwise obscure.

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

Send us a Tesco 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 inside two business days
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.

Tesco is usually collected alongside its competitors

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

Tesco data scraping: frequently asked questions

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

Yes, as a separate field with a computed effective price. This is the most important field in Tesco data. Clubcard penetration is high enough that the member price is the modal transaction price on promoted lines.

Where a line has no Clubcard Price, the field is null with a reason code. We never backfill it with the shelf price, because that single substitution can flip a competitive index from above-market to below-market.

Using maintained brand mappings rather than name matching, because the Exclusively at Tesco brands do not carry the Tesco name at all.

Name matching misses that group entirely, which understates private label share and computes the branded-to-own-label index against the wrong population. For private label analysis this is usually the field the whole exercise rests on.

Because display conventions vary by category — per 100g, per kg, per litre, per item — so taking the displayed figure makes cross-category and cross-retailer comparison break quietly.

We compute on a consistent basis per category and retain the displayed value alongside, so both are available and any discrepancy is visible rather than absorbed.

Yes, as a separate range with its own records rather than merged into the main catalogue.

Merging matters: Whoosh carries a narrower assortment, so folding it into the main catalogue makes its smaller range look like main-range availability gaps. Keeping them separate lets you analyse either without corrupting the other.

Only as far as Tesco exposes it publicly, which is limited compared with some US retailers. Online pricing is largely national with some regional variation.

We tell you during scoping exactly what store-level granularity is available rather than implying store precision the source does not provide. Overstating granularity is worse than reporting the national view honestly.

We quote individually. Drivers are category scope, SKU count, refresh frequency and whether Whoosh coverage is included. Full-catalogue coverage costs more than a defined category set.

A defined category at daily refresh sits at the lighter end; full catalogue with Whoosh and sub-daily promotional-period collection sits higher. One scoping call, a free pilot on your own categories within 24 hours, then a fixed monthly quote. Request a quote.

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