QR ordering FAQ: 50 questions answered

A small cafe gets the first table order in under an hour, including printing QR codes. A full-service restaurant with 40 tables and a long menu takes one afternoon, mostly typing menu items. No installer visit needed.

No. The QR points to a MobiTaste subdomain you get for free, like karakoy-cafe.mobitaste.com/... You can connect your own domain later from settings, but most cafes never bother.

Print them yourself. Open the Tables page, hit Print, get a PDF with one A6 QR per table. Stick on a coaster or table tent. We do not mail QRs because shipping adds days and you may want to reprint.

Yes. Each menu item has an English text field and a Turkish text field. Prices are shared. Guests switch language on the menu and see the right copy. Add a third language later if you want.

Not yet from a PDF, but you can paste a list. The Menu page has a bulk-add field where each line becomes an item with a default category and price. Categories you create first, items after.

No. The QR opens the menu in the phone browser, no install. We tested on Safari, Chrome, and Samsung Internet. A 4G connection and a recent phone are enough; nothing to fetch from a store.

The menu still loads if guests use mobile data. New orders queue and submit when your dashboard reconnects. Already-confirmed orders sit on the kitchen screen; a brief offline window does not lose tickets.

Yes. Every account ships with a demo table token. Open it on your own phone, place a fake order, watch it land on the kitchen screen. You can run a full dry run before the first guest sees a QR.

Yes, and that is the point. Each staff member gets a role: owner, manager, server, kitchen. The kitchen screen shows tickets and not prices. The owner sees revenue. You set this up under Staff.

Yes. Your organization can own several restaurants. Each restaurant has its own menu, tables, and team, but you log in once and switch between them. Billing rolls up to one invoice.

Starter is $10 a month, fits up to 20 tables, and includes the live order board and waiter approval. The first 50 MobiTaste customers stay locked at $5 a month for life on Starter.

No. The subscription is the full price. You pay $10, $25, or $60 a month depending on tier and there is no per-order cut, no transaction fee, no plus-tax-surprise.

Starter has a 14-day free trial and you do not enter a card. After 14 days you either subscribe or stay frozen with a read-only menu. Growth and Pro start their trial when you upgrade.

Starter is one restaurant, 20 tables, two locales. Growth is $25, three locations, 60 tables each, custom domain, analytics. If you grow past 20 tables in one shop, jump to Growth. Otherwise Starter is enough for years.

Yes. Cancel from the Billing page and the subscription stops at the end of the current month. No cancellation fee. Refunds for the current month are honored if you cancel within 30 days of the charge.

The early-50 lock at $5 a month is for life on Starter. Public Starter is $10. If we raise the public price later, the early-50 cohort stays at $5. Growth and Pro prices may change with notice.

Billing runs through Paddle in USD. Paddle bills your card in TRY using the daily rate and shows VAT on the invoice. So you swipe a TL card, the line shows USD, and TRY is what your bank charges.

Visa, Mastercard, American Express through Paddle. Apple Pay and Google Pay on supported browsers. No bank transfer at Starter; Enterprise customers can request invoice billing with a 12-month commitment.

Yes. Annual billing saves 16 percent on Starter, Growth, and Pro. Pay 10 months, get 12. You switch in the Billing page; the saving applies on the next renewal. Enterprise has its own multi-year terms.

Honest answer: most $5-and-under tools are free menu viewers, not ordering systems. MobiTaste Starter at $10 includes ordering, kitchen screen, and waiter approval. Below $10 you usually trade ordering for a static digital menu.

Yes. The QR opens a regular HTTPS web page. No app, no permissions asked, no contacts or photos accessed. The page sees the table token and the order; nothing else. Guests can close the tab and the session expires by itself.

On EU servers (Frankfurt), encrypted at rest. Turkish accounts also fall under KVKK. EU accounts under GDPR. We do not transfer guest data to the United States. Detailed routing in the security guide.

Postgres row-level security. Every query the dashboard makes is filtered by your restaurant id at the database level, not at the application level. If the app code were buggy, the database would still refuse cross-tenant reads.

By default, no. Guests do not log in, give a name, or leave an email. If you turn on the optional table-call feature, the guest may type a name they want the waiter to see; that is the only personal field.

Every menu, price, table, and staff change with a timestamp and the user who did it. Kept 12 months on Starter and Growth, 36 months on Pro, indefinitely on Enterprise. Exportable as CSV from the dashboard.

No. We do not sell guest or restaurant data. We use Paddle for billing and Cloudflare for the CDN, both as data processors under DPA. Names listed in the privacy page. No advertising trackers on the guest menu.

Yes. After cancellation you have 30 days to export menus, orders, and audit log as CSV. On day 31 we delete the data from production and on day 60 from backups. Confirmation email goes to the owner address.

Hashed with argon2id, the algorithm the OWASP cheat sheet recommends. We never see your password in clear. If we get breached, the hash file is not a password file. Two-factor login is on the roadmap for Q3 2026.

The table session sits idle. After 30 minutes of no activity it auto-clears so the next guest starts fresh. You can set the window between 10 and 90 minutes per restaurant. The waiter can also clear it manually.

Turn on waiter approval. The first order from every table waits for a staff tap in the order board. The kitchen never sees an unapproved order. Once a table is approved, follow-up orders go straight through unless you require approval each time.

Yes. The waiter view lets staff open the same menu, pick items for any table, and confirm. Useful for older guests, walk-ups, or the bar. The order shows on the kitchen screen with the waiter's name.

The cook taps the order card from In Progress to Ready on the kitchen screen. The waiter view turns the row green and a tone plays once on the floor tablet. No printer needed; KDS replaces the paper KOT.

Yes. Mark items as 86'd (out of stock) and they disappear from the guest menu within seconds. Edit a price, the next scan sees the new price. Changes show in the audit log so the team knows who did it.

Both orders go to the kitchen as two lines. The bill shows two of the item, not one. Each line carries the guest's choices (size, modifier) so the cook does not merge them by accident.

Yes. There is a Call waiter button on the menu screen. The waiter view rings on the floor tablet and shows the table number. Toggle it off per restaurant if you do not want it.

Kitchen language. You set it once under settings; the cook always sees orders in Turkish even if the guest browsed in English. Item names and modifiers translate at render time, so spelling stays consistent.

It works next to most POS, not in place of. The QR system handles guest-facing menu and orders; your POS handles payment, end-of-day, and accounting. Owners with a strict POS keep both. Owners without one often skip a POS for the first year.

Not natively at launch. We export orders as CSV that imports into Adisyo. A native Adisyo webhook is on the roadmap for Q3 2026. Menulux uses the same export route. Tell support which integration matters and we will prioritize it.

Yes, with a small adapter (a Raspberry Pi or a Star Micronics LAN printer). The dashboard sends a print job over your local network. We document the wiring in the setup guide. Most kitchens skip the printer and use the screen.

At launch we export a monthly orders + revenue CSV that your accountant imports into Logo or Mikro. A native integration for Logo is on the roadmap for Q4 2026. QuickBooks and Xero are not on the roadmap yet.

Not at launch. The QR menu places the order; the guest pays at the table or counter via your existing card terminal. Pay-at-table through iyzico is on the roadmap for Q4 2026, behind native Adisyo.

Yes on Growth and above. Add a CNAME from menu.yourbrand.com to cname.mobitaste.com; the dashboard provisions SSL automatically. Starter uses the slug.mobitaste.com subdomain. Most cafes never switch; some hotels prefer their own subdomain for brand.

Yes on Pro and Enterprise. The REST API exposes orders, menu items, and tables with a per-restaurant token. Webhooks fire on order created and order status changed. Documentation is at /api/v1/docs. Rate limit is 60 requests a minute on Pro.

Yes via webhooks on Pro. Set a webhook URL, get JSON on order events, route to Google Sheets through a Zapier or n8n bridge, or post to a Slack channel for the floor manager. We do not host the bridge for you.

Three things: a phone or tablet for the owner, a screen in the kitchen (a $150 Android tablet is enough), and one device for the floor (often a phone the headwaiter already carries). Guests use their own phones.

Yes if it runs iOS 14 or newer. The kitchen view is a web page; Safari renders it fine. Pin it to the home screen for full-screen mode. iPad Mini is the sweet spot; older iPad Pro models work but get hot under load.

A 9- to 11-inch tablet is the right size. A phone is too small for a busy kitchen; cards overlap and cooks miss orders. We have run a slow cafe on a phone, but for any restaurant past 30 covers a shift, get a tablet.

A Star Micronics TSP100 or any ESC/POS-compatible LAN printer works. Wire it to the same network as your kitchen tablet. The dashboard pushes the ticket over the LAN. USB-only printers need a Raspberry Pi bridge; LAN is simpler.

Anything past 5 Mbps download and 1 Mbps upload is fine. The bottleneck is usually Wi-Fi coverage at the back tables, not the line speed. Test by opening the menu on a guest phone from the farthest table during peak.

The kitchen view works on phone but expect to miss cards in a real rush. As a stopgap, push notifications fire on each new order and a tone plays. For a permanent setup, even a $120 Android tablet is a huge upgrade.