Two jobs that share one order
The cashier (or QR ticket) captures items, variants, and discounts. GST — or a restaurant-specific tax name your admin defined — must calculate on that check according to the outlet’s tax profile. Separately, the kitchen needs a KOT: item, station, and special instructions. If those two views diverge, you either serve the wrong plate or you print a tax invoice that does not match what left the pass.
Paper KOTs are still common. They jam, they smudge, they get stacked under a board. A kitchen display system is the digital form of that ticket. GST does not live on the KDS; accuracy does. The POS is the system of record for both.
GST on the restaurant bill (software view)
- Tax is configuration, not a slogan. Rates, names, and whether an item is inclusive or exclusive should be admin-defined. “GST-ready” only means the engine can represent those rules — not that your filing is automatically correct.
- Outlet ≠ brand. A group with doors in two states may need different tax profiles. That is a multi-outlet operating-system problem, not a second POS SKU.
- Discounts and voids change the tax base. Who is allowed to discount at 9 p.m. is a permission design. A leaked void is both a cash-leakage and a tax-invoice problem.
- UPI and cards are tenders, not tax. Local payment methods belong on the India commercial page; they do not replace GST configuration.
Confirm current GST slabs and invoice fields with your advisor. Software pages go stale; statute does not wait for marketing copy.
KOT in an Indian kitchen
A typical QSR or dhaba line still thinks in KOTs: one chit per ticket or per station. Fine dining fires courses. Cafes split bar and pastry. The software question is whether the KOT is paper, a printer, or a KDS — and whether modifiers (less spicy, Jain, extra shot) survive from the till.
If you still print KOTs, you still need the POS to be fast and the printer reliable. If you move to KDS, you are not “going paperless for SEO.” You are replacing a failure mode: lost chits during the dinner rush. See the KDS explainer and the KDS product page.
Busy service: one sequence
- Order on POS or QR with modifiers.
- Tax engine applies the outlet profile on the check.
- Kitchen receives KOT/KDS immediately — not after the guest has paid, unless that is your model.
- Status (preparing / ready) can feed an order status display if you run tokens.
- Close: tenders, split if needed, day-end with void/discount visibility for the manager.
What to walk through on a demo
- Create two tax profiles (for example two outlet regions) and switch the till between them.
- Ring a combo with a discount and show the tax lines on the invoice preview.
- Send the same ticket to KDS with a modifier the cook cannot miss.
- Void an item after fire — what does the kitchen see, and who was allowed to void?
- If you have more than one door, show outlet vs group sales without a spreadsheet merge.
India list price and feature inclusion live on Vyfoo pricing for India. This page exists so that page does not have to double as a tax textbook.
Questions operators ask
Is restaurant GST the same as a KOT?
No. GST is a tax configuration on the bill. A KOT (kitchen order ticket) is how the line sees what to cook. They meet on the same order: items and modifiers must be right on both the tax invoice and the kitchen ticket.
Can one POS handle GST in different states?
A restaurant operating system should let tax names and rates be admin-defined per region, not hard-coded to one filing pattern. Confirm how you attach a tax profile to an outlet — especially if you have more than one GSTIN.
Does this page replace a CA or GST consultant?
No. Use it to evaluate restaurant software workflows. Filing, input tax credit, and composition vs regular registration are professional questions. Vyfoo provides configurable tax on bills; it is not a substitute for a tax advisor.