How to Build a Digital Menu People Actually Read

The menu is the one page every guest at your tables will open. Not your website, not your Instagram — the menu. Here is how you build digital menu content that reads well: categories, 120-character descriptions, the seven tags, photos, and the toggle you'll be grateful for at 21:00 on a Friday.

The menu is free on every plan — unlimited categories and items, photos, prices, tags, up to three languages. None of it sits behind an upgrade.

Build the skeleton before you write a word

Open the Menu tab in your owner panel and lay out categories first. Coffee, Cold Brew, Pastry, Brunch, Wine — five tabs a thumb can reach.

The temptation is to mirror your printed menu exactly. Resist it. Paper is a poster; a phone is a column you scroll. If a category holds twenty-two items, that's a scroll of shame — split it. If it holds two, fold it into its neighbor.

Names and descriptions: 120 characters is the whole craft

The name is the name. "Flat White", not "Our Signature House Flat White Experience".

Descriptions cap at 120 characters per language, and that limit is doing you a favor. It's about one honest sentence — enough to answer the only question a guest has: what actually arrives on the table?

Good, and under the limit:

• "Double shot, silky steamed milk, 6 oz. House blend — chocolate and hazelnut."
• "Sourdough toast, smashed avocado, chili flakes, poached egg. Add bacon for $3."

Bad, and you already know why: "A delightful journey for your senses." That has never sold a coffee.

When in doubt, write down what your staff already say out loud when someone asks.

Price, currency, and no surprises

Each item takes a price and a currency, formatted for the content language — a guest reading in English sees the number the way they expect it.

One piece of discipline: if the price on the phone doesn't match the price at the register, you've manufactured an argument at your own counter. Update the menu the morning you change a price.

The seven tags — treat them as scarce

There are exactly seven: new, popular, vegan, vegetarian, glutenfree, spicy, chef. You can put up to six on one item. You should almost never put six on one item.

Tags mean something only when they're rare. If everything is popular, nothing is. Honest suggestions:

• popular and chef: two or three items across the whole menu. Total.
• new: only while it's actually new. Set a monthly reminder to clear the old ones.
• vegan / vegetarian / glutenfree: not marketing — information. Be exact; someone is making a real decision with these.
• spicy: only if it would surprise someone.

If the tagged items jump out at a glance, the tags are working. If they blur into the background, you've used too many.

Menu photos: most items don't need one

Each item takes one photo — JPEG, PNG or WebP, up to 5 MB — plenty for a phone shot in daylight.

But a half-photographed menu beats a fully-photographed one done badly. A beautiful shot next to a dim, flash-lit one makes the second item look worse than no photo at all.

So photograph the things people order with their eyes (the layered cake, the loaded brunch plate, the cocktail) and the things nobody can picture from the name alone. One or two heroes per category. Skip espresso and sparkling water.

One free trick: shoot everything on the same table, near the same window, at the same hour. Consistency reads as quality more than any single good shot.

The 21:00 toggle

Friday, 21:00, the last cheesecake just left the kitchen. Every item has an active/hidden toggle. One tap, and the next four tables never ask for it.

Owners forget it exists — teach it to whoever closes. Hidden isn't deleted: the item, photo and description wait for tomorrow's delivery.

No cart, no ordering — on purpose

The menu is view-only. No basket, no "order now", no payment. That's a decision, not a missing feature.

A cafe is not a delivery app. The moment a guest orders through a screen, you lose the thirty seconds where your server says "the Ethiopian is unreal today" — the thirty seconds your business runs on. The menu does one job well: it shows what you have, right now, with no app install.

What the guest sees

Their side is plain, which is the point: category tabs across the top and a search box. Someone who wants oat milk types "oat"; someone browsing taps Pastry.

The same QR also opens your games module — all 28 of them, Taboo included — so the wait stops being dead time. The demo venue is a real, fully-populated example to poke at, and the blog has more setup guides.

Every menu render is counted, so "menu views this month" shows on your dashboard even on the free plan — you'll learn fast whether the QR on table 4 gets scanned.

Go build it

Block out an hour. Categories, names, descriptions, a few photos worth taking, then tags — sparingly. That's a menu.

Registration is free: no card, no password, just your venue name and an email code. Start at Kafedeyim for business and go put the QR on the tables.