Real time, actually: how orders move without anyone refreshing

Most restaurant software says it is “real time”. In practice that often means the page fetches new orders every few seconds if someone leaves it open. That is polling. It works until the room is busy and three people are still shouting across the pass.

Real time, in a kitchen, is a push: the moment a cashier sends, the ticket appears on the prep screen. The moment a chef marks it ready, the waiter’s list updates. Nobody reloads anything.

What actually gets pushed

One order can touch four screens without being typed twice:

If any of those waits for a refresh, you do not have live operations. You have a report that happens to be on a tablet in the kitchen.

The channel underneath is a live socket — the same idea as a chat app. The till publishes an event; subscribed screens receive it. That is why a dead Wi-Fi in the dining room and a working network in the kitchen still look like a working restaurant: the kitchen is subscribed to the orders, not to a page reload.

Notifications are a smaller set

A push to a screen is not the same as a ping in someone’s pocket. Treat them differently or the phone becomes noise.

Worth a notification:

• A new ticket on your station, if the screen is not in front of you.
• A delivery assigned to you.
• A table that has asked for the bill, if you are the waiter on that section.
• A low-stock alert the next morning, not in the middle of Saturday service.

Not worth a notification:

• Every status change on every order. That belongs on the screen that already shows the rail.
• Marketing to staff. That is how the important ping gets silenced.
• “Dashboard updated.” If they have the dashboard open, they can see it.

Customer notifications — order accepted, on the way, at the door — are a different product. They are how an owned channel feels finished. They should come from your name, which is why branded apps carry their own messaging project rather than a generic one.

Real time is not offline

People mix these up because both are about a connection.

• Offline mode is what happens when the till cannot reach the server. Orders queue locally and catch up later, exactly once.
• Real time is what happens when the till can reach the server: everyone else sees the order now.

You need both. A live kitchen with no offline queue goes dark when the line drops. An offline queue with no live push means the chef is still walking to the printer. They are complementary, not alternatives.

How to tell if a vendor means it

Ask to stand in the kitchen. Send an order from the till. The ticket should be on the screen before you have put the tablet down. Then mark it ready; the waiter’s list should move without a pull-to-refresh.

If someone says “it updates every ten seconds”, that is polling. Ten seconds is a lifetime when four tickets are stacking and a steak is already in the pan.

The point is not modernity. It is that a busy pass has no spare attention for a reload button.