Platform · Esselunga

Esselunga Data Scraping

Dense where it trades and absent from most of the country. A panel here is regional, whatever the client's report calls it.

Esselunga data scraping collects pricing, promotions and availability from this Italian grocer. The point that matters for any analysis built on it: the retailer is dense in a small number of northern regions and absent from most of Italy. A panel here is a regional panel, and treating it as an Italian benchmark overstates what it can support.

Italy is one of the most regionally fragmented grocery markets in Europe. This retailer is the clearest example of why a national Italian figure needs several sources.

Get a free sample See sample data

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

esselunga_2026-08-25.jsonl LIVE FEED

{"retailer":"esselunga","region":"Example region", "name_local":"as published, Italian", "price":3.45,"currency":"EUR", "price_vat_basis":"incl_vat_as_displayed", "is_own_label":true,"own_label_tier":"standard"} {"is_variable_weight":true, "approx_pack_weight":420,"price_per_kg":14.90, "caution":"displayed price is an ESTIMATE. treating it as fixed skews all of fresh"} {"matchable_share_category":0.39, "region_coverage_note":"northern regions only. NOT an Italian figure"}

3 of 404,110 product rows · Italy, northernregional panel, stated as regional · schema v1.0

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

Esselunga at a glance

How we handle Esselunga specifically

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

Retailer: Esselunga — Italy, northern-concentrated
The point: Dense in a few regions, absent from most
So: A panel here is regional, not Italian
Italian market: Highly fragmented by region and operator
Own label: Strong, spanning tiers
Area conventions: Italian listings use varying pack conventions
Online: Available in served areas only
Refresh: Daily. Promotional cycles run weekly

Platform specifics

Regional density in a fragmented market

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

A strong regional benchmark is not a national one

Italian grocery is fragmented by region to a degree that surprises people used to the UK or France. Different operators lead different regions, and several large operators have no presence at all in parts of the country.

This retailer is dense where it trades and absent elsewhere. That produces a specific analytical risk:

A panel built here is representative of its regions and of nothing beyond them.
An "Italian price index" from a single operator describes wherever that operator trades.
Regional price levels differ materially across Italy, so the error is not small.
The composition problem compounds if operators are added or dropped mid-series.

region_coverage_note ships per batch naming the regions the panel represents and stating that it is not national — the same discipline our US regional grocery page applies to America.

What a national Italian panel needs

Several operators, each covering its own regions, with region as a dimension and no pooled national average unless you ask for one as a computed rollup.

Own label, and Italian pack conventions

Own label

Own-label penetration is strong and spans tiers. Flagged with own_label_tier from range naming, matched within the retailer, unmatched across retailers — as everywhere.

Because penetration is high, the matched share for a cross-retailer index is smaller than it looks. We report matchable_share_category before quoting.

Pack conventions

Italian listings vary in how pack size is expressed, and fresh categories use approximate weights extensively.

Variable-weight items display an approximate pack weight with a per-kilogram price. The displayed price is an estimate.
Treating it as fixed introduces systematic error in fresh categories.
We flag is_variable_weight and record both the per-kilogram price and the approximate pack weight, rather than presenting one derived figure.

VAT and unit pricing

Handled as on our European grocery page — VAT basis recorded as displayed and never adjusted, unit price computed alongside the displayed one with disagreement flagged.

Online coverage, and what we do not produce

Online is area-limited

Online ordering is available in served areas rather than nationally, and the online range is a subset of in-store range.

fulfilment_area is recorded where exposed, and range_note states that online is a subset. We do not infer in-store range from online listings.

What we do not produce

A national Italian figure from this retailer alone. Available as a computed rollup across several operators if you scope them.
In-store-only prices. Not published online.
Loyalty account data. No accounts created, in any market.
Sales, volumes, customer or employee data.

Names

Italian product names retained exactly, with translation additive only — the position our multilingual page sets out.

Scope

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

region_coverage_note per batch, stating the panel is regional
region as a dimension, with national figures only as computed rollups
matchable_share_category reported before quoting
own_label_tier from range naming, unmatched across retailers
is_variable_weight flagged, with per-kilogram price and approximate weight both recorded
VAT basis as displayed, never adjusted
Unit price computed alongside the displayed one, disagreement flagged
Italian names retained exactly, translation additive only
fulfilment_area where exposed, with range_note on online coverage

❌ What we do not, and why

A single-operator panel presented as an Italian figure
A variable-weight price treated as a fixed-pack price
In-store range inferred from the online catalogue
Own label matched across retailers
Loyalty account data, sales, customer or employee data

Core Esselunga fields

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

Field	What it is on this platform
retailer / region / fulfilment_area	The regional footprint is the point
product_id / ean	Identifiers where published
name_local	Italian, retained exactly
price / price_vat_basis	As displayed. Never adjusted
is_variable_weight / approx_pack_weight / price_per_kg	Estimate flagged, both figures kept
pack_size / price_per_unit / unit_basis	Computed by us
displayed_unit_price / unit_price_matches	Theirs, and whether it agrees
is_own_label / own_label_tier	From range naming
matchable_share_category	Reported before quoting
region_coverage_note / range_note	What the panel and the catalogue represent
observed_at	Timestamp

Use cases

What teams do with Esselunga data

Northern Italian regional benchmarking

A dense regional panel with the coverage note stated, which is the right reference for anyone competing in those regions and not beyond them.

Italian national index assembled correctly

Region as a dimension across several operators, since no single Italian operator covers the country and regional price levels differ materially.

Fresh category analysis with variable weight handled

Variable-weight items flagged with both the per-kilogram price and approximate weight, rather than a derived figure that treats an estimate as fixed.

Own-label positioning in a high-penetration market

Own label flagged with tier and the matched share reported, so a cross-retailer index states how much of each category it actually compared.

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

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

Esselunga is usually collected alongside its competitors

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

Esselunga data scraping: frequently asked questions

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

Not on its own. The retailer is dense in a small number of northern regions and absent from most of Italy, so a panel here represents those regions and nothing beyond them.

Italian grocery is fragmented by region to a degree that surprises people used to the UK or France, and regional price levels differ materially. We ship a coverage note saying what the panel represents.

Several operators, each covering its own regions, with region as a dimension. A national average is available as a computed rollup if you ask, with the operator and region detail retained.

Flagged, with both the per-kilogram price and the approximate pack weight recorded. We do not present a single derived figure.

The displayed price on a variable-weight item is an estimate, and treating it as fixed introduces systematic error across fresh categories.

Because own-label penetration is high, and own label has no equivalent at another retailer — no shared identifier, no matching product.

So a cross-retailer index runs on a smaller set than the catalogue size suggests. We report the share per category before quoting.

No. Online ordering is available in served areas rather than nationally, and the online range is a subset of in-store.

We record the fulfilment area where exposed and state that online is a subset, rather than inferring in-store range from online listings.

We quote individually on category scope, SKU count and refresh. This sits at the lighter end for a European grocer because the footprint is concentrated.

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

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