Cross-Contamination vs. Ingredients: What SB-68 Requires You to Disclose
Does SB-68 require you to disclose that your fries are cooked in the same oil as breaded shrimp? No. But the distinction between intentional ingredients and cross-contact is one most restaurant owners get wrong.
The Key Distinction
SB-68 requires disclosure of allergens that are intentionally added as ingredients in a menu item — allergens that you "know or reasonably should know are contained as an ingredient."
It does not require disclosure of cross-contact risks — situations where an allergen might transfer from one food to another through shared equipment, cooking surfaces, or utensils.
Example:
- ✅ Must disclose: Your Caesar dressing contains anchovies (fish is an intentional ingredient)
- ❌ Not required: Your grilled chicken was cooked on the same grill as shrimp (cross-contact)
What Counts as an "Intentional Ingredient"
An allergen is an intentional ingredient when it's deliberately added to a recipe or is a known component of a purchased ingredient. This includes:
- Direct additions — butter in a sauce (milk), soy sauce in a marinade (wheat + soy)
- Sub-ingredients in purchased products — whey in the bread you buy from your vendor (milk), egg wash on pastries
- Cooking oils that are allergens — peanut oil used to fry items (peanuts)
- Garnishes and toppings — sesame seeds on a bun, crushed peanuts on a pad thai
What Is Cross-Contact (Not Required by SB-68)
Cross-contact occurs when an allergen unintentionally transfers to a food that doesn't normally contain it. Common scenarios:
- French fries cooked in the same fryer as breaded (wheat) or shrimp (shellfish) items
- A grilled cheese made on the same flat-top where an egg was just cooked
- A salad prepared on a cutting board where tree nuts were just chopped
- Shared tongs used for both peanut-containing and peanut-free dishes
- A blender used for a milk smoothie and then a dairy-free smoothie
SB-68 does not require you to disclose these risks on your menu.
Why You Should Disclose Cross-Contact Anyway
Just because SB-68 doesn't require cross-contact disclosure doesn't mean you shouldn't address it. Here's why:
Liability Still Exists
If a customer with a severe peanut allergy eats your "peanut-free" dish that was cross-contaminated in your fryer, you may still face liability — especially if you knew the cross-contact risk existed and didn't warn the customer. SB-68 compliance doesn't shield you from negligence claims.
Customer Trust
Allergy-conscious diners appreciate transparency. A simple note like "Our kitchen uses shared equipment for items containing tree nuts, peanuts, and wheat" sets expectations honestly without requiring per-item disclosure.
Best Practice Approach
The recommended approach is two-tier disclosure:
- Per-item allergen identification (required by SB-68) — which allergens are intentional ingredients in each dish
- General kitchen statement (voluntary, best practice) — a blanket note about shared equipment and cross-contact risks
This gives allergy-sensitive customers the full picture without requiring you to trace every possible cross-contact path for every item.
Gray Areas to Watch
Some situations blur the line between ingredient and cross-contact:
- Shared fryer oil — If you fry shrimp in oil and then fry french fries in the same oil, is the shellfish an "ingredient" in the fries? Legally, probably not under SB-68. Practically, it's still a risk worth noting.
- Peanut oil for frying — If you deliberately use peanut oil to fry items, that IS an intentional ingredient and must be disclosed. The oil itself is the allergen.
- Butter on a shared grill — If you butter the grill before cooking a steak, the milk (butter) is an intentional ingredient in that steak's preparation and should be disclosed.
When in doubt, disclose. Over-disclosure is never a legal risk; under-disclosure can be.
Get Your Per-Item Disclosure Right
Focus first on what SB-68 requires: accurate, per-item identification of intentional allergen ingredients. Then add a general cross-contact statement as a best-practice layer.
MenuComply helps with the first step — AI identifies intentional allergen ingredients in each menu item. You verify, and publish a compliant disclosure in minutes.