Every meal, exactly once.
Double plates, ghost meals and friendly favours quietly eat your canteen budget. Staffelog puts a barcode on every ID card and a scanner on the counter phone, so the same person can never collect the same meal twice. Not by policy. By database.
Live in an afternoon|No hardware to buy|Free to start
Chaitanya Infra Pvt Ltd
RAVI KUMAR
Site Engineer
CIPL-012
Lunch issued
12:41 pm, counter 1
Already collected
lunch was taken at 12:41 pm
The leak
A paper register cannot say no.
When the caterer bills per plate and the only record is a notebook at the counter, nobody can prove who ate what. The waste is not one big theft. It is a second lunch here, a plate for a visiting friend there, every single day.
8-12%
of plates in unmonitored staff canteens are typically double collections or unregistered eaters.
3 meals x 70 staff
is 6,300 plates a month. At 60 rupees a plate, a 10% leak burns about 38,000 rupees. Every month. Silently.
0
duplicate meals once Staffelog is at the counter. The rule is a database constraint, so even two counters scanning the same card in the same second cannot double-issue.
Product
The whole canteen on one screen
This is the admin dashboard. Live counts as plates go out, trends by day or by month, and a feed of every scan the moment it happens.
Breakfast
52
07:00-10:00
Lunch
61
12:00-15:00
Dinner
15
19:00-22:00
Meals / staff
128 / 154
66 active employees
Last 7 days
Live activity
RAVI KUMAR
CIPL-012
SUNITA DEVI
CIPL-034
MD ARSHAD KHAN
CIPL-027
PABITRA ROUT
CIPL-047
The card
A barcode that costs nothing and cannot be gamed
Unguessable by design
Every card encodes a random 12-digit token generated by the database, never the visible employee number. Nobody forges a card by guessing the next serial in the series.
Print them yourself
One click renders every employee as a cut-ready A4 sheet with your logo. Laminate at the local shop for 10 rupees a card. Lost card? Reprint in seconds, old scans keep working.
Any phone is the scanner
No barcode gun, no POS machine, no hardware budget. The counter phone's camera reads the card in under two seconds, even in canteen lighting.
Card gets photographed or shared? It only ever grants what the person was already entitled to: one breakfast, one lunch, one tea, one dinner. The second scan of any copy is refused on the spot, with the original issue time shown to the manager.
The flow
What happens in the two seconds after a scan
One atomic database call makes every decision. There is no moment where two counters can race each other into a double issue.
- 1
Card scanned
The camera decodes the 12-digit token and sends it to the database with the selected meal.
- 2
Is this a real, active employee?
The token is matched against the roster of your organisation only.
Unknown card: ID not found, nothing issuedDeactivated employee: refused - 3
Already collected this meal today?
The one-per-day rule is a unique constraint in Postgres, checked and enforced in the same transaction.
Yes: refused, manager sees the original issue time - 4
Inside the meal window?
Outside the hours you configured, the manager gets a soft warning and must explicitly confirm. The issue is flagged in the audit trail.
Off-hours: confirm required, flagged forever - 5
Meal issued and written to the register
Green screen, beep, next person. The dashboard updates in the same second, the log is exportable forever.
Issued: counted, timestamped, attributed
Tracking
From gut feeling to a register that argues back
Live counts as they happen
Every scan lands on the dashboard in real time. Watch breakfast, lunch, tea and dinner counts climb plate by plate from anywhere.
Every employee has a history
Tap any person to see their meal log for 30 days, 3 months, 6 months or a year. Days fed, off-hours issues, last meal, all one tap deep.
Off-hours never slips through
A dinner issued at 5 PM needs an explicit confirm and is flagged forever in the audit trail. Flexibility for real life, accountability on record.
Reports your accountant will love
Any date range to Excel in one click. Reconcile plates served against caterer invoices with actual data instead of arguments.
How it works
Live before the next shift eats
Create your organisation
Sign up, name your company, done. You are the admin. No sales call, no onboarding fee.
Import the Excel you already have
ID, name, designation, phone. Columns map themselves. 66 employees imported in the time it takes to pour a chai.
Print cards, hand over a phone
Managers sign in with a username and password you set. They point the camera, Staffelog decides, the register writes itself.
Stop feeding ghosts.
Import your roster, print the cards and issue your first tracked meal before the next shift starts. The leak stops the same day.