86’d dishes: how one switch turns them off on the menu, the tablet and room service at once

It is nine at night and the hotel restaurant’s kitchen just ran out of the steak cut the printed menu has advertised for three months. The server already knows. The kitchen board already knows. The guest ordering from the tablet in their room does not know yet. They order the steak, wait twenty minutes and get an awkward call: it is gone. That guest is not upset about the meat. They are upset because the system lied to them.

The guest who orders what is no longer there

Ordering at a hotel carries an implicit promise: whatever appears on the menu, on the table tablet or on the room service digital menu exists and can be ordered. When that promise breaks, the guest does not just lose the dish they wanted. They lose trust in everything else the hotel offers, because if the menu lies on one line, why trust the other thirty?

The problem is rarely that the kitchen carelessly ran out of a product. The problem is almost always that the hotel has three or four surfaces where a guest can see the menu, and turning a dish off on one of them does not turn it off on the rest.

What "86’d" means in a hotel kitchen

A dish can sell out for two different reasons, and it is worth not confusing them. The first is that a key ingredient ran out, and with it every dish that uses it sells out too, not just one. The second is that the dish itself gets pulled by a kitchen decision, even though the ingredient still exists, for example because there is no longer time to prepare it properly before close.

Telling the two apart matters, because the first almost always turns off several dishes at once and deserves a check against inventory, while the second is a one-off operational call that can be turned back on the next day without further process.

One switch, every channel

The fix is not having someone walk through the printed menu, the table tablet, the digital menu (Digital menu) and the room service catalog (Room service) turning off the same dish four separate times. The fix is that the dish gets marked as sold out once, in one place in the system, and that mark reflects instantly on every surface where a guest can order, with no exceptions.

This sounds obvious stated plainly, but in practice many hotels still treat the printed menu, the tablet menu and the digital menu as three separate files someone updates by hand, at different times, all but guaranteed to fall out of sync.

What your system actually needs for this to work

It is not enough for the system to have an availability field per dish. That field needs to be the same one for every channel, not a copy that syncs every few minutes. A five-minute sync sounds fast until a guest manages to order within that window and the dish is already gone.

It is worth asking your point-of-sale provider directly how long an availability change takes to show up on the tablet and on the digital menu. If the answer is "a few minutes" instead of "instantly", that is exactly where the next phantom-dish complaint is going to come from.

How it propagates: from the kitchen to the system, from the system to every channel

The right flow starts in the kitchen, not in the dining room. When the chef or station lead marks a dish as sold out at the point of sale (Point of sale), that mark is saved to the restaurant’s catalog, which is the single source of truth on what is available. From there, every channel that displays the menu reads that same catalog in real time, so there is no separate file to update by hand.

The practical result: the server turns off the steak cut in the kitchen, and in the same second it disappears from the tablet at table seven, from the digital menu a guest has open on their phone, and from the catalog the front desk uses if someone asks over the phone.

The 86 report: what it says about your buying and your menu

Every time a dish is marked sold out, it leaves a record: which dish, at what time, on which shift. That report, gathered over a few weeks, tells two different stories depending on which dishes show up most often.

If the same dish sells out every Friday at eight at night, the problem is not buying, it is quantity ordered: you are buying less than your real Friday demand needs. If a dish sells out erratically, with no pattern of day or hour, the problem might be supplier quality or a badly calculated waste allowance.

An illustrative example

The numbers below are made up to show the reasoning; they do not describe any real property.

In the example, the steak cut sells out four times in four weeks, always on a Friday: that is a clear signal to buy more for that specific day. The seasonal dessert sells out six times, more than any other dish, always on a Saturday: it is probably worth increasing the batch prepared every Saturday before concluding the dessert "does not work".

Turning it back on in time

Turning a dish off is half the job. The other half is remembering to turn it back on once the new supplier order arrives, and that half is the one most often forgotten. A dish sold out on a Thursday for lack of product can still show as sold out the following Saturday, with plenty of inventory on hand, simply because nobody reversed the mark.

• Review the sold-out list every morning, not only when someone complains a dish is missing from the menu.
• Tie the dish coming back on to the confirmed arrival of the ingredient, not to the date the purchase order was placed.
• If a dish has been sold out for more than a week, decide whether it is really coming back or whether it should come off the menu until further notice.

Common mistakes managing availability

1. Turning the dish off only on the printed menu and forgetting the tablet or the digital menu, which keep showing it as available.
2. Confusing a sold-out ingredient with a sold-out dish and turning off only one of the several dishes that share that ingredient.
3. Leaving the decision to turn a dish off with a single shift, with no handoff telling the next shift to reconsider it once new stock arrives.
4. Never checking the sold-out report and only learning the pattern from scattered comments from the floor team.

What to do this week

1. Confirm that turning a dish off at the point of sale also turns it off on the tablet and the digital menu with no extra steps.
2. Review the last four weeks of the sold-out report and flag the two dishes that repeat the most.
3. For those two dishes, decide whether the fix is buying more, preparing a bigger batch, or dropping them from the menu.
4. Define who is responsible for turning a dish back on once new stock arrives, so it does not stay off longer than it should.
5. Explain the difference between a sold-out ingredient and a sold-out dish to the floor team, so they report it accurately.

Inn Restaurant links dish availability across the kitchen, the point of sale, the tablet and room service, with a single switch and a weekly sold-out report. If you want to see how it works for your hotel’s restaurant, book a fifteen minute demo (contact).