Foodini Logo
  • SB68
  • FoodTech
  • Stadiums & Events
  • Restaurants
  • Resources
  • Success Stories
Foodini Logo

Foodini - AI-Powered Dietary Intelligence

FacebookInstagramLinkedInTikTok

Solutions

  • FoodTech
  • Stadiums & Events
  • Restaurants
  • Software Integrations
  • SB 68 Solution
  • Foodini Software
  • Allergen Detection in 24 Hours

Resources

  • Featured Resources
  • All Resources
  • SB 68 Compliance Guide
  • SB 68 Compliance Requirements
  • MLB Allergen FAQ

Case Studies

  • All Case Studies
  • Wentworthville Leagues
  • Talisman Group
  • Rustic Root
  • Dalmar Hotel

Company

  • Mission
  • Privacy Policy
  • Terms of Service
  • Partner Terms of Service

© Copyright 2026 Foodini

Compliance & Legislation

Related resources

  • Compliance GuideLegislation & Guest Demands: Act NowLearn about the changing regulatory landscape and how to stay compliant while meeting customer expectations.5 min read
  • Policy UpdateNew York's Allergen Labeling Law: What Food Businesses Need to KnowComprehensive guide to New York's groundbreaking allergen labeling law for pre-packaged foods—requirements, deadlines, and compliance strategies.8 min read
  • Policy UpdateThe Tide is Turning: Michigan Joins the Movement for Safer DiningMichigan's House Bill 5402 proposes allergen disclosure requirements for all restaurants. Learn how this compares to California's law and what it means for your business.5 min read
  • Compliance GuideSB 68: Guide for Restaurant OperatorsEssential guide for restaurant operators on California's SB 68 allergen disclosure requirements and compliance strategies.8 min read
  • Compliance GuideSB68 Compliance Checklist for Restaurant Chains (2025)Your step-by-step roadmap to achieving full SB68 compliance: supplier verification, menu updates, staff training, and emergency protocols.5 min read
  • ExplainerWhat is SB68?Understanding California's landmark allergen disclosure law and its impact on the food service industry.3 min read
Browse all resources →Featured resourcesCase studies
Policy UpdateVirginia

The Allergen Law Nobody Saw Coming — and Why It Changes the Compliance Playbook

Virginia just signed the first state law that regulates what leaves the kitchen, not what the guest sees on the menu. It's a small statute with an outsized signal.

By Dylan McDonnell, Founder & CEO, Foodini | April 2026 | 8 min read

  1. Home
  2. ›
  3. Resources
  4. ›
  5. Virginia SB 183

The headline operators missed

On April 13, Governor Abigail Spanberger signed Virginia Senate Bill 183 into law. It takes effect July 1, 2026 — the same day California's SB-68 does. In the coverage cycle, Virginia got a fraction of the attention California received. It shouldn't have.

SB 183 is the first state allergen law in the United States that does something genuinely new. It doesn't regulate menus. It doesn't require QR codes. It doesn't mandate item-level disclosure. Instead, it requires that any restaurant that alters or substitutes a food item to accommodate a customer-identified allergy or sensitivity place an identifying marker — developed and standardized by the Virginia Board of Health — on that food item when it's prepared for delivery or carry-out.

That sounds narrow. It isn't. It's the first state to legislate the moment where most allergen incidents actually happen: the handoff from kitchen to customer.

Why this matters more than the word count suggests

For two decades, allergen litigation has told a consistent story. A guest communicates an allergy. Staff assure them the food is safe. Somewhere between the kitchen and the table — or the kitchen and the front door — the information gets lost. The dish that was prepared carefully gets swapped, mislabeled, or handed to the wrong person. The guest, trusting the assurance, eats it.

The two highest-profile cases of the last three years — Kanokporn Tangsuan's wrongful death at a Disney Springs restaurant in 2023, and Kayleen Brown's fatal pistachio reaction at a Florida high school in 2024 — both fit this pattern exactly. Verbal communication. Altered or substituted preparation. A breakdown at the handoff. A family left burying someone who trusted the system.

Virginia SB 183 is the first legislative response to that specific failure mode. It says: if you're altering food to accommodate an allergy, the food itself has to carry a mark that persists from the kitchen to the customer's hand. Not a verbal promise. Not a ticket pinned to an order. A physical, standardized marker on the item.

That is a meaningfully different compliance obligation than anything California, New York, Maryland, New Jersey, Illinois, or Missouri has on the table.

The gluten signal

Buried inside SB 183 is a second change that deserves attention on its own. The Virginia Board of Health is directed to develop markers for each major allergen — including gluten.

No other state allergen law currently mandates gluten disclosure. Federal law doesn't either. The FDA opened a review of gluten labeling standards in January 2026, and the industry has been watching to see which way that goes. Virginia has now answered the question for its own jurisdiction. Gluten is in. The practical allergen list in Virginia is Top 10, not Top 9.

For operators, that matters. For anyone with celiac disease — and I've had it since 2002 — it matters more. Gluten has been sitting in a regulatory gray zone for years: clinically serious, legally optional. Virginia just moved it out of that gray zone. Expect other states to follow, and expect the FDA review to accelerate.

The broader picture: regulation is moving from disclosure to operations

If you pull back and look at the last eighteen months of allergen legislation, the trajectory is clear.

  • California SB-68 (signed October 2025, effective July 2026) targets chains with 20+ national locations and requires Top 9 allergen disclosure on every menu item, physical or digital.
  • New York A6558A (signed November 2025, effective November 2026) applies to all food establishments regardless of size and requires written allergen notification on prepackaged food prepared and sold on premises.
  • Maryland HB 181, Michigan HB 5402, New Jersey S3394, Illinois SB3305, Illinois HB4686, Missouri HB3446 are all in committee or introduced, all applying to all operators with no size threshold, all requiring item-level allergen disclosure with digital delivery permitted.
  • Virginia SB 183 is signed, effective July 2026, applies to all restaurants, and requires physical markers on food at the point of fulfillment for altered or substituted items — including gluten.

The pattern is unmistakable. Scope is universalizing. California carved out big chains; every state that followed dropped the size threshold entirely. Allergen sets are expanding. Virginia added gluten; the FDA is reviewing it federally. The compliance surface is widening. Menus were the first battleground. Prepackaged on-premises food was the second. Delivery and takeout fulfillment is now the third.

Each new law adds a new layer of operational obligation. None of them are replacing the others. They stack.

What operators are underestimating

Most food service operators I talk to are still thinking about allergen compliance as a disclosure problem. Update the menu. Add a QR code. Train the staff. That's the California playbook, and it's necessary but no longer sufficient.

Here's what the post-Virginia reality looks like for a multi-state operator:

  • In California, you need per-item Top 9 disclosure on every menu and every third-party delivery platform by July 2026. Staff training is required alongside disclosure.
  • In New York, every piece of prepackaged food prepared on premises needs a written allergen notification by November 2026, regardless of whether you have one location or a thousand.
  • In Virginia, any time you alter a dish for an allergy — standard operating procedure at most full-service restaurants — you need a standardized physical marker on that food item when it leaves the kitchen for delivery or pickup, including for gluten.
  • In every other state with a pending bill, you should assume some version of the above is coming.

This isn't a menu redesign. It's a workflow integration problem. The operators who treat it as the former will spend the next three years in a permanent state of reactive compliance, updating laminated menus and retraining line cooks every time another state passes a bill.

The legal calculus has already shifted

There's a legal dimension to this that compounds the operational one. Once state disclosure statutes take effect, non-compliance doesn't just trigger regulatory fines — it triggers negligence per se. A plaintiff no longer has to prove the operator was unreasonable. The statutory violation IS the negligence.

Layer that on top of the two theories already in play:

  1. Strict products liability, where a plaintiff only has to show (a) the food contained an allergen, (b) it wasn't disclosed, and (c) it caused harm. No fault required.
  2. Breach of warranty, where any verbal or written representation that food is allergen-free — including menu labels and staff assurances — creates liability independent of negligence.

Post-July 2026, a non-compliant operator in California or Virginia faces all three theories simultaneously. And Virginia adds something neither California nor New York has: a statutory requirement that doesn't just apply to information given to the guest, but to the physical food itself. Failing to mark an altered dish isn't a disclosure failure. It's a fulfillment failure. And under SB 183, it's a statutory violation.

Juries have been awarding six-figure damages for allergen incidents where disclosure laws weren't even in effect yet. Massachusetts juries awarded $219,961 against a burrito chain in 2024 for serving a child a peanut-sauce dish despite a disclosed peanut allergy. Imagine the number when negligence per se is on the table.

What a defensible system actually looks like

Compliance-grade allergen infrastructure — the kind an operator can actually stand behind legally — has to do four things, and they have to connect:

  1. Capture the allergen ask at the order. Whether in-app, at the counter, or through a delivery platform, the customer-identified allergy or sensitivity has to be recorded as structured data, not a free-text note on a ticket.
  2. Translate it into preparation instructions. The kitchen needs to know what the alteration is, tied to the specific item and the specific guest.
  3. Mark the food at fulfillment. For Virginia-compliant operations, that means a physical marker on the dish or package — standardized to the Board of Health spec, applied at the point of preparation, visible at handoff.
  4. Document that all three happened. Audit trails are the defense against negligence per se and strict liability. If you can't show what was asked, what was prepared, and what was marked, you're exposed.

No operator I know of has all four stitched together today. Most have pieces — a POS system that captures allergen notes, a KDS that displays them, a kitchen culture that tries to act on them. But the pieces don't talk to each other, and they don't produce a record. That's the gap Virginia just made legally material.

The market read

Three states are now signed into law. Five more have active bills. The AAFA is working with legislators in additional states for 2026. The FDA is reviewing gluten labeling. Every enacted law has expanded scope or added a new compliance surface relative to the one before it.

This is not a trend that reverses. The political economy of allergen disclosure is straightforward — it polls well, it's cheap for states to mandate, the federal government is moving in the same direction, and every fatality that makes the news adds pressure. Operators waiting for regulatory clarity before investing in infrastructure are waiting for a stopping point that isn't coming.

The operators who will be in the strongest position in 2027 are the ones who build the compliance layer now — not because California requires it, but because California is the first of many and Virginia just rewrote what "compliance" means.

Foodini is the dietary intelligence platform that powers allergen compliance and ingredient-level menu data for food service operators, venues, and enterprise hospitality clients. Dylan McDonnell is the Founder and CEO, chairs the Guest Communication Board for the FARE Hospitality Alliance, and has lived with celiac disease since 2002.

For a comprehensive comparison of state allergen laws, federal framework, and case law landscape, request Foodini's Regulatory Intelligence brief at hello@foodini.co.

Elevate your business with Foodini. Get in touch.

Join our Partner Network