pre launch12 min read

Cloud kitchen vs casual dining: real costs, real margins, India 2026

Side by side capex, monthly fixed cost, channel margin, and break even of cloud kitchen vs casual dining in India.

By Forkcast Editorial · HORECA research team

Cloud kitchen looks cheaper to open. Whether it actually earns more is a different question once aggregator commission, ad spend, and refund drag are layered in. Side-by-side numbers for India 2026.

Capex comparison

LineCloud kitchen (₹L)Casual dining (₹L)
Equipment5-912-18
Interiors2-414-22
Deposit1-36-12
Licences1-22-3
Working capital1-34-8
Total10-2138-63

Monthly fixed cost

Cloud kitchen: ₹1.0-3.0 lakhs/month (small footprint, lean staff). Casual dining: ₹2.8-7.5 lakhs/month (higher rent, larger staff, utilities scale). On the surface cloud wins by a wide margin.

Variable cost — where casual dining wins

This is the part most cloud-kitchen pitches gloss over. Cloud kitchens are 90-100% aggregator-dependent. At a 22-25% commission rate, that's 22-25% of revenue gone to Zomato/Swiggy. Add packaging (5%), variable labour (5%), food cost (30%) and you're at 62-65% variable cost rate — versus 42-46% for a dine-in heavy casual-dining.

Cloud kitchen contribution margin: 35-38%. Casual dining contribution margin: 54-58%. The math means a casual dining can absorb a bad week without losing money; a cloud kitchen can't.

Break-even revenue

FormatFixed (₹L/mo)CMBreak-even revenue (₹L/mo)
Cloud kitchen (mid)2.037%5.4
Casual dining (mid)5.055%9.1

The cloud kitchen needs ~₹18,000/day to break even. The casual dining needs ~₹30,000/day. Cloud wins on absolute number — but the question is whether the cloud kitchen can sustain ₹18,000/day given its dependence on a small set of aggregator listings, ad-budget compounding, and a tougher refund profile.

Hidden lines for cloud kitchens

  • Ad spend — many cloud kitchens spend 6-12% of revenue on Zomato/Swiggy ads to stay visible.
  • Refund drag — packaging breakage, missing items, late deliveries lead to 2-4% revenue losses through refunds.
  • Listing cost — multi-brand cloud kitchens incur per-brand listing fees, not always offset by volume.
  • Brand fragility — a one-week rating drop below 4.0 can permanently shrink discoverability.

When cloud kitchen wins

  • You have an existing brand and just need a delivery node.
  • You're testing a cuisine before committing to a dine-in format.
  • You can hit ₹2.5L+/day from one brand by month 3 (rare; possible with strong product + city).
  • You're under-capitalised — opening a casual dining underfunded is worse than a well-capitalised cloud.

When casual dining wins

  • You can secure rent at <8% of expected revenue.
  • You're confident in dine-in catchment (footfall, parking, visibility).
  • You have a chef and a tested menu.
  • You can run with no aggregator presence for the first 60 days while you build dine-in repeat customers.
Run the numbers for your format →

More for you

We use minimal first-party cookies to keep the dashboard signed in and to measure aggregate usage. We do not sell or share your data. See our Privacy Policy and DPDP statement.
Cloud kitchen vs casual dining: real costs, real margins, India 2026 | Forkcast