Allergens and calories

The allergens and dietary tags

Qaema tracks 14 allergens: gluten, crustaceans, eggs, fish, peanuts, soy, milk, tree nuts, celery, mustard, sesame, sulphites, lupin and molluscs. Alongside them, ten dietary tags describe the dish itself: vegetarian, vegan, gluten-free, dairy-free, nut-free, low calorie, keto, high protein, kids and spicy. Both are set from the same chip picker in the item drawer.

Declared vs may-contain

Marking an allergen as declared means it’s an ingredient in the dish. May contain is a separate list for cross-contamination risk — a shared fryer or grill, say — and it’s treated differently by anything checking allergens against the item (see below).

Calories: manual vs agent estimate

A calorie value your agent supplied during an import or a chat is flagged internally as an estimate; the drawer shows an “est.” tag next to it with a link to confirm it once you’ve checked the number. Typing a value into the drawer yourself always clears the flag. The public menu shows only the plain number either way — a visitor never sees whether a calorie count came from you or from an estimate.

What the visitor sees

Allergen filters show only items with explicitly reviewed allergen information and no declared or may-contain match. Empty lists on old or unreviewed items are unknown, so those items are excluded when an allergen filter is active. In the item editor, check ingredients and cross-contact risks, then confirm that the information is complete. Changing either allergen list clears that confirmation. Republish to update the public menu.

Opening an item shows declared allergens, may-contain warnings and whether the venue has confirmed the information. Public MCP checks return unsafe for a declared or may-contain hit, safe only for explicitly reviewed information with no hit, and unknown otherwise. A dietary tag alone never establishes allergen safety. Diners should always confirm with staff before ordering.

Your responsibility

The platform stores and displays exactly what’s attested; it never infers an allergen or a calorie count on its own. An import from a photo or a menu PDF may suggest allergens or estimate calories, but that’s your agent’s work, not the platform’s, and it stays flagged as unconfirmed until you say otherwise.

With your agent

Set allergens on the shrimp biryani — declared shellfish, may contain gluten from the rice mix

calls set_allergens with the item id and the three lists in one go. Ask for audit_menu to find every item still missing calories, allergens or a photo across the whole draft.