Quick answer

A profitable Indian sweet shop runs on four disciplines: batch-level costing per kilogram (30–40% food cost target), weight-based billing that closes counter leaks, freshness rotation for a highly perishable product, and festival planning that treats Diwali as the year's P&L in miniature.

Why sweet shop math is different

A mithai shop is a factory and a retailer in one room. You manufacture (in batches, from volatile ingredients), you retail (by the gram, across dozens of SKUs), and your product expires in days. Restaurant-style dish costing doesn't fit — the unit that matters is the cost per kilogram per batch.

Discipline 1 — Batch costing that tracks ghee and dry fruit

Kaju katli lives and dies on cashew prices; most classics live on ghee, khoya and sugar. Cost every batch: ingredient quantities per production run ÷ output weight = cost per kg. When ghee moves 9% in a month — and it does — your per-kg costs and prices should know it the same week, not at year-end.

Discipline 2 — Weight-based billing at the counter

Loose sweets sold by the gram have two classic leaks: habitual rounding in the customer's favour and generous unbilled "taste" portions. Neither feels like theft; both add up to 2–4% of revenue across a busy counter. A scale-integrated POS weighs, prices and bills in one motion — with correct GST treatment for loose versus packaged sweets.

Discipline 3 — Freshness rotation and the production calendar

Most milk-based sweets have a 1–3 day quality window. Batch labels with production dates, FIFO display rotation, and an end-of-day count of what's approaching its window are non-negotiable. Track unsold-at-expiry per SKU per weekday — the same waste-log discipline as a bakery, with even tighter windows.

Discipline 4 — The festival P&L

For many mithai shops, Diwali fortnight plus Rakhi and Bhai Dooj produce a third to half of annual profit. Treat it as a project: last year's per-SKU sales as the baseline, ingredient purchases locked before the seasonal price climb, production in dated waves, temporary staff trained on the billing counter before the rush, and advance corporate/gifting orders taken against deposits.

30–40%
typical food cost range for Indian sweet shops
2–4%
of revenue lost to counter rounding and unbilled portions
1–3 days
quality window for most milk-based sweets
How KhanaOS helps: weight-based billing with weighing-scale integration is built in — plus batch production costing, festival-season planning views, and GST handling for packaged vs loose sweets. It's the sweet-shop workflow generic POS systems don't have.

Frequently asked questions

What food cost percentage should a sweet shop target?

Typically 30–40% — higher than restaurants, because ghee, khoya, dry fruits and sugar dominate the basket and their prices move sharply. Batch-level costing per kg, updated whenever ghee or dry-fruit prices change, is the core discipline.

How does weight-based billing work in a sweet shop?

The POS connects to the weighing scale: the selection is weighed, per-kg price computes the amount, and GST applies correctly for loose vs packaged sweets. It eliminates the classic counter leaks — habitual rounding and unbilled portions — that silently cost 2–4% of revenue.

How should a sweet shop plan for festival season?

Work backwards from last year's festival sales per SKU: lock ghee and dry-fruit purchases early (prices rise into Diwali), schedule production in dated batches, train temporary counter staff before the rush, and take advance orders with deposits for bulk gifting.