Every curry is a spice-level × protein decision. Your ordering platform should treat it that way. And stop taking a cut of the family biryani.

Indian food is the most modifier-heavy cuisine in the business. One curry base — tikka masala, korma, vindaloo, saag, madras, chettinad — multiplies across chicken / lamb / goat / shrimp / paneer / chana / vegetable, and then across mild / medium / hot / Indian-hot. Generic platforms flatten all of that into a free-text "notes" box, the spice level gets lost, and the order comes back. Zay-OS models curry base × protein × spice level as a real matrix so every dish fires exactly the way the diner built it.

The weekday lunch thali — dal, sabzi, rice, roti, raita, pickle, sweet — is a fixed-format order that generic platforms turn into eight confusing line items. Zay-OS ships it as one thali SKU with the rotating curry as a pick-one modifier, so the office lunch crowd orders in two taps. Tiffin-style repeat lunch orders reorder from history in one motion, which is how you keep the Monday-to-Friday dabba habit on your own channel instead of a marketplace's.

Biryani is the family order and the margin engine. Zay-OS sells it the way it is actually eaten — single serving, family pack feeding 4, party tray feeding 8-12 — with raita, mirchi ka salan, extra masala, boiled egg, and extra meat as priced add-ons instead of giveaways scribbled into a notes field. The pack builder does the serving math so the Friday-night family order is sized right the first time, at full margin, with 0% commission.

The bread basket is where an Indian ticket climbs: garlic naan, butter naan, cheese naan, peshwari, tandoori roti, laccha paratha, kulcha. Dine-in servers upsell it automatically; delivery marketplaces bury it three menus deep. Zay-OS surfaces breads and rice upgrades (jeera rice, saffron rice, extra basmati) as one-tap add-ons at checkout, so a two-curry order reliably leaves with the naans that pay for the tandoor.

Many Indian restaurants in the US run three cuisines under one roof — a South Indian dosa/idli/Udupi vegetarian section, a North Indian/Mughlai tandoor-and-gravy section, and an Indo-Chinese section (gobi manchurian, chilli paneer, hakka noodles, szechuan fried rice). Each needs its own modifier logic: dosa fillings and chutney choices are not curry proteins, and manchurian dry-vs-gravy is its own switch. Zay-OS gives each section native structure instead of one flattened list.

For a big share of the Indian diner base, dietary rules are hard constraints, not preferences. Zay-OS carries veg / vegan / Jain (no onion, no garlic) / halal / gluten-free flags at the item and modifier level, so a Jain diner can filter the menu to what they can actually order and a halal-observant family can see sourcing at a glance. If halal is core to your concept, the halal vertical page covers zabiha framing and Ramadan flow in depth.

Indian catering is big-format — weddings, engagement and mehndi functions, pujas, corporate Diwali parties — and it is where the full-margin volume lives. The catering builder handles per-tray and per-guest math (feeds 25 / 50 / 100), lead-time windows so the kitchen can plan the masala and meat order, and scheduled pickup or delivery. Catering-scale orders bill at a flat 10% instead of the per-order fee, which is still a fraction of a marketplace cut on a four-figure order.

The Indian restaurant year has its own calendar: Diwali sweets, snacks, and party trays; Holi; Navratri vrat menus (no onion, no garlic, fasting-appropriate); Ramadan iftar boxes and Eid biryani volume; and the cricket World Cup rush that fills every living room with orders. The pre-order and scheduling flow takes festival orders days ahead with lead-time windows, so the kitchen batches the mithai run instead of drowning in day-of tickets.

DoorDash, Uber Eats, and Grubhub orders ingest into the same kitchen tablet as your direct Zay-OS orders. One menu is the single source of truth across every channel — no double-entry, no tablet wall next to the tandoor, no 86ing the goat biryani in four different apps when the handi runs out on a Saturday night.

The Zay-OS schema carries Hindi and transliterated alternateName variants so diners searching the way they actually type — "indian restaurant near me," "biryani near me," "भारतीय रेस्तरां," "veg thali near me" — find your storefront. The visible storefront stays in your brand language, but the discovery layer reaches the Hindi-and-Hinglish-searching diner base that generic platforms never index for.