Skip to main content
GullySystem
Hospitality

Business solutions for Tiffin services

Explore software for work such as “A trial offer of a few meals, with a call afterwards”. Review each business function below, including when it fits and what to check before implementation.

Tiffin services

How the business operates.

A tiffin service sells a daily habit. Subscribers choose a plan, a diet and a delivery slot, and the kitchen cooks to that count before the first round leaves. A pause received at nine at night changes how much rice is cooked at five in the morning, and the cook has to know it. Dawn is the deadline.

Plans, pauses and skip dates

Hold each subscriber’s plan, meal type, slot and start date, with pauses, holidays and extra boxes entered up to the cut-off hour.

Daily menu and kitchen count

Set the menu for the day and read a count per dish and diet variant, which the cooks work from before the first round leaves.

Packing list and rounds

Group boxes into rounds with stops, slots and door notes, and print a packing list for each rider with bag labels.

Delivery confirmation

A rider marks every stop as delivered, skipped or refused and notes the empty box picked up. When a subscriber complains, the office opens that stop’s entry first.

Box and deposit register

Track steel boxes and bags issued, returned and lost per subscriber, with the deposit held and refunded.

Prepaid wallet and renewals

Run balances down by delivery, list plans near their last meal for the day’s calls, and record cash, transfer and card payments.

Ingredient purchase list

Raise buying lists for vegetables, grain, oil and cooking gas from the coming days’ counts, and log what the kitchen received.

Diet and allergy variant sheet

Every subscriber’s diet type, spice level and food allergies are recorded once on the profile. Kitchen staff see them on the packing sheet beside every box. Changes apply next cycle.

Delivery address and landmark book

Gate codes, floor numbers, landmarks and preferred drop points are kept per subscriber. New riders read them on their round list. Edits made by a regular rider reach the office the same evening.

Festival and holiday menu calendar

Special thali days, closed days and extra-charge menus are set on a calendar ahead of time. Subscribers receive a notice. The kitchen head sees the adjusted count before purchasing.

The records that hold the operation together.

  • Subscriber records. Keep address, door notes, diet notes, phone numbers and plan history for each subscriber and for every person eating, so a household of three can hold three different diets.
  • Plans and meal types. Define weekly, monthly and prepaid plans, lunch and dinner slots, vegetarian and non-vegetarian boxes, and add-ons such as extra rotis, parathas or curd.
  • Pauses, skips and holidays. Accept a pause, a skip or an extra box up to the cut-off, and carry the change into the next day’s count.
  • Daily menu and kitchen count. Set the day’s menu, whether khichdi, poha, pulao or a full thali, and read the count per dish and diet variant, with portion sizes, for the cooks.
  • Purchase and kitchen stock. Raise a buying list for vegetables, atta, ghee, oil and cooking gas from forward counts, and log receipts from the market.
  • Packing lists and labels. Print a packing list by round, with labels showing the name, slot, diet note and door instruction, and a separate count of lids and carriers sent out.
  • Rounds and rider sheets. Group stops into rounds, assign a rider and vehicle, and give each rider a sheet or phone view with the order of stops.
  • Delivery confirmation. Mark stops delivered, skipped or refused, with the time and a note, and answer a missing-box call from the record.

Operational bottlenecks to check

Late pauses become wasted food

A subscriber who pauses after the cook has started still shows on the count. The portion is made and packed. Nobody eats it.

Diet variants are remembered, not recorded

No onion, no garlic, a vegan box or a nut allergy note lives in one packer’s head. A new packer sends the standard box and the subscriber complains.

Rounds are built from memory

A rider knows the route by heart until falling ill. The substitute does not know which gate needs a call, which flat takes two boxes, or which office closes its door at half past twelve for a meeting.

Box returns and deposits drift

Steel boxes and carry bags go out daily. Few are logged on return. Deposits are refunded on a guess, and the stock of boxes shrinks.

Prepaid balances are unclear

A wallet topped up in cash, by transfer or at the door is tracked in a notebook. The subscriber and the owner quote different balances at renewal.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Sign-up

    A subscriber chooses a plan, meal type, diet notes and slot, gives the delivery address, and pays a deposit for the boxes. A record and a wallet are opened.

  2. 2. Cut-off

    Cut-off arrives. Pauses, skips and extra boxes are accepted up to the kitchen cut-off, after which tomorrow’s count is fixed, totalled by dish and diet tag, and shown to the cooks.

  3. 3. Cooking

    The cooks see the menu with the count per dish and diet variant, and the buying list for the coming days. Dal, sabzi and jeera rice quantities scale up.

  4. 4. Packing and rounds

    Boxes are packed by round and stop, with a label on each tier showing name, diet note and door instructions. Riders collect their sheet.

  5. 5. Delivery and collection

    Each stop is marked delivered, skipped or refused with a time, and the empty box from the previous day is ticked as returned or reported missing at the door.

  6. 6. Renewal

    The wallet runs down with each delivery. Subscribers whose plan is about to lapse appear on a call list, and the payment they make is entered against their own record.

Roles and responsibility boundaries.

For the owner

See boxes cooked and delivered, wallet balances, lapsed plans, box stock and complaints by round, and judge whether a new kitchen or an extra rider is justified yet.

For cooks

Read the day’s menu with the count per dish and diet, and the buying needs of the coming days, before the first gas burner is lit.

At the packing counter

Pack from the round list, check each label against the diet note, and hand every rider a sorted set of bags with the lids counted.

For riders

Follow the order of stops with door notes and slots, mark each box delivered, and tick the empty collected before riding on to the next gate.

At the phone desk

Take sign-ups, pauses and renewals, and see a subscriber’s plan, balance and recent deliveries on one screen while the caller is still on the line.

Reports your managers need.

  • Boxes cooked by dish and diet variant
  • Deliveries by round, rider and slot
  • Skipped and refused stops with reasons
  • Wallet balances and plans ending this week
  • Steel boxes and bags out, returned and missing
  • Deposits held by subscriber
  • Complaints by round and dish

Connections to scope

  • WhatsApp or other messaging
  • SMS
  • Email
  • Card and transfer payments
  • Accounting export
  • Label printer

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Plans, slots and diet variants

Monthly, weekly and trial plans sit beside lunch and dinner slots and vegetarian, egg, vegan or no-onion variants, each priced the way you price it today. The hour after which an order misses tomorrow’s kitchen sheet is set exactly as you run it, with a different cut-off for each kitchen if you have several.

Menu cycle

A weekly or fortnightly menu rotation is loaded, with festival-day specials and seasonal vegetables slotted in, so the kitchen count follows the day’s dishes.

Subscribers and balances migrated

Names, addresses, diet notes, wallet balances and box deposits arrive from your sheet or notebook, and your own staff check them before the first morning.

Rounds and riders

Each round is laid out stop by stop, with door notes and the rider who walks it, as your kitchen runs it now.

Hosting and changes

GullySystem hosts the system. Our staff make changes to plans, menus, rounds and label layouts when you ask, so nobody on the packing counter touches a setting.

Limitations to settle before implementation

  • A few regulars need only a notebook.
  • A restaurant with tables and a dine-in menu will find Restaurant Management System closer to its work, since orders there start at a table, not at a subscriber’s door.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • A trial offer of a few meals, with a call afterwards
  • A menu for the week shared before it starts
  • A WhatsApp number answered at fixed hours, with a message that says when you reply
  • A record of every customer: address, plan, payment, leave and end date
  • A waiting list for the months when the kitchen is full
  • Clear notes on festival days, holidays and how a stopped plan is refunded
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements