Daily tiffin billing becomes difficult when lunch orders repeat but the quantities occasionally change. A recurring schedule saves repeated entry, while a daily review keeps the schedule aligned with actual supplies. Both parts matter: automation without exception handling can create a tidy but incorrect bill.
Watch the DAM demo
Tiffin Service & Daily Delivery: DAM App Full Tutorial
Watch DAM’s tiffin and daily-delivery tutorial to understand the app workflow alongside this guide. For planning topics such as pricing, menus and marketing, use the article’s examples; the video demonstrates the app rather than every business process.
Also watch: Daily subscription billing and monthly statements. This related tutorial uses milk and newspaper examples.
Explore more tutorials on the DAM YouTube channel.
Decide what each recurring schedule represents
Use a clearly named item such as “Lunch Tiffin” or “Dinner Tiffin.” Specify whether quantity means individual meals or a family pack. If one family pack serves four people, do not sometimes record one pack and sometimes record four meals under the same price.
Choose the correct start date. Starting a new customer from the first of the month when service began on the tenth can introduce charges for meals never supplied. Similarly, a weekday-only agreement should not become a seven-day schedule.
Create the schedule in DAM
The existing DAM recurring guide describes this workflow:
- Search for New Recurring and select the appropriate entry book.
- Select the customer and add the meal product or service.
- Enter the daily quantity and price.
- Choose the start date and frequency.
- Set an end date if the arrangement has a known finish.
- Create the recurring workflow and review its occurrences.
App labels can vary by version. The official recurring tutorial demonstrates the underlying daily-supply flow using milk and newspapers.
A worked lunch example
A customer receives two meals per weekday at ₹80 each. Five supplied days produce 10 meals and ₹800 of charges. On Wednesday the customer requests only one meal. The correct weekly quantity is nine, and the charge is ₹720. Adjust the day's quantity rather than recording an unrelated ₹80 discount without an explanation.
Prevent duplicates when adding old dates
Before generating past occurrences, check whether those dates already exist as manual invoices or delivery entries. Backfilling a recurring schedule and leaving the original manual bills can charge the customer twice. Compare date, customer, meal and quantity, not just invoice number.
If historical details are incomplete, a documented opening balance is often easier to reconcile than inventing a delivery history. Keep the customer’s confirmation with the migration record.
Review exceptions every day
Check extra meals, customer leave, kitchen holidays and failed deliveries. At month end, review the day-by-day quantities before producing a consolidated statement. Record customer payments separately; changing the schedule does not record money received.
Related: skip-day billing, delivery register and switching from a notebook.
Should lunch and dinner share one schedule?
Only when their prices, days and cancellation rules are identical and the record stays clear. Separate schedules are easier to understand when either meal varies.
Download DAM and pilot one recurring meal schedule.