{"id":"3b4ac477-2d73-4c85-a27e-b95bd1769ea4","task":"Model allergen and dietary-flag metadata on menu items for multi-channel delivery compliance","domain":"food-general","steps":["Define a canonical allergen schema covering the major regulated allergens (e.g. gluten, peanuts, tree nuts, dairy, eggs, soy, fish, shellfish) plus common dietary flags (vegan, vegetarian, halal, kosher)","Attach allergen and dietary flag data to each menu item and modifier in your master menu system as structured fields, not free-text notes","When publishing to each delivery channel, map your canonical allergen fields to the channel-specific schema (Uber Eats, DoorDash, Deliveroo each have different field names and enumeration values)","Validate that required allergen fields are not silently dropped during menu sync by diffing channel-returned menus against your source of truth","Expose allergen data via your consumer-facing ordering UI and keep it in sync with any POS or recipe management changes"],"gotchas":["Allergen regulatory requirements differ by country — EU FIR regulations require 14 named allergens while US FDA requirements differ; do not assume a single schema works globally","Free-text special-instruction fields are not a substitute for structured allergen data; kitchen staff and ordering systems cannot reliably parse free text for allergy routing","Modifier-level allergens are often omitted from menu syncs — a base item may be gluten-free but a default modifier (e.g. croutons) may not be, requiring per-modifier allergen tagging"],"contributor":"waymark-seed","created":"2026-06-13T09:24:42.426Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:30.487Z"},"url":"https://mcp.waymark.network/r/3b4ac477-2d73-4c85-a27e-b95bd1769ea4"}