A slow sold-out signal is quietly expensive: you sell what the kitchen can no longer make, and pay the apology in comped dishes and reviews. Real-time availability means: the moment the kitchen drops a dish, every surface that could still sell it knows — fast enough that the next guest doesn't order into a lie.
It's a small moment with big consequences: the kitchen drops the trout because it's out. The only question is — how fast does the rest of the world know? If minutes pass between “out” and it disappearing from the menu, in that window the next guest opens the menu, orders the trout, and gets an apology moments later. A slow sold-out signal is a lie in slow motion.
Real-time availability flips that around: the moment the kitchen drops a dish, every surface that could still sell it knows about it — web, app, the menu at the table, connected platforms. Two seconds is a fair time on the in-house network; thirty seconds is the road to a run of one-star reviews for “ordered, but never got it.”
Announce immediately, don't poll later
The heart of it is the direction of the signal. A system that only asks every few minutes whether something has changed is always too late. Better that the change announces itself — the moment the dish is dropped, the message goes out to every surface at once. And it has to be robust against everyday chaos: if a manager double-taps in the heat of it, the dish can't be dropped twice and then accidentally revived.
Stay honest when the network wobbles
No network is perfect. If the connection drops briefly, the change shouldn't be lost, but wait and catch up as soon as it's back — and when in doubt, honestly show when the status was last updated. That honesty isn't a flaw, it's part of the trust: a “last updated a minute ago” is better than a false availability that pretends everything is current.
Turn “sold out” into a suggestion
When the data is right, a sold-out dish doesn't have to end in a dead end. Instead of a flat “not available,” the page can suggest a fitting substitute to the guest — a similar dish the kitchen can deliver. That way a small operational detail becomes a moment of good service instead of a letdown. And who dropped what and when stays traceable, in case a pattern shows up.
The 7 most common mistakes
- Minutes of delay before a dish disappears everywhere.
- Only polling instead of announcing the change immediately.
- Only one channel updated — the menu, app or platform lags behind.
- No protection against double-tap — the dish gets accidentally revived.
- The change gets lost when the network drops briefly.
- No honesty about the last status during connection trouble.
- A flat “sold out” instead of a fitting substitute suggestion.
How to make availability fast
Frequently asked questions
Aren't two seconds overly precise?+
What happens if the Wi-Fi drops briefly?+
Does the dish really have to disappear on every channel at the same time?+
Isn't a sold-out modal just the end of the order?+
Availability is trust
Whether a dish is out, the kitchen knows immediately — the question is whether the guest finds out in time. An availability that announces itself across every channel in seconds, is guarded against the pitfalls of everyday service, and turns “sold out” into a suggestion, turns a quiet operational risk into a trust product. Nobody orders what the kitchen can't deliver anymore — and that's exactly what a guest remembers.
