SB 869 requires chain restaurants to add a conspicuous added-sugar indicator and a short factual warning where customers choose beverages that contain substantial added sugar. The rule targets beverages sold for immediate consumption and covers physical and electronic menus used at the point of selection.
The measure forces operators and their menu vendors to identify which standard beverage items meet the bill’s ‘high added sugar’ test and to display both an icon next to those items and a standardized warning message at the customer’s point of selection. For chains, that will mean recipe audits, menu updates across formats, and coordination with any digital platforms that publish their menus.
At a Glance
What It Does
The bill requires an added-sugar icon to appear immediately adjacent to each standard menu beverage item that meets the statute’s test for high added sugar, and it requires a factual warning statement to be shown conspicuously at the point where customers make their selection. The statute defines “high added sugar content” by reference to one-half of the FDA’s daily reference value for added sugar as measured by the FDA’s labeling standard in effect on January 1, 2026.
Who It Affects
Operationally the rule targets national and regional restaurant chains and the vendors who design and host their menus; it also affects third-party platforms when the chain posts and controls the menu content there. Nutrition staff, compliance teams, and point-of-sale and digital-menu engineers will be responsible for implementation; consumers are the intended information recipients.
Why It Matters
This bill extends menu disclosure rules beyond calorie labels to added-sugar content and explicitly reaches digital and third‑party presentations when the chain controls the listing. That raises calculation, design, and integration questions for chains and platform partners while creating a new baseline for consumer-facing nutritional warnings.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 869 builds a menu-labeling obligation around a single nutritional trigger and a specific presentation requirement. The statute lays out what counts as a menu and a point of selection broadly (drive-through boards, printed menus, beverage and dessert menus, kiosks, electronic menus, and internet listings).
It draws a line around the kinds of beverage offerings that are in scope by creating the category “standard menu beverage item” — a class that includes items prepared or poured on-site like fountain drinks, blended beverages, and single-line variable beverages (for example, a flavored fountain drink listed once).
The bill also anticipates some real-world variety: it excludes items that already carry added-sugar labeling on their packaging, short-run items offered for fewer than 30 days, drinks that begin below the high-sugar threshold but are later customized by the customer, alcoholic beverages, and spoon‑eaten frozen dairy products. That creates a compliance checklist: operators must know whether an item is listed as a standard menu beverage, whether an item is temporally short-lived, whether existing packaging carries added‑sugar labeling, and whether the item will be customized at point of sale.Operationally, chains will need to determine the added sugar per stated serving for every covered beverage recipe, pick or commission an icon and place it consistently next to qualifying items, and ensure the required factual warning appears wherever selections are made.
Because the statute covers online menus and third‑party menus that the chain “posts and controls,” implementation will typically require coordination with website administrators and delivery or ordering platforms to preserve icon placement and the point‑of‑selection warning across different display formats.Practically speaking, the most complex technical tasks will be (1) measuring added sugar for variable or customizable beverages and for items sold in multiple serving sizes, (2) deploying icons and warnings across disparate menu systems and display sizes without losing prominence or clarity, and (3) deciding how to treat beverage items sold via mass-preparation systems (self-serve or dispenser systems) or via third-party API feeds. The statutory text supplies the placement and wording requirements for the warning, but it leaves implementation details — icon design, styling, and workflow changes — to operators and their vendors.
The Five Things You Need to Know
The law becomes effective for compliance on January 1, 2028.
It applies to restaurants that are part of a chain operating 20 or more locations under the same name and offering substantially the same menu items.
Menus covered include printed and electronic menus, menu boards, drive‑through listings, and menus on the internet — including third‑party platforms where the chain posts and controls its own menu content.
The statute explicitly exempts prepackaged beverages that carry added‑sugar labeling, items on a menu for fewer than 30 calendar days, non‑high items that customers later customize, alcoholic beverages, and spoon‑eaten frozen dairy products.
The provided text sets out display and wording obligations but does not include an enforcement or penalty scheme in the quoted sections.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Who counts as a 'chain restaurant'
This subsection defines the covered commercial entity: restaurants and similar retail food establishments that operate as part of a chain doing business under the same name and offering substantially the same menu. The definition reaches franchise and corporate models by linking control to brand and menu uniformity rather than ownership structure. That designates which operators must prepare to comply while excluding single-location independents.
How 'high added sugar' is measured
The statute ties the trigger for labeling to a quantitative test based on the FDA’s daily reference value for added sugar as it existed on a fixed historical date. Anchoring the test this way provides a single reference point for compliance calculations but freezes the benchmark to a specific regulatory moment rather than linking it to a moving FDA standard.
Scope of 'menu' and 'point of selection'
The bill lists multiple menu formats that count as the primary menu and defines the point of selection as the place where customers view options and make their choice. That broad language is purposively inclusive — kiosks, drive-through boards, paper menus, in-store menus, and internet listings all qualify — which means chains must assess presentation and prominence across physical and digital touchpoints.
Which beverages are 'standard menu beverage items' and exclusions
This subsection sets the universe of beverage items to be evaluated (those prepared or poured on site, including blended and variable single-line items) and then carves out specific categories from coverage. Those carve-outs — for items with pre-existing package labeling, short-run items, customer-customized non-high items, alcohol, and spoon-eaten frozen dairy — narrow but do not eliminate the operator’s need for recipe-level review and item tracking.
Display requirement and required warning language
This section requires that qualifying beverage items carry a conspicuous added‑sugar icon immediately adjacent on the menu and that the accompanying factual warning statement appear prominently at the point of selection. The statute prescribes the wording structure of the warning and places a prominence requirement on both the icon and the text, which will drive how menus and digital interfaces are redesigned to accommodate the notice.
This bill is one of many.
Codify tracks hundreds of bills on Healthcare across all five countries.
Explore Healthcare in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Consumers seeking nutritional information — The bill gives customers an immediate visual cue on menus that a beverage contributes a large share of the daily added‑sugar limit, helping quick comparisons at point of purchase.
- Public‑health advocates and agencies — The disclosure creates a standardized channel for conveying added‑sugar risk at scale and may be usable in public‑health monitoring or education campaigns.
- Menu designers and nutrition-services vendors — Vendors that build menu systems or nutrition calculations can sell updated services (recipe audits, icon libraries, integration work) to chains needing compliance support.
Who Bears the Cost
- Chain restaurants subject to the law — They must audit recipes, update printed and digital menus, integrate icon and warning displays across POS and online systems, and coordinate with third‑party platforms, generating one‑time and ongoing costs.
- Third‑party ordering platforms and delivery apps — Where chains post and control menu content, platforms will need to accept and preserve icon and warning markup and possibly change UI templates to keep the notices prominent.
- Compliance and operations teams at chains — Staff time and potential consulting expenses to calculate added sugar per serving (especially for variable/customizable drinks) and to design compliant displays will increase operational overhead.
Key Issues
The Core Tension
The central dilemma is simple: the bill improves consumer information by mandating a clear warning for high‑added‑sugar beverages, but it does so by imposing nontrivial operational, design, and measurement burdens on chains and their platform partners — burdens that are harder to resolve for customizable, variable, or digitally displayed beverages where menu control and technical constraints are fragmented.
The statute solves the notice problem by requiring a visible icon and a factual statement, but it leaves many implementation details unresolved. Anchoring the nutritional trigger to the FDA’s daily reference value on a historical date creates a clear single standard but risks misalignment if federal guidance changes; operators must use that historical benchmark even if later FDA updates revise recommended values.
The bill also prescribes prominence but does not specify exact icon size, color contrast, or placement rules for small mobile displays, which will force design judgments and could lead to inconsistent consumer experiences.
Another practical tension concerns beverages sold in variable sizes or custom formats. The law makes variable single-line items in scope but exempts certain customer-modified items; operators will need policies for when a variable offering crosses the threshold in different configurations and for how to treat combination beverages assembled at dispensers.
Technical integration with third‑party platforms is another weak point: the statute covers third‑party menus only when the chain posts and controls the content, but real-world platform agreements often leave presentation controls to the platform; resolving who implements and verifies the icon and warning will require contract changes. Finally, the quoted sections do not set out enforcement mechanisms, timelines for corrective action, or safe-harbor testing procedures, leaving uncertainty about oversight, compliance verification, and legal risk.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.