Hide sold-out dishes on the QR menu between services

The fish of the day is gone. Service knows. The paper menu does not. For an hour you keep selling something the kitchen cannot plate — or the team runs table to table to warn people.

That warning gets forgotten. The guest gets angry. You lose a dish and a bit of trust.

Paper cannot delete a dish at 14:10

Crossing it out looks cheap. Pulling the sheet and reprinting does not arrive in time. “Tell them at the table” does not scale on a Saturday with a full terrace.

A QR menu is not magic. It is the ability to show or hide a dish by location — bar, terrace, dining room — without touching the code already printed.

What you do in Ordenala between services

You open the panel (or finish publishing what you designed without an account) and hide the dish. Guests who scan now do not see it. Guests who already had the menu open refresh and do not see it either.

You can leave it visible only at the bar if a short portion remains, and hide it in the dining room. Zone prices still apply. Allergens and languages do not break because you did not generate a new PDF.

The team stops being the patch

When the carta lies, staff become the menu. That is exhausting and uneven: table 12 gets the warning; table 4 does not.

A digital menu that matches tonight means fewer “sorry, it’s gone” after taking the order. It means the tourist does not order in English a dish that no longer exists. It means Instagram and the table say the same thing.

Print the QR once. The 86 lives in the panel.

Basic covers two locations and an internal-path QR. Standard and Premium add locations, languages, and a subdomain. On every plan the gesture is the same: hide or show without reprinting.

Design first without signing up. Publish when the menu looks like tonight’s kitchen, not yesterday’s.

Create my QR menu — hide what’s gone in a minute. No account until you publish. No reprint.