ChefoBooking
Book meals, count plates
Take meal bookings for every service you run. Before your cutoff they confirm themselves. After it, late bookings, changes and cancellations wait in one queue for your decision — so the kitchen never cooks to a number nobody agreed to.
Sign up with your mobile number · no card, no setup fee
Every meal service shows the confirmed quantity split across the options you actually serve — Veg, Non-Veg, Jain, whatever you've set up. A zero is shown too, because a kitchen needs to see the zero.
Set a deadline per service. Bookings before it confirm themselves instantly. Bookings after it aren't refused — they become a request you can accept when you have room, or decline when you don't.
Once the cutoff passes, no customer can quietly alter a confirmed booking. A late change leaves the original untouched and waits in your queue until you decide.
Who accepted what, when, and what the numbers were before and after. When somebody asks why the kitchen cooked 200 and not 185, the answer is written down.
A hard deadline just tells a customer “no” and leaves you on the phone. Here, the deadline decides who confirms a booking — the system, or you.
The rule underneath all three: after the cutoff, nothing silently alters the kitchen's confirmed requirement. A late request contributes exactly zero until you accept it.
From registering to a confirmed plate count, four steps — nothing hidden in between.
Verify your mobile with an SMS code, name your business, and add the meal services you run. Nothing else is required to start taking bookings.
You get a public page at booking.chefo.in. Customers open it, pick a meal and a date, enter quantities, and leave a phone number. No account, no app, no password.
Anything that arrives after the cutoff lands in your approval queue with the plate difference spelled out — +8 meals, −3 meals — so a decision takes a second.
The Today screen holds one number per service, split by option, refreshed as decisions are made. Pending requests are listed separately and never counted until you accept them.
Anywhere people book meals ahead — one plate or eighty, once or every day.
Take headcounts from every floor or team, then hand the kitchen one confirmed number per service.
A site supervisor books 80 lunches in one submission — one record with a per-option breakdown, not eighty rows.
Residents book the meals they'll actually eat, so nothing is cooked for a room that's empty tonight.
Run a service with no cutoff at all — orders stay open and auto-confirm until you stop taking them.
Everything needed to take a booking, decide on the late ones, and hand the kitchen a number it can cook to — in one dashboard, with nothing hardcoded to somebody else's menu.
Create your accountBreakfast, Lunch, a night-shift meal — each with its own serving window and its own cutoff, which can fall on the day before for a kitchen that preps overnight.
Veg and Non-Veg are just rows you can rename or replace. Add Jain, Egg or Thali A, restrict one to lunch only, and every booking form and kitchen count follows.
Late bookings, change requests and cancellations in a single list, oldest first, each showing exactly how many plates the decision moves.
Your own link with your name, address and live cutoff status. It tells the customer up front whether their booking will confirm or need your approval.
Build a role like “Counter staff” from a grid of permissions and assign it. Viewing never implies editing, and nobody can grant a permission they don't hold.
A phone number is recognised on the next booking, so a regular site or office arrives with its history attached instead of being retyped every morning.
A link you hand out or print as a code. It shows the meals you're taking today and says, before anything is filled in, whether a booking will confirm or need your approval.
The parts you don't see, working the same way every time.
You sign in with an SMS code to your registered mobile — the same phone verification as the rest of Chefo. A password is optional and only exists if you set one.
Hiding a button is presentation. Every action is independently checked on the server, so a hidden page reached by typing its URL still returns nothing.
A resolved request keeps what was asked and what it replaced, forever. Renaming an option later doesn't rewrite what last month's kitchen sheets said.
A cutoff resolves to a real instant in your business's timezone, so the answer to “has it closed?” is the same on your screen, the customer's, and the server.
The practical things operators ask before signing up.
No. They open your link, book, and leave a mobile number. That number is how they look up or cancel a booking later — there is no signup, password or app.
Leave its cutoff empty. That service stays open and every booking auto-confirms, which is the right setup for a stall taking orders until it runs out.
Yes, and it confirms immediately whatever the clock says — asking you to approve your own booking would be theatre.
Not until you accept it. Confirmed and pending are shown as two separate numbers and are never added together.
Switch bookings off from the dashboard and write a short message customers will see. Existing bookings are untouched — only new ones stop.
Future bookings use the new name; past ones keep the name they were made with, so an old kitchen sheet still matches the day it described.
Yes. Give them their own account with a login ID and password, and a role that says exactly what they may open.
No — this is a separate product for one-off meal bookings rather than recurring subscription plans. It has its own dashboard, its own data, and its own booking page.
Verify your mobile, name your business, add your meal services — and share your booking link. There's nothing to install and nothing to pay upfront.
Create your account