Issue single-use QR meal tokens for every session, scan them at the counter to serve and reconcile bookings against servings - no paper, no double-spend, no manual counting.
Meal token
Lunch · Today
#MTK-9F2K7Q
ValidBuilt for
Physical coupons can be duplicated, shared or forged and end-of-day counting is slow and error-prone. A digital token is single-use, tied to a member and a session and verified instantly.
Members book breakfast, lunch or dinner in advance; a QR token is issued on their phone.
Staff scan the QR to verify it is valid and unused, then mark it served.
Bookings, servings and no-shows are tallied automatically for the day.
Each token works once, for one session - it cannot be reused or duplicated.
Members book ahead so the kitchen knows counts before service.
A scan confirms valid / used / expired in under a second, even offline-tolerant.
Issue guest tokens and add-ons alongside the main meal.
See booked-vs-served to cut over-preparation and food waste.
Cancel within the window and auto-refund to the wallet.
One connected flow - from booking a meal to serving it and settling the books.
South Indian Meals
Rice · Sambar · Poriyal
Chapati Combo
2 chapati · curry
Curd Rice
A member books a meal and receives a single-use QR token. Counter staff scan it to verify and mark it served; the token then cannot be used again.
No. Each token is single-use and tied to a member and session, so copies or screenshots are rejected after the first scan.
Yes - breakfast, lunch and dinner are booked per session and scanned at serving time.
Get a guided demo with your canteen or mess set up the way you run it.