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
Compliance GuideCalifornia

Third-Party Delivery Apps and Allergen Disclosure: Who Owns the Responsibility?

When a guest orders through DoorDash, Uber Eats, or Grubhub and has an allergic reaction because allergen information was wrong or missing — who is liable?

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

  1. Home
  2. ›
  3. Resources
  4. ›
  5. Third-Party Delivery Allergen Liability

A restaurant in California gets 35% of its orders through DoorDash. The DoorDash menu listing for that restaurant was built from a photo of a physical menu, supplemented by descriptions the restaurant submitted eighteen months ago. Since then, the kitchen has changed suppliers for two core proteins and rotated in a new sauce. The allergen information on DoorDash reflects none of those changes.

On July 1, 2026, that restaurant is non-compliant. The gap is not on the physical in-store menu, which the operator updated. The gap is on the third-party platform — a channel they treat as someone else's system, managed by someone else's team, and therefore someone else's problem.

This is the most common SB 68 compliance misconception I encounter: operators who have done the work on their in-house menus but have not addressed delivery platforms because they believe the platform bears some share of responsibility for what is displayed there. They do not.

What SB 68 Actually Requires for Digital Menus

California's SB 68 requires that any restaurant chain with 20 or more locations nationally and at least one California location disclose the nine major food allergens for every menu item on "all physical and digital menus."

The current consensus view among legal firms advising restaurant groups is that "all digital menus" means the restaurant's own website, first-party online ordering platforms, and third-party delivery platforms: DoorDash, Uber Eats, Grubhub, Instacart, and any other delivery or ordering application where a consumer can see a menu and place an order.

The obligation runs to the operator, not to the platform. If a menu exists in any digital form that a consumer can access to make ordering decisions, allergen information must be present and accurate on that surface. The restaurant is the party that bears the exposure when disclosure is absent or inaccurate.

The Liability Question: Who Gets Sued?

When an allergic guest orders through a delivery platform, has a reaction because allergen information was wrong, and decides to take legal action, the restaurant is the primary target.

  • Strict liability attaches once the restaurant is on notice of a food allergy — independently of SB 68, under common law. If a guest communicates an allergy at any point in the ordering process, and a mistake happens after that point, the restaurant bears strict liability for consequences regardless of fault.
  • Negligence per se applies post-July 2026: once SB 68 takes effect, a restaurant without compliant allergen disclosure on all digital menus is in statutory violation. Under negligence per se, that violation itself constitutes negligence — a plaintiff doesn't need to prove the restaurant was unreasonable.
  • The ADA precedent is instructive. Over the past decade, thousands of lawsuits have been filed against restaurants for digital accessibility non-compliance. The same plaintiff infrastructure exists for allergen disclosure failures — and third-party delivery platform pages are publicly accessible and easily verified.

What the Platforms Will and Won't Do

Most major delivery platforms have menu management tools that allow operators to add allergen information. DoorDash, Uber Eats, and Grubhub all have some form of this. The challenge is that these tools require the operator to populate them — they do not pull allergen data automatically — and many operators have either not used them or populated them with information that is now outdated.

For a chain with 50 California locations and a presence on three delivery platforms, manually maintaining accurate allergen information across 150 platform listings — and updating every listing every time a recipe or ingredient changes — is not operationally sustainable.

The Practical Compliance Path

  1. Build the source of truth centrally. Accurate allergen data at the recipe and ingredient level, verified by a qualified source, feeds every surface. When the data is right at the centre, every surface that draws from it is right.
  2. Connect to delivery platforms through integrations, not manual updates. Platforms with API connections to menu management systems allow allergen data to propagate automatically when it changes at the source.
  3. Document the connection. The audit trail showing when allergen data was updated and which surfaces reflect the current data is the compliance record that matters in an inspection or legal proceeding.
  4. Test before July 1. Every California location, every platform, every menu item.

Common Questions

Can a disclaimer replace allergen disclosure on delivery platforms?

No. The law requires accurate per-item allergen disclosure. A blanket disclaimer does not satisfy that requirement and does not eliminate liability.

What if a franchisee manages their own delivery listing?

SB 68 applies to both franchisors and franchisees. A non-compliant franchisee listing exposes both parties.

Does this apply to ghost kitchens?

Yes. A delivery-only ghost kitchen has the same SB 68 obligations applied entirely to its delivery-platform menus.

Foodini connects allergen data from your recipe system to every digital surface — in-store, website, first-party ordering, and third-party delivery platforms — so one change at the source propagates everywhere automatically.

See how Foodini handles multi-channel allergen disclosure →

Related Articles

  • SB 68 Compliance Checklist
  • SB 68 Non-Compliance: Penalties, Liability & What Operators Need to Know
  • Digital Menu Allergen Tagging: A Complete Platform Guide

Elevate your business with Foodini. Get in touch.

Join our Partner Network