Skip to main content
GullySystem
Hospitality and food · Software for restaurants

Join sales, recipe cards, kitchen stock and aggregator payouts into one record.

Restaurants run on a POS, printed kitchen order tickets, two delivery-platform tablets and a store register, so food cost, wastage and the platform payout stay unclear. Our Restaurant Management System is the POS itself, with recipe cards, indents, purchases, platform orders and the day close in one record. Where you keep your current POS, a costing layer is built beside it as custom work.

Share your requirements
At a glance

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

What the kitchen used, what was bought, what the delivery platforms paid and what reached the accounting package are four records that rarely agree. Laying all four side by side is where the work starts.

How the work runs today

Orders arrive from the tables, the parcel counter and two delivery-platform tablets. Captains punch kitchen order tickets, the kitchen cooks from printed slips, and the cashier settles each bill by cash, card or mobile wallet.

By seven every morning the store keeper has issued vegetables, meat, oil and spices against the kitchen’s indent, and ordered more from suppliers on WhatsApp. Month-end stock is counted, and food cost is worked out in Excel, roughly, by the owner on a Sunday.

Delivery-platform payouts land weekly, after commission, ad spend, promotions and penalties. Accounts try to match them order by order, then push the month into the accounting package.

Where it breaks

What goes wrong for restaurants without a proper system.

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 his rate against what was agreed. The rate creeps up quietly.

What the software does

What we would build for restaurants.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

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.

Before you talk to a supplier

A requirements checklist for restaurants.

What to cover, which reports to ask for and what to put to every vendor, ready to print or save as a PDF.

Open the checklist
Ready product

A product already built for restaurants.

It is adapted to how your business works before it goes live, and anything your trade needs that it lacks is added then.

Restaurant Management System

Table and counter orders, kitchen tickets (KOT), menu and recipe stock, platform orders, POS billing with tax and day close for restaurants.

See the product
More products

Other products in the same sector as restaurants.

Solutions inside

The business modules restaurants use most.

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

All solutions by area

AI by department

Where AI can help restaurants.

Each one reads records you already keep, and a person approves every decision.

Plate by plate food cost reading

Store issues are set against recipe cards and plates sold, and the assistant explains whether a margin moved because an ingredient rose or a portion grew. It suggests which dishes to look at first. The owner or head chef decides whether to change a recipe, a portion or a price.

Platform payout mismatch flags

A weekly statement mixes commission, promotions, ad spend and cancellations. Matching each payout line to the bills behind it, the assistant points out orders that were paid short. The accounts person reviews the list, decides what to raise with the platform, and keeps the record.

Supplier rate creep alerts

Vegetable and grocery suppliers bill every week. Purchase entries are read against agreed rates and earlier bills, and the assistant lists items whose price has crept upward. The purchase manager decides whether to question the supplier, ask for quotes elsewhere or accept the change.

Void and complimentary pattern review

Complimentary rounds, staff meals and cancelled bills pile up on the shift report. Each is read by counter, shift and reason, so the assistant can surface patterns that look unusual. It does not accuse anyone. The manager looks at each case and decides what, if anything, to do.

Connections

Tools restaurants often connect.

Worldwide

Where we work with restaurants.

Services

The services behind it.

API and System Integration

Accounting software, WhatsApp, payment gateways, tax portals and your own apps sharing one set of numbers.

Learn more

Data Engineering and Business Intelligence

Dashboards that answer the owner’s Monday questions without anyone building an Excel sheet first.

Learn more

Business Process Automation

Approvals, reminders, follow-ups and reports that run on their own instead of on someone remembering.

Learn more

ERP, CRM and Business Software Implementation

One record of stock, orders, customers and accounts, set up so your team opens it every day.

Learn more

All our other services

Guides

Written for restaurants.

Practical notes on running the business, not product marketing.

Who Records What in a Restaurant: Owner, Captain, Kitchen, Store and Cashier

How record keeping splits across a restaurant’s captains, kitchen, store, cashier and owner, so food cost, wastage and collections can be read each day.

Learn more
How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, accounting reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Our work in this sector

Software we have built and run in this sector.

Published with the client’s agreement, with what was built and what changed.

All case studies
Paying guest accommodation

SAM Atithi Pavathi: bed-level occupancy as the source of truth

PG management software where allocation, rates and invoices are derived from bed-level occupancy and not maintained in parallel spreadsheets.

Read the case study
Common questions

Questions restaurants ask before they call.

Do we have to change our POS?

Not necessarily. Where your POS allows an export or an API, a costing and stock layer can be built beside it as custom work once its supplier confirms what it exposes. Our Restaurant Management System replaces the POS, billing and ticket printing itself.

Can it show us where a delivery platform short-paid?

The payout sits against each platform bill, so a short payment shows order by order. Naming each deduction takes extra work. Recovering the money is still your claim with the platform.

Is the inventory in our POS not good enough?

For one outlet with a short menu, often it is. Use what you already have first. This earns its place once you run a central kitchen or several outlets.

Can it handle a central kitchen supplying several outlets?

Yes. A central kitchen and its outlets share one menu and one stock view. How production moves out to each outlet is settled with you at set-up.

How is a restaurant back-office system quoted?

The parts chosen: recipe costing, store indents, purchases, delivery-platform reconciliation, wastage log and day close. Outlets, central kitchens, users and the point of sale you already run all matter. Opening stock lists must be entered. Your own bills are put on screen first, and the itemised quotation follows.

What should a restaurant gather before work starts?

Bring recipe cards, a store indent, supplier bills, a delivery-platform payout statement, a wastage note and a day-end sheet. Once those are in hand, the chef, store keeper, manager and accountant each give time to reply to questions and check screens.

If we move away, who owns the recipe and stock data?

The restaurant, and the code alongside it. Recipes, purchases and day-end figures export as ordinary files whenever you need them, so no part of the stock history stays locked inside the system. Whoever built the system keeps supporting it. GullySystem hosts, with another route open if you want one.

What happens after I share my requirements?

An engineer reads what you send and replies within one business day. We then look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough. You get a short written summary ordered by priority, with no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. That first review settles the scope, and the cost goes into a written proposal before any work starts.

In Bengaluru

Bengaluru areas with many restaurants.

Across India

Cities where restaurants are common.

Related

Related industries.

Category

Part of these wider groups.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements