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

The POS says we sold well, but the kitchen stock tells a different story by Sunday night.

Restaurants run on a POS, printed KOTs, aggregator tablets and a store register, so food cost, wastage and Swiggy or Zomato payouts stay unclear. GullySystem works around the POS you already have, connecting sales, recipes, stock and accounts. It starts with a free technology audit of how your kitchen and counter run today.

At a glance

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

What was used in the kitchen, what was bought, what the aggregators actually paid, and what went into Tally are four separate records that rarely agree.

How the work runs today

Orders come from the tables, the takeaway counter and two aggregator tablets. Captains punch KOTs, the kitchen cooks from printed slips, and the cashier closes the bill in cash, UPI or card.

Every morning the store keeper issues vegetables, meat, oil and masalas to the kitchen from a register, and orders more from suppliers on WhatsApp. Month-end stock is counted, and food cost is worked out, roughly, in Excel.

Aggregator payouts arrive weekly after commissions, discounts and penalties. Accounts try to match them to orders and push the month’s sales into Tally.

Where it breaks

What goes wrong for restaurants without a proper system.

Food cost is a guess

Without recipes linked to sales, you can’t tell whether biryani margins fell because of chicken prices or because portions grew.

Aggregator payouts don’t add up

Commission, ad spend, discounts and cancellations are buried in weekly statements. Short payments are rarely caught.

Stock goes missing between store and kitchen

The register shows what was issued, not what was used. Wastage and pilferage look the same.

Supplier bills pile up unchecked

Vegetable and meat suppliers bill weekly. Nobody checks rates against the order, and the rates creep up.

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 costing linked to POS sales

Each menu item’s recipe, so every sale reduces ingredients and shows food cost by dish.

Store issue and kitchen stock

Issues to the kitchen logged by shift, with a daily closing count and variance against sales.

Purchase orders and supplier rates

Orders to suppliers with agreed rates, and bills checked against them before payment.

Aggregator reconciliation

Weekly payouts matched to orders, with commission, discounts and penalties split out.

Wastage log

Spoiled or returned food recorded by item and reason, for the weekly review.

Day-end to Tally

Sales by GST rate, payment mode and outlet posted to Tally each day.

How it works

How the work runs from Bengaluru for your city.

  1. 01

    The audit, by call

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

  2. 02

    A written proposal

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

  3. 03

    Build in short rounds

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

  4. 04

    Go-live, in person when it helps

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

  5. 05

    Support online

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

Common questions

Questions restaurants ask before they call.

Do we need to change our POS?

No. We connect to your POS where it allows export or an API, and build the costing and stock layer beside it.

Can it send the day’s sales to Tally?

Yes. Sales, GST and payment modes post to Tally daily, and purchases can follow the same route.

Isn’t a POS with inventory good enough?

For a single outlet with a short menu, often yes. Turn on your POS inventory first. Custom work helps when you run a central kitchen, several outlets or a large aggregator business.

Can it handle a central kitchen supplying several outlets?

Yes. Central kitchen production is sent to outlets as a stock transfer, and each outlet’s sales draw it down. You see food cost by outlet, not just for the whole business.

What happens in the free technology audit?

We 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 to start. You get a report ordered by priority, and there is 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. The audit 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.

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.

  • No obligation
  • We reply the same working day
  • Your details stay private

Your details are private and secure. Protected by reCAPTCHA.