Restaurant Nutrition Data: How Restaurant-Tech Teams Track Menu Calories and Allergen Changes (2026 Guide)

Introduction

A diet app still shows last quarter's calorie figure for a popular burger. The chain changed its recipe last month, and the official number is now different. A meal-planning tool still lists a sauce as sesame-free after the supplier changed. Stale menu data is more than an inconvenience – for allergens it can mislead people.

Restaurant nutrition data is the structured record of calories, macronutrients and allergen information that restaurants publish for their menu items on nutrition pages, PDFs, delivery apps and menu boards. Restaurant-tech teams collect it, standardise it by item and portion, and monitor it for changes so apps and analytics stay current.

This guide is for restaurant-tech, nutrition and diet apps, food-service distributors, QSR brands and health-tech teams. It explains the rules that make restaurants publish this data, where it lives, which fields to capture, how to detect changes, and when to build or buy.

Last updated: 9 October 2026 | Author: Actowiz Solutions Data Team

Why does restaurant nutrition data exist in the first place?

Most public restaurant nutrition data exists because menu labelling and allergen laws require it. Large chains in several countries must show calories on menus, and food businesses must give allergen information for non-prepacked food.

That legal backbone matters for data teams in three ways:

• Coverage is predictable. Chains above a size threshold publish more consistently than small independents.
• Formats follow the rule. Calories per portion, a daily reference statement and allergen matrices appear because regulators ask for them.
• Changes follow menus. Recipe changes, new suppliers and limited-time offers all trigger updates that a static dataset will miss.

Nutrition and allergen data is also commercially useful. Diet apps need it to log meals, health-tech platforms use it in meal recommendations, distributors use it to check product specifications, and QSR brands benchmark their menus against competitors.

What do the rules require in each country?

Requirements differ by country, so a global restaurant nutrition data project must record which rule applies to each item. The table summarises the main official rules we checked today; always confirm current requirements with the regulator.

The 14 allergens listed in the GOV.UK guidance are celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, peanuts, sesame, soybeans, sulphur dioxide and sulphites (above 10 parts per million), and tree nuts. Australia's list differs slightly – for example, FSANZ asks for each tree nut to be named separately – so store allergens as a country-aware code list, not free text.

Where does restaurant nutrition data live?

Restaurant nutrition data is spread across several public sources, and each one behaves differently. The richest source is usually the chain's own nutrition page or PDF; delivery apps add calories but rarely full nutrition panels.

• Chain nutrition pages. Item-level calories, macronutrients and allergen filters, often with a nutrition calculator.
• Nutrition and allergen PDFs. Full tables by item and size, typically versioned by date. These are the most complete and the hardest to parse.
• Delivery apps and online menus. Calories by item where the law requires online display (for example in England), sometimes allergen notes.
• In-store menu boards and kiosks. The legal display point for calories, but not practical to collect at scale; use the chain's digital equivalents instead.
• Restaurant ordering websites. Item pages with portion sizes and customisation options.

Actowiz Solutions has delivered projects collecting menu calories and nutrition data from public restaurant nutrition pages. Our restaurant menu scraper and food data scraping services cover these sources; for packaged-food labels, see our nutrition data for grocery SKUs in Singapore example.

Which fields should a menu nutrition dataset include?

A useful dataset records the item, the portion, the nutrients, the allergens and the evidence behind each value. Without portion and source fields, two calorie numbers for the same burger cannot be compared.

Example values are illustrative only. Keep "contains" and "may contain" separate, and never convert a missing allergen field into "allergen-free".

How do you detect nutrition and allergen changes?

Change detection means saving every version of each item's data, comparing it with the last version, and alerting only on meaningful differences. This is what turns a one-off scrape into a monitoring service.

A practical restaurant allergen tracking workflow:

• Capture on a schedule. Collect nutrition pages, PDFs and delivery menus daily or weekly, depending on how often the chain updates.
• Version everything. Store the raw file (HTML or PDF) with a hash, so you know instantly whether anything changed.
• Parse to structured rows. Extract tables from PDFs into item-level fields; keep the page or table reference.
• Diff by item key. Match items across versions using chain + item name + portion, then compare each field.
• Classify the change. New item, removed item, calorie change, macro change, allergen added, allergen removed, portion change.
• Set alert rules. Allergen additions or removals are high priority; small rounding changes in calories can be low priority.
• Review and publish. A human checks high-priority alerts against the source before downstream apps update.

PDF diffing needs care: column shifts, merged cells and footnotes can look like changes. Compare parsed values, not raw text, and keep the before/after snippet in each alert.

Who uses menu calorie and allergen data?

The main buyers are teams that put menu items in front of consumers or make decisions about menus.

• Nutrition and diet apps – let users log restaurant meals with up-to-date calories and macros.
• Restaurant-tech platforms – power allergen filters, menu search and dietary tags.
• Health-tech and meal-planning services – recommend items that fit a plan, with clear disclaimers.
• Food-service distributors – check how customers' menus use their products and spot reformulations.
• QSR brands – benchmark calorie ranges, portion sizes and allergen-free options against competitors. Our food delivery market intelligence work adds price and availability context, as in this menu and pricing tracking case study.

What are the accuracy and compliance caveats?

Restaurant nutrition data is informational. It reflects what the restaurant published at the time of capture, and recipes, suppliers and preparation can change before a dataset is refreshed.

• Not medical advice. Apps should state that data is for general information and is not a substitute for professional advice.
• Allergens: confirm with the restaurant. Consumers with allergies should always check with the restaurant before ordering. Cross-contact in kitchens is common and not always captured online.
• Show the date and source. Display "as published by the restaurant on [date]" so users can judge freshness.
• Public data only. Collect publicly available business information, respect site terms and applicable law, and avoid logins, paywalls or CAPTCHA workarounds. Menu data contains no personal data and should stay that way.

Should you build or buy a nutrition data pipeline?

Build if you track a handful of chains in one country and have engineers to maintain PDF parsers. Buy when you need many chains, several countries and reliable change alerts.

Ask any provider how they handle PDF changes, how they separate "contains" from "may contain", and how quickly they flag allergen changes.

Frequently Asked Questions

What is restaurant nutrition data?

Restaurant nutrition data is the set of calories, nutrients and allergen details that restaurants publish for their menu items. It usually comes from chain nutrition pages, downloadable PDFs and delivery apps. Data teams standardise it by item and portion size so apps, distributors and brands can compare menus and track changes over time.

Which restaurants must show calories on menus?

It depends on the country. In the US, chains with 20 or more locations must show calories under FDA rules. In England, businesses with 250 or more employees must show kcal per portion. In India, FSSAI rules cover establishments with a central licence or 10 or more outlets. Australian states run their own kilojoule schemes.

What are the 14 allergens?

Under EU and UK rules they are celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, peanuts, sesame, soybeans, sulphur dioxide and sulphites above 10 parts per million, and tree nuts. Australia uses a similar but not identical list, so datasets should store allergens with country-specific codes.

How often should menu allergen data be updated?

Weekly is a common baseline, with daily checks for chains that change menus often or run frequent limited-time offers. More important than frequency is versioning: keep each published version, diff it against the last one, and alert immediately when an allergen is added or removed so downstream apps can update quickly.

Can apps rely on scraped allergen data?

Apps can use published allergen data to help users filter menus, but it should never be the final word. Show the source and capture date, label it as informational, and tell users to confirm allergens with the restaurant before ordering. Recipes and kitchen practices can change faster than any dataset refreshes.