The problem: Indian meals are never a single food
Open any diet planning software and try to build a typical Indian lunch. You add roti, then dal, then sabzi, then curd. Four separate items sitting in a flat list — no relationship between them. The client sees four independent foods and wonders: "Can I skip the dal? Is the curd optional? What if I want rice instead of roti — does the dal still apply?"
This is the Indian meal composition problem. Unlike Western meals where a "chicken breast with broccoli" is self-contained, Indian meals are inherently compositional. Roti is never eaten alone — it needs dal or sabzi. Idli without sambar is incomplete. Rice without a curry is just... rice.
Every Indian dietitian knows this intuitively. But until now, no meal planning software represented it in the data model. Foods were either standalone items or "alternatives" (pick one). There was no way to say "these foods go together."
How MealStack solves this: Side dishes and food combos
MealStack introduces two concepts that map directly to how Indian meals work:
- Side dishes (companions) — foods that "go with" a main item. Chutney with idli. Raita with biryani. Salad with rajma chawal.
- Food combos — saved combinations you can insert with one click. "Roti + Dal + Sabzi" as a reusable unit.
How it looks in the builder
When you add a side dish to a food item, it appears indented below the parent with a subtle connector line. This visual nesting immediately communicates the relationship: "these foods are eaten together."
🍽️ Lunch — 1:30 PM
● Rajma (Kidney Beans) 1 katori 180 kcal
+ Steamed Rice 1 katori 180 kcal
+ Green Salad 100g 25 kcal
+ Onion Raita 1 katori 60 kcal
● Buttermilk 1 glass 40 kcal
The rajma is the "main" item. Rice, salad, and raita are its side dishes. Buttermilk is standalone. The client immediately understands: rajma + rice + salad + raita is one unit; buttermilk is separate.
Alternatives with side dishes — the combo swap
Here's where it gets powerful. When you combine alternatives with side dishes, each alternative can have its own companions. When the client swaps, the entire combo changes:
Option A (selected):
● Idli (2 pieces) 120 kcal
+ Sambar 80 kcal
+ Coconut Chutney 45 kcal
Option B:
● Poha 200 kcal
+ Peanuts 50 kcal
+ Lemon wedge 5 kcal
When the client picks Option B, the nutrition recalculates for the entire combo — not just the main food. No other tool does this.
AI auto-pairing: zero manual work
When you use AI to generate a meal plan, MealStack's AI already understands Indian food pairing rules. It knows that roti needs dal, idli needs sambar, and rice needs a curry. The AI assigns roles to each food — "base", "protein", "side", "accompaniment" — and the system automatically creates the companion relationships.
Generate a full day with AI, and every meal comes pre-structured with proper food pairing. No manual grouping needed.
Save combos for one-click reuse
Built a perfect "Roti + Dal + Sabzi" combination? Save it as a combo. Next time you need it, insert the entire combo into any meal with one click. The system tracks which combos you use most and surfaces them at the top.
Common combos Indian dietitians save:
- Roti + Dal + Seasonal Sabzi (North Indian lunch base)
- Idli + Sambar + Chutney (South Indian breakfast)
- Rice + Rasam + Papad + Curd (South Indian lunch)
- Paratha + Curd + Pickle (North Indian breakfast)
- Dosa + Sambar + Chutney (South Indian breakfast variant)
- Chapati + Paneer Sabzi + Salad (Protein-rich dinner)
How it works in the client portal
On the client's side, companions appear with a "+" prefix under the main food. When alternatives are available, expanding the options shows each alternative with its own side dishes. Tapping "Use this" swaps the entire combo — main food plus all its companions.
Nutrition totals update instantly to reflect the selected combo. The shopping list includes all companion foods. PDF exports show companions indented with a "+" prefix.
Why this matters for client compliance
When clients see a flat list of 5 foods in a meal, they cherry-pick. They eat the rice but skip the dal. They have the roti but not the sabzi. The meal becomes nutritionally incomplete.
When foods are visually grouped as a unit, clients understand the intent: "these go together." Compliance improves because the plan communicates not just what to eat but how to eat it.
No other tool does this
We checked every major nutrition software — Nutrium, NutriAdmin, Foodzilla, Zoconut, mealPlan.fit. None of them have a concept of "foods that go together." They all treat meal items as a flat list. Some have alternatives (pick one), but none have companions (eat together).
This is a uniquely Indian problem that requires an India-first solution. MealStack is the first nutrition platform to solve it properly.
Try it free
Food combos and side dishes are available on all plans, including the free tier. Create your first meal plan with proper Indian meal composition in under 15 minutes.
Start free — no credit card needed