Tiffin subscriptions that run themselves
Customers subscribe to breakfast, lunch or dinner once. Every day after that, their order is placed automatically and paid from their wallet. When they travel, they pause a day in one tap — and the kitchen count updates on its own.
Tiffin subscription management means a customer signs up once for the meals they want, and the system places and charges each day's order automatically. In TifTif, customers choose breakfast, lunch or dinner, pay from a prepaid wallet, and can pause or resume any single meal on any day up to that meal's cutoff.
- Meals
- Breakfast, lunch, dinner
- Charged
- Daily, from the wallet
- Pause
- Any meal, any day, before cutoff
- On pause
- Wallet refunded if already charged
Subscriptions without the spreadsheet
Orders place themselves
Each active subscription becomes that day's order automatically — nobody copies a list from WhatsApp each morning.
A calendar per customer
Customers see every day of the month: placed, delivered, paused or cancelled, meal by meal.
Pause any meal, any day
Away for lunch on Friday? One tap on that day pauses just that meal, up to the meal's cutoff.
Refund built in
If the day's order was already placed, pausing refunds the wallet immediately. No manual adjustment.
Resume just as easily
Changed plans? Resume the day and the order is placed in the next cycle.
Every subscription in one list
The admin panel shows every active and paused subscription, so you know tomorrow's load today.
A paused lunch, step by step
- Customer taps Friday → Lunch
- Pause
- Before the lunch cutoff?
- Yes — allowed
- Order already placed?
- Cancelled, wallet refunded
- Kitchen count
- Updated automatically
- Rider round
- Stop removed
A pause keeps a customer a cancel would lose
Customers rarely cancel a tiffin because they dislike the food. They cancel because they are travelling for a week and cannot be bothered to message you, then never restart.
Letting them pause the exact days they are away — without calling anyone — removes that reason to leave. Their subscription is still there when they are back, and the refund lands in their wallet, ready for the next meal.
- Pauses and resumes lock at each meal's cutoff, so your kitchen count is final before you cook
- The pause is recorded per day and per meal, not as a vague "on hold"
- If a pause cancels an order that was already placed, the customer is notified of the refund
From sign-up to daily delivery
-
1
Customer subscribes
Picks the meals and portion they want, and tops up the wallet.
-
2
Orders place daily
Each day's order is created and paid from the wallet automatically.
-
3
Kitchen gets the count
After the cutoff, the admin panel shows exactly how many of each meal to cook.
-
4
Rider delivers
Orders join the round for that meal, in the optimised order.
More of the platform
On this page
Can customers pause a single meal instead of the whole day?
Yes. Pauses are per meal and per day, so a customer can skip Friday's lunch and still get Friday's dinner.
Until when can a customer pause?
Until that meal's cutoff time, which you set in the super admin. After the cutoff the kitchen count is locked.
What happens if the wallet runs out?
An order is only placed when the wallet can pay for it. Customers get a "wallet running low" alert when their balance drops below a threshold, so they top up in time.
Can a customer cancel the subscription completely?
Yes, from the app, before the next cutoff. Any unused wallet balance stays in their wallet.