
Pilots opening
Every canteen you run, in one place
Staff, diners, requests and support for one site or a hundred. Built in India, with pilots opening now.
Scroll to see how it worksWho it's for
Built for the people who feed a lot of people
Different kitchens, the same problems: many sites, many people, and nobody sure who changed what.
Corporate cafeterias
Facilities and HR teams feeding employees across one campus or many offices.
- Requests from the floor reach the right team, with a record of who did what.
- Diners kept apart from staff, with sponsor details when the company pays.
Regional caterers
Catering companies running canteens for several clients at once.
- Each client site with its own staff and timezone, all in one account.
- Roles scoped so a site manager sees their site, and head office sees all.
Hospitals
Kitchens that feed patients, staff and visitors around the clock.
- Every change recorded, by person and site, in an append-only audit log.
- Tickets and live chat between your own teams, whatever the hour.
Universities and schools
Dining halls and hostels with large, changing groups of diners.
- Records imported from a spreadsheet, every row checked by a dry run first.
- Permissions per role, so student staff get exactly the access they need.
What's inside
Everything a canteen team touches, in one place
Each area is scoped to your sites, and every change lands in one audit log.
Users, roles and permissions
Give each role exactly what it needs from one permission tree. Nobody can grant more than they hold.Staff and reporting lines
Staff by site and department. Reporting lines follow from positions, and move up when someone leaves.Sites, imports and audit log
One site or a hundred in one account. CSV imports with a dry run first, and every change in one audit log.Diners
Everyone you feed, kept apart from staff, with sponsor details when someone else pays and an optional staff link.Operations hub
Requests from every site in one queue. Assign them, comment, and follow each status change from open to done.Support center
Tickets routed to department queues, with live chat between the person asking and whoever picks it up.
A day at a canteen
From the morning shift to the last change of the day
Five moments from an ordinary day, and where each one lands in CanteenCrowd.
- 07:00Staff
The morning shift, site by site
Each site sees its own staff, departments and reporting lines. A manager at one canteen never wades through another's.
- 11:40Operations hub
The steam table stops heating
The counter lead raises a request. It lands in the operations hub, goes to maintenance, and every status change is on record.
- 13:15Support center
The night shift can't sign in
It becomes a ticket in IT's queue. Whoever picks it up answers over live chat, and the whole thread stays on the ticket.
- 16:30Bulk import
Twelve new joiners start tomorrow
Import them from a spreadsheet. A dry run checks every row first and shows exactly what's wrong, before anything is saved.
- 19:00Audit log
Who changed what today?
Every change, by every person, at every site, is in one audit log. Filter it, open an entry, export it as CSV.
In our words
Why CanteenCrowd works the way it does
Every request, every ticket and every change, from every site, recorded once, in one place your whole team can trust.
A site manager should see their site. Head office should see every site. Nobody should need a spreadsheet to work out who sees what.
- account for every site
- 1
- permission tree, set once
- Per role
Before
Spreadsheets, chat groups and guesswork
- Requests lost in chat groups and phone calls
- A different staff spreadsheet at every site
- Nobody sure who changed what, or when
- Every new site means starting the paperwork again
After
One place, one record, every site
- Every request in one queue, assigned, with its full history
- Staff, departments and reporting lines for every site, in one account
- One audit log for every change, by person and site
- A new site in settings, its staff imported from a CSV, every row checked first
By the numbers
Small numbers we can stand behind
No made-up percentages. These are true today.
- areas live today
- 6
- Operations, support, staff, diners, users and sites
- more on the roadmap
- 5
- From the plans pilot customers help shape
- minutes on a pilot call
- 30
- A screen share, not a slide deck
- business day to reply
- 1
- To every pilot request
Coming next
What we're building next
Planned, not built yet, and no dates on purpose: pilot customers help decide the order.
Menu and recipes
PlannedIngredients, versioned recipes and menu items offered per site and meal period. Allergen and dietary labels come from the ingredients, so they can't drift.
Purchasing
PlannedVendors, purchase orders for anything from rice to tent rentals, invoices and vendor payments: one balance per vendor.
Inventory
PlannedStock by site and storage location: goods received, issued, wasted and transferred, and stock counts that settle the difference.
Events
PlannedOne-off occasions, from a conference lunch to a client function: catering, run of show, budget, guest groups and crew, from reusable templates.
Integrations
PlannedExports for Tally, connectors for Zoho Books and ERPNext, a point-of-sale link for menus and daily sales, and an API with webhooks.
Pricing
Priced by site, not by seat
Every paid plan has everything that's live today. Pick the one that fits how many sites you run.
Free
Opens when Events launchesPlan one-off events, on your own.
Freeno card, no charge
1 user
- Event management only
- 1 user
Starter
One canteen, everything in it.
₹7,999$99per month + GST
1 site
- Every live area
- CSV imports with a dry run
- Audit log with CSV export
- Email support
Growth
A few sites under one roof.
₹29,999$399per month + GST
Up to 5 sites
- Everything in Starter
- Access scoped site by site
- A guided onboarding call
- Email and phone support
Network
Regional caterers and campuses.
₹89,999$1,199per month + GST
Up to 25 sites
- Everything in Growth
- Help importing your existing staff and diner lists
- Priority support
Prices per month. Indian prices exclude 18% GST. Running more than 25 sites? Talk to us.
FAQ
Questions we get asked
What counts as a site?
A canteen location with its own staff, diners and timezone. One account can run one site or many, and access can be limited site by site.
Can we try it before we commit?
Yes, that's what a pilot is: CanteenCrowd on your own sites, with your own people. We agree the length and terms on the first call.
Is our data kept apart from other customers'?
Yes. Every account's records are separated by the database itself, not only by the app's code, and every change is written to your own audit log.
Does it need an install?
No. It runs in the browser, on a computer or a phone.
Does it connect to Tally or our point of sale?
Not yet. Accounting exports and a point-of-sale link are on the roadmap; tell us what you use and it helps decide the order.
See it on your own canteens
A 30-minute call: we share a screen and walk through it with your sites in mind. No slides, no commitment.