QvianQvian
Restaurant operations

From the table to the kitchen pass to the bill — one service view.

Take the order, fire it to the kitchen, plate it, and settle the bill — while recipes draw down ingredients, food cost stays visible, and the day's takings flow through to connected accounting.

Service board — DinnerDemo data
Open tables
9
Covers
142
KOT queue
6
Table 4 · Dining4 coversSent to kitchen
Table 9 · Dining2 coversPlating
Takeaway · #T-118PickupPreparing
Orders firing · stock drawing down
Service flow

Seated, ordered, fired to the kitchen, served, and paid.

Service runs the way the floor expects — seat the table or scan a QR, take the order, send the KOT to the kitchen, plate and serve, then settle the bill. Ingredients draw down as dishes go out, and the takings flow through to connected accounting.

Step 1
Seat / scan

Seat a table or scan a QR to open a tab.

Step 2
Order taken

Add dishes, modifiers, and covers to the order.

Step 3
Sent to kitchen

The KOT fires to the kitchen display.

Step 4
Prepared

The kitchen cooks and marks tickets ready.

Step 5
Served

Dishes reach the table; ingredients draw down.

Step 6
Paid

Settle the bill — split, cash, card, or transfer.

Order · Table 4Demo data
DishCourseQtyPriceLine
Reef Fish Curry · no chilliMain2180360
Garlic NaanSide345135
Fresh Lime SodaDrink455220
Bill total (MVR)715
Settle the bill
CardMVR 400
CashMVR 315
SettledMVR 715
Bill closed · ingredients drawn down

Order and bill figures use fictional demonstration data.

Floor & tables

See the whole dining room — covers, status, and open tabs.

The floor view shows every table with its covers and where it is in service — seated, ordering, sent to the kitchen, plating, or ready for the bill — so front-of-house keeps the room moving.

Table 12 covers
Seated
Table 44 covers
Sent to kitchen
Table 66 covers
Ordering
Table 92 covers
Plating
Table 113 covers
Served
Table 125 covers
Ready for bill
Table 142 covers
Open
Table 154 covers
Sent to kitchen

Table layout and covers use fictional demonstration data.

Kitchen display (KDS)

Tickets the kitchen can act on — with prep times in view.

KOTs arrive on the kitchen display as tickets the line can work through. Each ticket shows the table, the dishes with modifiers, and how long it has been on — so the kitchen bumps orders in the right order and nothing sits too long.

Table 4 3:12
2× Reef Fish Curry
no chilli
3× Garlic Naan
Bump when ready
Table 9 6:40
1× Tuna Steak
medium
1× House Salad
dressing on side
Bump when ready
Takeaway #T-118 9:05
2× Chicken Biryani
1× Raita
Bump when ready

Kitchen tickets and prep times are illustrative.

Recipes, ingredient costing & stock consumption

Each dish has a recipe — and each recipe deducts ingredients.

Build a recipe per dish from costed ingredients, and selling that dish draws those ingredients out of stock. With the ingredient cost set against the menu price, food cost percentage stays in view so the menu is grounded in what you actually pay.

Recipe · Reef Fish CurryDemo data
IngredientQtyUnit costLine cost
Reef fish fillet180 g0.22 / g39.60
Coconut milk120 ml0.06 / ml7.20
Curry mix20 g0.18 / g3.60
Onion & aromatics60 g0.04 / g2.40
Recipe cost (MVR)52.80
Food cost
Recipe cost
MVR 52.80
Menu price
MVR 180
Food cost
29%
Margin
71%
Reef fish fillet− 180 g
Coconut milk− 120 ml
Curry mix− 20 g
Sale deducts ingredients from stock

Recipe, costing, and food-cost figures use fictional demonstration data.

QR ordering

Diners scan, browse, and order from the table.

Put a QR code on the table and diners open the menu on their phone, order for their table, and the order lands in the same service flow — sent to the kitchen as a KOT, with no double entry at the counter.

  • QR opens the menu for the table
  • Diners order from their own phone
  • Orders join the same kitchen flow
  • Fired to the KDS as a KOT
Table 6 · QR menuLive
Reef Fish CurryMainMVR 180
Chicken BiryaniMainMVR 160
Garlic NaanSideMVR 45
Fresh Lime SodaDrinkMVR 55
Sent to kitchenKOT fired
Delivery & takeaway

Dine-in, takeaway, and delivery — one kitchen, one flow.

Run takeaway and delivery alongside dine-in. Each mode tags the order so the kitchen knows whether it is plating for a table, packing for pickup, or handing to a rider — and every mode draws down the same stock.

Orders · By modeDemo data
OrderModeItemsTotalStatus
#T-118Takeaway3MVR 380Preparing
#D-204Delivery5MVR 640With rider
Table 4Dine-in9MVR 715Served
#D-205Delivery2MVR 240Packing
Dine-in

Tables, covers, and open tabs on the floor.

Takeaway

Pickup orders packed and tracked to collection.

Delivery

Orders tagged for the rider, through one flow.

QR & app

Scan-to-order joins the same kitchen queue.

Order modes and figures use fictional demonstration data.

Yes. Orders move from the floor to the kitchen and draw down stock, so teams work from one connected view.

Recipes, ingredients, and usage are kept together so food cost and menu performance are easier to see.

Customers can browse, order, pay, and track through the Qvian Consumer App, shaped around your service modes.

Yes. Tip distribution sits alongside attendance, shifts, and payroll for front-of-house and kitchen teams.

Yes. Each venue gets the tools it needs while owners keep a clear view across locations.

See Qvian built for Restaurants & Cafés.

Book a demonstration focused on your industry and the areas most relevant to your team.