Daily rhythm
From morning approval to midnight forecast.
Approve the number. Check the stock. Run service. Reconcile. Close. The forecast runs overnight. Seven stages. One loop.
The kitchen ran today. Close it honestly.
Dinner just ended. In, prepped, wasted, leftover — per ingredient. Appetisers, mains, gravies, sauces. The way the kitchen actually moves.
Yesterday carries forward
Leftovers within their shelf life become tomorrow’s starting stock.
Waste and leftover stay apart
Cooking-side waste is its own line.
The right people see it
Owners and managers, the moment it’s submitted.
What sales implied. What the kitchen used.
Kitchen closed. Upload the day’s sales. The gaps surface.
Right unit, every ingredient
kg, L, pcs — picked correctly.
Tolerance band
Small variance is normal. Only real gaps flag.
Tomorrow improves
The forecast picks up the corrected pattern.
A number for tomorrow.
While the kitchen sleeps, the math runs. Every ingredient. Every quantity. Every confidence. Ready before the chef walks in.
Day one: sensible. Week four: sharp.
It learns the rhythm. Quietly.
Festivals, already in the math
Holi, Diwali, Ganesh Chaturthi, Republic Day.
Confidence per ingredient
Low confidence is a signal — use judgement there.
The chef decides.
The forecast is waiting. Scan, accept, override. Every decision is recorded.
Approve. Override. Edit again.
If the day changes, the number can change.
Print a clean prep sheet
No clutter. Hand it to the kitchen.
Audit trail
Who approved. Who changed it. When.
Stock vs the number.
Morning stock goes in. The system flags OK, LOW, or OUT — per ingredient. Service starts knowing what is at risk.
Three states
OK. LOW. OUT.
OUT links straight to inventory
The vendor is pre-selected.
No blind spots
Nothing surprises the kitchen at 7 PM.
Service runs. Nothing in the way.
Lunch and dinner happen. The POS stays the source of truth. AnnapurnaOps reads the day after — never during.
POS untouched
We don’t sit between you and your POS.
Dish-level detail
Every dish, every quantity, every bill — as-is.
Branches stay separate
Begumpet never sees Hi-Tech City.
Book a party. The number adjusts.
Festivals, buffets, holidays, private dinners. Add them when you know. The forecast does the rest.
Meal-aware
A dinner buffet doesn’t inflate Lunch prep.
Capacity-aware
See how a booking fills the room — and reshapes the day.
Instant notifications
The right people, the moment a booking is added.
The nightly math
Between dinner and dawn.
Sample numbers from the Cream Centre pilot. Real benchmarks will land as the rollout settles.
0 min
to close one branch
0 night
for the forecast to regenerate
0
hours of quiet before service
Pilot in progress. Numbers update as the data settles.
What changes
Five tools. One WhatsApp group. Gone.
Most kitchens we meet run a closing register, a forecast spreadsheet, a POS dashboard, an inventory ledger, and a manager group chat. Five places where the signal dies.
Manager judgment
Manager guesswork
Branch-level views
One mega spreadsheet
POS as source of truth
POS as a dead end
Notifications by role
WhatsApp messages to all
Try the loop
One day in, you’ll know if it fits.
Close one day. Get one forecast. Approve it the next morning. That's the whole test.