The questions that
actually come up.

In the connected dashboard, every change you confirm is saved straight away: there’s no draft to apply and then a “save changes” button. When saving finishes you’ll see “Changes saved to your menu”.

• If saving fails, you’ll see the error and your change stays on screen. A save that didn’t happen is never shown as done.
• If the server confirms the save but sends back a menu that can’t be shown in full, your change is already saved: the dashboard tells you and carries on with what you just sent, without blocking you.
• What the dashboard does stop for is data it can’t read, for example when reloading: it keeps the menu you can see and doesn’t save over it, so older data isn’t overwritten. Let us know before you carry on editing.
• In the local demo, with no account, the menu is only saved in the browser you’re using.

If your menu changed on another device or in another tab, the dashboard notices when you save and asks you to reload the saved data before you carry on. Work from the other device is never overwritten without warning.

• Open Where your work is saved and use Reload saved data.
• The dish you were editing is kept when you reload: nothing you were typing is lost.
• If there’s a local change that couldn’t be saved, you’re asked to confirm before it’s discarded.
• To avoid it, edit from one device at a time, especially during service.

Each photo is prepared on your own phone or computer before it leaves it: it’s resized to 1000 pixels on the longest side, saved again as a JPEG and stripped of camera metadata, including location.

• Accepted formats: JPG, PNG or WebP, under 5 MB. If the image can’t be read, the dashboard says so instead of leaving it half done.
• If it’s still too large after resizing, choose a smaller image: there’s a limit per photo.
• Photos are optional. A dish without a photo shows its text first and doesn’t leave a grey gap.
• If a photo doesn’t load, the dish shows without an image; another dish’s photo is never used.
• If your menu was saved but a photo couldn’t be uploaded, reload the saved data to try again.

Your menu starts out private. When you press Publish menu, anyone with the link can see it, and Link and QR for your tables appears, with the link, a copy button and a QR code you can download as a PNG.

• The QR code doesn’t change when you edit dishes or prices: print it once.
• The link’s identifier is permanent, precisely so that printed QR codes keep working.
• Hide menu asks you to confirm, and the QR code opens nothing until you publish again.
• Before publishing you can check it with the owner’s preview, which needs you to be signed in and doesn’t show unpublished dishes.

Marking a dish as sold out, or bringing it back, takes one tap, with no confirmation window and an instant Undo, because it’s the action you use most in the middle of service.

• A sold-out dish disappears from the diner’s menu and from the recommendations.
• Actions that destroy work, such as deleting a dish, restoring the example or hiding the menu, do ask you to confirm.
• Diners can’t order, pay or call a waiter from the menu: TableFlow only helps them decide. If you mark something as sold out, nobody ends up with an order you can’t serve.

Unfinished dishes are kept separately and only in the browser you’re using, split by account and restaurant. They aren’t published as dishes until you confirm them.

• On another phone or computer you won’t see those unfinished dishes, even if you sign in with the same account.
• Clearing your browser data, or using a private window that you then close, deletes them.
• If the browser blocks storage, the dashboard warns you and asks you not to close an unfinished dish, rather than losing it silently.
• The theme you chose in the demo and the “tutorial completed” mark also live in that browser.

In the Languages section of the dashboard you choose the main language of your menu (English, Spanish, Catalan or French), the one you write it in, and the currency for your prices (euros, pounds or US dollars).

• Anything you don’t translate shows in your menu’s main language.
• The dashboard works in English or Spanish: switch with the English or Español button.

Email cristiancaride@gmail.com: that’s where your account and your restaurant are checked, and where cancellations are handled. We reply by email; there’s no phone line or support hours.

• Tell us what you were doing, what you expected and the exact text of any error message.
• If you can’t sign in with Google, first try another network or browser, and mention it in your message.
• If you need a copy of your text and prices, download it from Help and data for your menu in the dashboard before you write.
• Don’t send passwords or your customers’ data to describe the problem.