A daily delivery register answers “what did we supply?” A monthly bill answers “what should this customer pay?” Keeping the first record clear makes the second easier. The register should identify the date, customer, lunch or dinner, planned quantity, actual quantity and exception reason.
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.
Use separate planned and actual quantities
A recurring order is useful for planning the kitchen, but an expected meal is not evidence of a completed supply. A family may request an extra portion; another customer may cancel before the cutoff. Record the change in the day's supply record rather than relying on a message that will be hard to find later.
A practical register could look like this:
| Date | Customer | Meal | Planned | Supplied | Note |
|---|---|---|---|---|---|
| 11 Oct | Meera | Lunch | 1 | 0 | Approved leave |
| 11 Oct | Amit | Lunch | 1 | 2 | Extra meal confirmed |
| 11 Oct | Kavita | Dinner | 1 | 1 | Supplied |
These are fictional entries. The supplied lunch total is two, not the planned total of two for a different combination of customers. Customer-level accuracy matters as much as the kitchen total.
Run three daily checks
Before cooking, confirm known skips and extra orders. Before dispatch, check customer, slot and quantity. After the round, reconcile unsuccessful deliveries and corrections. Decide who updates the record so the cook and delivery person do not both enter the same extra meal.
Use a short exception vocabulary: customer leave, kitchen closure, extra portion, failed delivery and correction. Keep private address details accessible only to people who need them for delivery.
Connect delivery records to DAM billing
DAM has daily delivery and recurring workflows. Use them to review meal quantities and exceptions before sharing statements. If your team uses a separate dispatch list, reconcile it with DAM's customer records each day. Do not describe the billing app as proof of rider delivery unless you have a confirmed delivery record.
When an owner corrects a date, check whether an invoice has already been generated and whether the customer received a statement. Correct the billing record consistently rather than only editing the kitchen list.
Related: daily recurring billing, skipped meals and billing disputes.
Should lunch and dinner use separate rows?
Yes when quantities, delivery times or prices can differ. One daily total can hide a cancelled lunch and an extra dinner.
Download DAM and compare one day's meal record with its generated charges.