Taking a tiffin order on WhatsApp is easy for the first ten customers and painful for the next forty. The customer sends "1 tiffin from Monday", you reply with the price, they send a UPI screenshot, and you write it in a notebook. Multiply by 50, add daily skips, address changes and "did my payment go through", and your mornings are gone. This guide shows how to structure daily, weekly and monthly tiffin orders on WhatsApp so that each one takes the customer a minute and takes you nothing.
It covers the three plan types and the message flow for each, the rules you need for skips and cut-offs, how to collect payment in advance without arguments, and how to get a clean morning count of meals and addresses.
Why free-text WhatsApp orders stop working
A tiffin service has a problem that a restaurant does not: the same customer orders every day with small variations. The daily message is rarely "order one meal"; it is "skip tomorrow", "two tiffins on Thursday", "deliver to the office instead of home this week", or "can I change to the non-veg plan". Each is a small edit to an ongoing arrangement, and free text does not record arrangements.
The symptoms are familiar. You cook three meals nobody wanted because the skip was buried in a chat. A customer insists they paid for the month and you cannot find the screenshot. Your delivery person has a hand-written list with yesterday's addresses. None of this is a WhatsApp problem; it is a structure problem. The fix is to give each plan type a fixed flow and to record every change against the customer, not in a chat scroll.
Daily orders: one message, one meal, paid upfront
Daily or one-off orders are for trial customers and irregular eaters. The flow should be short: the customer opens your menu (a store page link or a bot menu inside WhatsApp), picks the meal and any extras, confirms the delivery address and slot, and pays by UPI or chooses cash on delivery. They get an automatic confirmation with an order number and the delivery window.
Two rules make daily orders manageable. First, a cut-off: orders for lunch close at 8 or 9 pm the previous evening, or by 10 am at the latest if you can handle it. Second, a clearly higher per-meal price than the plan rate, so daily customers have a reason to move to a plan. The pricing logic is in tiffin service pricing: monthly and per-meal rates.
A daily order also serves as the trial for a new customer. Make the first message after delivery a one-tap link to the weekly and monthly plans.
Weekly plans: the bridge from trial to habit
A weekly plan (usually six meals, Monday to Saturday) suits students, people on short work assignments and anyone who is not ready to commit for a month. The customer picks a start date, pays for the week in advance, and the plan creates six scheduled orders. Each morning's count includes them automatically.
The message flow is: plan selection, start date, address and slot, payment, then a confirmation listing the six dates. At the end of the week, an automatic renewal message with a one-tap link to pay for the next week or to upgrade to monthly. If you run this manually, send the renewal reminder on Friday evening, not Monday morning, so that nobody is left without lunch while they decide.
Monthly plans: where the business actually lives
Monthly plans are the core of a tiffin service: predictable volume, advance cash and a customer who will stay for months if the food holds up. The flow is the same as weekly with two additions: a skip allowance and a renewal reminder a few days before the plan ends.
Set the plan up as 26 meals (Monday to Saturday) or 30 if you serve Sundays, with the price shown as a monthly total and the effective per-meal rate. Make the customer choose the plan type (veg, non-veg days, one or two meals) and the default delivery address at sign-up. Every later message from that customer is then an edit to a known plan, which is far easier to handle than a new order.
| Plan type | What the customer sends or taps | What you record | Cut-off rule | Payment |
|---|---|---|---|---|
| Daily | Menu pick, address, slot | One order with order number | Previous evening, 8 pm | UPI before cooking, or COD |
| Weekly | Plan, start date, address | Six scheduled meals | Skips by 8 pm previous day | Full week in advance |
| Monthly | Plan, start date, address, preferences | 26 scheduled meals plus skip balance | Skips by 8 pm, max 4 carried forward | Full month in advance, reminder 3 days before renewal |
Skips, pauses and changes: the rules that save your mornings
The single most important part of taking tiffin orders on WhatsApp is the skip rule, because skips are the most frequent message you will receive. Decide and publish three things: the cut-off (8 pm the previous evening is standard), what happens to a skipped meal (carried forward to the end of the plan, up to four or five a month), and what happens to a late skip (charged, because the meal is cooked).
Pauses of a week or more should extend the plan end date. Address changes for a single day should be allowed up to the same cut-off. Plan changes (veg to non-veg, one meal to two) take effect from the next renewal unless you are happy to pro-rate. Put all of this in a short "how it works" message that every new customer receives, and on your store page. The full set of rules and message templates is in skip days, pauses and refunds for tiffin subscriptions.
When a customer skips, confirm it back with the new balance: "Skipped Tuesday 14th. 3 carry-forward meals remaining." That one line removes most disputes.
Collecting payment before the first meal
Advance payment is non-negotiable for plans. The way to make it painless is to put the payment inside the ordering flow: the customer picks a plan and pays by UPI or card in the same conversation, and the plan activates on payment. No screenshots, no "I will pay on Friday". For customers who insist on cash, allow cash on delivery for daily orders only, and move them to online payment when they take a plan.
Renewals need a reminder three days before the plan ends, with a one-tap payment link, and a second reminder on the last day. If payment has not arrived by the renewal date, the plan pauses rather than running on credit. This feels strict and is actually kind: it avoids the awkward conversation about ₹3,000 of dues at month-end.
Your morning: one count, one route list
The output of a well-structured order flow is a morning that starts with two things: the number of meals to cook by type (say, 38 veg, 9 non-veg, 6 large) and a list of delivery addresses in route order with any one-day changes highlighted. If your system cannot produce both before you light the stove, it is not doing its job.
At the end of the day, mark each meal delivered. This closes the order, lets the system send a short "delivered, rate your meal" message, and keeps the skip balance accurate. The complete guide to starting a tiffin service covers how the morning count fits into the rest of the daily routine.
What this looks like on Tezzu
On Tezzu the whole flow above runs on your own WhatsApp number and a free store page at tezzu.in/store/your-name, with no app for customers to install. Your menu holds the meal types as items with variants (veg, non-veg, large) and add-ons (extra roti, sweet), and the ordering bot walks the customer through item, address, delivery slot and payment. Scheduled orders and pre-orders let a customer book meals for specific dates in advance, and menu scheduling by weekday shows Tuesday's rotation on Tuesday.
Payments run on UPI and cards through Razorpay, with cash on delivery as an option you control, and coupons can auto-apply for first orders or renewals. Delivery zones with distance-based charges keep your route tight. Every order lands in the live dashboard with its status, and the staff app announces new orders out loud, so your delivery person can work from the same list you see.
Once a meal is marked delivered, the customer is asked for a rating, and the customer insights view shows who orders regularly and who has stopped. Plans start at ₹999 a month with a 7-day free trial, a flat ₹10 per order and no commission. The tiffin service case study shows this set-up at 200 meals a day.
See the tiffin flow end to end
The tiffin service page shows how plans, skips, payments and the morning count work on Tezzu, with your own WhatsApp number and no customer app.
See how it works for tiffin servicesFrequently asked questions
How do I take tiffin orders on WhatsApp Business?
Start by publishing a fixed menu and plan list, a skip cut-off and advance payment rules, and ask customers to order through a link rather than free text. The WhatsApp Business app alone cannot record plans or payments, so beyond 20 to 30 customers most services connect an ordering bot or store page to their WhatsApp number to create orders automatically.
Can customers book a monthly tiffin plan on WhatsApp?
Yes. With an ordering system connected to your WhatsApp Business number, a customer picks the monthly plan, start date, preferences and address, pays by UPI or card in the same chat, and the plan creates the scheduled meals. Renewal reminders go out automatically before the plan ends with a one-tap payment link.
How do I handle skip days in a WhatsApp tiffin service?
Publish a cut-off, typically 8 pm the previous evening, and carry forward skipped meals to the end of the plan up to a monthly limit. Same-day skips are charged because the meal is cooked. Confirm every skip back to the customer with the remaining carry-forward balance so there is a written record on both sides.
Is cash on delivery a good idea for tiffin orders?
Cash works for one-off daily orders but creates collection problems on plans. Keep COD as an option for first-time daily customers and require online payment in advance for weekly and monthly plans. With UPI available almost everywhere in India, most customers are comfortable paying a plan upfront when the link is in the chat.