Food Delivery Menu Data: Benchmark Prices, Fees & Promotions on Uber Eats
Food delivery data scraping gives restaurant operators, analysts and delivery-market teams a structured view of how menus are built and priced on the apps customers actually use. A store page on Uber Eats holds sections, dish names, descriptions, prices, a rating and cuisine tags. Collected at scale, that becomes a menu price benchmark.
To show what this looks like in practice, we pulled a small free sample: 112 menu items from four Chicago restaurants. You can download it on the Uber Eats Chicago sample dataset page. This post walks through what the sample contains, what the numbers say, and how to use this kind of data without fooling yourself.
One note up front: delivery fees and delivery times are the fields people ask about most, and they are the ones this sample does not contain. We explain why below.
Why food delivery data scraping matters for pricing
A restaurant's delivery menu is often priced differently from its in-store menu, and nobody outside the business can easily see how competitors price theirs. Delivery apps are the one place where a whole neighbourhood's menus sit side by side in a consistent format.
Teams use that for a few things:
- Competitive pricing. Compare your burger, bowl or pizza against the same category nearby.
- Menu engineering. See how many items a competitor lists per section, and which dishes they push into featured slots.
- Market entry. Check typical price levels for a cuisine before opening a ghost kitchen or a new location.
- Product building. Train menu-classification, recommendation or price-prediction models on real listings.
For the wider picture of which platforms are worth collecting from, see our guide to target platforms for data collection.
What our Uber Eats sample shows
The sample covers four restaurants chosen from the Chicago city page: a pizza chain, a burrito chain, a Thai restaurant and a Nigerian kitchen. We kept up to 28 items per store, 112 rows in total. All figures below are computed from that CSV, so treat them as a snapshot of four stores, not a statement about the whole Chicago market.
Headline numbers
- Across all 112 items, the average listed price is $21.97 and the median is $15.75. The gap between the two shows a long tail of expensive items.
- Prices range from $3.25 to $85.00. The top of that range is a catering-size order at the burrito chain; the bottom is a side item.
- 28 items (25%) are under $10, and 36 items (32%) are over $20.
- 32 of 112 items (29%) carry the popular flag.
Popular items are not cheaper by default. The average popular item costs $19.62 (median $19.99), against $22.92 (median $13.99) for the rest. The averages suggest popular items are cheaper, but the medians point the other way. The difference comes from the non-popular group containing both the cheap sides and the expensive family and catering bundles. Looking at the average alone would mislead you.
Store-level differences are large:
| Restaurant | Rating | Items | Avg price (USD) | Median price (USD) | Popular items |
|---|---|---|---|---|---|
| Rosati's Pizza (1518 W Chicago Ave) | 4.3 | 28 | 35.19 | 36.39 | 10 |
| Chipotle Mexican Grill (230 W Monroe) | 4.6 | 28 | 24.10 | 12.95 | 0 |
| Silver Spoon Thai Restaurant | 4.6 | 28 | 12.17 | 12.24 | 2 |
| Nigerian Kitchen | 4.4 | 28 | 16.44 | 19.99 | 20 |
The pizza store averages $35.19 because pizzas and party-size items are priced per pie. The Thai restaurant has the tightest range, from $8.99 to $21.99. The burrito chain's average of $24.10 is pulled up by bundles; its median of $12.95 is closer to what a single customer pays.
Section averages show where price is set. In this sample, Pizza items average $39.29, Family Meals average $69.53, Appetizers average $12.55 and Sides average $3.57. Section structure matters as much as the dishes themselves: a "Family Meals" section is a deliberate upsell.
Data quality is good but not perfect. 7 of the 112 items have no description, and the review count is capped at 1000 for the busiest stores, so it should be read as "1000 or more".
About fees and promotions
The title of this post mentions fees and promotions, so here is a straight answer. In our sample, delivery fee and delivery time (ETA) are not in the data. On Uber Eats those values depend on the delivery address, the time of day and sometimes the customer's account, so they are not part of the public store page's structured data. The same goes for most promotions and member-only discounts.
What you can compare reliably is the listed menu price. If you need fee and ETA benchmarks, you need to collect them for a fixed set of delivery addresses and times, and record those inputs next to every value. Anything else produces numbers that look precise but cannot be compared.
Which fields matter and why
| Field | Why you want it |
|---|---|
item_price_usd |
The core benchmark. Compare by cuisine and section, using medians as well as averages. |
menu_section |
Lets you group like with like, and shows upsell structures such as family bundles. |
is_popular |
Marks items the store features. Useful for seeing where a restaurant places its anchor price. |
item_name, item_description |
Needed to match equivalent dishes across stores or to train classifiers. |
restaurant_rating, review_count |
Context for whether higher prices go with higher ratings. |
cuisine |
Segmenting the market. |
store_url, scraped_at_utc |
A stable key and the capture time, which you need for any time series. |
Practical use cases
Restaurant groups can check whether their delivery prices sit above or below nearby competitors in the same cuisine, and whether competitors are pushing bundles.
Delivery and market analysts can track average item price by cuisine over time and flag stores that change prices.
Food-tech teams can use menu text and prices as training data for item classification, allergen tagging or price suggestions.
Consultants and investors can sample a city's menus to get a first read on price levels before commissioning a larger study.
Common challenges
Anti-bot measures. Delivery apps are actively protected, and a plain request can work one day and fail the next. Reliable collection needs a managed setup that can escalate from plain requests to residential IPs and browser rendering when needed.
Location dependence. What you see depends on where the request appears to come from. Fix the geography and record it.
Large, nested menus. One store can list hundreds of items across many sections, with the same dish repeated in a featured section and its regular one. Deduplicate by section and name, and decide up front how you treat repeated items. In our sample, an item counts as popular when it also appears in the store's featured section.
Modifiers and sizes. A "Build Your Own Pizza" at 12, 14 and 18 inches is three rows with three prices. Compare like sizes, not item counts.
Layout changes. Store pages change. Parsers that depend on the embedded structured data break less often than ones that depend on page markup, but both need monitoring.
How often to refresh
Menu prices on delivery apps change more often than most people expect, so the right schedule depends on the question:
- Weekly is enough for market-level benchmarks by cuisine.
- Daily suits competitive monitoring of a defined set of rivals.
- Several times a day only makes sense if you are also tracking fees, ETAs or promotions, and then only with fixed delivery addresses.
Always keep the capture time so you can build a time series later. The same logic applies to other price-sensitive categories; our post on grocery price monitoring with Tesco data covers refresh rhythm for supermarket shelves.
FAQ
Is it legal to collect Uber Eats menu data? We collect only public store pages, with no login and no personal data. Legal questions depend on your jurisdiction and use, so check the platform's terms and talk to your own counsel before building a commercial product on the data.
Can I get delivery fees and ETAs? Not from the public page alone. They vary by address and time, so they need to be collected for fixed addresses and recorded together with those inputs.
How many restaurants can you cover? This sample has four. A full dataset can cover many more restaurants, other cities and a scheduled refresh. Tell us your target and we'll scope it.
Why does the average price differ so much from the median? Menus mix cheap sides with large bundles. The median is closer to what a typical single item costs, so report both.
Get a sample of your own target
If you want menu data for your own city, cuisine or list of competitors, request a free sample of your own target and we'll send you a CSV like the one described here. Datasets start from $49; see pricing. For a different industry, take a look at our Zomato restaurant sample, and download the Uber Eats Chicago sample to test the fields against your own workflow.
Author: DataHarbor Team