Platform · Morrisons

Morrisons Data Scraping

The same product, from the same retailer, at three different prices depending on which app you opened.

Morrisons data scraping collects product listings, pricing and availability from Morrisons' own channel and, where in scope, from the third-party delivery platforms its range also appears on. That is the distinguishing point: Morrisons products are sold through several surfaces at different prices, so a single Morrisons price does not exist and a feed that reports one has silently picked a surface.

A UK shopper can buy the same Morrisons product on Morrisons' own site or through two or three delivery apps, at different prices. Which of those is 'the Morrisons price' is a question the data has to answer explicitly.

Get a free sample See sample data

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

morrisons_2026-08-25.jsonl LIVE FEED

{"surface":"own_channel","price_setter":"morrisons", "ean":"50011*** redacted", "price":2.15,"currency":"GBP", "multibuy_mechanic":"3 for 2", "is_own_label":true,"own_label_tier":"core"} {"surface":"third_party","platform":"platform-a", "ean":"50011*** redacted","price":2.65, "note":"same product, same retailer, different surface — neither is THE price"} {"price_loyalty":"null", "gated_reason":"loyalty_signin_required", "gated_share_category":0.22, "caution":"standard price NOT substituted"}

3 of 604,220 product-surface rows · UKsurface on every record · markup not inferred · schema v1.0

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

Morrisons at a glance

How we handle Morrisons specifically

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

Retailer: Morrisons — United Kingdom
The distinguishing point: Its range also sells on third-party delivery platforms
Consequence: Several prices for one product, depending on the surface
So: A single Morrisons price does not exist
Price setter: Morrisons on own channel; frequently marked up on third-party
The critical field: surface, on every record
Vertical integration: Own manufacturing means own-label depth is unusual for the UK
Refresh: Weekly on own channel; faster where third-party promotional activity matters

Platform specifics

What multi-surface distribution does to a price series

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

Three surfaces, three prices, one product

Morrisons sells through its own website and through third-party delivery platforms. The same product frequently carries different prices on each.

Own channel is Morrisons' own pricing.
Third-party platforms frequently carry a markup, because the retailer is covering platform commission.
The markup is not constant across products or platforms, so it cannot be corrected with an adjustment.

Why this is not a detail

A competitor benchmarking Morrisons on third-party platform prices will conclude Morrisons is more expensive than it is. Benchmarking on own-channel prices misses what a large and growing share of shoppers actually pay.

Neither is wrong. Both are wrong if you do not know which one you have.

surface is on every record and the surfaces are never blended. Where you take more than one, the same product arrives as separate records with the platform named — the same rule our Uber Eats page applies from the platform side.

Vertical integration makes own label behave differently

Morrisons owns manufacturing and food production capacity to a degree unusual among UK grocers. That has a practical consequence for the data rather than being a corporate-history footnote.

Own-label depth is greater in categories where it manufactures, and the tiering within them is more developed.
Own-label price movement can be independent of branded movement in those categories, because the cost base is not a supplier's price.
Fresh and prepared categories carry a higher own-label share than a typical UK grocer.

As everywhere, own-label lines are flagged and marked unmatched across retailers — no shared identifier, no equivalent product, never paired on name similarity.

What is worth measuring here specifically is the divergence between own-label and branded movement within a category. On a retailer buying everything in, those tend to move together. Where manufacturing is owned, they need not.

UK grocery mechanics, and what we will not compute

Multibuys and loyalty pricing

UK grocery leans heavily on multibuy mechanics and loyalty-card pricing. We capture mechanics as displayed and keep them separate from base price.

We do not compute an effective unit price on a multibuy, because a three-for-two effective price depends on whether the shopper buys three — a basket we cannot see. The same position as our Ocado Zoom page.

Loyalty-gated prices

Where a price requires a loyalty card, we record it only if it is publicly displayed to an anonymous visitor. Where it is gated, the field is null with a reason and we report the gated share — and we never substitute the standard price, for the reason set out on our Whole Foods page.

Unit pricing

UK law requires a displayed unit price. We capture it, compute our own from parsed pack data, and flag disagreement, which is usually a listing error worth surfacing.

Scope

What we collect on Morrisons, 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 on every record — own channel and third-party platforms never blended
price_setter recorded, since third-party listings frequently carry markup
Own label flagged, with tier where a category carries more than one
Own-label versus branded movement measurable within a category
Multibuy and loyalty mechanics as displayed, separate from base price
Loyalty-gated prices null with a reason, and the gated share reported
Displayed unit price captured, with our computed value and disagreement flagged
Pack parsed, with unit price on a stated basis
In-stock state per surface, since availability differs

❌ What we do not, and why

A single Morrisons price presented without naming the surface
An effective unit price computed from an assumed multibuy basket
Standard price substituted where a loyalty price was gated
A markup inferred where only one surface is observed
Own label matched across retailers on name similarity

Core Morrisons fields

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

Field	What it is on this platform
surface / platform	own_channel or the named third-party platform
price_setter	Morrisons, or the platform arrangement where different
product_id / ean / ean_missing_reason	Identifiers, with nulls reasoned
price / currency	Price on this surface
price_loyalty / loyalty_price_public / gated_reason	Loyalty price only where publicly shown
gated_share_category	Reported per category, per batch
multibuy_mechanic / multibuy_text	As displayed, separate from base price
is_own_label / own_label_tier / cross_retailer_matched	Flagged, tiered, unmatched across
unit_price_computed / unit_price_displayed / unit_price_matches	Ours, theirs, agreement
in_stock	Per surface, since availability differs
observed_at	Timestamp

Use cases

What teams do with Morrisons data

Effective competitive position across surfaces

Own channel and third-party platform prices as separate records, so a benchmark reflects what shoppers on that surface actually pay rather than a figure that is right for one channel and wrong for the others.

Platform markup measurement

Where both surfaces are in scope, the difference is an observation you compute from two records rather than a percentage we assert.

Own-label versus branded divergence

Where manufacturing is owned, own-label prices need not move with branded ones — a divergence worth measuring and one most UK grocers do not produce.

UK multibuy intensity

Mechanics captured as structures separate from base price, so promotional depth is measurable without an effective price resting on an unobservable basket.

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

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

Morrisons is usually collected alongside its competitors

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

Morrisons data scraping: frequently asked questions

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

There isn't one, and that is the point of the page. Morrisons sells through its own site and through third-party delivery platforms, and the same product frequently carries different prices on each because the retailer is covering platform commission.

Neither figure is wrong. Both are wrong if you do not know which you have. surface is on every record.

Where both surfaces are in scope, yes — as an observation you compute from two records. Where only one is observed, no.

The markup is not constant across products or platforms, so an inferred figure would be a model presented as a measurement.

Because where a retailer owns manufacturing, own-label prices need not move with branded ones — the cost base is not a supplier's price. On a retailer buying everything in, they tend to move together.

That divergence is measurable here and is a finding most UK grocers' data does not produce.

No. A three-for-two effective price depends on whether the shopper buys three, which is a basket we cannot see.

We capture the mechanic as displayed and keep it separate from base price, so you can apply whichever basket assumption your analysis needs rather than inheriting ours.

Recorded only where publicly displayed to an anonymous visitor. Where gated, the field is null with a reason and we report the gated share per category.

We never substitute the standard price — that would show the retailer as less promotional than it is, and show it confidently because the column is populated.

We quote individually. The main variable is how many surfaces are in scope — own channel alone is a conventional UK engagement, and each third-party platform adds a full set of records.

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

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