86'd at 2 pm, discovered at 4: closing the sold out gap

86'd items are daily life in a cafe: the last banana bread sells, the oat milk runs dry, the cold brew keg kicks mid afternoon. Running out is not the failure. The failure is the gap between the kitchen knowing and the register knowing, and in most cafes that gap is measured in disappointed customers.

Why does the whiteboard method fail?

The classic fix is a whiteboard or a shouted "86 oat milk!" across the room. The cashier mid transaction does not hear it, the next shift never reads the board, nobody erases it when stock returns, and delivery apps keep selling what you cannot make.

Every failure lands the same way: an order taken, sometimes paid, for something that does not exist. Then the refund, the void on your Z report, and a customer who trusts your menu a little less.

You ran out of an ingredient, not a drink

You did not run out of iced oat lattes; you ran out of oat milk, and oat milk touches maybe seven menu items. A system with recipe level inventory already stores that mapping.

So the barista taps one thing, "oat milk: out," and the fan out is automatic. All seven items grey out at the register with a reason, while items where oat is only an optional modifier stay sellable with that modifier disabled. One tap, total coverage, zero shouting.

What should the register do at the counter?

Block, do not warn; a cashier moving fast clicks through any dialog, but an item that cannot enter the cart protects them. The register should also offer the nearest live alternative, turning "sorry, wala na po" into "oat is out, but the fresh milk version is ready." That one sentence saves walkouts.

The flag must follow the item everywhere it lives: both registers, the kitchen display, and connected delivery menus. A cafe that 86es at the counter but keeps selling on the apps has automated its own bad reviews.

Coming back is half the feature

Restocking must be one tap too: the delivery arrives, someone taps "oat milk: back," and seven items wake up at once. Better still, let inventory automate both ends, warning the counter when oat drops below one carton and restoring availability the moment the delivery is logged.

The restock tap is also a timestamp. It closes the outage window in your log, which makes sold out hours measurable instead of anecdotal, and it spares the counter the classic morning surprise of yesterday's dead items still greyed out.

What does sold out time actually cost?

Once 86 events are system events instead of whiteboard scribbles, you get a log: what ran out, when, how often, for how long. Oat milk dying every Saturday at 2 pm is not bad luck; it is an ordering rule waiting to be written, the same way your hourly sales curve writes your roster.

The log also prices your understocking. If your best pastry earns ₱1,400 an hour when available and spends six hours a week 86'd, the case for one more tray per delivery just wrote itself.