A customer travelling for three days should be able to understand how those days affect the bill. The answer depends on the agreed plan. A pay-per-delivered-meal plan, a fixed monthly subscription and a prepaid meal pack need different treatment. Decide the rule before accepting an order, then apply it consistently.
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.
Write a simple cancellation policy
Tell customers the cutoff time, how to request a cancellation and what happens after food preparation starts. For example: “Please request a lunch cancellation by the previous evening. Approved skipped meals are not charged under the per-meal plan.” This is an illustrative business policy, not a rule every tiffin operator must use.
Keep kitchen holidays separate from customer cancellations. If your kitchen does not supply a scheduled meal, record that exception rather than expecting the customer to notice it later.
Calculate the bill using the correct model
Under a per-meal plan, 26 scheduled lunches at ₹80 with three approved skips produce 23 chargeable lunches: 23 × ₹80 = ₹1,840.
Under a prepaid 20-meal pack, three skipped dates might leave three meals available for later use if that is the agreed policy. Do not both extend the meal balance and issue a cash credit for the same skip.
Under a fixed monthly plan, the agreement may define specific credits or no credit for late cancellation. Explain that term before signup and show any adjustments clearly on the statement.
Record the exception in DAM
DAM's existing daily-supply guide describes opening the recurring workflow, selecting the affected dates and using Set Item Delivery to switch delivery off. Review the resulting quantities and statement. For quantity changes, adjust the actual meal count rather than removing the entire day.
A longer pause and a single skipped date are different operations. After resuming a paused workflow, review the first expected delivery and any older generated documents. Do not assume changing a future schedule automatically corrects every historical invoice.
Reconcile before sharing the monthly bill
Compare the customer's cancellation messages with the daily record. A useful exception note includes the date, lunch or dinner, quantity, reason and agreed billing treatment. Share the calculation with the customer when resolving a disagreement.
Related: recurring setup, advance meal packs and billing disputes.
What if a cancellation arrives after the cutoff?
Apply the policy the customer accepted. Explain the charge and retain the request; avoid changing the rule only when a dispute occurs.
Can I credit a skipped meal twice by mistake?
Yes. Removing a delivery and entering a second adjustment can duplicate the credit. Recalculate the final balance before sharing it.
Try DAM with a sample skipped date before using the workflow for all customers.