Getting started · 6 min read
How DashDine works
A complete picture of the smart restaurant ordering system: how customers order, how the kitchen and runners fulfil, and how managers stay on top of it all in real time.
Who this is for
Owners and managers seeing DashDine for the first time.
A smart restaurant ordering system
DashDine manages restaurant orders from customer ordering through kitchen preparation and fulfilment. Customers order from their own phones, the kitchen sees every order the moment it lands, runners deliver to tables and cars, and managers watch the whole operation from one dashboard.
The result is faster ordering, fewer order mistakes, and a clear view of where every order stands at any moment — without paper tickets, shouting across the pass, or honking horns in the parking lot.
The surfaces of DashDine
- Customer ordering app — a white-label, mobile-first web app your guests open from a printed code or a direct link. No download required; it carries your name, logo, and colors.
- Runner / Kitchen Display System (KDS) — a tablet screen where kitchen staff and runners see live orders, flash on new arrivals, and move each order through its statuses.
- Kiosk — a staff order-entry screen for walk-ins and phone orders, so counter staff enter orders into the same pipeline customers use.
- Admin dashboard — where owners and managers configure the menu, branding, branches, staff PINs, promotions, reports, and billing.
- Onboarding wizard — a short guided setup that runs after signup and creates your first branch.
Your restaurant brand and its branches
Every account in DashDine is a restaurant brand. The brand owns the global identity — name, logo, colors, default language, and currency — and one or more branches.
A branch is a single location. Branches own the menu, opening hours, dine-in tables, staff PINs, and the order types you accept (dine-in, takeaway, carside). Plans scale by branches: Pro includes one branch, Growth includes three, and extra branches can be added to either.
How an order travels through the system
- 1
A customer scans your code (or opens the direct link) and lands on your white-label menu.
- 2
They build a cart, choose dine-in, takeaway, or carside, and submit. The order is created with status "new".
- 3
The order is pushed in real time to the kitchen display for that branch. The card flashes and an audible alert plays.
- 4
Staff move the order through its lifecycle: new → preparing → ready → out for delivery → completed. Each transition is mirrored on the customer order tracking page.
- 5
The completed order joins your order history and reports — revenue, top items, peak hours, and branch performance.
The three order types
- Dine-in — the customer orders from a table code; the order carries the table number so runners know exactly where to deliver.
- Takeaway / pickup — the customer orders ahead and collects at the counter when the tracker shows the order is ready.
- Carside — the customer parks, orders from the car, and enters vehicle color, model, and plate digits. The runner sees a bold line like "WHITE LAND CRUISER - 660" and walks the order out.
A multi-language customer experience
Customer-facing surfaces — the storefront, the ordering flow, the kiosk, and the runner screens — support multiple languages, including English and Arabic with full right-to-left layout. Your customers order in the language they are comfortable with.
The admin dashboard itself is in English for now, so plan staff training accordingly.
Frequently asked
Do customers need to download anything?
No. The customer ordering app is a mobile-first website. Customers scan the code or open the link in any phone browser — there is nothing to install.Does the kitchen display work on iPad?
Yes. It is designed for tablets in landscape. iOS users should add it to the home screen so the audio alert keeps working in the background.What happens if the internet drops on the tablet?
A "Connection lost" banner appears and the screen reconnects automatically, then resyncs the order list so nothing is missed while it was offline.