Platform · Meal-kit platforms

Meal Kit Data Scraping

The advertised per-meal price assumes the biggest plan and a first-box discount. Almost nobody pays it.

Meal kit data scraping collects recipe ranges, plan structures and pricing from subscription meal-kit services. The pricing structure is the point: the advertised per-meal price typically assumes the largest plan size and an introductory discount, so it is the lowest number the service can honestly display and not what a continuing subscriber pays.

This is the Apartments.com concession problem in a different industry: a headline that is real, and reliably below what anyone pays after the first month.

Get a free sample See sample data

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

mealkit.jsonl LIVE FEED

{"service":"service-a","country":"GB", "advertised_per_meal":3.49, "advertised_plan_basis":"5 meals x 4 servings, with intro offer", "note":"the grid MINIMUM, with a discount. this is the number on the homepage"} {"plan_meals_per_week":3,"plan_servings":2, "plan_total_price":40.99,"per_meal_derived":6.83, "ongoing_per_meal":6.83, "note":"smallest plan, no intro. 96% above the advertised figure"} {"intro_discount_value":"null","intro_duration_boxes":"null", "ongoing_per_meal":"null", "ongoing_null_reason":"intro_terms_not_quantified", "shipping_cost":3.99}

3 of 44,220 service-plan rows · multi-marketa grid, not a price · both intro and ongoing delivered · schema v1.0

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

Meal-kit platforms at a glance

How we handle Meal-kit platforms specifically

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

Scope: Meal-kit and recipe-box subscription services
The headline: Per-meal price at the largest plan, with intro discount
Reality: Smaller plans cost more per meal
And: The intro discount expires
So: A price grid, not a price
Plan dimensions: Meals per week × servings per meal
Shipping: Frequently separate, and sometimes free above a threshold
Refresh: Weekly for recipe range; daily where promotional offers rotate

Platform specifics

A price grid, and an offer that ends

These are the reasons a Meal-kit platforms dataset needs its own handling rather than a shared retail schema.

Per-meal price is a function of plan size

Meal-kit pricing is a grid: meals per week by servings per meal. Per-meal cost falls as either dimension rises.

The advertised figure is almost always the grid's minimum — the largest plan.
A small plan can cost substantially more per meal than the headline.
So a single advertised price describes one cell of a grid and is presented as the product's price.

We deliver the full grid — every plan combination with its total and its derived per-meal figure — with plan_meals_per_week and plan_servings on every record.

advertised_per_meal is captured separately and flagged with advertised_plan_basis, naming which cell it corresponds to. A comparison between services on advertised figures compares two different plan sizes unless the basis is matched.

The introductory offer is not the ongoing price

Almost all of these services run introductory pricing — a discounted first box, frequently with further discounts across the first several deliveries.

The advertised per-meal price typically includes it.
It expires, on a schedule that varies by service.
So there are two prices: the one that attracts a subscriber and the one they pay from month two.
A comparison on advertised prices compares acquisition offers, not products.

We capture intro_offer_text as published, plus structured intro_discount_value and intro_duration_boxes where quantified, and ongoing_per_meal computed for each plan cell after the offer expires.

Both are delivered. The acquisition price and the steady-state price are different questions and both are legitimate — what is not legitimate is publishing one and calling it the price.

Shipping

Frequently separate and sometimes waived above a plan threshold. Captured as its own field, never folded into the per-meal figure, with shipping_waived_threshold where published.

Recipes, markets and what we do not collect

Recipe range

The weekly recipe range is a genuine competitive variable — breadth, dietary coverage and rotation rate all differ between services.

recipes_available_week, dietary_tags and recipe_rotation_rate are delivered, with premium or surcharged recipes flagged since those carry an additional per-serving charge.

Markets

Services operate different plan structures and price levels by country. country is a dimension and a cross-market comparison needs the plan basis matched as well as the currency.

What we do not collect

Subscriber counts, churn or revenue. Not published.
Account data or delivery addresses. No accounts created.
An ongoing price where the intro terms are not quantified. Null with a reason.
Ingredient sourcing or supplier data. Not published.

Scope

What we collect on Meal-kit platforms, 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

The full plan grid, with total and derived per-meal for every combination
plan_meals_per_week and plan_servings on every record
advertised_per_meal captured with advertised_plan_basis naming its cell
intro_offer_text as published, with structured value and duration where quantified
ongoing_per_meal computed per plan cell after the offer expires
Shipping as its own field, with waiver threshold where published
Recipe range, dietary tags and rotation rate
Surcharged premium recipes flagged
country as a dimension

❌ What we do not, and why

An advertised per-meal figure presented as the price
A cross-service comparison without matching the plan basis
An ongoing price computed where intro terms are not quantified
Shipping folded into the per-meal figure
Subscriber counts, churn, revenue or account data

Core Meal-kit platforms fields

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

Field	What it is on this platform
service / country	The service and its market
plan_meals_per_week / plan_servings	The grid dimensions
plan_total_price / per_meal_derived	For every cell
advertised_per_meal / advertised_plan_basis	The headline, and which cell it is
intro_offer_text / intro_discount_value / intro_duration_boxes	As published, and structured where quantified
ongoing_per_meal / ongoing_null_reason	After the offer, or why not computed
shipping_cost / shipping_waived_threshold	Separate. Never in the per-meal figure
recipes_available_week / recipe_rotation_rate	A real competitive variable
dietary_tags / is_surcharged_recipe	Coverage, and which carry extra
currency	As displayed
observed_at	Timestamp

Use cases

What teams do with Meal-kit platforms data

Plan-matched competitive comparison

The full grid with plan basis recorded, so two services are compared at the same meals-per-week and servings rather than at whichever cell each chose to advertise.

Acquisition versus steady-state pricing

Introductory and ongoing per-meal figures delivered separately, since the price that attracts a subscriber and the price they pay from month two are different questions.

Recipe range benchmarking

Weekly range, dietary coverage and rotation rate, which is where these services compete once price is normalised.

Surcharge structure analysis

Premium recipes flagged with their additional charge, which raises the realised per-meal cost above any grid figure.

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

Send us a Meal-kit platforms 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.

Meal-kit platforms is usually collected alongside its competitors

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

Meal-kit platforms data scraping: frequently asked questions

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

Because it typically assumes the largest plan size and includes an introductory discount — so it is the lowest number the service can honestly display.

A smaller plan costs substantially more per meal, and the intro discount expires. Almost nobody pays the headline on an ongoing basis.

By matching the plan basis. Each service advertises whichever grid cell produces the best number, so comparing advertised figures compares two different plan sizes.

We deliver the full grid with meals per week and servings on every record, and record which cell the advertised figure corresponds to.

Per plan cell, where the introductory terms are quantified. Where they are not — an offer described without a stated value or duration — it is null with a reason.

Both the acquisition price and the steady-state price are delivered, because they answer different questions and both are legitimate.

Captured as its own field and never folded into the per-meal figure, with the waiver threshold where published.

Folding it in would produce a per-meal number whose composition changes with plan size for two separate reasons at once.

Yes — it is where these services compete once price is normalised. Breadth, dietary coverage and rotation rate all differ.

We also flag surcharged premium recipes, which raise the realised per-meal cost above any grid figure.

We quote individually. Service count and market count drive it, since each service has its own grid structure and each market its own plan and price levels.

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

See real Meal-kit platforms 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