86ing an item cleanly

Running out of something on a Saturday night is not a failure — it usually means you sold well. The failure is the twenty minutes afterwards, when the kiosk is still taking orders for it, a server has just promised it to a table, and the kitchen is discovering both facts one ticket at a time.

What has to happen the moment an item goes down

• ✓Every ordering surface stops offering it. Not eventually — before the next guest taps.
• ✓Orders already placed get resolved deliberately, by someone talking to the guest, rather than discovered at the pass.
• ✓Anything the item is a component of comes down too. A combo containing an 86'd item is still sellable unless someone thinks about it.
• ✓The floor knows, so nobody promises what the kitchen cannot deliver.
• ✓It comes back on when the item does, which is the step most often forgotten.

Where the gaps usually are

The classic failure is a system where each ordering channel keeps its own copy of the menu. Someone 86s the item on the POS, and the kiosk, the QR menu and the web ordering page each need their own action — so whichever one is furthest from the person doing it keeps selling for the rest of service.

The second gap is combos and modifiers. An item can be down while a combo that contains it, or a modifier that adds it, is still perfectly orderable. It is worth checking how your setup handles that before a busy night rather than during one.

Multi-location makes it sharper

With more than one site, 86ing needs to be a location decision. One kitchen running out should not remove the item from a store across town that has plenty, and a system that only supports account-wide availability forces exactly that choice.

How Opero handles it

Availability in Opero is a single predicate shared by every ordering path: an item is sellable when its catalog record is active and its effective availability is true. The per-location setting is deliberately three-state rather than a checkbox — unset means inherit the catalog, and a location can force an item on or 86 it locally without touching anywhere else.

Because the POS, kiosk, QR ordering and web ordering all read one menu spine, 86ing at the register removes the item from the kiosk and the QR menu in the same moment. There is no per-channel copy to remember, which is the failure this whole article is about.