Choosing the best allergen management software for small restaurants starts with a legal wrinkle most buying guides skip entirely. Starting in November 2026, a single-location deli in Rochester can be legally required to label allergens on food it makes ahead of time. A 15-unit taco chain based entirely in Texas will not be — not under either of the two new laws reshaping menu labeling in 2026. The dividing lines are not what most independent operators assume.
Two states passed allergen disclosure laws within months of each other, and they trigger on completely different criteria. California’s law counts locations. New York’s law counts nothing — it looks at how the food was made. Confusing the two is not a paperwork error; it is the kind of mistake that leads an operator to believe they’re exempt when they aren’t, or a diner with a food allergy to trust a menu that was never actually vetted.
The quick answer: most single-location independents are not covered by California’s law, but a growing number of grab-and-go operations — delis, bakeries, prepared-food cases — will be covered in New York regardless of size once its law takes effect. Three tools worth knowing about exist at very different price points: AllerIQ (genuinely free for one location), EveryBite (diner-facing, enterprise-priced), and AllergyMenu.app (ingredient-level, partially unpublished pricing). What follows is where each law actually applies, why AI-generated allergen tagging is already producing dangerously wrong labels, and which tool fits which kind of restaurant.
What California’s SB 68 (ADDE Act) Actually Requires — and Who It Skips
California Senate Bill 68, known as the ADDE Act, takes effect July 1, 2026. It requires disclosure of the FDA’s nine major allergens — milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soy, and sesame — on menu items at covered restaurants, per the California Restaurant Association’s official summary.
The threshold is where most operators stop reading and get it wrong. The law applies to restaurant chains with 20 or more locations nationally, operating under the same name with a substantially similar menu, with at least one of those locations in California. A single-location restaurant, anywhere, is not covered. Neither is a nine-unit regional chain that happens to be based in Sacramento.
Two details matter beyond the headcount:
- Wheat is covered. Gluten broadly is not. The nine allergens are the FDA’s statutory list, and wheat is one of them — but barley and rye, the other two grains that contain gluten, are not on that list and are not required disclosures under SB 68. A menu item can be fully SB 68-compliant and still contain barley malt or rye flour without a flag. Celiac diners relying on this law as a gluten screen will be disappointed.
- Disclosure doesn’t have to be on the printed menu. The law allows digital disclosure — a QR code linking to allergen data — as long as a written fallback is available for guests who ask. That is a meaningfully lower bar than reprinting menus every time a recipe changes.
Reaction on r/Celiac to the location threshold was blunt. “20 locations? So it’s useless,” one commenter wrote when the law was first reported. Another pushed back on the framing that it does nothing: “It’ll force chains to do it there and many will do it everywhere. It won’t help with small or mom and pop places in California.” Both are correct about different things — the law will not touch a neighborhood restaurant, but chains rarely maintain two separate menu systems by state, so California’s threshold tends to export the disclosure nationally once a chain builds the infrastructure.
Coverage of the law was corroborated in reporting from the Washington Times in late June 2026, alongside legal summaries circulated by employment and hospitality law firms tracking the rollout for chain clients.
New York Is a Different Law — and It Can Catch Small Restaurants CA’s Law Doesn’t
New York’s allergen labeling law, signed November 12, 2025 and effective November 2026, works nothing like California’s. This is the part of the compliance picture most coverage flattens into “the allergen law” — and that flattening is exactly what causes independent operators to miscalculate their own exposure.
There is no location-count threshold in the New York law. A restaurant with one location, no franchise agreement, and no chain affiliation can be fully covered. Coverage instead turns on what kind of food is being sold — specifically, items that are prepared and prepackaged for sale on the same premises before a customer places an order. A deli case of pre-made sandwiches. A bakery’s grab-and-go shelf. A prepared salad sitting in a cold case, ready to grab. Reporting from Allergic Living, published the day after the bill was signed, and from WXXI News the following day, both describe the trigger the same way: it is about the food, not the business size.
Made-to-order items are not covered. A sandwich built when a customer orders it, at the counter, is outside the law’s scope even at a location that also sells pre-made items covered by it.
The practical result: a single-location bakery in Rochester with a grab-and-go case can be legally obligated to disclose allergens on that case, while a single-location, made-to-order sandwich shop three blocks away — selling comparable food, at a comparable price point — has no such obligation. Same city, same size, different exposure, because the laws measure completely different things.
This is general information, not legal advice. Neither California’s nor New York’s threshold is simple enough to self-diagnose from a blog post, and the honest next step for any operator uncertain where they fall is a conversation with their local health department or an attorney — not an assumption of exemption based on headcount alone.
Why This Matters Even If You’re Not Covered: When AI Wrote the Allergen Labels, It Got Them Dangerously Wrong
Neither law requires most independent restaurants to do anything yet. That is a reason to be careful about labeling voluntarily adopted through AI tools, not a reason to ignore the category — because the failure mode already showed up in public.
A widely discussed thread on r/Celiac described a restaurant menu where a dish billed as nut-free plainly wasn’t. “One of the dishes was a Thai cashew chicken stir-fry. marked nut-free. cashews. marked nut-free,” the poster wrote. When asked how that happened, the owner gave an answer that should worry every operator considering automated menu tools: “she was surprised. said they used a menu generation tool that auto-translates and auto-tags everything, and she just assumed its accurate because ‘the AI said so.’”
The replies in that thread are the more important part. One commenter zeroed in on why a wrong label is worse than no label at all: “that’s terrifying. a green icon makes you lower your guard completely, thats the whole point of it.” Another was more direct about what the failure actually reveals about the technology: “restaurant owners really need to understand that AI is not a food safety tool, it just guesses words that sound right.”
That diagnosis lines up with a separate, well-documented failure mode: AI-generated recipes getting basic food facts wrong is not a one-off bug — it’s a structural property of how language models generate text. A model trained to predict plausible-sounding words has no actual awareness of what’s in a dish. It can label a cashew stir-fry “nut-free” with the same fluency it uses to label an actual nut-free dish, because it isn’t checking ingredients — it’s pattern-matching language. The same failure mode shows up in the AI tools writing your menu descriptions, where a generated description can read perfectly while quietly misstating an ingredient.
For a restaurant not yet legally required to disclose anything, the lesson is not “wait until forced.” It’s that voluntary allergen labeling built on unverified AI output is a liability an operator is choosing to create, with no law requiring them to create it.
3 Allergen Management Software Picks for Small Restaurants (Free, Diner-Facing, and Ingredient-Level)
Three tools cover meaningfully different use cases. None of them should be treated as a substitute for verifying ingredients internally — all three are systems for organizing and displaying data a kitchen still has to supply accurately.
AllerIQ is built for the single-location independent. Its free tier covers one location and one menu, indefinitely, with no credit card required, according to the vendor’s own site. It has the FDA’s Top 9 allergens built in by default, and — notably — the allergen mapping is reviewed by registered dietitians rather than left entirely to self-reported kitchen data. It also flags cross-contact risk (“may contain”) separately from direct ingredient allergens, a distinction most cheaper tools skip.
EveryBite solves a different problem: it’s a diner-facing SmartMenu that lets guests filter a restaurant’s menu by allergen, with a green/yellow/red visual system rather than a static ingredient list. It launched at JRECK Subs in New York in April 2024 and has since scaled to more than 50 U.S. chains across roughly 4,000 locations, reaching over 1 million diners and more than 150,000 monthly active users, per reporting from Allergic Living and Healio. EveryBite’s pricing is quote-only — the vendor does not publish a rate card, and no monthly figure should be assumed.
AllergyMenu.app centers on ingredient-level data: it maps allergens down to individual ingredients rather than dish-level tags, and pairs that with a free customer-facing app. Restaurants get a free first-month trial. Beyond that, the vendor’s own pricing page invoices in GBP, and its paid tiers are not fully published — worth flagging plainly rather than guessing at a U.S. dollar figure.
One estimate circulating among industry aggregators puts multi-location allergen automation software in the $300 to $900 a month range. That figure is not vendor-confirmed by any of the three tools above — it’s a third-party estimate, and should be treated as a ballpark for budgeting conversations, not a quote.
Operators already running recipe costing software that already tracks ingredient-level data have a head start here — allergen tagging and ingredient costing pull from the same underlying data set, and a kitchen that has already digitized its recipe book is not starting from zero.
Which Allergen Management Software Should Small Restaurants Actually Pick?
Pick AllerIQ if the operation is a true single-location independent. The free tier removes cost as a barrier entirely, and dietitian-reviewed mapping addresses the exact failure mode described in the r/Celiac thread above — a human checking the AI-adjacent output rather than trusting it blindly.
Pick EveryBite if the priority is the diner-facing experience at scale. A 4,000-location footprint and a filter-by-allergen interface make sense for a regional or national chain managing brand consistency across locations, but the enterprise, quote-only pricing model makes it a poor fit for a single unit evaluating options on a tight budget.
Pick AllergyMenu.app if ingredient-level precision matters more than diner-facing polish. A restaurant with a complex, frequently changing menu — a bakery reformulating recipes seasonally, a deli sourcing from multiple suppliers — benefits from ingredient-level mapping more than a slick front-end filter. The unpublished paid pricing is a real gap worth confirming directly with the vendor before committing.
None of the three should be adopted purely because a law now exists. The New York deli case and the California chain threshold are two different triggers, and a restaurant outside both is still free to choose based on operational fit — or to choose not to adopt anything yet.
Our Take
The two-law confusion is the real risk here, more than either law individually. A California-based independent reading headlines about “the allergen law” and concluding they’re covered — or a New York deli reading the same headlines and concluding they’re exempt because they’re small — are both making the same category of mistake: treating two laws with opposite trigger logic as one law with one threshold.
The stronger position for any independent restaurant, covered or not, is separating two decisions: first, determine actual legal exposure under each law’s specific criteria (location count for California, food preparation type for New York), and second, decide independently whether voluntary allergen disclosure is worth adopting regardless of legal requirement. The second decision should not wait on the first. A restaurant with zero legal obligation that adopts AI-generated allergen tags with no human verification has created more risk than a restaurant with no allergen labeling at all.
That is the exact point made in the r/Celiac thread that surfaced the mislabeled cashew dish: “an unmarked menu is safer than a wrongly marked one. at least with an unmarked menu you know to ask. a wrongly marked menu tells you its safe when it isn’t.”
Frequently Asked Questions
Does my restaurant have to comply with California’s SB 68 if I only have one location?
No — SB 68 applies only to chains with 20 or more locations nationally operating under the same name with a substantially similar menu, with at least one location in California. A true single-location independent, in California or anywhere else, is not covered by this specific threshold. Confirm exact status with a local health department or attorney if any part of the operation involves shared branding or a multi-unit agreement.
Could my small restaurant in New York be covered by its allergen law even though I’m not a chain?
Yes, potentially. New York’s law has no location-count threshold at all — it applies based on whether food is prepared and prepackaged on-site before a customer orders, such as a deli case or bakery grab-and-go shelf. A single-location operation selling any prepackaged prepared food can be covered regardless of size.
Does the wheat disclosure under SB 68 mean my menu is safe for gluten-sensitive or celiac guests?
Not fully. SB 68 requires disclosure of wheat as one of the FDA’s nine major allergens, but barley and rye — the other two gluten-containing grains — are not on that list and are not required disclosures. A dish can be SB 68-compliant while still containing gluten from a non-wheat source.
Are any of these three tools free to use long-term?
AllerIQ’s single-location, single-menu tier is free indefinitely with no credit card required. AllergyMenu.app offers a free customer-facing app and a free first month for restaurants, but its ongoing paid pricing is not fully published. EveryBite does not offer a public free tier; its pricing is quote-only.
What should a restaurant do if it’s not legally required to disclose allergens but wants to anyway?
Prioritize human verification of any AI-assisted tagging before publishing it to guests, since language models have no actual awareness of ingredients and can mislabel dishes with full confidence. A tool with dietitian-reviewed mapping, like AllerIQ’s, adds a verification layer that a raw AI-generated menu description tool does not.
When exactly do these laws take effect?
California’s SB 68 (ADDE Act) takes effect July 1, 2026. New York’s allergen labeling law was signed November 12, 2025, and takes effect in November 2026.
The Only Safe Assumption Is to Check, Not Guess
California’s law counts locations; New York’s counts food type. A restaurant can be exempt from one and covered by the other, and the only way to know which applies is to check the specific criteria against the specific operation — not to extrapolate from headlines about “the allergen law.” For restaurants outside both laws’ scope today, the AI-generated mislabeling already documented on r/Celiac is reason enough to verify any voluntary allergen tagging with a human before a guest trusts a green icon that was never actually checked. An unmarked menu tells a guest to ask. A wrongly marked one tells them not to — and that’s the more dangerous menu.
References
- California Restaurant Association — Allergen Disclosures: SB 68 — https://www.calrest.org/allergen-disclosures-sb-68
- Washington Times — California requires major restaurant chains to disclose menu allergens (June 30, 2026) — https://www.washingtontimes.com/news/2026/jun/30/california-requires-major-restaurant-chains-disclose-menu-allergens/
- Allergic Living — NY law brings allergen labeling to deli, bakery packaged foods (November 13, 2025) — https://www.allergicliving.com/2025/11/13/ny-law-brings-allergen-labeling-to-deli-bakery-packaged-foods/
- WXXI News — New state law requires food allergen labeling for deli and bakery products (November 14, 2025) — https://www.wxxinews.org/local-news/2025-11-14/new-state-law-requires-food-allergen-labeling-for-deli-and-bakery-products
- Allergic Living — Menu platform aims to transform restaurant food allergy safety (April 8, 2025) — https://www.allergicliving.com/2025/04/08/menu-platform-aims-to-transform-restaurant-food-allergy-safety/
- Healio — Digital platform sorts online restaurant menus by allergic ingredients — https://www.healio.com/news/allergy-asthma/20250212/digital-platform-sorts-online-restaurant-menus-by-allergic-ingredients
- AllerIQ — product and pricing — https://alleriq.app/
- AllergyMenu.app — pricing — https://allergymenu.app/pricing/
- r/Celiac — thread on an AI-generated menu mislabeling a nut-free dish — https://reddit.com/r/Celiac/comments/1ux0fo4/found_a_restaurant_menu_fully_generated_by_ai_the/
- r/Celiac — thread reacting to California’s SB 68 location threshold — https://reddit.com/r/Celiac/comments/1o8kdgs/california_passed_a_law_that_restaurants_will_be/
- Multi-location allergen automation pricing range ($300–900/month) — third-party aggregator estimate, not vendor-confirmed.
