Restaurant
The list at the table, on every phone.
Lunch, dinner, and drinks on one published list — counter QR, print, and TV. No guest app.
At the table
Put the food menu on their phone.
- Working copy in the builder. Guests see the last published snapshot.
- Snap a printed card. Import can translate. You still approve every line.
- Order queue on Plus+. Guests pay from the list.
- Same QR after you edit. One site is one business.
At the table
The list they read is the list they order from.
A QR on the table or the counter opens the list they already have in their pocket. Specials and 86’d dishes change on the published snapshot — you are not reprinting the card between tickets.
During service
Hide what sold out. Keep taking the rest.
One tap takes a dish off the live list. Guests scanning after that stop asking for it. Publish when the board is right. The QR on the door stays the same.
Payments
Pay when they order
They pay in full now from the food menu, or pay at the counter. You run the queue.
Three steps
List it. Order it. Get paid.
- 01Draft the list
- 02Publish a snapshot
- 03Put the QR on the counter
FAQ
Straight answers
We already have a website. Why another URL?
Your site is the brand story. ServeSlate is the working list at the table — prices, sold-out dishes, and a QR that updates without a developer. Keep the website. Put this link on the counter.
Can lunch and dinner share one QR?
Yes. Split the list into categories. Guests open one link and move between lunch, dinner, and drinks. You are not running two sites.
What do guests see while we 86 a dish?
Drafts stay in the builder. Hide the item and publish. The public URL and QR show the last snapshot until you publish again.