Reliability and updates
How fast your changes reach guests, and how the guest menu keeps working on a weak connection or when our servers have a problem.
On this page
The guest menu is built to open fast for every guest, to show your changes quickly, and to keep working when a connection drops or something fails on our side.
How fast changes reach guests
A change reaches guests once it is live: saved on a published menu, or published — see Publish a menu.
- A guest who opens or reloads the menu after that sees the change straight away.
- A guest who already has the menu open sees it update by itself within about two minutes, while the page is on screen. What they added to their order and their place on the page stay as they were.
When a guest's connection drops
Once the menu has opened, guests keep reading it without a connection: they scroll, search, filter and open dishes as before. A bar at the bottom of the screen tells them they are offline and seeing the saved menu, and goes away when they are back online. The page then checks for changes you made in the meantime.
Photos the phone had not loaded yet can't be shown while it is offline. An order sent without a connection waits on the phone — see Questions about orders.
When our servers have a problem
Guest menus are served from a worldwide content delivery network, close to your guests. If our servers or database fail, a menu guests have already opened keeps opening, in its last version, until the problem is fixed. A page no guest has opened before can't be shown until then.