Meal plan subscriptions that keep their own count

A tiffin subscription is not a magazine subscription. It changes constantly — someone is away next week, someone wants to move from five days to three, someone paused in March and has eleven meals left they would like to use. Every one of those changes has to land in tonight's cook count, or the count is fiction.

That is the actual problem this solves. Not billing — counting.

Plans that match how tiffin is really sold

Kitchens sell in three shapes and Tiffinware supports all of them: a weekly plan, a monthly plan, or a fixed number of meals to be used whenever. That third one is the awkward case most software cannot express, and it is extremely common — customers buy twenty meals and eat them across six weeks.

Plans carry their own weekly menu, so a veg plan and a non-veg plan can run different rotations without you maintaining two systems. Customers can hold more than one plan at once — lunch and dinner, or one for themselves and one for a parent.

Pauses and skips, without a recount

Customers pause for a holiday and skip individual days. Both flow in from the customer portal or get recorded by you, and both are counted automatically at your cutoff — the point each day where the count locks and the cook sheet is generated.

Meals are not lost to a skip. They stay on the subscription, which is what customers expect and what most spreadsheets get wrong.

Switching plans mid-cycle

Someone on a monthly plan wants to move to weekly, three weeks in. This is the change that generates the most awkward WhatsApp negotiation in a tiffin business, because it needs arithmetic nobody wants to do in a chat window.

Tiffinware computes the credit for unused meals and applies it to the new plan. The customer sees the number, you see the number, and nobody is negotiating from memory.

Wallet credit that behaves like money

Credit from a switch, a refund or a goodwill gesture lands in a spendable wallet on the customer's account. It carries across plans rather than being locked to the one it came from, and it is drawn down automatically on the next purchase.

Credits can carry an expiry date, so a wallet balance does not become an open-ended liability sitting on your books forever.

Renewals you see coming

Renewals run automatically for customers with a card on file. For everyone else — which in a Canadian tiffin business is most people, paying by Interac e-transfer — the renewals and revenue at risk report shows what is due, what is overdue, who is cancelling and who is running low on credit.

That report is the difference between a renewal you saved with a three-day reminder and a subscription that lapsed because nobody noticed.

Add-ons per delivery

Extra rotis on Thursdays, a side of yogurt, a second portion when guests are over. Add-ons attach to an individual delivery rather than to the plan, so they show up on the packing list for that day and on the bill without altering the subscription.

See it working with sample data in the live demo — no signup. If you are still deciding what to charge, how to price a tiffin service has the arithmetic.