12 features your tiffin software must have: a checklist

Every tiffin software demo looks good for the first ten minutes. This checklist is for the next thirty: twelve features a meal-subscription business actually depends on, and how to test each one live instead of on a slide.

Customers and orders

1. Subscriptions that place their own orders

Each day’s order should be created automatically from the customer’s subscription. Test: ask how tomorrow’s order list is built. If the answer involves anyone clicking through customers, it is not automatic.

2. Pausing a single meal on a single day

Customers must be able to skip Friday lunch without touching Friday dinner — themselves, without messaging you. Test: pause one meal, then ask what happens to the money and to the kitchen count.

3. A prepaid wallet with automatic refunds

Customers top up once and each meal is debited; cancellations and pauses refund automatically. Test: cancel an order before its cutoff and watch the wallet balance.

4. Per-meal cutoffs with a countdown

Breakfast, lunch and dinner each need their own cutoff, visible to customers. Test: try to order after the cutoff. The system should move you to the next available day, not accept it.

Kitchen and delivery

5. Kitchen counts at the cutoff

Exact quantities per dish and portion size, final at the cutoff, split by delivery round. Test: ask to see tomorrow’s lunch count.

6. Route optimisation

Each rider’s stops ordered into the shortest round from your kitchen. Grouping by area is not the same thing. Test: ask them to plan three riders’ rounds live and show the stop order.

7. A rider app

Numbered stops, a route to each delivery, and one-tap status updates. Test: hand the rider app to someone who has never seen it and ask them to deliver a test order.

8. Live tracking for customers

The rider on a real road map with an ETA. Test: watch a test delivery from the customer’s side.

Running the business

9. Support tickets with refunds

Complaints handled in the app, resolved with a note and an optional refund in one step. Test: raise a ticket as a customer and resolve it as the admin.

10. Reports you will read

Revenue trend, orders per day, meal mix, rider performance and a tax summary. Test: ask which meal made the most money last month.

11. Roles and access

Staff should see only what they need, and removing someone should cut their access immediately — enforced on the server, not just hidden in the menu. Test: ask how access is enforced and what happens when a staff member leaves.

12. Your brand and your data

Your name on the apps and the store listing, and your data in accounts you control. Test: ask whose developer account publishes the app and where the database lives.

Bonus: questions about money safety

A prepaid wallet holds customers’ money. Ask how balances are changed — they should only move through checked server-side operations — and whether abuse cases such as negative quantities, self-applied discounts or fake payment confirmations have been tested. Ask about daily backups.

Use the checklist

TifTif does all twelve — see them on the features page, or book a demo and run this checklist on us. For pricing models and ownership questions, read the buyer’s guide.