RailCanteen: the workshop canteen, booked ahead, cashless and accounted for.
We built RailCanteen for a workers' canteen at a mechanical workshop of Indian Railways. Staff book tomorrow's meals from their phones and pay by UPI; the kitchen cooks to confirmed counts; serving happens by QR; and every rupee, refund and complaint is on the record for the canteen team.
- Industry
- Railways, staff welfare canteen
- Deployment
- Workshop canteen, Indian Railways
- Platforms
- Staff mobile app, canteen app, web dashboard
- Payments
- UPI via BillDesk, wallet and counter orders
What a cash-and-coupon canteen really costs.
Cash and coupons at the counter
Hundreds of workers on fixed shift breaks queued at a counter to pay cash or trade paper coupons. Serving time went into handling money and tokens instead of food, and the busiest thirty minutes of the day were the slowest.
The kitchen cooked blind
The canteen team had to guess how many breakfasts and lunches to prepare each day. Guess high and cooked food is wasted; guess low and workers at the end of the queue go back to their shift without a meal.
Payment disputes nobody could settle
With UPI, money can leave a worker's account while the confirmation never reaches the canteen, especially when a collect request is approved minutes later. Every such case became a dispute with no transaction trail on the canteen's side to resolve it.
A welfare service with no records
Orders, collections, refunds and complaints lived in registers and memory. There was no daily account of meals served and money collected that the canteen committee could actually stand behind.
Book ahead, pay by UPI, serve by QR, account for everything.
RailCanteen moves ordering and payment out of the lunch rush and onto the worker's phone, and gives the canteen team one governed system from menu to money.
Booking before cooking
Menus carry per-meal cutoff windows, and the cart books for today or tomorrow. Orders close before the kitchen fires up.
Payments the server trusts
Every gateway exchange is signed and verified server-side. The phone's word is never the final word on money.
Reconciliation on autopilot
A scheduled job re-checks pending payments with the gateway, confirms late UPI approvals and refunds orphaned payments.
QR at the counter
Each order carries QR codes per meal type. Serving is a scan and a tap, and unpaid orders cannot be confirmed.
A wallet that closes the loop
Cancellations become instant wallet credit, usable against the next order, with partial per-meal refunds supported.
Role-scoped administration
Admins, permission-scoped sub-admins and shop-mapped staff keep the canteen accountable without slowing it down.
From tomorrow's menu to a served meal.
Nine steps. Booking closes before cooking starts, and money is verified before food is served.
- 01
Staff sign up once
A worker registers on the mobile app with OTP verification and is mapped to their shop in the workshop.
- 02
Browse the day's menu
Meals are published per weekday with veg markers and prices. Each meal has an ordering window, so breakfast and lunch close for booking hours before serving.
- 03
Book in advance
The cart accepts meals for today or tomorrow, one serving date at a time. This is what turns orders into a production forecast for the kitchen.
- 04
Order is created
One order groups the worker's breakfast and lunch items, each with its own QR code for the counter.
- 05
Pay by UPI
Payment runs through the BillDesk gateway with signed requests. Wallet credit from earlier refunds can be applied to reduce the amount.
- 06
The server confirms the payment
The backend verifies the transaction with the gateway itself. A recovery job re-checks pending payments on a schedule, so a delayed UPI approval still confirms the order automatically.
- 07
The kitchen sees real counts
Confirmed orders roll up on the canteen dashboard and app: how many of each meal, for which date, before cooking starts.
- 08
Serve by QR
At the counter the worker shows the order QR, the canteen team confirms it, and the order moves through Pending, Confirmed and Delivered.
- 09
After service
Cancellations credit the worker's in-app wallet, complaints are filed against the exact order, and daily reports close the books.
The capabilities that matter most.
Advance booking and menus
- Day-wise menus with per-meal availability windows and cutoff times
- Booking limited to today and tomorrow, one serving date per order
- Veg and non-veg flags, prices and images on every meal
- Meal timings the canteen team can adjust themselves
- Promotional banners pushed to the staff app
Payments that settle themselves
- UPI payments through BillDesk with HMAC-signed requests and responses
- Server-side verification with the gateway, never trust the phone alone
- A scheduled recovery job that re-checks pending payments and confirms late UPI approvals
- Automatic refunds for payments whose order was never generated
- Wallet credits for cancellations, including partial per-meal refunds
- Manual counter orders for staff who still pay cash
Fulfilment at the counter
- A QR code per order and meal type for fast serving
- A clear order lifecycle: Pending, Confirmed, Delivered, Cancelled
- Unpaid orders cannot be confirmed, so serving always matches money
- Push notifications to the worker at each status change
- A canteen-side app for the team working the counter
Administration and control
- Three role tiers: staff, sub-admin and admin
- Per-module view permissions for sub-admins on the dashboard
- Customers mapped to workshop shops for accountability
- Daily transaction report with date range, status filters and refund tools
- Meal, customer and complaint records exportable for the committee
Eight modules, one canteen.
Dashboard & Analytics
The daily picture
Order counts, revenue trends, top meals and recent customers for the canteen team, with date-range filters on everything.
Meal & Menu Management
What gets cooked
Create and update meals with prices, images, weekday availability and serving windows. Soft delete keeps history intact.
Staff Ordering App
The worker's counter
OTP sign-in, day's menu, cart, advance booking, UPI payment, order QR codes, wallet, history and complaints on the worker's own phone.
Payments, Wallet & Refunds
The money engine
Gateway integration, server-side verification, scheduled reconciliation, automatic and one-click refunds, and wallet credits reused on the next order.
Order Fulfilment
The serving line
Order queues for the canteen team, QR confirmation at the counter, status workflow and per-meal cancellation with refunds.
Transactions & Reports
Closing the books
A daily transaction report with filters and per-day totals, meal-wise consumption reports, and CSV and PDF exports.
Complaints & Engagement
The feedback loop
Complaints filed against specific orders and tracked to action, push notifications, and banners for canteen announcements.
Users, Roles & Shops
The setup
Staff accounts mapped to workshop shops, sub-admins with per-module permissions, and admin control over the whole platform.
What the canteen gains.
Real outcomes tied to what the platform does. The exact numbers are best measured on each deployment.
The queue becomes a QR scan
Ordering and payment happen before the break. At the counter there is only serving.
The kitchen cooks to real numbers
Booking cutoffs hours before serving give the team exact meal counts before cooking starts, which is how over-production gets cut.
Cashless by default
UPI covers the everyday case, the wallet absorbs refunds, and manual counter orders keep cash as the exception rather than the rule.
Payment disputes resolve themselves
Delayed UPI approvals are found and confirmed by the server on its own, and orphaned payments are refunded automatically.
Refunds stay in the system
Cancellations credit the worker's wallet instantly, ready for the next order, with the trail kept.
One live operating picture
Dashboard, order board and reports give the canteen team and the committee the same numbers.
Control without bottlenecks
Sub-admins run day-to-day service with only the modules they are permitted, while admins keep oversight.
Everyone stays informed
Workers get push updates at each order step, and the canteen team is notified as paid orders arrive.
Enterprise grade under the hood.
Backend
Node.js and Express on MongoDB. REST APIs for the apps and dashboard, QR generation, email templates and scheduled background jobs.
Mobile
Flutter apps for staff ordering and for the canteen team, with OTP sign-in, push notifications and an in-app update service.
Web dashboard
React with Vite, Material UI and PrimeReact data tables, date-range filtering, CSV and PDF export.
Payments
BillDesk gateway integration with JWS-signed payloads, server-side transaction retrieval, a scheduled reconciliation sweep and gateway refunds.
Security
JWT sessions, OTP verification, role-based access with per-module permissions for sub-admins, and signature verification on every gateway exchange.
Operations
Separate dev and production environments with CI pipelines, environment-driven configuration and soft-delete master data.
Where this platform fits.
Any institution that feeds a known workforce or community on fixed timings and needs the books to balance.
An architecture built to grow.
Demand forecasting
Order history per meal and per day is already captured, ready to drive predictions beyond the advance-booking window.
Subscriptions and meal plans
The wallet and recurring order data provide the base for weekly or monthly meal plans.
Inventory and kitchen production
Confirmed meal counts can feed ingredient planning and stock consumption as a natural next module.
Multi-canteen scale
Shop-mapped customers and role scoping extend to multiple canteens and locations on the same platform.
ID and biometric integration
Employee-ID based sign-in and attendance-linked entitlements fit the existing account model.
Deeper analytics
The transaction and consumption data already collected supports wastage, uptake and revenue analysis per meal.
Built for shift breaks, subsidized meals and public accountability.
Run a canteen, cafeteria or mess?
Talk to the team that put a live workshop canteen on advance booking and UPI. No slide deck, just answers.