FDA Menu Labeling Calorie Disclosure for Chains, FALCPA Allergen Declarations, State Weights and Measures Portioning Rules and Food Safety Recordkeeping: Compliance for US Restaurant Costing Software

This article is part of our series on Custom Restaurant Recipe Costing Platform Development for US Restaurant Groups: Building an Invoice Price, Yield and Menu Engineering System

Introduction: Some of This Applies to You and Some Does Not

Restaurant costing compliance software has an unusual feature to deal with: the largest obligation applies only to operators above a threshold, and groups near it frequently do not know which side they are on.

Menu labeling requirements attach to covered establishments, defined by criteria including the number of locations operating under the same name and offering substantially the same menu. A growing group crosses that line at some point, and the obligations arrive with it.

Allergen exposure applies to everybody, though through different mechanisms than packaged food labeling. Portion representation applies to anybody who states a weight or a count.

And food safety recordkeeping applies to everybody, with traceability requirements for certain foods having developed and their timing having moved.

The connection to a costing platform is specific: these obligations describe recipes, and recipes change. This is educational content, not legal advice. Restaurant costing compliance software is the regulatory layer of the full custom software development guide to recipe costing platform development, and it shapes what appears in culinary and finance consoles.

FDA Menu Labeling Calorie Disclosure for Chains

Who Is Covered

The requirement attaches to covered establishments, with coverage determined by criteria including the number of locations doing business under the same name and offering substantially the same menu items.

Establishments not covered may elect to register voluntarily. A growing group should establish its position rather than assume it, since crossing the threshold brings obligations that take time to implement. The criteria themselves belong with counsel rather than in an article. Which obligations become concrete product features is mapped in Recipe Costing Software Features: Must-Haves in 2026.

What Must Be Disclosed

Calorie information for standard menu items on menus and menu boards, a statement about daily caloric intake, and additional written nutrition information available on request.

Temporary items, custom orders and certain other categories are treated differently. The specifics matter and belong with counsel rather than in a summary.

The Reasonable Basis Requirement

Declared values must have a reasonable basis, which concerns the method used to determine them: nutrient databases, laboratory analysis, cookbooks or other reasonable means, with documentation substantiating the figures.

Which is where a costing platform becomes relevant, because the substantiation describes a recipe, and a recipe that has changed no longer substantiates the declaration.

Allergen Declarations in a Restaurant Context

This area is frequently described loosely, and the distinction matters.

Federal food allergen labeling law governs packaged food, requiring major food allergens to be declared on labels. Restaurants serving food that is not packaged for retail sale are generally not subject to that labeling regime in the same way.

A restaurant’s exposure arises differently: from the accuracy of what it tells a guest who asks, from state and local requirements that have expanded in a number of jurisdictions covering menu notices, staff training and allergen awareness, and from the duty owed when a guest discloses an allergy and relies on the answer.

The foundation in every case is knowing what is in the food, which depends on ingredient-level information from suppliers, maintained as products change.

Supplier substitution is the recurring danger. A supplier shipping a different formulation of a sauce or a bread can introduce an allergen nobody in the kitchen chose, and the only defense is that the platform holds current ingredient documentation and surfaces changes.

And the boundary this framework holds absolutely: a platform records ingredient-level allergen information. It cannot account for shared fryers, shared surfaces, shared utensils or a cook under pressure, and it never describes a dish as safe for a guest. Obtain counsel, since requirements vary by state and locality. Establishing which of these apply to your group is the first job of a consulting engagement, as covered in Why Restaurant Group Leaders Need a Technology Consultant.

State Weights and Measures Portioning Rules

The surface operators think least about, and one that carries a straightforward exposure.

When a menu states a weight or a count, that is a representation about what the guest receives. State weights and measures authorities oversee such representations, and enforcement does occur in food service.

The particular complication is that a stated weight can refer to different things. A steak advertised at a weight may be describing the pre-cooked weight, and rules and guidance exist about how such claims should be made and qualified so a guest is not misled.

Which connects directly to portion specification in a recipe. If the menu says one thing and the specification says another, or if the specification drifts downward over time while the menu stays the same, the representation becomes inaccurate.

Drift is the realistic risk rather than deliberate misrepresentation. A portion reduced during a cost pressure period, a scoop size changed, a supplier delivering a smaller average piece.

So the design position: menu claims linked to the specifications that support them, a specification change surfacing the claim it affects, and no feature anywhere framed as reducing a portion while a stated weight remains. Obtain guidance from the relevant state authority.

Food Safety Recordkeeping and Traceability

The obligations that sit around a costing platform rather than inside it, and that share its underlying data.

Food safety regulation at the operating level runs through state adoption of a model code and local health jurisdiction enforcement, covering temperature control, sanitation, employee health, training and the records demonstrating each.

Supplier approval and the records showing where food came from are part of that, and they overlap directly with the supplier and ingredient data a costing platform holds.

Traceability requirements have developed. Federal rules require additional recordkeeping for foods on a designated list, concerning the ability to trace product through the supply chain, with the covered list and the compliance timetable both having been subject to change.

Groups handling listed foods should establish their current position rather than rely on any summary, since this area has moved and may move again.

The practical overlap with costing is real: a platform already holding supplier records, lot information where captured, and ingredient-to-recipe relationships is holding much of what a traceability exercise needs. Whether to build that connection deliberately is a scoping decision worth making explicitly rather than discovering during a recall. Verify current requirements with the agency and counsel.

Other Obligations

Health department permits and inspection requirements for each location. Employee food safety training and certified manager requirements, which vary by jurisdiction.

Local menu disclosure ordinances, which some cities and counties impose beyond federal requirements.

Country of origin and sourcing claims where a group makes them, since those are representations too. Organic, sustainability and welfare claims, which carry their own substantiation requirements. Dietary claims such as gluten-free, which has a defined regulatory meaning and is frequently used loosely on menus.

Advertising and promotional accuracy generally. Supplier agreements and specification compliance. Recall procedures and the ability to identify affected product quickly. And record retention across supplier, training and inspection documentation.

What This Means for the Build

Five positions follow and belong in a first release.

Declarations linked to the recipes they describe, so a recipe edit surfaces what it affects and routes it rather than completing silently.

Supplier product changes surfaced as events, since substitution is how an undeclared allergen most often arrives.

Allergen data recorded per ingredient with its source and date, presented as ingredient-level fact and never as a safety conclusion about a dish.

Menu claims including portion weights linked to the specifications supporting them, with specification changes surfacing the claims they touch.

And nutrition estimates, where the group produces them, recorded with the method used and requiring qualified review before anything is published.

None of these is expensive to build at the start, and together they are most of what restaurant costing compliance software amounts to. The first is the one most platforms lack entirely, and the one whose absence reaches guests.

Conclusion

Establish whether your group is covered by menu labeling rather than assuming. Link declarations to the recipes that substantiate them so a change routes for review.

Record allergen data as ingredient fact and never as a safety conclusion. And treat supplier substitution as the event it is.

Confirm the specifics with food regulatory counsel and a qualified nutrition professional, and verify traceability requirements with the agency since that area has moved. This is educational content, not legal advice, and it is worth briefing the software companies in the United States quoting you on where the platform’s job stops.

If you are scoping a costing platform, asking what currently happens when a chef changes an ingredient in a dish with a published calorie figure is the question most likely to surface a gap.

Frequently Asked Questions