Real-time 86 means the moment a sous marks trout gone, every surface that could sell trout knows it—before the next table opens the QR menu. Two seconds is a reasonable bar on venue networks; thirty seconds is how you earn one-star “bait and switch” reviews at scale.
Inventory events must ride the same spine as checkout architecture and menu integrity—no shadow “web-only” availability.
Third-party marketplaces, if still connected, should receive the same truth with documented lag; when lag is structural, communicate honestly on your owned channels rather than pretending parity.
Event fabric, not polling
Push updates to carts, menus, and marketplaces where integrated; avoid cron jobs that drift. Idempotency matters when managers tap twice in panic.
Version events with monotonic clocks or sequence IDs so out-of-order packets do not resurrect dead SKUs.
Graceful degradation
When offline, queue events and reconcile; show honest “last updated” if you must. Silence is worse than a brief delay with explanation.
Train staff to use paper backup protocols only when digital is truly dead—hybrid chaos confuses guests more than a short pause.
Audit and postmortems
Log who86’d, when, and whether auto-recovery cleared the flag. Patterns reveal training gaps or vendor lag.
Weekly review mismatch tickets: orders accepted after an86 that should have blocked—each one is a bug or a training hole.
Guest-facing copy matters
Replace “sold out” modals with suggested swaps when you have data; empty error screens train abandonment.
Menuella inventory speed
Mobile manager and Menuella propagate 86 state globally—inventory truth as fast as the pass can speak.
Fast inventory is a trust product: guests reward brands that stop selling ghosts, and the kitchen rewards brands that stop apologizing.
