How a café POS handles billing, GST and daily operations

An 11am order for two cold coffees and a sandwich should take about fifteen seconds to bill. In a lot of cafés it takes closer to a minute, because the person at the counter is toggling between a paper KOT pad, a calculator for the GST split, and a notebook for the day's cash count. None of those steps are hard on their own. Stacked together across two hundred bills a day, they're where the afternoon goes.

A café POS doesn't replace judgment — your staff still decide what to discount and when to comp a table. What it should do is collapse the mechanical parts of a shift — opening the till, billing, sending tickets to the kitchen, invoicing correctly, counting cash at the end — into steps that don't need a second person checking the math. Here's what that looks like across an actual day, from open to close.

Opening the till: starting a shift with a number you trust

Every shift should start with a declared cash float — say ₹2,000 in the drawer before the first bill. In a system with cash shift and drawer reconciliation built in, the person opening the counter logs that starting amount against their own staff login before taking a single order. It sounds like a formality, but it's the only thing that makes the day's closing count meaningful later — without a known starting number, a ₹300 shortfall at 10pm could be a billing error, a missed order, or just an open float nobody logged. With staff accounts and roles, that opening entry is tied to the person who did it, not to "the counter" in general, so if two people work the same shift on different logins, each one's cash movements stay separable.

Billing: the four hundred times a day part

This is where most of the shift actually lives. A table orders, a waiter or counter staff rings it up, and the bill needs to reflect exactly what was served — including the stuff that happens after the first tap. A customer adds a second lassi. Someone wants a discount because the espresso machine was slow that day. A table gets held because they're still deciding on dessert. POS billing that's actually built for a café (not adapted from a retail till) treats discounts and held orders as first-class actions, not workarounds — you don't need to void and rebill to fix a running order.

Waiter tableside quick-add matters here too. If a waiter can add items to an existing table's order from where they're standing instead of walking back to the counter, that's one less trip per addition, and on a busy Saturday that adds up to real minutes. And because everything writes to the same order in real time, the kitchen display system reflects the addition immediately — the kitchen isn't guessing whether "one more lassi" was actually rung in.

If an order needs to be cancelled outright — wrong table, duplicate entry, customer left — cancel with a reason keeps a record of why, rather than the order just disappearing. That record is what saves you from a confused conversation with a partner or auditor three weeks later about why Tuesday's sales don't match Tuesday's food cost.

GST invoicing without the mental math

Every bill that goes out to a dine-in or takeaway customer in India generally needs to be a proper tax invoice — GSTIN, tax breakup, sequential invoice number, the works. Doing that by hand on a calculator, per bill, is exactly the kind of task a POS should be doing invisibly in the background: it applies the right GST rate, generates the sequential invoice number, and hands you a digital receipt the customer can actually keep, without anyone at the counter opening a spreadsheet. If GST invoicing mechanics specifically are what you're trying to get right — rates, invoice numbering rules, what a compliant restaurant bill needs to contain — that's covered in more depth in GST billing for restaurants; this piece is about where that invoicing step sits inside the rest of the shift, not the compliance rules themselves.

The practical win during a live shift is speed: the invoice is correct the first time, so there's no reprint, no manual tax correction, no customer standing at the counter while someone recalculates a CGST/SGST split by hand.

Payments: cash, UPI, and not making the customer wait

A café's payment mix on a normal day is rarely one method. Customer UPI at the table, pay at counter for takeaway, some cash, and — if the café is on a plan with Razorpay switched on — a card or online payment option too. The bill shouldn't change shape depending on how someone's paying; the total and the GST invoice are the same regardless, and reconciling which payment method covered which bill at the end of the day is what actually varies. A café running its ordering through QR code ordering at the table has this partly solved already, since the payment method gets captured at the point the order is placed rather than reconstructed later from memory.

Reports through the day, not just at the end

A manager shouldn't have to wait for closing time to know whether the day is on track. Core reports that update in real time — sales so far, what's selling, what's sitting — let someone glance at a phone at 3pm and notice that the lunch thali sold out an hour early, or that a particular table has been "held" for forty minutes with no update. That's the difference between operational software and a system that's just a faster calculator: recommendations and live numbers turn the POS into something you check during the shift, not just something you close out of at night.

Closing the shift: cash reconciliation and the day's actual numbers

At close, the cash drawer should be counted against what the system says it should hold — the opening float, plus every cash bill rung up during the shift, minus any cash refunds. If those two numbers don't match, you want to know it that night, with the specific bills to check, not three days later when it's impossible to reconstruct. This is the other half of cash shift and drawer reconciliation: the opening declaration at the start of the day is what makes the closing count mean something.

For a small single-outlet café doing, say, 120 bills a day at an average ticket of ₹220, that's roughly ₹26,000 moving through the till daily across two or three payment methods. A ₹150 mismatch is easy to lose track of by hand and genuinely easy to spot when the system is doing the running total for you.

What this costs to run

None of the operational flow above needs a separate add-on — POS billing, KOT, the kitchen display system, GST invoicing, digital receipts, cash shift reconciliation, and core reports are part of the base experience on every KhaoPiyo plan, starting from the Starter plan at ₹999/month for one café and up to three staff. There's no hardware to buy — it runs in a browser on whatever device the counter already has, a thermal printer is optional, and KhaoPiyo doesn't take a commission on sales; it's a flat subscription. A café can also sign up and start billing for free before choosing a paid plan, which is a reasonable way to see whether the daily flow actually fits before committing to anything.

If you're comparing this against what you use today

Most other restaurant POS software in India can bill, print a KOT and produce a GST invoice — that part is table stakes. The difference in daily use shows up in whether discounts and held orders need a workaround, whether the cash count at close is a manual tally or a comparison against a system total, and whether a manager can see the day's numbers without waiting for it to end. If you're evaluating options generally rather than looking at KhaoPiyo specifically, how to choose restaurant POS software walks through the questions worth asking any vendor, and restaurant POS software cost in India breaks down what these systems actually cost once you look past the headline price.