DishMark

Five decisions, then one consolidated report.

Nothing about the shape of your search is decided for you, and nothing about how much of it we managed to cover is hidden from you.

  1. 01

    Choose the area

    Enter a town, village, city, full postcode or postcode district, then pick a radius from 5 to 100 miles. You can instead select a whole county or administrative area, or combine several areas into one report. The selection is drawn on a map, with the establishment count, before you commit.

    England, Wales, Scotland, Northern Ireland, the Scottish islands, the Channel Islands and the Isle of Man are all selectable.

  2. 02

    Choose the establishments

    Pubs, restaurants, cafés, coffee shops, cafeterias, buffets, fish and chip shops, kebab shops, burger restaurants, pizza restaurants, bars, breweries and taprooms, food trucks and ghost kitchens. Narrow further by cuisine, by service type, by ownership, or by which delivery marketplaces an establishment appears on.

    Leaving a filter empty includes everything, rather than silently applying a default.

  3. 03

    Say what to analyse

    Search complete menus, or focus on particular dishes, menu sections, ingredients, dietary claims or price bands. If you only care about what a cheeseburger costs, the report can be only that.

    Dishes are matched to a canonical taxonomy, so "Cod & chips (reg)" and "regular cod and chips" are benchmarked together.

  4. 04

    Choose the cadence

    A one-off market snapshot, or weekly or monthly monitoring for twelve months. Recurring reports perform fresh discovery alongside re-checking the establishments already known, so newly opened sites appear and closures are flagged.

    Each recurring report is compared against the one before it, and every change is listed with its evidence.

  5. 05

    Read it, or export it

    Your report appears in the portal as soon as it is built. Download it as a combined PDF, an Excel data workbook, a CSV of the benchmark table, or audit JSON containing every observation with its source and timestamp. Add recipients and they get their own secure link.

    Every format is generated from the same frozen result, so the dashboard and the workbook cannot disagree.

What happens between you clicking build and the report appearing

Most menu-benchmarking tools crawl the whole area the moment you ask, which is why they take hours. DishMark does the collecting beforehand.

DishMark maintains a continuously-refreshed index of UK food businesses and the menus they publish. Discovery and menu reading happen on a background cadence, against the areas our customers actually monitor.

When you build a report, we resolve your area, select the establishments in it, and check how recently each one was read. Anything already current is used immediately. Anything stale is queued for collection, and the coverage funnel tells you precisely how much of your report was already current and how much was collected for it.

The result is that a report over a well-covered area is ready in under a second, and a report over an area we have never seen still returns immediately with whatever is known, rather than making you wait for a crawl to finish.

Where the time goes
Resolve your area
no network calls — area data is held locally
Select establishments
one indexed geospatial query
Check freshness
one aggregate over the selection
Collect what is stale
queued; the report does not wait
Aggregate every section
run concurrently, from precomputed prices
Freeze the result
written once, so re-reads are instant
Freshness is reported, never assumed
Every figure carries the date it was read. If part of your area was last checked a week ago, the report says so rather than presenting stale prices as current. Read the methodology.