What the Pattern on Your Restaurant Table Really Is: How Contactless Menus Work
How black-and-white patterns replaced paper menus
Small black-and-white patterns started appearing on restaurant tables as an infection-control measure in 2020. To cut down on contact through paper menus handled by one guest after another, huge numbers of restaurants put a code on every table. Once the hygiene argument faded, many of those codes stayed in place, because other advantages had become visible. Swapping a dish takes nothing more than an edit in an admin screen, with no printing and no reinserting of pages. Photographs and allergen notes can be added without fighting for space on a printed sheet. The display language can follow whatever the guest's phone is set to. None of those three benefits has anything to do with hygiene, so in restaurants that had already wired the system in, it simply became part of daily operations.
From scan to menu screen, step by step
What the pattern holds is not a picture but a single line of text. In most restaurants that text is a URL along the lines of https://restaurant-domain/menu?t=12. The camera reads the light and dark cells, turns them back into that string, and the phone hands the URL to its browser. From there it is an ordinary web page: the browser sends an HTTP request to the server and displays the HTML and images that come back. No dedicated app is needed because the whole sequence is split between the camera and the browser, two things the phone already has. The t=12 on the end is extra information that identifies the table, and the server reads that value as "someone is viewing from table 12". Even when every guest opens the same menu page, each table carries a different URL, and that is the big difference from a paper menu.
How an order reaches the kitchen and the bill
Because the table number rides along in the URL, orders are tied to the table as well. When a guest picks dishes on screen and submits them, the server stores the table number, the items, the quantities and the time received as a single order record. On the kitchen side that record flows into a printed ticket or a queue on a display, and the cook reads it as "one fried chicken for table 12". Follow-up orders arrive under the same table number, so the tickets stack up into one bundle per table. At payment, the tickets are grouped by table number and totalled, so the register only has to produce the sum for the table that called for the bill. The old sequence of walking the floor to take orders, relaying them by voice to the kitchen and gathering tickets by hand is replaced by a chain held together by that one value: the table number.
Preparing the table codes and keeping them current
The first thing to prepare at installation is a list of URLs that differ only in the value on the end, one per table. A restaurant with 40 tables generates 40 URLs in one batch, converts each into a code and prints them. For mounting, a laminated card lying on the table or a printed sheet in an acrylic stand are both easy to work with, and either can be swapped in a few seconds. The code needs a margin of at least four modules around it, the quiet zone, so resisting the urge to crowd it with frames and decoration pays off directly in read rates. What really matters in daily use is keeping a table-to-code chart on the restaurant's side. If tables are rearranged or a new one is added and the chart is not updated, orders start flowing to the wrong seat. A single walk-through before opening, looking only for smudges, curling and chipped corners, heads off most read failures.
Estimating code size and printing costs
The side length of a code can be worked back from the distance you want it read at. A useful rule of thumb is a reading distance of three to ten times the side of the code, so a 3 cm code covers roughly 9 to 30 cm and a 5 cm code roughly 15 to 50 cm. A card that guests pull close and lean over works at 3 cm, but if you want it read from the far corner of the table, plan on something closer to 5 cm. The money side can be estimated too. If a 40-table restaurant prints 50 copies of an A3 folded paper menu at 80 yen each, that is 4,000 yen, and revising it once a season comes to 16,000 yen a year. On the digital side, hosting the page at 1,000 yen a month is 12,000 yen a year, plus the separate labour of photographing dishes and entering data. Unit prices and revision cycles differ from one restaurant to the next, so these figures are only an estimate built on stated assumptions. Even so, they show that the paper cost does not simply vanish, and you can check that for yourself by substituting your own prices.
What happens at tables with weak reception
In a basement or a seat surrounded by thick walls, the code may scan while the page refuses to open. The cause is the connection, not the code, so reprinting the code changes nothing. What the restaurant can do is build the page so the text menu appears first and the photographs load afterwards, which makes the wait feel shorter. Even when content already loaded stays cached on the phone, the very first view still needs a connection, so this does not fully rescue a table with weak reception. The dependable fallback is keeping a few paper menus on hand and handing one to any table where loading stalls. It also helps to print the table number and the URL in plain characters next to the code, so a guest whose scan fails can type the address in, and so anyone calling a server can say which table they are at.
Why paper menus stay in service alongside
Restaurants that never fully drop paper each have concrete reasons. Some guests cannot comfortably read small type on a screen, some are not used to operating a smartphone, and some are away from a charger and watching their battery. At other tables, several people leaning over one booklet and pointing at dishes is the point of the meal, and that cannot be reproduced when everyone stares at their own screen. Allergen checks also work differently on paper and on screen. Under Japan's food labelling standards, allergen labelling is required for packaged processed foods, while dishes served to guests at the table fall outside that requirement. Showing allergens on a digital menu is a voluntary effort by the restaurant, and how much information is covered varies from place to place. If symptoms can be serious, the reliable move is to ask a member of staff rather than relying on what is on screen.
Scanning tips, and a word on fake stickers
When a code will not read, start by changing the distance between the phone and the code. Too close and the whole frame will not fit in the viewfinder; too far and each cell of the pattern becomes too small to resolve. In a dim room, raising screen brightness helps recognition, and with an acrylic stand, tilting it slightly to keep the lights from reflecting off the surface often does the trick. If it still will not open, there is nothing wrong with asking for a paper menu. One more thing worth watching for: there are schemes where a different sticker is pasted over the legitimate code. Take one look at whether the domain of the page you land on matches the restaurant's name, and if you are suddenly asked to log in or type a credit card number, stop there.