Requirements checklist
What to ask for when choosing software for tiffin services.
A checklist built from how tiffin services work, to print or save as a PDF and bring to any supplier meeting.
What the software should cover
Tick each one that matters to your business.
- Plans, pauses and skip dates
- Daily menu and kitchen count
- Packing list and rounds
- Delivery confirmation
- Box and deposit register
- Prepaid wallet and renewals
- Ingredient purchase list
Roles that need their own access
Who logs in, and what each person may see or change.
- For the owner
- For cooks
- At the packing counter
- For riders
- At the phone desk
Reports to ask for
Ask to see each one with your own sample data.
- Boxes cooked by dish and diet variant
- Deliveries by round, rider and slot
- Skipped and refused stops with reasons
- Wallet balances and plans ending this week
- Steel boxes and bags out, returned and missing
- Deposits held by subscriber
- Complaints by round and dish
Systems it may need to connect to
Note which ones you already run.
- WhatsApp or other messaging
- SMS
- Card and transfer payments
- Accounting export
- Label printer
Questions for any vendor
Put these to every supplier you are comparing.
- Can a pause arrive after cooking starts?
- How are diet variants shown?
- Does it plan delivery routes?
- Can prepaid meals carry over when a subscriber pauses?
- How are steel boxes tracked?
- Can we move our subscriber sheet in?
- Can subscribers see their own balance and history?
- Who owns the subscriber data?
- What does it cost?
- Is it needed under fifty boxes a day?
Where the work usually breaks today
Circle the ones you recognise. They set the order of the project.
- Late pauses become wasted food
- Diet variants are remembered, not recorded
- Rounds are built from memory
- Box returns and deposits drift
- Prepaid balances are unclear
Prefer to talk it through? See the tiffin services page.
