SatStackdecks
01 / 10
CONFIDENTIAL — SALES OVERVIEW · Q4 2026
Food-delivery merchant network data

The restaurant supply network —
in daily detail.

A multi-platform, venue-level time series of the delivery economy: every restaurant on the major apps, every day — presence, ratings, review volume and churn, joined by a stable cross-platform merchant identity.

6platforms
Uber Eats · Just Eat · Wolt · Bolt · Glovo · Deliveroo
250k+/day
venue observations tracked daily
400+markets
cities & regions across 30+ countries
T+1
daily snapshots, point-in-time history
Alternative data for investment, credit and operating decisions · figures verified against current coverage
02 · The product

Not order data. The merchant network that order data depends on.

Consumer-transaction datasets measure demand. We measure the supply side — the asset base the platforms monetize: how many restaurants are listed where, how they're performing, and when they leave.

One stable identity across every app

Each merchant is matched across platforms into a canonical ID — chain-safe, city-aware. See the same restaurant on Wolt, Uber Eats and Just Eat at once, and watch it move between them.

WOLT UBER EATS JUST EAT one merchant · live on 3 apps · leaves Wolt on this date — the map updates daily
Illustrative

What's in a row

Per venue × platform × day:

Presence & online state Rating 0–5 (raw preserved) Review count & velocity Cuisine · chain · brand Coordinates · market · country Canonical merchant ID

Aggregates ship too: market-level counts, new listings, and a daily verified merchant-churn metric.

Aggregate-only · no PII, no review text · collected from public sources · GDPR-clean
03 · What it reveals

Four signals you can't get from quarterly data — or from static POI files.

Supply-side growth, platform by platform

Merchant-base counts per market are a leading indicator for platform revenue — visible in days, not quarters.

platform A — growing +22% 90d platform B — flat (−2%)
Illustrative

Churn — with a verified cause

Two very different events, one honest split: full closure (left the market) vs platform switch (moved to another app). Every candidate is re-probed live before it counts.

Aclosed Bswitched unverified→re-probe
Illustrative

Merchant health, at distance

Rating drift and review velocity per venue — plus detection of new openings from unrated-venue state, months before they appear in any registry.

venue rating path — healthy +0.3★ / 90d
Illustrative

The multi-homing map

Which merchants run on one app and which run on several — with 14,000+ cross-platform matches already resolved. Platform overlap and share shifts become measurable.

Wolt Uber ∩
Illustrative
All series are point-in-time: any historical date reconstructs the exact network state that day
04 · Use case — private equity & venture capital

Find the right target before the market does.

A daily origination screen over the entire restaurant universe: operators worth approaching now — healthy enough to buy, weak enough to want the conversation.

The signal

Merchants with sustained demand momentum loss — review velocity declining vs. their own baseline and vs. a healthy market — plus rating drift and thinning platform presence. Filtered for independence, recent activity, and confirmed still operating.

The action

Build a ranked universe of struggling-but-alive restaurant and SMB businesses, refreshed daily. Approach founders with current, verified store-level facts — not a directory scrape.

The value

Origination pipelines months ahead of brokers. Chain & brand footprint views for buy-and-build programs. Proof-of-life verification before any call is made.

Honest by design

This is a demand-momentum screen, not a bankruptcy oracle. Distress leads 6–18 months — we flag the decline curve and verify the merchant is trading now; your diligence layers the rest.

No warm call lists

Independent operators preferred, chains filtered out. Each candidate carries its current rating trajectory and review volume — the conversation opener is specific, not generic.

Portfolio monitoring

The same lens works after close: track how acquired stores perform, market by market, against every comparable in the network.

05 · Use case — trade credit & invoice insurance

You underwrite SMBs. Now you can see them weekly.

Your book's restaurant and food-SMB names rarely file anything useful before they fail. Their delivery footprint is a live, public operating proxy that updates every day.

The signal

Per-counterparty monitoring at portfolio scale: review velocity stalling, rating drift, venues going dark or leaving platforms, cross-platform presence shrinking — compared against the market baseline.

The action

Watch the whole book on one dashboard. Adjust limits, pricing and intervention on evidence — not on lagged financial filings or payment patterns that arrive too late.

The value

Early warning measured in months, not days. A defensible, dated evidence trail for limit decisions and, when needed, claims.

Point-in-time, always

Every observation is timestamped. Reconstruct exactly what a merchant's network looked like on any date — your side of any dispute is documented from day one.

One identity per borrower

Canonical merchant IDs mean one counterparty, one profile — even when it trades on two, three or four apps at once.

Coverage that matches your book

400+ markets across 30+ countries, EU-deep. If your insureds trade on food-delivery apps, they're in the dataset.

06 · Use case — funds & investment research

Delivery-platform fundamentals, before the prints.

For coverage of Uber, DoorDash, Just Eat Takeaway, Delivery Hero, Deliveroo, Wolt — the merchant network is the asset base those valuations rest on. We make it observable daily.

The signal

Merchant-base growth and churn per platform × market; new listings; multi-homing shifts — the supply-side momentum that precedes order and GMV trends.

The action

Model platform growth ahead of quarterly disclosures. Read per-market share movement from cross-platform churn: a merchant leaving app A for app B is market share you can see now.

The value

Daily, market-level, point-in-time supply data — the dimension your demand-side order/GMV feeds simply don't cover. 6 listed platforms exposed, one subscription.

Churn split = thesis-grade

Type A closures are a macro/liquidity gauge; Type B switches are a competitive tell. Reported separately, live-verified — never a single ambiguous number.

Market-level series

Counts, growth, churn and average rating per platform per market, aligned to the exact geography your models already use.

Clean provenance

Aggregate-only, public sources, no PII — a dataset your compliance desk clears, not fights.

07 · And more

The same network, many lenses.

SME & corporate lending

Credit monitoring

Live health checks on restaurant borrowers between financial statements — covenant-relevant signal for banks and alternative lenders.

Restaurant groups & franchisors

Portfolio benchmarking

Per-location performance vs. every comparable in the network; franchisee health and brand-standard compliance at a glance.

CPG & food brands

Channel presence

Where your products are available on delivery apps — and where competitors' are. Distribution and shelf analysis at chain + market level.

Retail real estate

Tenant & location viability

F&B tenant health and delivery density as a location-quality proxy for portfolios, leasing and development decisions.

M&A advisory

Target screening

Structured screening universes over thousands of operators, with current performance context for valuation and process design.

Macro & market research

Sector activity gauges

Restaurant-sector entry, exit and churn as regional consumption and small-business-health indicators.

If your question involves restaurants, food delivery or SMB health — ask. The lens set keeps growing.
08 · How it's built

A production pipeline, not a scrape.

01

Collect daily

Native collectors per platform read public discovery surfaces across 1,000+ probe points — cities, postcodes, grids — in scheduled daily sweeps.

02

Normalize

Schema-on-write into a warehouse; ratings normalized to 0–5 with raw scales preserved; cuisine, chain and brand enrichment applied.

03

Join identities

Venues are matched across platforms into a stable, chain-safe merchant ID — the layer that turns five app views into one restaurant.

04

Verify & deliver

Churn candidates are re-probed live — absence must be confirmed twice before it counts. T+1 delivery as CSV, Parquet or API.

Quality is the product

Capture floors per platform, watchdogged refresh windows, self-healing re-fires and anomaly guards run every day. Absence ≠ churn is a solved problem, not a caveat — that verification loop is the difference between a signal and a noise generator.

09 · Build vs. buy — honestly

You could build this. Here's the math.

Your team is exactly the one we'd expect to build it. That is precisely why we want you to see the full picture before you do. This is not a capability question — it's a cost and timing question.

Maintenance
✓ 6 platforms × 30+ countries operate on their own schedules. We absorb every surface change, rate-limit shift and anti-bot update as routine ops.
✗ Each platform changes its data contract on its own calendar. This is not a build — it's a permanent operational discipline with an on-call rotation.
History
✓ Accumulating since June. Churn and trend analysis need months of depth to mean anything — we're past that threshold and adding history every day.
✗ Your clock starts at zero. The first 3–6 months of a build produce data with no statistics attached to it.
Verification
✓ Live re-probe loops separate real closures from capture noise — absence must be confirmed, twice, from live sources.
✗ Untangling absence from noise is the hidden 90% of the cost — and the part most builds discover last, after the first false signal.
Focus
✓ Your team stays on the proprietary edge — the models, the overlays, the diligence — and leaves commodity plumbing to us.
✗ Your analysts price risk; a scraper team fights crawler blocks. The best builders are wasted on the commodity layer.
The hybrid path: if you need coverage or fields we don't ship, build the custom layer on top of our feeds. You keep the build budget for the part that's actually yours.
10 · Specs & next step

One conversation, then a pilot.

CadenceDaily snapshots, T+1 · history accruing since June 2026
Coverage6 platforms · 400+ markets · 30+ countries · ~250k venues/day
Identity layer14,000+ merchants matched across two or more platforms
MetricsMerchant counts, new listings, verified churn (A/B split), ratings, review volume
DeliveryCSV / Parquet / JSON — bulk or per-market · API on request
ComplianceAggregate-only · public sources · no PII · no review text · GDPR-clean

Sample the data

A real slice of venue snapshots and a daily series — see the grain, the ratings, the identity layer before any commitment.

Coverage check

Bring your universe — a portfolio, a market set, a watchlist. We verify what's in the data, honestly, before you license anything.

Pilot

Run your use case against the live feed for a defined period. If the signal isn't there, we don't expect a renewal.

Illustrative figures verified against current pipeline coverage · aggregate-only product · hello@satstack.group
use ← → keys