UK QSR Menu Price Data: Tracking Starbucks, Costa, Greggs, Pret and McDonald's Prices (2026 Guide)

Introduction

A latte in a London station, a sausage roll in Leeds and a Big Mac meal ordered on a delivery app can carry three different prices from the same brand. For pricing and revenue management teams, that spread is the whole story. QSR menu price data is how you see it.

What is QSR menu price data? QSR menu price data is a structured, store-level record of what quick-service and coffee chains charge for each menu item, captured from public chain menus and delivery apps such as Just Eat, Uber Eats and Deliveroo. It shows price by location, channel, size and promotion over time, so teams can benchmark and track change.

This guide explains how UK chains such as Starbucks, Costa, Greggs, Pret and McDonald's price by location and channel, which public sources to track, the fields worth capturing, and how pricing, franchise and insight teams use the data. Our restaurant chains, orders, menus and pricing API covers the collection layer this guide describes.

Why does UK QSR menu price data matter in 2026?

Price pressure has not gone away. The ONS reports that the 12-month CPI rate for restaurants and hotels was 4.1% in August 2026, up from 4.0% in July (Source: ONS, Consumer price inflation, UK: August 2026). Chains are deciding, item by item, how much of their cost growth to pass on.

Company reports show the same tension. Greggs said its like-for-like cost inflation was about 5.5% in 2025, and that where savings could not offset costs it used "careful pricing activity". It expects input cost inflation of around 3% in 2026 (Source: Greggs plc, Preliminary Results for 2025, March 2026).

Channels are also shifting. Greggs reported that delivery reached 6.8% of company-managed shop sales in 2025, and its app was scanned in 26.7% of company-managed shop transactions, up from 20.1% in 2024 (Source: Greggs plc, 2026). When more orders run through apps and aggregators, a single "menu price" is no longer enough. You need the price in each channel.

Who uses it? Typical buyers include:

• QSR and coffee-chain pricing / RGM teams benchmarking core items against direct competitors.
• Franchise groups checking that franchised stores follow recommended prices and promotions.
• Restaurant-tech and delivery-tech companies building menu, pricing or market-mapping products.
• Analysts and consultants tracking inflation pass-through and value positioning across the sector.

How do UK chains price by location?

Most large UK chains do not charge one national price. Public evidence points to three common patterns, and good menu price tracking should capture all three.

• London vs regions. Central London, airport and station stores often sit on higher price tiers than suburban or regional stores. Older public evidence shows the spread within London alone: a 2017 Londonist survey of 57 McDonald's branches found Big Mac meal prices ranging from £4.09 to £4.69 (Source: Londonist, 2017). The prices are dated, but the pattern of tiered pricing is the point.
• Travel hubs and alternative sites. Stations, airports, motorway services, hospitals and campuses often have their own pricing. Greggs says over half of its new openings were in alternative sites such as forecourts, retail parks, hospitals and university campuses, with planned openings at Manchester Airport and several railway stations (Source: Greggs plc, 2026).
• Franchised vs company-operated stores. Franchise partners may have pricing freedom within brand guidance, which can create small local differences on the same item.

Because these tiers are rarely published as a list, the practical way to map them is to capture prices store by store, then group stores into tiers using postcode, site type and region.

In-body image: qsr-price-channels-uk.webp – alt: Diagram of in-store, chain app and delivery app menu prices for one UK store

In-store vs app vs delivery app: where do prices differ?

The same item can show different prices in each channel. Delivery platforms charge restaurants commission, and some restaurants raise menu prices on apps to recover it. In a 2021 investigation, Which? found one restaurant dish priced at £12.95 direct, £13.95 on Just Eat and Uber Eats and £14.95 on Deliveroo, and restaurants told Which? they paid 15% to 35% commission (Source: Which?, June 2021). That example is an independent restaurant, not a chain, but it shows why delivery app markup UK analysis needs item-level data.

For chains, compare these price points for the same store and item:

• In-store / own-website menu price where the chain publishes one (often by store).
• Own-app price, including app-only deals that are visible without logging in.
• Aggregator menu price on Just Eat, Uber Eats and Deliveroo for the same store.
• Fees around the item – delivery fee, service fee and small-order fee shown publicly at checkout preview, kept separate from the item price.

Price differences between channels are a store-and-time-specific fact. Record them as observed values with timestamps, for example for the median aggregator-vs-in-store gap on a core coffee item.

Which chains and sources should you track?

Start with the brands and public sources below. Each chain publishes menus differently, so coverage and price visibility vary by source.

Public price surveys show why the competitive set matters. A January 2025 analysis by Vouchers4real, using Uber Eats prices from 82 UK towns and cities, put the average hot drink price at £2.22 at Greggs, £3.85 at Caffè Nero, £3.88 at Pret, £4.05 at Costa and £4.28 at Starbucks (Source: Vouchers4real via Public Sector Catering, January 2025). That is a useful coffee chain price comparison UK benchmark, and also a reminder that it reflects delivery-app prices, not in-store prices.

For chain-level collection detail, see our McDonald's UK food data scraping, Costa Coffee restaurant data scraping and Starbucks food data scraping work.

In-body chart: uk-coffee-chain-hot-drink-prices-2025.webp – alt: Average UK hot drink price by coffee chain, Uber Eats data, January 2025

What data fields should QSR menu price data include?

A useful dataset is more than item name and price. These are the fields we recommend for UK QSR menu price data, in snake_case so they load cleanly into a warehouse.

Two fields deserve special care:

• size / variant – coffee prices change by size and milk. Without this field, a "latte price" comparison mixes small and large cups.
• captured_at – menu price tracking is only useful over time. Timestamps let you see price changes, new items and removed items.

How does calorie labelling help with menu data?

Calorie data is now part of the public menu in England. Under the calorie labelling rules that came into force on 6 April 2022, businesses with 250 or more employees must show the energy content of food in kcal, refer to the portion size, and display the statement "adults need around 2000 kcal a day" (Source: GOV.UK, Calorie labelling in the out of home sector: implementation guidance).

The guidance also says the requirement extends to food sold on a website or mobile app, including third-party delivery apps. The rules apply to food sold in England only.

For data teams this has two benefits. First, calorie values are a strong matching key – the same item on the chain site and on Deliveroo usually carries the same kcal value, which helps link listings across channels. Second, calorie data supports price-per-portion and healthier-menu analysis. Do not treat this as legal advice; it simply shows why kcal is worth capturing.

How to collect, clean and match UK QSR menu prices

• Define the store sample. Pick stores by region, London vs non-London and site type (high street, station, airport, retail park, forecourt). A national picture needs a spread, not just central London.
• Collect from public menus. Capture chain website menus and public aggregator store pages on a set schedule – weekly for benchmarking, daily around launches and price reviews.
• Normalise items. Map item names across channels ("Flat White Regular" vs "Flat white"), split sizes and milks, and separate meal bundles from single items.
• Match across channels. Use chain + store + item + size, with kcal as a tie-breaker, to line up in-store, app and aggregator prices.
• Quality-check. Flag outliers, missing prices, duplicate stores and sudden jumps before data is delivered. See our price monitoring and price intelligence guide for QA steps.
• Deliver and track change. Send data as CSV, JSON, API, S3 or Snowflake, with a change log of new, removed and repriced items.

How do teams use QSR menu price data?

• Price benchmarking. Compare core items – coffee, breakfast roll, burger meal – against a defined competitor set by region and site type.
• Inflation pass-through. Track menu prices against ONS restaurant and hotel inflation to see which chains passed on cost growth, and on which items.
• Franchise compliance. Check that franchised stores show the recommended price and the current national promotion, and flag stores that drift.
• Delivery-channel pricing. Measure the gap between in-store and aggregator prices by chain and city to inform delivery pricing and fee strategy.
• Menu change and new-item tracking. Spot seasonal launches, limited-time items and removals as they appear on public menus.
• Market mapping for restaurant-tech. Feed store, menu and price coverage into product and sales planning.

An anonymised example: a coffee-and-food-to-go brand wanted to compare its station-store prices with nearby competitors. We captured public prices for a set of core items across stations and high streets in several UK regions, on both chain menus and delivery apps, and delivered a weekly file with a change log. Results are reported qualitatively here; site-tier price gaps would appear as.

Legal and compliance basics

• Public data only. Collect prices, menus and calorie values that are publicly visible, without logging in or bypassing paywalls.
• Respect site terms and robots rules, and keep request rates modest.
• No personal data. Do not collect customer reviews tied to identities, account data or staff details.
• Member prices. Include loyalty or subscription prices only where the chain publishes them openly.
• This is general information, not legal advice.

Build vs buy: choosing a menu price data provider

An in-house scraper can work for a few stores. At UK scale – thousands of stores, four or more channels, frequent menu changes – most teams look for a provider. Ask each provider:

• Coverage: which chains, stores and channels (own site, Just Eat, Uber Eats, Deliveroo)?
• Freshness: what refresh cadence, and how fast are new items picked up?
• QA: how are sizes, meal deals and duplicate stores handled?
• Delivery: CSV, JSON, API, S3 or Snowflake? Is there a change log?
• Security and usage rights: how is data stored and what may you do with it?
• Sample: can you see a sample for your own chains and cities first? We typically deliver one within 48 hours.

Key takeaways

• QSR menu price data shows what UK chains charge by store, channel, size and promotion over time.
• UK chains price by location tier – London, regions and travel hubs – so national averages hide real gaps.
• Delivery app prices can differ from in-store prices; compare them item by item with timestamps.
• England's calorie labelling rules make kcal a reliable field for matching items across channels.
• Use the data for benchmarking, inflation pass-through and franchise compliance.

Frequently Asked Questions

What is QSR menu price data?

It is a structured record of the prices that quick-service and coffee chains list for each menu item, by store, size, channel and date. It is collected from public chain menus and delivery apps such as Just Eat, Uber Eats and Deliveroo.

Do UK chains charge different prices in London?

Many do. Public surveys show price differences between branches, with station, airport and central London stores often priced higher. The only reliable way to measure it is store-level price capture grouped by region and site type.

Are delivery app prices higher than in-store prices in the UK?

Sometimes. Which? found restaurants raising app prices to recover 15% to 35% commission in 2021. Gaps vary by chain, store and item, so measure them directly rather than assuming one markup.

Do calorie labels appear on delivery apps in England?

Yes. GOV.UK guidance says the calorie labelling requirement for businesses with 250 or more employees extends to websites and mobile apps, including third-party delivery apps, for food sold in England.

How often should menu prices be tracked?

Weekly is enough for most benchmarking. Daily tracking helps around price reviews, launches and promotions. Choose the cadence by use case and budget.

Can you include loyalty or app-only prices?

Only where they are publicly visible without logging in. Member-only prices behind accounts are not collected.

Conclusion

You can also reach us for all your mobile app scraping, data collection, web scraping , and instant data scraper service requirements!