Build Your Own Bundle for Thali and Meal-Box Kitchens: Let Customers Assemble the Order

A build your own meal box is a menu item where you set the structure and the customer fills in the choices: one sabzi from four, one dal from two, rice or roti, a sweet if they want it, at one bundle price. For a thali or meal-box kitchen it removes the most tiring part of taking orders, the swap request. "Can I have rajma instead of chole?" stops being a message you answer forty times a day and becomes a tap the customer makes on their own.

This post walks through how the bundle is built, how to price it so the margin holds whatever the customer picks, and what the customer sees when they order it on WhatsApp or your store page. The worked numbers are for a lunch thali, but the same structure fits office meal boxes, family dinner packs and diet meal plans.

Why a fixed thali loses orders you never see

A fixed thali is easy for the kitchen and hard for the customer. Anyone who does not want one of the five components either orders somewhere else, or messages to ask for a swap. If the swap gets a quick yes, the kitchen now has an order that differs from the printed one, and the person taking it has to remember to tell the cook. If it gets a slow reply, the lunch window passes and the order is gone.

The usual fix is to list every combination as a separate item: Rajma Thali, Chole Thali, Paneer Thali, each with a roti version and a rice version. The menu grows to thirty near-identical items, customers scroll past half of them, and a price change means editing thirty lines. The thinking behind keeping a cloud kitchen menu short is covered in fewer items, higher margins; a build-your-own bundle is how you keep the menu short and still offer every combination.

How a build-your-own bundle is structured

Think of the bundle as a short form with a fixed price. Each section is a question, each question has a list of answers, and each has a rule about how many answers the customer may pick.

• Base: pick one of steamed rice, jeera rice, 3 rotis, or 2 rotis with a small rice.
• Dal: pick one of dal tadka or dal makhani.
• Sabzi: pick one of four, rotating by weekday.
• Sides: pick up to two of salad, raita, papad, pickle.
• Sweet: optional, pick one of gulab jamun or kheer.

The customer cannot submit the order until the required sections are answered, so every order that reaches the kitchen is complete. There is no "which dal?" call back. The kitchen ticket lists the choices in the same order every time, so a cook reading forty tickets at 12:30 sees the same layout on each one.

Two decisions shape the whole thing. First, which sections are required and which are optional. Base and dal are required; the sweet is optional. Second, whether every choice inside a section costs you roughly the same to make. Keeping the choices within a section close in cost is what makes a single bundle price safe, and the next section shows why.

Pricing the bundle so the margin holds

With a fixed-price bundle, the customer can pick the most expensive option in every section. Your price has to survive that case, so cost the worst-case thali first and set the price against it.

Price this thali at ₹179 and the cheapest combination leaves ₹113 before rent, staff and delivery, while the dearest leaves ₹73. Both are workable. Price it at ₹139 and the paneer-plus-makhani customer leaves you ₹33, which is gone the moment you pay a rider. So the choice is either ₹179 for everything, or ₹149 with paneer and dal makhani moved out of the free sections and offered as paid upgrades at ₹30 and ₹15.

The paid-upgrade route is usually better for a thali kitchen. The headline price stays low enough to compete with the ₹120 to ₹150 lunches around you, and the customers who want paneer pay for it without feeling cheated, because they chose it. The wider maths of combo pricing, including how to decide what the anchor price should be, is in pricing meal deals that lift order value.

What this looks like on Tezzu

On Tezzu a build-your-own bundle is created in the menu builder next to your ordinary items and combos. You give the bundle a name and a price, then add its sections. Each section gets a name, the items the customer may choose from, and the rule for that section: pick exactly one, pick up to two, or optional. The items inside a section are menu items you have already created, so the kitchen sees "Dal makhani" on the ticket, spelled the way it always is.

On WhatsApp, the customer taps the thali from the menu and the bot walks through the sections one at a time: base, then dal, then sabzi, then sides. Each step is a list to pick from, so nobody types "rajma" in a spelling the bot has to guess at. On the store page at tezzu.in/store/your-name and the web menu, the same bundle shows as one card with its sections laid out on a single screen, and the order cannot be placed until the required picks are made.

Every channel uses the same bundle definition. Add a Friday sabzi on Thursday night and it is in the WhatsApp flow, the store page and the QR menu together. Pair that with menu scheduling and the Friday sabzi can be set to appear only on Fridays, which is how a rotating thali runs without anyone editing the menu each morning.

The order lands in the live dashboard and the staff app with every pick listed under the bundle name, and the KOT prints the same way. The full walk-through of building bundles alongside categories, variants and add-ons is in building your menu in Tezzu, and the complete list of what the dashboard and staff app do with those orders is on the features page.

Three bundle designs for thali and meal-box kitchens

The weekday lunch thali

Four required sections, one optional sweet, priced at the low end with paid upgrades for paneer and non-veg. This is the volume product: it has to be assembled in under four taps on a phone during a ten-minute office break. Keep the sabzi list to four and change them by weekday rather than listing eight at once.

The office meal box for five or more

Same sections, but the bundle is sold as a pack of five and the customer picks one sabzi for the whole pack. Teams ordering together rarely want five different sabzis, and a single pick keeps the kitchen fast. Price the pack with a small discount per box, say ₹169 instead of ₹179, so the person collecting money from colleagues has a reason to order as a group.

The family dinner box

Larger portions, two sabzi picks instead of one, a bread section with a quantity choice, and a dessert that is included rather than optional. This box is where the ₹299 to ₹399 orders come from, and a two-pick sabzi section is what lets a family of four agree on one order. The same structure, with different components, runs the meal deals that pizza and burger joints sell.

Mistakes that make a bundle harder to order

Too many sections. Six questions is already a lot on a phone. If a section has only one real answer for most customers, make it a default and move on.

Unequal costs inside a free section. If paneer sits next to aloo gobi at the same bundle price, the bundle margin is set by paneer. Either price for it or move it to a paid upgrade.

Vague item names. "Sabzi of the day" on the ticket means the cook has to ask someone. Name the actual dish, and use scheduling to show the right one on the right day.

No quantity on the bread. "Roti" without a count leads to a complaint at the door. Make it "3 rotis" or let the customer pick a count.

Frequently asked questions

What is a build your own meal box?

It is a menu item with a fixed price and a set of sections the customer fills in: a base, a dal, a sabzi, sides and so on. The kitchen defines which choices are allowed in each section and how many the customer may pick. The customer assembles the meal from those choices, and the order arrives complete with every choice listed.

How do I price a customisable thali online?

Cost the most expensive combination a customer could pick and set the bundle price so that combination still leaves a margin you can live with. If one choice, such as paneer, pushes the cost too high, take it out of the free section and offer it as a paid upgrade. Check the cheapest combination too, so the price is not so high that it scares off the plain-dal customer.

Can customers order a build-your-own bundle on WhatsApp without an app?

Yes. On a WhatsApp ordering bot the sections are presented one at a time as lists to pick from, so the customer taps rather than types. The same bundle appears on your store page and web menu as a single card. Customers do not install anything; the order goes to your dashboard and staff app with every choice recorded.

Does a bundle work for a meal box that changes daily?

Yes, if the ordering system lets you schedule items by weekday. You keep one bundle, and the sabzi section contains all the dishes you rotate through, each scheduled to show only on its day. The customer always sees the right choices for today, and you do not rebuild the bundle each morning.