Skip to main content
GullySystem
Hospitality

Stock Tracking and Alerts for Tiffin services

Record stock movements and flag items reaching configured levels.

Inventory Management

Does this function belong in your operation?

Use when the business holds physical stock or consumables requiring quantity control.

Goods are received, issued, transferred or counted.

Rice, atta, oil, vegetables and packing foil each carry a minimum level against the day’s cooking plan. A shortage alert reaches the kitchen head before the market run. Buying follows the real count.

Bring the records the workflow depends on.

  • Item and location list
  • Opening quantities
  • Reorder and movement rules

Outputs to check

  • Item-location balance register
  • Movement and count-adjustment history
  • Replenishment exception list

Follow the stock tracking and alerts workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Set opening stock

    Approve item-location quantities and tracking rules.

  2. 2. Record movements

    Capture authorised receipts, issues, sales and transfers.

  3. 3. Compare counts

    Investigate physical differences before adjustment.

  4. 4. Review thresholds

    List shortages using the appropriate item and location level.

  5. 5. Handover replenishment

    Send requirements to purchasing or production without treating an alert as an approved order.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Storekeeper

Issues material against a job, counts a rack on a slow afternoon, and answers for the difference. Every difference gets a name.

Counter staff

Checks recorded stock and location before confirming availability under the business's reservation rules.

Owner

Reads the alert list and the dead stock report, which is where the tied-up working capital sits.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Count differs from record

Investigate recent movements and approve an adjustment with the reason.

Negative balance attempted

Apply the agreed hold or exception rule and expose the cause.

Goods held for inspection

Keep them distinct from stock available for issue or sale.

Can this work independently?

Stock tracking can run from entered receipts and issues, but every physical movement needs a record. Purchase, sales, production and warehouse connections provide those movements. Reorder alerts signal a threshold; purchasing still decides quantity, supplier and approval.

Systems and records it connects with

  • Purchase order management: Authorised supplier commitments and open line balances.
  • Goods receipt: Counted, accepted and rejected supplier-delivery quantities.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Multi-outlet stock: Outlet quantities and acknowledged transfer movements.

Configure, test and introduce the workflow.

  • Show us the godown and the counters. A note lists the locations and the item groups.
  • Supply levels per item and place, or ask for suggestions from history. Balances and alerts then appear for trial. A count is taken and loaded as the opening balance. The team checks a sample against the shelf.
  • Each group practises receipts, issues and transfers. Short cards for the shelves follow. Alerts reach named people. A review once the opening season ends lists slow stock.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Movements reconcile with location balances.
  • Count adjustments retain approval.
  • Alerts use the correct item and location threshold.
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.

See the full industry workflow, reports and implementation plan →

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.

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.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  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.

Industry reports to connect with

  • 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

Questions before implementation.

When should tiffin services consider stock tracking and alerts?

Use when the business holds physical stock or consumables requiring quantity control. Goods are received, issued, transferred or counted.

What should we bring to the requirements discussion?

Bring anonymised examples of Item and location list; Opening quantities; Reorder and movement rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Record stock movements and flag items reaching configured levels. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Recorded balances depend on timely movement entries. Physical availability must be confirmed through the agreed count and reservation process.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Movements reconcile with location balances. Use this check when reviewing the first working version.

Talk to us

Discuss stock tracking and alerts for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

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