Breakfast menu
Runs from open until 11:00.
Digital Menu / QR Menu
Your menu, on every table, in every language.
One catalog drives QR menus across branches, languages, and allergen rules. Update once, live everywhere — and yes, the same catalog runs your POS and every marketplace.
Start here
The QR menu is the front door to your whole operation.
The QR menu is where most operators first meet dojofood. Thousands of cafés and restaurants print our code, paste it on the table, and let customers scan — the menu, the photos, the allergens, in whatever language the customer chose.
It works the same way at one table or a hundred: scan, browse, see exactly what's available right now. What makes it different is what sits behind it.
The QR menu reads from the same catalog that runs your POS, your kitchen display, and your marketplace integrations. Same items. Same prices. Same 86 logic. When you're ready, the rest of the operating system is one switch away — no menu rebuild, no migration.
Start with the QR menu. Add the POS when you outgrow the cash drawer. Add marketplaces when delivery picks up. Same catalog the whole way.
One catalog, every QR code
Update once. Live on every table in seconds.
Most restaurants run more than one menu. A breakfast menu and a dinner menu. A bar menu and a kitchen menu. A two-language tourist menu and a three-language summer menu. Plus the takeaway sheet. Plus the late-night list.
In most QR menu tools, that means rebuilding the menu inside the tool — usually by hand, usually by someone who doesn't run the kitchen, usually a week later than the kitchen needed.
dojofood doesn't have a separate menu inside the QR tool. The QR menu reads from your catalog. Change a price in the catalog, every QR menu in every branch shows the new price within seconds. Add a new dish, photograph it once, write the description once, tag the allergens once — every QR menu picks it up.
86 the burrata at 9:15pm because you ran out. The QR menu shows it grayed out at 9:15:03pm. No edit. No screen swap. No one printing a new card.
Time-of-day
Breakfast at 10:59. Lunch at 11:01. Same QR code.
The QR code on the table doesn't change. The menu behind it does.
Lunch menu
Takes over from 11:01 until 16:00.
Dinner menu
Runs from 16:01 until close.
Late-night list
Comes in at 22:00 on Fridays and Saturdays only.
You set the windows once. The system handles the switch. The customer scans the same QR they scanned last week and sees the right menu for the moment they walked in.
Some operators run a different breakfast menu on weekends. Some run a tasting menu only on Thursdays. Some run a kids' menu that surfaces only on certain branches. All of that is configuration, not a separate menu file.
The details
The boring details that matter.
The QR menu is where tourists, regulars with allergies, and the table that doesn't speak your language all meet. The details are the trust.
Languages
Turkish, English, German, Arabic, Russian, French — whatever your operation needs. Translations live on the item in the catalog, not in a separate menu file. Add a language once; every QR menu in every branch gains it.
Allergens and dietary tags
Gluten, nuts, dairy, shellfish, vegan, vegetarian, halal — tag once in the catalog, filter on the customer's screen. The customer turns on "no gluten" and the menu hides what they can't eat.
Photos
Upload once. Show on the QR menu, the website, the marketplaces that accept your photos, the POS if your team uses image mode. One image, every channel.
Descriptions
Operator-written, in every language you support. Not auto-translated by a chatbot — written by you, kept by us.
Modifiers
"No onions, extra cheese, sauce on the side" — the same modifier tree your kitchen sees on the KDS.
Per-branch variation
Branch 02 sells the rooftop cocktail. Branch 01 doesn't.
If you run more than one location, the QR menu respects that. Branch 02's terrace has a cocktail nobody else carries. Branch 01 has a kids' corner. Branch 03 runs a 24-hour late menu that the other two don't.
You don't need three QR menu tools. You don't need three menu files. The catalog carries everything; each branch's QR menu surfaces what's enabled for that branch.
When a customer scans the QR code at Branch 02, they see the cocktail. When they scan at Branch 01, they don't. Same catalog, different surface — set by the rule, not by a copy-paste.
Preview
Scan the staff QR before lunch service. See what the customer sees.
Every change you make gets a preview link. Open the staff QR on your own phone, see the menu the way a customer will see it, in any of your languages, at any of your branches, on the time window you choose.
If something looks wrong — a missing photo, a translation that drifted, a price that didn't propagate — you catch it before the dining room does. Not at 8:30pm when a table flags it.
Edge cases
86'd live. Time-windowed. Course-paced.
86'd items, live
Stock runs out, the QR menu marks it unavailable in seconds. The customer scrolling at the table sees the grey, the customer about to order sees nothing they can't have.
Time-windowed items
A weekend brunch combo that only appears Saturday and Sunday 10:00 to 14:00. Set the window, walk away.
Marketplace overlap
The QR menu is one channel. Uber Eats, Yemeksepeti, Trendyol Go, Getir Yemek, Migros Yemek (and Wolt, Bolt Food as they land) are others. Same catalog feeds them all. The QR menu doesn't fight the marketplace menu — it's the same menu, surfaced differently.
Course pacing
If you sell tasting menus, the QR menu can show the courses in order or hide later courses until the previous one fires. Optional, configurable, off by default.
See it on your phone
Start with the QR menu. Grow into the operating system.
20 minutes with our team. Bring your current menu (PDF, paper, screenshot — whatever you have). We'll show you the QR menu live, in your languages, on your phone, before you leave the call. Live in days, not months. Real humans when it breaks. Monthly billing. No setup fee. No payment-processing lock-in.