Publishing a menu that stays true to what the kitchen serves.
One dish can carry four correct prices depending on where it sells. A page that copied the figure once publishes a stale answer the rest of the time.
The chef takes the hake off and the till is right in a minute. On Saturday the site still sells it, and a four-top loses the dish they chose the restaurant for.
The documented item has no allergen field, no ingredient list, no description. The line carrying the most risk is the one the till was never built to hand over.
The documented events are order events; nothing announces a menu change. A site told to cache and not to poll serves a stale dish until somebody notices.
The paper menu said Ribeye, 10oz, £29. The website says dry-aged for twenty-eight days, and the pass has to defend a sentence nobody in the kitchen wrote when a guest disputes it.
Immunity boosting broth read fine on a chalkboard for years. On a published menu it is a marketing communication, and the wrong wording is a breach rather than a flourish.
A guest is charged more than the menu said, and the argument happens at the table. The rule most owners cite does not even apply to a restaurant, and a drinks list carries a second duty nobody mentions.
When a recipe, supplier or substitute changes, stale allergen details can split the kitchen record, menu and staff answer before the next service.
A menu link may open on a phone yet leave guests pinching tiny text, waiting for a download or reading an out-of-date file.
A POS connection can be live while wrong names, variants, prices, availability or tax fields reach the public menu.
A free-from or vegan menu label can outlive the evidence behind it, creating a dangerous mismatch between the public promise and the kitchen.
A guest can reach checkout without clear allergen information, then receive a different answer with the order. Build one reliable two-stage check.
