Customers skip the days they travel and pause the weeks they are away, all by themselves. You cook to a real headcount, and nobody pays for a meal they never ate.
"No tiffin today, travelling." Multiply by forty customers and three chat apps, and the kitchen count is wrong before the rice is on.
A cooked meal delivered to an empty flat is cost, fuel and an unhappy customer, three losses in one box.
Monthly plans meet real life. Counting who skipped what, and what is owed back, turns the first of the month into arithmetic and arguments.
Office customers eat Monday to Friday, some want Saturdays, one wants alternate days. Holding the patterns in your head does not scale past a street.
Travelling tomorrow is two taps in the customer’s app before your cutoff. The kitchen count updates itself, and the uneaten meal is never cooked.
Weekdays only, alternate days, veg on Tuesdays. Each customer’s pattern is their own, and the daily count is simply the sum of them all.
The wallet is charged per delivered meal, so a skipped day is automatically an unspent day. Month-end adjustments stop existing as a category.
Lunch has a deadline. Runsheets come sorted by area and building, so the last dabba is still hot, and a printed backup covers a bad-signal day.
The parts of Lanemi a tiffin kitchen leans on every day.
| Feature | What it does for you |
|---|---|
| Self-service skip and pause | Travel days and away weeks handled by customers, before your cutoff. |
| Flexible subscriptions | Weekday-only, alternate days, veg days. Any pattern per customer. |
| Prepaid wallet | Charged per delivered meal. Skipped days cost the customer nothing. |
| Nightly forecast | Tomorrow’s headcount, locked before the shopping and the stove. |
| Ordered runsheets | Sorted for the lunch window, printable as a backup. |
| Disputes and credits | A missed or wrong dabba is a quick credit, recorded fairly. |
| Reports | Meals by day, churn and the customers quietly slipping away. |
A dabba service in Mumbai, a meal-prep round in Toronto, a lunchbox run in Jakarta. Your currency, your payment methods, your rules.
Lanemi began on a farm delivering fresh dairy, where a wrong count means wasted food by lunchtime. The skip-ahead-of-cutoff design exists because perishables punish late information. We run our own round on it daily.
Read our storySkips land before the rice goes on. We cook for the people actually eating today.
Month-end adjustments used to take a day. Now there’s nothing to adjust.
[placeholder quotes: replace with real vendor testimonials before launch]
Yes, one day, a date range or an open-ended pause, all from their app before your cutoff. The kitchen count updates automatically.
Nothing to refund. The wallet charges per delivered meal, so a skipped day is simply never charged.
You can price how you like, but most kitchens find per-delivery wallet charging kills the month-end adjustment fight, which is why we lead with it.
Yes. Different items on different weekdays is one subscription, and the daily count splits by dish so the kitchen knows what to cook.
Print the runsheet before the round as a backup, finish on paper, and update the records when you are back online.
Short, practical, and no filler. Leave any time.