Bookings, menus, online ordering, search. Written by the people building the product, between services.
A booking form that collects too much or explains privacy too late can leave restaurants with uncontrolled guest records, confused customers and complaints.
A borrowed food photo can trigger a rights dispute, takedown and urgent website rework when a restaurant cannot prove who authorised its use.
Missing entrance, seating, toilet or parking details can make a guest abandon the visit or arrive at a barrier the restaurant could have explained.
A booking button can hide a second contract, annual renewal and variable cover fees, leaving a restaurant’s true website cost unresolved.
A missed .uk renewal can leave a restaurant site looking normal for 30 days, then stop the domain resolving and threaten every direct guest route.
A withdrawn draft and moving timetable can send a restaurant towards the wrong tipping policy. Here is what applies now and what still awaits consultation.
An unchecked restaurant guest-list export risks unreadable columns, altered values and unmanaged personal data during a staff handover.
A cheap booking tier can leave guest history, messaging and export behind an upgrade, turning a growing guest list into a costly contract decision.
A restaurant can look ready on Google while its booking or ordering button opens the wrong branch, a dead page or a journey guests cannot finish.
A vague booking acknowledgement can send guests towards the door while staff are still checking the table, turning one unclear status into a service dispute.
A mandatory booking or delivery fee shown too late can turn a routine restaurant checkout into a refund exercise and a live CMA enforcement risk.
A web booking, a phone promise and a walk-in can claim the same table within minutes, leaving staff to resolve the conflict in front of waiting guests.
