Photograph the menu you already print. Platter reads it, sets it properly, and puts it behind a QR code you never have to reprint. Change a price from the floor and every table sees it.
No integration, no POS, no training. Three steps, and the longest one is waiting for the reader.
012 minutesPhotograph the paperWhatever you already print: a laminated card, a PDF, a page in a notebook. Straight down, whole page in frame.
0230 secondsCorrect the draftEvery dish, price and section comes back editable, with the reader's uncertain lines flagged. Nothing is live yet.
031 minutePrint the codePublish, then export an A6 tent or a sheet for every table. That code never needs reprinting again.
Photograph the sheet. The reader pulls out dishes, sections and prices, keeps the order you wrote them in, and hands back a draft, flagging every line it wasn't sure of.
The code encodes a link, never menu content. Raise a price, hide a dish, switch the whole theme. Every tent already standing on a table keeps working.
The paper menu regenerates from the same dishes, so the wall can never disagree with the screen.
Mark a dish and it takes the seal, then rises into the popular shelf at the top of the menu.
Vegetarian, vegan, pork, seafood, gluten-free, plus an allergen list on every dish card.
Set your own, and optionally show an approximate second price beneath it for visitors.
Staff flip sold-out and nothing else. Managers edit and publish. You keep billing.
A concierge panel on the menu answers what is mild, what is popular, and what sits under a price.

Mark a dish gone from your phone, standing on the floor. It sinks to the bottom of its section, dims, and stops being ordered. At 04:00 it comes back on its own.
Each theme is a different set of typographic decisions, not a colour swap, and every one previews on your real dishes before you commit. See all four →
Platter counts taps, not orders, so it never pretends to be revenue. What it does tell you is which dishes get opened, which never do, and what diners typed that returned nothing.
Each one is either a dish to add, or a name to change. Jollof is on this menu, filed under Nigerian Dishes, where nobody looked.
The right-hand column is the entire pricing page. Most of it is free, and stays free.
Dishes, sections and prices, set to be read on a phone across a dark table.
Photograph the paper. It comes back editable, and stays a draft until you publish.
One per menu or one per table, exported as PNG, SVG or a print-ready sheet.
Regenerated from the same menu, so the paper can never disagree with the screen.
Mark a dish gone from the floor. It sinks, dims, and returns at 04:00.
What diners opened, what they searched for and didn't find, and when they look.
Dinner, bar, breakfast, Christmas. Each with its own theme and its own code.
Lacquer, Carafe, Counter, Palm, previewed against your real dishes.
Point your address at the menu. No Platter mark anywhere on it.
Managers edit, staff flip sold-out, you approve. Revoke when they leave.
No. The code opens the menu in the browser already on their phone. No download, no account, no login. That is the entire point.
Upload whatever you have. The importer reads the dishes, prices and sections into a draft. It gets things wrong sometimes, which is exactly why it lands as a draft. You correct it, then publish.
Yes, from your phone, and it is live immediately, including on the codes already sitting on the tables. That is the difference between a dynamic code and a printed PDF.
Nothing. The code encodes a link, never menu content. Edit prices, hide a dish, switch the whole theme. Every tent already on a table keeps working.
Jīn Cāntīng runs 258 across 19 sections on Platter. Nobody typed them in.
One menu, the import, QR codes, print and insights, forever, without a card. Pro is for more than one menu, your own domain, or people other than you editing.
