Skip to main content
GullySystem
Hospitality

Business solutions for Restaurants

Explore software for work such as “Weekday dinner footfall”. Review each business function below, including when it fits and what to check before implementation.

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.

Purchases and supplier bills

Record each day’s purchases and supplier bills, with the balance owed per supplier. Checking each bill against agreed rates is added on request.

Delivery-platform reconciliation

Hold the platform payout against each bill. Platform statements are matched at day close. Splitting out commission, promotions, ad spend and penalties is a custom addition.

Wastage and spoilage log

Record spoiled or returned food by item and reason, ready for the Monday review.

Complimentary bills, voids and day close

Enter complimentary dishes, discounts with a reason and cancelled items before the day closes, alongside the cash, card and wallet totals.

Day-end figures for the accountant

Read sales and purchase figures by outlet. No accounting package connection comes out of the box. An export is priced once the ledger layout is settled.

Table reservations and waiting list

Phone bookings and walk-ins for a Saturday dinner are listed by party size and table, with a waiting list behind. The host seats the next party when a table frees. No-shows are marked.

Menu and price changes

Dishes, prices, add-ons and combo offers are set once and flow to the POS, the parcel counter and the delivery tablets. The manager sees which items are off today. Specials carry end dates.

Tips and staff meals

Card tips are pooled and shared out by shift, and staff meals are logged as a cost against the kitchen. The cashier sees the pool at day close. Shares are recorded per person.

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.
  • Delivery platform orders. Keep aggregator orders in the same order list as dine-in, with the platform name, its order number and the payout against each bill.
  • Table bookings and waiting list. Note bookings taken on the phone or on WhatsApp, hold the waiting list on a busy evening and seat guests in turn.
  • Kitchen stock and indents. Count provisions, vegetables and packing material in the store, issue them against kitchen indents and record wastage with a reason.
  • Supplier purchases and bills. Record the vegetable, grocery, dairy and meat purchases of each day, hold supplier bills and keep what is still owed to each supplier.

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.

Stock goes missing between store and kitchen

The register shows what was issued and never what was used, so wastage and pilferage look identical from the office.

Complimentary bills and voids go unquestioned

Complimentary rounds, staff food and cancelled bills are approved at the counter, and nobody reviews them against the shift until much later.

Supplier bills pile up unchecked

The vegetable supplier bills every week, and nobody compares that rate against what was agreed. The rate creeps up quietly.

Follow the work across teams.

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

  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.

Roles and responsibility boundaries.

For owners

Read sales by dish and daypart, the dine-in and delivery split, store issue against dishes sold, discounts given and collections by mode.

For captains and stewards

Open a table, punch items with portions and instructions, see what is still in the kitchen and call for the bill.

For the kitchen

See tickets at your station in the order they came, mark dishes ready and flag an item the kitchen has run out of.

For the cashier

Settle bills across cash, card, wallet and platform collections, print or send the bill and close the shift.

For kitchen store and purchase staff

Receive purchases, issue against kitchen indents, enter wastage and watch items that have fallen below their indent level.

Reports your managers need.

  • Sales by dish, section and daypart
  • Dine-in, parcel and delivery platform shares
  • Kitchen ticket times by station
  • Store issue read against dishes sold
  • Table occupancy and covers by session
  • Collections by cash, card, wallet and platform
  • Discounts, cancellations and wastage

Connections to scope

  • WhatsApp
  • SMS
  • Email
  • Card and mobile wallet payments
  • Thermal kitchen and bill printers
  • Delivery platform order feeds
  • Accounting export, scoped at set-up
  • Biometric attendance device

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.

Your menu, sections and rates

Dishes, portions, section order and the rates you charge for dine-in, parcel and platform orders are entered as your card reads today.

Floors, tables and counters

The table layout of each floor, the counters that bill and the names your staff use for them are set up before you go live.

Kitchen stations and printers

Which dishes print at the grill, the main range or the beverage counter follows how your kitchen is arranged.

Recipes and store issue

How finely a recipe is held, and whether issue is counted per dish or per day, is settled with you at set-up.

Hosting across outlets

GullySystem runs the hosting, so a second outlet and a central kitchen share one menu and one stock view. Our staff change rates and dishes when you ask.

Limitations to settle before implementation

  • A home kitchen sending a few orders a day over WhatsApp may find a notebook and bank transfers enough.
  • A caterer quoting by the plate for weddings and events will find Catering Management Software fits better.
  • A bakery selling cakes and savouries over a counter should look at the Bakery Management System instead.

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.

  • Weekday dinner footfall
  • Weekday lunch for nearby offices
  • Birthday and celebration bookings
  • Office team lunches and parties
  • Direct delivery and takeaway orders
  • Festival and seasonal menus
  • Sunday family lunch and buffets
  • New outlet launches
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