Skip to main content
GullySystem
Hospitality

Stock Tracking and Alerts for Restaurants

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.

Vegetables, meat, oil, spices and dairy are counted in the store and the cold room. An alert fires when onions or chicken run low, and the store keeper orders before the evening rush. Expiring stock is listed.

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.
Restaurants

How the business operates.

Most kitchens already have a decent POS for billing and KOTs. The trouble starts after the bill is printed.

Recipe cards read against sales

Give every menu item its recipe and portion. Rice, chicken and oil issued from the store can then be read against each plate sold.

Store indents and kitchen issues

Raise the kitchen’s indent, issue against it, and keep store counts, so what left the store can be read against what was sold.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Menu, portions and recipe cards. Hold sections, dishes, half and full portions, rates by order type and the recipe behind each dish, so the kitchen and the counter read one menu.
  • Table plan and dine-in orders. Lay out floors, tables and covers, open an order against a table, add items through the meal and move or merge tables as guests shift.
  • Kitchen tickets (KOT) and order status. Send each item to the station that cooks it, show what is pending at the pass and mark dishes ready, served or cancelled.
  • Counter and parcel orders. Take token orders at a counter, record parcel charges and packing, and bill without a table being involved at all.

Operational bottlenecks to check

Food cost is a guess

Recipe cards are not linked to sales, so you cannot tell whether the rice dish margin fell because chicken went up or because the portion grew. The owner simply guesses.

Platform payouts do not add up

Commission, ad spend, promotions and cancellations sit inside one weekly statement, and a short payment on a handful of orders goes unnoticed.

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. Order taken

    A guest is seated at a table, or orders at the counter, or the order arrives from a delivery platform. Items, portions and any instruction go on the order.

  2. 2. Kitchen ticket

    The order prints or appears at the station that cooks it. Starters, main course, grill and beverages reach their own stations with the table number on each ticket.

  3. 3. Serving and packing

    Each dish is marked ready and served, or packed for a parcel or rider. Items added later in the meal join the same table order.

  4. 4. Bill and payment

    The table bill carries dishes, taxes and any service charge the restaurant applies. Payment is taken in cash, by card, by mobile wallet, or collected by the platform.

  5. 5. Day close

    At the end of the shift the collections are counted against the bills. Store issue, wastage and complimentary dishes are entered before the day is closed.

  6. 6. Follow-up

    Guests who gave a number can be sent an offer or a booking reminder by WhatsApp. Feedback given at the table is kept against the visit.

Industry reports to connect with

  • Sales by dish, section and daypart
  • Dine-in, parcel and delivery platform shares
  • Kitchen ticket times by station
  • Store issue read against dishes sold

Questions before implementation.

When should restaurants 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