Platform · MediaWorld

MediaWorld Data Scraping

In Italy, as across the EU, the crossed-out price has a legal meaning. So we keep the one the retailer shows, and do not invent our own.

MediaWorld data scraping covers product and price data from Ceconomy's Italian retailer — MediaMarkt under another name. Under the EU rules on price reductions, an announced discount must be set against the lowest price in the prior 30 days. So the reference price MediaWorld shows is recorded as displayed, with its stated basis, and our own 30-day low is a separate, labelled calculation from our own observations.

A discount percentage is only as meaningful as the price it is taken from. In the EU, that price has rules.

Get a free sample See sample data

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

mediaworld_sample.jsonl LIVE FEED

{"name_it":"as published","price":399.00,"reference_price_displayed":449.00,"reference_basis_text":"as worded on the page"} {"our_observed_30d_low":429.00,"derived_from_our_observations":true} {"note":"both shown. no conclusion drawn"}

illustrative sample rows · ITtwo 30-day lows, kept apart · schema v1.0

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

MediaWorld at a glance

How we handle MediaWorld specifically

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

Retailer: MediaWorld — Ceconomy, Italy
Same group as: MediaMarkt and Saturn
Reference price: The retailer's 30-day low, as displayed
Our 30-day low: Separate, labelled, from our own observations
Language: Italian names kept as published
Marketplace: Seller on every row where shown
Ownership: JD.com offer for Ceconomy pending (Sept 2026)
Refresh: Daily; hourly around promotions

Platform specifics

Two 30-day lows, and why they are kept apart

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

The reference price is the retailer's statement

Since the EU's price-indication rules were updated, a retailer announcing a price reduction must show the lowest price it applied in the prior 30 days as the reference. So the crossed-out figure is not decoration; it is the retailer's statement about its own history.

We record it as displayed, with any wording that states its basis.
We do not recompute it and overwrite it. The retailer knows every price it applied; we know the prices we observed.
Our own 30-day low from our own schedule is a separate field, labelled derived_from_our_observations.
Where the two differ, both are shown. We do not conclude that either is wrong.

So reference_price_displayed and our_observed_30d_low never share a column.

Italy, the group, and what we do not do

Italy as its own market

Italian product names, promotions and range, in euro. Nothing is translated in place; translation is additive.

The group

Same group as MediaMarkt, and its marketplace sellers are recorded the same way. JD.com's offer for Ceconomy was still awaiting approvals in September 2026; nothing about the data depends on it.

What we do not do

Overwrite the retailer's reference with our figure, call a discount compliant or non-compliant, or present our 30-day low as the retailer's.

Scope

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

reference_price_displayed with its stated basis
our_observed_30d_low as a separate, labelled field
Both shown where they differ, with no conclusion drawn
Italian names kept as published, translation additive
seller_name wherever a marketplace seller is shown
Promotion windows recorded as stated
Model numbers exactly as published
Shared schedule with other Ceconomy countries if wanted
Hourly collection around major promotions

❌ What we do not, and why

The retailer's reference price overwritten by our calculation
A discount judged compliant or non-compliant
Our 30-day low presented as the retailer's
Italian names replaced by translations
Account or customer data

Core MediaWorld fields

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

Field	What it is on this platform
product_id / model_number / name_it	As published
price / currency	As displayed
reference_price_displayed	The retailer's crossed-out figure
reference_basis_text	Its stated basis, if worded
discount_displayed	As shown
our_observed_30d_low	derived_from_our_observations
seller_name	Where not MediaWorld
promotion_name / window_stated	As published
stock_status	As displayed
name_en	Additive translation
observed_at	Timestamp

Use cases

What teams do with MediaWorld data

Promotion depth, measured properly

Discounts as the retailer states them, alongside what we observed, each labelled.

Italian electronics price monitoring

A daily series in euro with Italian names intact.

Cross-country Ceconomy comparison

One model across Italy, Germany and other markets, never converted.

Promotion calendars

Stated windows recorded, so a promotion's start and end are data.

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

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

MediaWorld is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. MediaWorld 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 consumer electronics data covers, and a MediaWorld-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

MediaWorld data scraping: frequently asked questions

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

We do, as a separate field. But the retailer's reference is its own statement about every price it applied, and we only see the prices we observed. So both are kept, labelled.

No. We show both figures. Whether a discount is compliant is a legal judgement, not a data one.

Same group; it is how the group trades in Italy. Its own site, range and promotions.

Only additively. Italian names stay as published.

No. The offer was still awaiting approvals in September 2026, and nothing in how prices are recorded depends on it.

It depends on categories and frequency. Adding MediaWorld to an existing Ceconomy collection is usually modest.

Talk to us.

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