Skip to main content
GullySystem
Hospitality · Tiffin Service Management Software

Subscriptions, daily count, packing, rounds and box returns, connected.

Manage a tiffin service in one system. Subscribers hold plans with a diet, a slot and a start date, and pauses are entered up to the kitchen cut-off. The day’s count by dish and diet goes to the cooks, the packing list goes to the counter, and each round goes to a rider. Deliveries, empty steel boxes and wallet balances close back into the same subscriber record, so a missing box or a lapsed plan is found by search.

Share your requirements
  • Plans, meals and diet variants keyed your way
  • Names, balances and deposits carried over
  • Menu and round edits done by our staff

Kitchens that send daily meals to offices, hostels and homes use this system, and our team prepares it around their menu and rounds. Owners, cooks, packers and riders work from it. Each subscriber record carries the plan, diet, slot and balance, and every delivery updates the kitchen count, the round sheet and the box register.

Where it breaks today

What goes wrong before the software.

Pauses arrive after cooking starts

A subscriber texts a pause at midnight. The cooks start the dal and jeera rice at dawn, and unless that message reaches the count a full tiffin gets cooked, packed and carried out for nobody.

Diet variants live in one person’s head

No onion, vegan, no garlic, a nut allergy note or a larger portion is remembered by the packer who has done it for years. A substitute packs the standard box.

Rounds exist only in the rider’s memory

Which gate needs a call, which office takes six boxes and which stop closes at noon is written nowhere, so every handover starts with a phone call. A sick rider takes the route with him.

Missed deliveries are argued, not checked

A subscriber says the box never came. The rider says he left it with the watchman at the gate, and with no stop-by-stop record the owner credits the meal just to end the call.

Boxes and deposits drift

Steel boxes, lids and cloth bags go out every day and return unevenly, with a lid missing here and a whole dabba carrier forgotten at an office there. Deposits are refunded on recollection. Stock falls unnoticed.

Plans lapse without a call

A prepaid plan ends on Tuesday. The box stops, and the subscriber assumed it renewed while the owner assumed the subscriber would ask, so a regular lunch customer goes quiet without a word.

How it runs

How the work flows through it, step by step.

  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.

Modules

What is inside.

Every module can be switched on, left out or changed to match how your team already works.

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.

Box and deposit register

Log steel boxes, lids and bags issued and returned per subscriber, with deposits held, refunded or kept, so a missing carrier is named before the next cycle begins.

Wallet and renewals

Run prepaid balances down per delivery, record cash, transfer and card payments, and list plans near expiry for the morning renewal call.

Complaints and feedback

Log a cold box, a wrong diet or a late round against the stop, the rider and the dish, so a pattern shows by round and by recipe.

Solutions inside

The business modules it is built from.

Each one is also available on its own, or inside a system built for you.

  • Subscription Billing

    The cycle’s charge is raised from the plan, delivered boxes draw the balance down, and plans near their last meal are listed for a renewal call.

  • Production Planning

    Tomorrow’s subscriber list becomes a count per dish and diet variant, so the cooks make what will be eaten and little else.

  • Client Portal

    A subscriber logs in to pause a week, skip a Friday or add a box, and the change reaches the kitchen count before the cut-off.

  • WhatsApp, SMS and Email Notifications

    A message goes to the subscriber when a round leaves and when the box is dropped, using the messaging channel the subscriber chose.

  • Stock Tracking and Alerts

    Rice, flour, oil, vegetables and cooking gas are counted against forward menus, and a low level raises a buying entry before the market run.

  • Vehicle and Trip Management

    Each round is a trip with a rider, a vehicle, a start time and an ordered list of stops, recorded as it is run.

  • Ticket Management

    A cold box or a wrong diet becomes a numbered complaint against the stop, rider and dish, with an owner and a reply.

  • Receipts Management

    Cash at the door, transfers and card payments are each receipted against the subscriber and added to the wallet balance.

Services

How we would put it in.

Setup, data migration, integrations and anything built on top.

Who uses it

One system, each person sees their part.

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

The numbers the owner asks for.

  • 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
Good fit

Who this is built for.

  • Home-style tiffin kitchens run by one family
  • Office lunch services with fixed corporate stops
  • Hostel mess and student meal subscriptions
  • Diet and fitness meal-plan kitchens
  • Weekly meal-prep businesses selling plans to households
  • Services with several kitchens or delivery bases
Honest answer

When it is not the right choice.

  • 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.
Made to fit

Adapted to your business before it goes live.

You are not handed a login and left to it. The product is set up around your records, your people and the tools you already use.

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.

Works alongside

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

Questions owners ask before a demo.

Can a pause arrive after cooking starts?

Only until the cut-off you choose. After that the day’s count is fixed, and a late change is recorded as a skipped box with a reason, so the wallet follows your own rule.

How are diet variants shown?

Each variant is a tag on the subscriber, like no onion or a nut allergy note, and the kitchen count totals by tag while the label repeats it.

Does it plan delivery routes?

It groups stops into rounds you define and orders them for the rider, using the sequence your riders already walk. Map-based route optimisation is not in the base product. It would be a separate quotation.

Can prepaid meals carry over when a subscriber pauses?

Yes. A prepaid plan counts meals delivered and not calendar days, so paused days leave the balance untouched, while plans sold by the calendar month follow whichever rule you set.

How are steel boxes tracked?

Each box issued is recorded against the subscriber with a deposit line, each empty collected is ticked at the stop, and the missing list is read off the register.

Can we move our subscriber sheet in?

Yes. Names, addresses, diet notes and wallet balances are loaded from your sheet, and your phone desk checks a sample of them before the first live morning.

Can subscribers see their own balance and history?

Yes. A login page or a message summary, whichever you choose, shows the plan, the balance, upcoming pauses and the last deliveries, so fewer calls reach the phone desk.

Who owns the subscriber data?

You do, and subscriber lists, wallet balances, deposit lines and delivery history can be handed to you as spreadsheets whenever you ask, in a layout named in the quotation.

What does it cost?

No price is shown here. The figure depends on kitchens, riders, subscribers and what is migrated, and your own menu and plans are shown in a demonstration before any proposal arrives.

Is it needed under fifty boxes a day?

Perhaps not yet. A sheet and a messaging group can hold that list until pauses and several delivery rounds begin to collide, and then it is worth sharing your requirements.

Wondering what it would cost? Share your requirements and an engineer will come back with a scope.

Industries

Businesses that use this.

Related

Related products.

Book a demo

See Tiffin Service Management Software with your own data.

Tell us how you run things today. We’ll show you the parts that matter to you and say plainly what would need changing.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements