Payments / F&B · 2023
Skip the queue, not the meal
UX/UI for a no-app, QR-based canteen ordering platform for college campuses — scan a code, order, pay by UPI and collect with a digital token.
Role
Product Designer — UX/UI
Timeline
2023 · 8 weeks
Team
1 designer · 2 engineers · founder
Platform
Mobile web (no install)
No app
Scan-to-order in the browser
UPI
Pay with what students already use
Token
Digital pickup, no shouting names
01 · Overview
Campus canteens compress a day's demand into two 30-minute breaks. The result: queues that eat the break, counter staff overwhelmed by simultaneous shouted orders, and students who simply give up on eating.
Fraxnl turns any table or poster into a storefront — scan a QR, browse the live menu, pay by UPI and get a numbered token, all in the browser. I designed the student ordering journey and the counter-side flow that keeps pickups moving.
02 · The Problem
What we were trying to solve
A 30-minute break loses 20 minutes to queueing — ordering, paying and collecting all happen at one counter, serially, at shout volume. And no student will install an app for a samosa.
Pain point 01
One counter does three jobs
Ordering, payment and handover all bottleneck at the same person — the queue moves at the speed of the slowest transaction.
Pain point 02
App installs are a dead end
Storage-constrained phones and 30-second attention spans mean any install requirement loses the majority of hungry users instantly.
Pain point 03
Pickup is chaos
Orders announced by shouting names over a crowd — missed calls, cold food, and disputes about whose plate that was.
03 · Research
What the users taught us
I spent break times in campus canteens timing queues, interviewed students and canteen staff, and mapped where the serial counter process could be parallelised.
The QR has to do everything
Scan → menu in under 3 seconds, no sign-up wall, or students walk to the queue instead. The browser flow had to beat standing in line, every time.
UPI is the universal wallet
Every student already pays with UPI daily — introducing any other payment step would have added friction to the one moment that must be frictionless.
Staff need order flow, not order chaos
The counter screen had to queue, batch and sequence orders — an unordered flood of tickets would just move the chaos behind the counter.
04 · Design Process
From tangled problem to shipped solution
Stage 1 — Problem Identified
The queue is three queues in a trenchcoat
Timing studies showed the wait wasn't cooking — it was the serial order-pay-collect loop at a single counter. Splitting those steps apart was the whole opportunity.
Stage 2 — Problem Scoping
No-app as a hard constraint
We committed to browser-only up front, which scoped everything else: session handling without accounts, payment via UPI intent, and tokens that survive a locked phone screen.
- Guest-first flow — order without creating anything
- Two users designed for: the student and the counter
Stage 3 — Solution Shaping
A menu that works one-handed in a corridor
Wireframes optimised for the real context: walking, hungry, between classes. Big touch targets, live item availability, a persistent cart, and a checkout that's a single UPI tap.
Stage 4 — Impact Testing
Testing against the queue itself
Prototype tests had one benchmark: is scan-to-paid faster than joining the line? Iterations cut steps until the answer was always yes — menu tap-count halved and the sign-up wall stayed gone.
- Scan-to-paid time measured against physical queueing
- Counter screen tested with canteen staff during service
Stage 5 — Solution Deployed
Live on campus
Fraxnl launched with partner canteens — QR codes on tables and posters, UPI payment, numbered digital tokens, and a counter display sequencing pickups calmly.
05 · The Solution
The decisions that shaped it
The shipped flow parallelises the canteen: students order and pay from wherever they stand, the kitchen sees a sequenced queue, and the counter only does handover — matched by token number, not shouted names.
Decision 01
Scan-to-menu in seconds, no gate
The QR opens a live menu instantly in the browser — no install, no OTP, no account. Ordering is quicker than deciding to queue.
Decision 02
One-tap UPI checkout
Checkout hands off to the student's own UPI app and returns with payment confirmed — the entire pay step uses muscle memory they already have.
Decision 03
The digital token
A bold, numbered token screen designed to be readable at arm's length across a counter — pickup becomes a number match instead of a name shouted over noise.
Decision 04
A calm counter display
Orders arrive sequenced with clear ready/waiting states, so staff work a tidy queue instead of a flood — the chaos doesn't just move behind the counter.
06 · Impact
What changed
Fraxnl shipped to campus canteens and turned the break-time bottleneck into a parallel flow.
0 installs
Full journey in the browser
1 tap
Payment via UPI intent
Live
Deployed with partner canteens
- Students order the moment the break starts — from the classroom, corridor or lawn — instead of racing to a line.
- The counter handles handover only, clearing pickups by token number at a steady rhythm.
- No-app + UPI meant zero onboarding friction: the first scan is the whole learning curve.
- Canteens gained order history and demand visibility they never had on paper.
07 · Learnings
What I'm taking with me
- 01
The strongest UX constraint was a business decision — 'no app' forced every flow to earn its place in seconds.
- 02
Designing both sides of a marketplace moment (student and counter) is the only way to actually remove a queue, not relocate it.
- 03
In payments, borrowed trust beats built trust: riding UPI's muscle memory outperformed any custom checkout we could design.