California's SB 68 Allergen Disclosure Law: A July 2026 Compliance Checklist for Restaurant Chains

If your restaurant operates 20 or more locations under the same name and at least one of them is in California, the menu you printed last month is probably already out of date. As of July 1, 2026, California's Senate Bill 68 — officially the Allergen Disclosure for Dining Experiences (ADDE) Act — requires covered chains to disclose the presence of the nine major food allergens on every standard menu item, across every menu format they use.

This isn't a niche compliance footnote. Food allergies affect an estimated 32 million Americans, including roughly 26 million adults and 5.6 million children, and about a quarter of all anaphylactic reactions happen while people are eating out. More than half of restaurant-related allergic reactions occur even after the customer told staff about the allergy. California just became the first state to turn that gap into a legal disclosure requirement, and other states are watching closely — which means this checklist is worth reading even if you're not headquartered in California today.

Who Actually Has to Comply​

SB 68 borrows its threshold from the federal menu-labeling rule (the same one that requires calorie counts on chain menus). You're covered if your restaurant meets all three of these conditions:

• 20 or more locations operating under the same name, counted nationwide — not just in California
• Substantially the same menu across those locations
• At least one location physically in California

The location count is chain-wide. A restaurant with 5 locations in California and 16 more spread across other states still hits the 20-location threshold and is covered. Conversely, a single-location independent restaurant or a small three-store local group falls outside the law entirely, regardless of how sophisticated its menu is.

Exemptions: compact mobile food operations (think food trucks and carts) and nonpermanent food facilities (temporary event stands, pop-ups) are explicitly excluded.

If you franchise, note that franchisors and franchisees typically share the "same name, same menu" characteristics that trigger coverage — don't assume franchise structure exempts individual locations from a chain-wide obligation. Confirm this with counsel before July 1 rather than after an inspection.

What Has to Be Disclosed​

Covered restaurants must identify the presence of the "Big 9" major food allergens in every standard menu item:

1. Milk
2. Eggs
3. Fish
4. Crustacean shellfish
5. Tree nuts
6. Peanuts
7. Wheat
8. Soybeans
9. Sesame

This list matches the FDA's federal major-allergen list (sesame was added federally in 2023, so if your allergen documentation predates that, it's already stale). The law requires disclosure of allergens "known or reasonably should be known" to be present — meaning documented recipe ingredients, not just what happens to be top-of-mind for the kitchen.

How Disclosures Must Be Formatted​

Restaurants have three acceptable approaches, and you can mix them across channels:

1. Direct menu placement — the allergen list appears immediately below or next to each menu item, on the physical page or screen.
2. Digital format with a written backup — a QR code or digital link is allowed, but only if you also offer a written alternative (a printed chart, grid, or booklet) for guests who can't or don't want to scan a code.
3. Standardized names or pictograms — common allergen names or recognized icons are acceptable in place of spelling out full ingredient lists, as long as they're unambiguous.

Critically, this applies everywhere a customer might order, not just the dine-in menu: printed menus, menu boards, drive-thru boards, self-service kiosks, your website, your mobile app, and third-party online ordering platforms (DoorDash, Uber Eats, Grubhub listings included, to the extent you control that content). A chain that updates its in-store menu boards but leaves allergen info off its app or delivery-platform listing is still out of compliance.

An 8-Step Path to July 1 Readiness​

Legal and compliance advisors covering SB 68 converge on roughly the same sequence. If you haven't started, this is the order that gets you there fastest:

1. Confirm you're covered. Count locations chain-wide, verify menu similarity across them, and confirm at least one California location. Document this determination — you'll want the paper trail if anyone ever asks why you did or didn't comply.
2. Document every ingredient in every standard menu item. This is the heaviest lift. You need a current, accurate ingredient list mapped to each of the nine allergens for each item — not a "best guess" from whoever wrote the original recipe card.
3. Coordinate with suppliers for current specs. Ingredient formulations change. A sauce that didn't contain tree nuts last year might today if a vendor reformulated. Get current spec sheets, not ones from your onboarding folder.
4. Pick your disclosure format(s) and update every platform. Decide on direct listing, digital-plus-backup, or a mix, then apply it consistently across menus, boards, kiosks, the website, the app, and delivery platforms — not just the channel that's easiest to edit.
5. Add a cross-contact disclaimer (optional but recommended). SB 68 doesn't require a shared-kitchen/cross-contact warning, but legal commentary consistently flags it as a low-cost way to reduce liability exposure alongside the mandatory allergen list.
6. Train staff on the new system. Front-of-house and kitchen staff need to know where allergen information lives, how to answer guest questions, and what to do when a guest flags an allergy — the disclosure requirement doesn't replace the need for a human response.
7. Build a change-tracking process. Menu items and supplier formulations change constantly. Assign ownership for reviewing allergen data whenever a recipe or supplier changes, so your disclosures don't quietly go stale six months from now.
8. Keep records and consult counsel. Maintain documentation of your allergen data, menu update history, and staff training — especially if you operate in multiple states with different (or no) allergen disclosure requirements, since a multistate compliance strategy needs legal review.

Enforcement and the Real Risk​

SB 68 is enforced by the California Department of Public Health, but the practical risk most legal advisors flag isn't a regulatory fine — it's civil liability. Once a restaurant has allergen information on the menu (mandatory) or a customer has verbally flagged an allergy (common), the bar for proving negligence in an allergic-reaction lawsuit gets lower. Legal commentary on SB 68 specifically warns that the new disclosure requirement is likely to increase allergy-related litigation against restaurant chains over the next year, simply because there's now a documented standard to measure a restaurant's conduct against.

That cuts both ways: chains that treat SB 68 as a real operational change — accurate ingredient documentation, trained staff, a maintained change-tracking process — build a defensible record. Chains that treat it as a one-time menu reprint create a paper trail of stale, inaccurate disclosures that's arguably worse than having none.

Common Compliance Mistakes to Avoid​

A few patterns show up repeatedly in early guidance on SB 68, and each one is an easy way to end up technically "disclosing" while still being effectively wrong:

• Treating the menu update as a one-time project. The biggest failure mode isn't skipping disclosure — it's disclosing once at launch and never updating it again. A seasonal special, a reformulated sauce, or a new supplier can silently introduce an allergen that isn't reflected on the menu three months later.
• Covering the dine-in menu but forgetting delivery platforms. Third-party ordering apps often pull menu data from a separate feed than your in-house POS or website. Updating one doesn't automatically update the others — each platform needs to be checked individually.
• Assuming franchise structure changes the analysis. Franchisors and franchisees sharing a name and menu typically both fall under the chain-wide location count. Don't wait for a corporate memo that may never come; confirm your specific obligation directly.
• Relying on memory instead of documented spec sheets. "The kitchen knows what's in the dish" isn't a defensible compliance record. Written, current supplier specifications are what actually protects you if a disclosure is ever challenged.
• Skipping staff training because the menu already lists allergens. A printed disclosure doesn't stop a guest from asking a server a follow-up question. Staff still need to know where to point, what the icons mean, and how to escalate an allergy concern to a manager or the kitchen.

Is This Just a California Problem?​

Not for long, probably. SB 68 is the first state-level law of its kind, but food-allergy advocacy groups have been pushing similar menu-labeling requirements in other statehouses for several years, and California's law is widely expected to become the template other states borrow from — much like California's Wayfair-era sales tax rules and privacy laws (CCPA) became de facto national standards once large chains built the compliance infrastructure once and applied it everywhere. If you operate in California today, the ingredient documentation, supplier coordination, and disclosure workflow you build for SB 68 is very likely infrastructure you'll reuse for the next state that passes something similar — so it's worth building it properly rather than as a one-off patch.

Why Your Records (Not Just Your Menu) Matter Here​

The compliance work behind SB 68 — ingredient documentation, supplier spec tracking, a change log every time a recipe or vendor changes — is fundamentally a recordkeeping problem, and it's easy to let it live in someone's inbox instead of a real system. The same discipline applies to the financial side of running a multi-location chain: if you can't produce a clean, auditable trail of what changed and when, you're exposed whether the question comes from a health inspector, a plaintiff's attorney, or your own accountant at tax time.

Keep Your Financial Records as Clean as Your Allergen Records​

Compliance deadlines like SB 68 are a good reminder that documentation you can actually produce — not documentation you assume exists — is what protects a growing restaurant chain. The same logic applies to your books. Beancount.io offers plain-text accounting that gives you a complete, version-controlled, auditable history of every financial change, so your records are as defensible as your allergen disclosures need to be. Get started for free and see why finance-savvy operators are moving to plain-text accounting.