California SB 68: What Restaurant Operators Need to Know Before July 1

California's Senate Bill 68 takes effect July 1, 2026. If you operate a restaurant in California — or a chain with California locations — this law directly affects what you're required to show on your menu, and the deadline is weeks away.

This guide covers exactly what the law requires, which operations it applies to, where restaurants typically run into problems, and how to get compliant before the deadline.

What SB 68 Actually Requires

California SB 68 extends and strengthens existing menu labeling requirements. The core obligation is straightforward: covered restaurants must display calorie counts for standard menu items at the point of ordering.

That means:

• Calories must appear on printed menus, menu boards, and digital menus
• The calorie count must be displayed clearly, adjacent to the item name or price
• A statement about daily calorie intake context must appear on the menu (typically "2,000 calories a day is used for general nutrition advice")
• Calorie counts must reflect the standard preparation of the item as it's actually served

This isn't a suggestion or a best practice. As of July 1, it's a legal requirement with enforcement mechanisms.

Which Restaurants Are Covered

SB 68 applies to restaurant chains with 20 or more locations operating nationally, where the menu items are substantially the same across locations. This mirrors the federal FDA menu labeling rule that California is aligning with and extending.

If you operate fewer than 20 locations, you are not currently covered by the federal standard — but California's law has provisions that affect smaller operators too, particularly around transparency requirements tied to digital menus and consumer-facing ordering systems.

The practical reality: even if your group is under the 20-location threshold, health-conscious California diners expect calorie information. The question is increasingly not whether to display it, but how.

What "Standard Menu Items" Means in Practice

This is where operators run into the most confusion. A standard menu item is any item that appears on your menu regularly — not daily specials, not seasonal items listed separately, not custom orders.

What this means operationally:

• Your core menu needs calorie counts on every item
• If you run a rotating seasonal menu, items that appear for more than 60 days need counts
• Modifiers and add-ons that change calorie content significantly need to reflect that change (e.g., "add avocado +80 cal")
• Digital menus must display the same information as printed menus — you can't comply on paper but leave your QR menu blank

That last point catches multi-location operators by surprise. If you've moved to QR menus and let your printed menu compliance lapse, your digital menu now carries the same legal weight.

The Accuracy Problem

Displaying calorie counts is one thing. Displaying accurate ones is another — and this is where liability actually lives.

The law requires that your calorie counts reflect how the dish is actually prepared. Not a generic estimate. Not what a similar dish at a similar restaurant contains. Your dish, your ingredients, your portions.

This creates a real problem for restaurants that have been using rough estimates, or worse, AI-generated nutrition guesses based on recipe names rather than actual ingredients.

If a guest with diabetes or a metabolic condition relies on your calorie count to make a meal decision, and that count is materially wrong, the legal exposure is meaningful. The documentation trail matters — were your numbers generated from verified government data, or were they approximated?

USDA FoodData Central, the official U.S. government nutrition database, is the standard that holds up to scrutiny. It's what hospitals, food scientists, and the FDA itself relies on. If your calorie counts are sourced from that database and tied to your specific ingredients and portions, you have a defensible record.

Where Multi-Location Operators Run Into Compliance Problems

Running a compliant menu across multiple California locations is operationally harder than it sounds. The problems tend to cluster around the same failure points:

Inconsistent data across locations. Location A updated the salmon dish when the supplier changed. Location B is still showing the old numbers. Both are legally exposed.

Menu updates that don't propagate. A dish gets reformulated. The kitchen knows. The menu doesn't. If your update process requires coordinating reprints or manual digital menu edits location by location, some locations will always lag.

Seasonal and LTO items. Limited-time offerings that run longer than 60 days fall under the standard menu requirement. Operators who treat LTOs as outside the compliance scope are often wrong.

Digital menu gaps. Operators who got compliant on print menus and assumed QR menus were a separate system. They're not — the same requirements apply.

No audit trail. Compliance isn't just about what's on the menu today. It's about being able to show, if asked, that your data came from a verified source and was updated when your recipes changed.

How to Get Compliant Before July 1

The path is straightforward but requires moving now. You have weeks, not months.

Step 1: Audit your current menu data. For every standard menu item, do you have a calorie count? Is it sourced from verified data or an estimate? If you don't know where the number came from, assume it needs to be redone.

Step 2: Fill gaps with verified data. For any item missing calorie counts or relying on estimates, run the actual ingredients through a USDA-based calculator. Input your specific portions and preparation method — not a generic version of the dish.

Step 3: Update every menu surface simultaneously. Print, digital, and QR all need to show the same numbers. If your digital menu is managed separately from your print menu, this is the moment to fix that disconnect.

Step 4: Add the required calorie context statement. The text "2,000 calories a day is used for general nutrition advice" or equivalent must appear on all covered menus. It's often forgotten in the rush to add item-level data.

Step 5: Document your data sources. Keep a record of when your calorie counts were generated, what database they came from, and what ingredients they reflect. If your menu changes, update the record.

Step 6: Build a propagation process. For multi-location operators, the compliance process only works if an update at the source reaches every location immediately. A manual process will drift. You need a system where one change updates everywhere.

The Broader Transparency Shift

SB 68 is part of a longer trend. California has been at the front of restaurant nutrition transparency for over a decade. The federal FDA menu labeling rule established the 20-location threshold nationally. Several other states are moving toward similar requirements.

Operators who treat this as a one-time compliance checklist will be back in the same position in two years when the next requirement arrives. Operators who build accurate, centralized nutrition data into their menu management now are positioned for whatever comes next.

Health-conscious diners — already the fastest-growing restaurant segment — use nutrition information to decide where to eat. A menu that displays accurate calorie counts confidently isn't just compliant. It's a sales tool for the guests most likely to become regulars.

How TASTEEM Handles SB 68 Compliance

TASTEEM's USDA nutrition calculator generates calorie counts from your actual ingredients, sourced from the official USDA FoodData Central database. Every number is tied to your specific recipe — not a generic estimate of what the dish typically contains.

For multi-location operators, a menu update in the TASTEEM dashboard propagates to every QR code and website widget instantly. No reprints, no location-by-location edits, no drift. Every surface — digital menu, QR code, website widget — shows the same verified data simultaneously.

The FDA Label Generator produces downloadable, FDA-compliant nutrition labels for every dish, including the calorie context statement required by SB 68. If you need documentation of your compliance process, that's the paper trail.

For California operators who need to close a compliance gap before July 1, setup takes 30 minutes. The nutrition data you enter flows immediately to every guest-facing surface.