May contain statements: when to use them and when not to

"May contain nuts." Guests see it everywhere — sometimes for good reason, sometimes as a blanket disclaimer. Precautionary allergen labelling (PAL) is useful when it reflects a real risk assessment. It becomes noise when every dish carries the same vague warning.

What "may contain" is for

Precautionary statements communicate possible unintended presence of an allergen due to shared equipment, processing or environment — not deliberate ingredients.

Deliberate ingredients should be declared as allergens in the normal way. "May contain" is not a shortcut for incomplete recipe knowledge.

When a warning is justified

Consider a precautionary statement when:

• You have identified a realistic cross-contact route
• Controls cannot eliminate that route for the dish in question
• The warning is specific (which allergen, broadly why)
• Your team can explain it consistently if asked

Examples: a bakery bench that always handles wheat flour; a fryer shared with battered gluten items; a pastry section using tree nuts on adjacent trays.

When not to use it

Avoid "may contain" when:

• You simply have not checked the ingredients
• You want legal cover without assessing risk
• Every item on the menu gets the same line by default
• The allergen is definitely in the recipe (declare it properly instead)

Overuse trains allergic guests to ignore all warnings — including the ones that matter.

Be specific and honest

Better: "Prepared in a kitchen that also handles peanuts; we cannot guarantee absence of peanut cross-contact."

Worse: "May contain allergens" with no detail.

Specificity helps guests decide. Vague fear helps nobody.

Align packaging and plated food

For PPDS items, ingredients lists with emphasised allergens cover deliberate presence. Precautionary statements on packs should still match your risk assessment — and match what FOH says about the same product sold loose or plated.

Inconsistency between a packed sandwich label and the café's verbal advice destroys trust.

Operational discipline

1. Document which stations create cross-contact risk
2. Decide which dishes inherit which precautionary notes
3. Review when layout, suppliers or volume changes
4. Train staff not to invent extra warnings mid-service

Store those notes with the dish data so QR menus and staff tools stay aligned. Quiteful supports dish-level detail alongside the 14 regulated allergens so warnings sit next to facts, not instead of them.

Free-from claims are a higher bar

"May contain" and "gluten-free" are different worlds. A free-from claim needs controls that meet the claim. If you cannot meet that bar, do not make the claim — use clear ingredient data and honest cross-contact language instead.

Talk to guests like adults

People managing anaphylaxis risk are used to trade-offs. They would rather hear a precise limitation than a cheerful guarantee you cannot defend. Pair digital filters for ingredient exclusions with plain notes where cross-contact remains.

Bottom line

Use precautionary statements sparingly, specifically and only after thinking. Declare ingredients accurately always. That combination is clearer for guests and more defensible for your business.

Read more on cross-contact vs ingredients, or see Quiteful dietary tags for structuring guest-facing menu information.