F&B Menu & Meal Orders (PL-T188)

MenuItem stores multi-language names and descriptions, the EU-14 allergen list, dietary flags (vegetarian, vegan, gluten-free, halal, kosher), the kitchen station that should prepare it (cold, grill, fryer, bar), and the course (starter, main, dessert, drink). MenuPackage bundles items at a price strictly less than original_total, with min_party_size enforcement so a "sharing platter for four" can't be added to a booking of two. MealOrder is attached to a Booking; its subtotal/total rolls into Booking.total_amount, so a single payment captures both lane and food.

Time-window availability (available_from / available_until HH:MM strings on each item) means lunch specials disappear from the menu after 14:00. When a customer has declared allergens on their profile, the wizard surfaces an allergen acknowledgement gate before submit — they must explicitly confirm conflicts. On submit, the order writes with status = ordered, the kitchen-printout pipeline serializes an ESC/POS payload over raw TCP to the configured station printer, with PDF-by-email and a manual print-from-screen mode as fallbacks.

Reprint is idempotent — the first-print timestamp is stamped once and reprints are recorded on the audit trail without double-firing the printer. The status lifecycle (draft → ordered → preparing → ready → delivered → cancelled) drives a kitchen display screen that polls GET /chain/kitchen/queue filtered by station and broadcasts on chain.kitchen.{tenant}.{location} via SSE so any updates appear instantly. A second SSE channel chain.bookings.{tenant}.{location} keeps the front-of-house calendar in sync.

The customer CMS picks the right language via Accept-Language.