A daily changing menu for a tiffin service is normal, and so is the hour it costs every morning. Someone types today's dishes into a WhatsApp broadcast, forwards it to three groups, answers "aaj kya hai?" twenty times anyway, and then re-types the same menu next Monday. Rotating menus fix this by making the weekday part of the menu itself: Monday's rajma chawal is scheduled to appear on Mondays, and it does, without anyone touching it.
This post shows how to design the rotation, how menu scheduling turns it into a menu that changes on its own, what customers see each day on WhatsApp and the store page, and how to run a two-week or four-week cycle without the setup growing out of hand.
What the morning menu message actually costs
Take a tiffin service doing 80 lunches a day. The morning routine is familiar: type the menu, send it to the broadcast list, paste it into the family group, the office group and the PG group, then field the replies. Half the replies are orders, half are questions the message already answered. Call it 45 minutes of a working owner's time, six days a week.
The bigger cost is the orders that go wrong. A customer reads yesterday's message and orders the chole that was Tuesday's dish. The person taking orders either refuses, which loses the order, or accepts and adds "make one chole" to the cook's list, which means one extra dish cooked for one person. Multiply that across a week and the kitchen is cooking off-menu more than it realises.
A rotating menu removes both costs. The customer opens WhatsApp or your store page and sees only today's dishes. There is nothing to type in the morning and nothing to order by mistake.
Design the weekday rotation on paper first
Before touching any software, write the rotation as a table. A one-week cycle with lunch and dinner looks like this for a North Indian tiffin.
| Day | Lunch (₹120) | Dinner (₹110) |
|---|---|---|
| Monday | Rajma, jeera rice, 3 roti, salad | Aloo gobi, dal, 4 roti |
| Tuesday | Chole, rice, 3 roti, pickle | Palak paneer, 4 roti |
| Wednesday | Kadhi chawal, 2 roti, papad | Mix veg, dal, 4 roti |
| Thursday | Dal makhani, rice, 3 roti | Bhindi, dal, 4 roti |
| Friday | Paneer bhurji, rice, 3 roti | Veg pulao, raita |
| Saturday | Chole bhature | Khichdi, kadhi, papad |
Two things to notice. The lunch price and dinner price stay fixed across the week, so a monthly subscriber knows what they pay. And each day's meal is one item, named by the dish rather than "Monday lunch", so the customer reading the menu knows what they are getting. If you want a few standing extras, such as a sweet at ₹25 or extra roti at ₹8, keep them as separate items that show every day. More rotation templates, including four-week cycles, are in tiffin service menu ideas: 4-week rotation templates.
How menu scheduling turns the table into a self-running menu
Menu scheduling lets you attach days and times to any item or category. Monday's rajma lunch gets the rule "Monday, 7 am to 12 pm" for ordering, so it is visible on Monday morning and hidden the rest of the week. Tuesday's chole gets "Tuesday, 7 am to 12 pm". Do this once for each row of the table and the rotation is built.
The time window matters as much as the day. A tiffin kitchen needs orders in by a cut-off, often 10 am for lunch and 5 pm for dinner. Setting the window to close at the cut-off means a customer who opens the menu at 11:30 sees the dinner options and tomorrow's note, rather than a lunch they cannot have. This is the same mechanism that breakfast cafes use to switch items off at 11 am, applied to a whole day's meal.
Categories make this faster. Put all six lunches in a "Lunch" category with its own ordering window, then give each item only its weekday. The window is set once; the days are set six times. For the general pattern of menus that switch on a schedule, including breakfast, lunch and dinner at a restaurant, see rotating menus that switch automatically.
What this looks like on Tezzu
In the Tezzu dashboard, each menu item and category has an availability setting with weekdays and a time window. For a tiffin service you create a Lunch category and a Dinner category, set each category's window to the ordering hours and cut-off, and then create one item per day inside each. Monday Rajma Lunch is ticked for Monday only; Tuesday Chole Lunch for Tuesday only. The price sits on the item, so the ₹120 lunch price is entered six times and never again.
Once the days are set, the menu changes on its own. A customer who opens your WhatsApp chat on Wednesday morning and asks for the menu sees Kadhi Chawal under Lunch and nothing else from the rotation. The store page at tezzu.in/store/your-name shows the same item. There is no Monday dish to order by mistake, and no message to send announcing what is cooking.
When a dish is finished early, you snooze the item from the dashboard or staff app and it disappears from both channels until you bring it back. When the rotation changes for a season, you edit the six items in place rather than rebuilding anything; the weekday rules stay where they are.
Orders come into the live dashboard with the day's dish named on each one, so the cook's count for the morning is a single list: 64 rajma lunches, 11 with extra roti, 9 with the sweet. The staff app alerts whoever is on the phone that morning. Detailed setup steps, including how category rules and item rules combine, are in menu scheduling in Tezzu, and the full list of what the menu and ordering tools do is on the features page.
Set your rotation once and stop typing it
Build the week's menu with weekday rules in an afternoon, and from then on customers see today's tiffin by themselves. Every plan starts with a 7-day free trial, then ₹10 per order and no commission.
Start your free 7-day trialRunning a two-week or four-week cycle
A one-week rotation gets repetitive for a monthly subscriber. Most tiffin services settle on two weeks, some on four. Weekday scheduling alone cannot tell week one from week two, so the practical approach is to keep both weeks' items in the menu and keep only the current week switched on. On Sunday evening, switch week one's twelve items off and week two's twelve on. It takes a few minutes, which is still far less than typing the menu daily.
Name the items so the switch is easy to do without mistakes: "Wk1 Mon Rajma Lunch", "Wk2 Mon Kadhi Lunch". The customer sees the dish name and the price; the week label is for you. Keep the standing extras, the sweet and the extra roti, outside the weekly groups so they never need touching.
Whichever cycle you run, resist adding choice to every day. A tiffin customer is paying for not having to decide. One lunch, one dinner, a couple of extras, and the occasional Saturday special is a menu people stay subscribed to.
Pairing the rotation with subscriptions and reminders
A rotating menu answers "what is for lunch today". The other half of running a tiffin service is "who is eating today", and that is handled by how you take orders: daily, weekly or monthly plans, skip days and pauses. The approach that keeps both halves tidy is described in how to take tiffin orders on WhatsApp.
The one message worth still sending is a weekly one. A Sunday evening campaign to your subscribers with the coming week's dishes, sent from the same number they order on, reminds them you exist and lets them skip the day they dislike in advance rather than on the morning. Because the menu itself is already right in the chat, the message can be short.
Frequently asked questions
How do tiffin services manage a daily changing menu?
The ones that have stopped typing it each morning use menu scheduling: every dish is given the weekday it is served, and the ordering system shows only that day's dishes. Customers see today's tiffin on WhatsApp or the store page, order within the cut-off window, and the kitchen gets a single count per dish. Multi-week cycles are handled by switching the current week's items on and the other week's off.
Can customers order tomorrow's tiffin today?
Yes, if you combine the rotating menu with scheduled orders or pre-orders. The customer picks tomorrow's date and sees that day's dish. Many tiffin services instead run monthly subscriptions, where the customer is eating every day by default and only needs to skip days, which makes advance ordering unnecessary for regulars.
What is the best cut-off time for tiffin orders?
Most lunch services close ordering between 9 am and 10:30 am, and dinner between 4 pm and 5:30 pm, depending on how long cooking and delivery take. Set the ordering window to end at your real cut-off, so the menu stops accepting orders at the same moment the kitchen stops taking them.
Do I need a separate app for a rotating menu?
No. A WhatsApp ordering system with weekday scheduling does it inside the chat and on a web store page. Customers do not download anything; they open the chat or the link and see today's menu. The schedule is managed from your dashboard, and the same rules apply across every channel.