Restaurant menu datasets

Menu items and prices,
delivered to your bucket.

Our data team builds restaurant menu datasets to your list of brands and stores. Every item keeps its section, price, size options and the URL it came from.

Sample restaurant_menus.parquet
Illustrative menu rows in the delivery schema, with section, item, variant, price, currency and source
item_namemenu_sectionvariantpricecurrencysource_name
Pepperoni pizzaPizzasLarge13.09USDDoorDash
Chicken wingsSides8 pieces8.99USDChain ordering page
Caesar saladSaladsRegular7.49USDDoorDash
Garlic breadSides4.99USDChain ordering page
Iced teaDrinksMedium2.79USDDoorDash
source_url and crawled_at on every row
Trusted by 150,000+
companies
of all sizes
[ 01 / 08 ]
·
Datasets
//
Datasets
//

Datasets we build

Menu datasets are custom builds: you name the brands, stores or regions, and we scope the fields and refresh schedule with you.

Delivery app store menus

[ CUSTOM ]

Full DoorDash store menus in the US and Canada, with categories, items, descriptions, prices, images, item ratings and size or topping options. Store hours, cuisines and fees come with each store.

jsonparquetcsv
DoorDash
US and Canada stores · weekly or monthly

Chain menus by store

[ CUSTOM ]

Store-level menus from pizza and quick-service chains, with variants, sizes, toppings and the price at each location.

jsonparquetcsv
Restaurant chain ordering pages
Per store, US and Canada · weekly or monthly

Menu price tracking

[ CUSTOM ]

Repeated snapshots of the same stores, so price changes, new items and removed items show up as dated rows you can compare.

parquetcsv
Any of the sources above
From your first delivery · weekly or monthly
Need something else?

Describe the sources and fields, and our data team builds a custom dataset from Alexandria's data providers, web pages and PDFs.

Request a custom dataset
[ 02 / 08 ]
·
Sources
//
Sources
//

Where the data comes from

Every dataset is built from Firecrawl Alexandria and the full Firecrawl search and scrape suite.
[ FIRECRAWL ALEXANDRIA ]
400+

data sources behind one API

Every dataset starts in Firecrawl Alexandria. Our data team picks the right sources for your build.

Explore providers
[ BEYOND ALEXANDRIA ]

...and the full Firecrawl search and scrape suite

Our data team can also build datasets from any public page, PDF or site outside Alexandria with the same API teams use to search, scrape and interact with the web at scale.

Need a specific source? Tell us what you need and we'll build it as a custom dataset.

Request a custom dataset
[ 03 / 08 ]
·
Sample
//
Sample
//

Restaurant menu dataset sample

The common fields, one row per menu item. Every field is customizable to your requirements: add, rename or drop columns when we scope the build.
[ 04 / 08 ]
·
Use cases
//
Use cases
//

What teams build with it

Who orders menu data and what they do with it.
  1. [ 01 ]

    Menu price benchmarking

    Restaurant brands and pricing teams compare their prices with nearby competitors, store by store, and watch how they move week to week.

  2. [ 02 ]

    Food and menu trend research

    Foodservice manufacturers, distributors and research firms track which items, ingredients and price points spread across menus.

  3. [ 03 ]

    Menu onboarding for ordering platforms

    Online ordering and POS platforms import a merchant's menu as structured items and options instead of retyping it.

  4. [ 04 ]

    Nutrition and diet apps

    Apps that log meals or filter dishes start from menu items, descriptions and published calories for the restaurants their users visit.

[ 05 / 08 ]
·
Delivery
//
Delivery
//

Delivered your way

Choose the slice, the file format and where it lands. Every row keeps its source URL and crawl date.
[ FILE FORMAT ]
Parquet, JSONL or CSV
parquetjsonlcsv
[ CONTENT ]
Markdown, the original files, or both
markdownhtmlpdfdocx
[ DELIVERY ]
A download link or your own bucket
downloads3gcsr2
[ UPDATES ]
Once, monthly or weekly
oncemonthlyweekly
[ LICENSING ]
Open licenses only, or unstated licenses flagged
open-onlyflagged
[ PERSONAL DATA ]
As published, or names, emails and phones redacted
as-publishedredact
Every row carries
doc_idurlsource_nametitledoc_typedoc_formatjurisdictionpublished_atcrawled_atmarkdownraw_htmlpdf_uritoken_countrights_basislicense
[ 06 / 08 ]
·
How it works
//
How it works
//

From request to delivery

Our data team confirms the size of every slice before anything is delivered.
  1. [ 01 ]

    Pick a dataset or describe one

    Choose from the catalogue, or tell us the sources, fields and volume you need for a custom build.

  2. [ 02 ]

    Choose the slice and delivery

    Narrow it by brand, store, region or refresh period, then pick the format, licensing filter and destination.

  3. [ 03 ]

    Review a sample

    Ask for about 1,000 rows first, so you can check the fields and coverage before the full delivery.

  4. [ 04 ]

    Get the full set and refreshes

    The dataset lands in your bucket or as download links, then refreshes weekly or monthly if you choose.

[ 07 / 08 ]
·
FAQ
//
FAQ
//

Frequently asked questions

Coverage, fields, licensing and delivery for restaurant menu data.
Menu data
Ordering and delivery
[ 08 / 08 ]
·
More datasets
//
More datasets
//

Other dataset categories

Every category ships in the same delivery format, so datasets combine in one pipeline.
//
Get started
//
Get a sample of restaurant menu data.
Our data team scopes the slice with you and sends about 1,000 rows before the full delivery.
Are you an AI agent? See setup options