Coffee Shop QR Menu

The Modifier Problem, and How Not to Solve It Badly

Every café hits this within a week of building a digital menu. A latte comes in three sizes. It can be made with whole, oat, almond or soy. It can be single or double shot. Represented as separate items that is twenty-four entries for one drink, and a menu nobody can read.

The wrong solution is to create them all. The menu becomes a list where the eye cannot find anything because every third line is a near-duplicate of the one above.

The right shape is one item, with the variants in the description and the price structure stated once. “Latte — 12oz / 16oz, oat, almond or soy +75¢.” One line the guest reads in two seconds, instead of six lines they have to compare. Split into separate items only where the difference is genuinely a different drink rather than a different size of the same one — a cortado is not a small latte, and should be its own entry.

The same discipline applies to your food case. A pastry list is short and changes daily; it wants to be a category of six or eight items you edit each morning, not a permanent list with half of it crossed out.

Rotating Beans and the Origin Note

Speciality cafés have an information problem that printed menus solve badly: the coffee changes, and the interesting part is exactly the part that changes.

When you rotate a single origin every few weeks, the printed board says “filter coffee” and a chalk scrawl says the rest, if there is room and if someone remembered. Everything that justifies the price — producer, region, process, what it actually tastes like — either lives in a server’s head or does not get communicated at all.

On a digital menu that information costs nothing to carry. The current single origin gets a real description with its producer and tasting notes, and when the next lot lands you change the text rather than the board. Guests who care read it; guests who do not scroll past. Nothing about the printed code changes.

This is also the cheapest staff training you will ever do. A new barista in their first week can read the current origin note off the same menu the guest is reading, which is a considerably better answer than an improvised one.

Reading in a Queue Is a Different Job

Café menus get read in two quite different situations and most are only designed for one.

At a table, the guest has time. They are seated, they may be staying an hour, they will scroll. Depth is welcome — the origin note, the food case, the description of what a cortado actually is.

In a queue, they have about forty seconds and one hand, and someone is behind them. What they need is the drinks list, the prices, and nothing between those and their eyes. If your first category is a long food-case list, a queueing guest reaches the counter without having found the coffee.

The resolution is category order rather than two menus. Drinks first, always, because that is what the queue is deciding. Food case second. Anything discursive — the origin story, the retail bags, the loyalty details — last, where the seated guest will still find it and the queueing guest will not have to scroll past it.

If you have both a counter and a seating area, that ordering serves both. It is a five-minute decision at build time that most cafés get backwards because they built the menu in the order the printed board happened to use.

Frequently Asked Questions