Published: March 22, 2026
A walkthrough for restaurant owners signing up for the first time. The goal is one working test order from your own phone before the twenty-minute mark. CSV import, QR sticker print, waiter approval — everything you need.
You’ve decided to try MobiTaste. This guide takes you from “just signed up” to “first test order approved by my waiter” in twenty minutes. The steps mirror the in-app setup checklist on your dashboard — but with the screenshots and the why-this-matters that the checklist doesn’t include.
Create your workspace with your email, a password, your name, and your restaurant’s name. We auto-pick a URL slug from the restaurant name; you can override it. After signup you’re logged in immediately and a verification email lands in your inbox. Click it. (If it doesn’t arrive, the dashboard has a Resend button that respects a 60-second cooldown.)
In Settings, fill in your phone and address. These show on the guest menu — guests use them to verify they’re at the right place when they scan the QR. Logo upload is on the roadmap; for now we use your restaurant’s name in the menu header.
While you’re in Settings, take a look at the Order intake & approval block. The default is “first order per session needs waiter approval” — the security default we wrote about. You can flip it to “never approve” if you trust your guests not to abuse the QR, or “every order needs approval” if you’re running a high-stakes venue. Most owners leave it on the default.
In Tables, click “Add a table” and name each one. We accept anything —
T1..T12, Window 1, Patio A. Each table gets a unique URL token
generated server-side; the QR code embeds that token plus your restaurant
slug.
Click “QR PNG” on each table to download a print-ready PNG. We default to 4×4 cm on the printed page — small enough to fit a table tent, large enough to scan in dim lighting. Print them, stick them to the tables.
Why these URLs never change. Your printed QR is a permanent credential. If you accidentally delete and re-create a table, you’ve just turned all your printed stickers into garbage. Treat the QR like a key — don’t reissue casually.
On the Menu page, click Import CSV. Download the template. Open it in Excel/Google Sheets. The columns:
category,name_en,name_tr,description_en,description_tr,price,currency,is_availableFill in a row per item. Categories you reference but haven’t created get
auto-created with the same name. Prices are decimals (12.50, or
12,50 in Turkish-formatted spreadsheets — both work). Currency is
one of EUR, TRY, USD.
A few tips:
In the Staff page, send an invite to your waiter’s email. They get a
single-use 7-day link. The link drops them into a “Pick a password”
form pre-filled with their email and your restaurant’s name; once
they submit, they’re logged in as staff with the waiter function.
Their default landing is /owner/orders, which is the kanban. The
incoming pending-approval section is at the top; the rest of the
kanban tracks the workflow.
On your own phone, scan the QR for table T1 (or whatever you named your first table). You’ll see the menu render with your CSV items grouped by category. Tap an item, add to cart, submit.
On your computer, watch the orders page. Within milliseconds (real-time push, no refresh), the order appears in the pending-approval section. Tap Approve.
Your test order is now in the PENDING column of the kanban, ready to
be marked Preparing → Ready → Served → Completed.
chef function. They
see a KDS-style view at /owner/orders filtered to approved orders only./owner/billing.If you get stuck anywhere, the in-app email support is sent to the address we know about — no ticket queue, just reply.