# Tifflo

> Tifflo is the operations desk for a tiffin kitchen. It tells the kitchen what to cook tonight, what to pack in the morning, and who has run out of meals — so the answer stops living in a WhatsApp group and in one person's head.

Tifflo is a multi-tenant web application used by the office side of a meal-subscription kitchen: the owner and the admin staff. It is not used by drivers and not used by end customers. It is currently a private pilot, taking on its first kitchens in the Greater Toronto Area, Canada. Tifflo is free for pilot kitchens; there is no published price and no billing in the product yet.

Contact: mail@shaheem.dev
Apply: https://tifflo.app/#apply (a short form; there is no self-serve signup — each pilot kitchen is set up by hand, usually within one to two business days)

## Who it is for

Owner-operated tiffin and home-meal kitchens, typically with 20 to 100 standing subscribers on prepaid weekly or monthly plans, currently run on WhatsApp plus a notebook or a spreadsheet. Kitchens delivering within a tight radius, where the packing list matters more than the route.

Kitchens delivering with one driver or the owner's own car get the most from it today; multi-driver routing is on the roadmap rather than in the product.

## What it does today

- **Prep** — the cook list for a date: every subscriber's meals aggregated into dish and quantity, split by meal period. Orders for a cook date are generated by pressing a button. The list is printable.
- **Deliveries** — the packing list for a date: one row per customer, per meal, with address. Each meal can be delivered, skipped or undone. Marking a meal delivered is what spends a meal credit.
- **Customers** — subscription lifecycle (pause, resume, cancel), payments recorded by staff, and a prepaid wallet. Starting a subscription mid-week pro-rates the term against the plan's own delivery days.
- **Menu** — dish catalogue, plans with pricing tiers, and a week × day × meal-period rotation editor. A rotation is either evergreen (loops forever) or dated (runs between two dates — the monthly-rewrite model). Both are modelled in one system.
- **Dashboard** — meals today with delivered/pending/skipped, cash collected this month against the same day-number last month, customers with four meals or fewer left, and the next cook date together with whether its orders exist yet.
- **Settings** — kitchen profile, timezone and prep timing, meal periods, dietary and plan tags.

Two things are unusual and worth naming:

- **The wallet counts meals, not money.** A customer has a number of meals remaining, not a dollar balance. A skip costs nothing. The balance cannot go below zero. Every payment, delivery, skip, refund and manual correction is a permanent ledger row with a date and the staff member who made it; corrections require a reason.
- **Both menu models coexist.** An evergreen looping rotation and a menu rewritten every month are the same kind of object with a different mode, so a kitchen does not have to bend its menu to fit the software.

## Not built yet

Stated plainly so nobody is surprised in a demo. These are absences in the current build, not permanent design decisions — Tifflo is being built toward covering the whole tiffin operation.

- WhatsApp notifications. Today customers message the kitchen as they always have, and staff enter the change into Tifflo by hand. Tifflo is the record, not the messenger.
- Delivery routing and route optimisation, and any map view.
- A driver app or driver login. Deliveries are marked by whoever holds the packing list.
- Scheduled or overnight processing. Order generation is a manual action; the dashboard shows whether the next cook date's orders exist.
- Customer self-service. Customers have no login, no app and no portal, and are not asked to install anything.
- Online payments. Payments are recorded by staff after the fact.
- Data export beyond browser print, and analytics beyond the dashboard tiles.
- A general audit log. Money and meal movements are attributed; other actions are not yet.
- Self-serve signup. Kitchens are created and configured by hand, on purpose, during the pilot.

## What is being built next

In build order: driver logins and a driver view; WhatsApp notifications; scheduled order generation; route planning. Pilot kitchens influence that order. No dates are published.

## Getting started

There is no self-serve trial. A pilot starts with a conversation, then a hand migration: the kitchen's dishes, plans, menu cycle and current subscriber balances are entered together, the switch happens at a menu-cycle boundary rather than mid-cycle, and the first week runs in parallel against the kitchen's own records.

Email mail@shaheem.dev to start that conversation.