Bookings, menus, online ordering, search. Written by the people building the product, between services.
Last week's numbers arrive three different ways, so a quiet fortnight gets blamed on the wrong thing and the spend moves off a channel that was working.
A manager reads that guaranteed hours are law and starts rewriting contracts. That duty is not in force, while the record duties that are already carry a penalty.
An operator hears the packaging rules now apply and starts budgeting for fees. Most single-site restaurants fail the threshold test, and assuming wrongly costs money either way.
Staff are being told digital ID is now allowed, and a refusal at the bar is an argument in front of a queue. The Order that would permit it has not been made.
The till export carries a name and a price, not the dish description or the allergen line. The page a guest relies on is left holding what the catalogue lost.
The change was saved and never published, and there is no rollback. The kitchen believes the menu moved while a guest still reads a stale one, and the wrong dish reaches the pass.
The published specification carries fifteen endpoints and none touches the menu. A site built assuming a menu feed waits on something that is not documented.
A product carries a price per group and the group overrides it. Whoever copied one figure onto the site copied a single case and left the rest wrong.
An item record exists to complete a sale, so it stops at a name and a price. What a guest with an allergy must read is missing before the page is built.
A guest reads £24 on the page and is billed £27 at the table, and the wrong figure becomes a dispute in a full room. Three routes can move that price; none is the website.
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.
