KhanaOS POS: A Complete Walkthrough — From First Login to End-of-Day Reports

Most restaurant software demos show you a sales deck. This article shows you the actual screens.

What follows is a walkthrough of KhanaOS POS from the moment you log in for the first time — through billing, payment, customer capture, staff management, inventory, and the end-of-day dashboard. No sales copy. No benchmark comparisons. Just a clear explanation of what each screen does and why it is built the way it is.

If you want to test any of this yourself, the free trial gives you full access with your own data for 7 days.

Two Logins — Owner and Staff

The first screen you encounter is the login. KhanaOS has two access modes: Owner and Staff.

This is not just a feature. It is a design philosophy.

Your biller — who may be a part-time employee, a family member, or a cashier you hired three months ago — does not need to see your monthly revenue figures, your profit margins, or your supplier costs. They need to see the billing screen and nothing else. Your manager needs reports but not the ability to change menu prices. You, as the owner, need everything.

[SCREENSHOT: login screen showing owner vs staff access selector]

KhanaOS enforces this through granular page-level permissions. When you create a staff login, you assign access module by module, using a simple checkbox interface. Billing — checked. Reports — unchecked. Menu management — unchecked. Dashboard — unchecked.

The result is that every person in your operation sees exactly what they need to do their job, and nothing they should not.

The Billing Screen — Built for Speed

The billing screen is the screen your staff will look at for eight to twelve hours a day. It was designed to be fast above everything else.

[SCREENSHOT: billing screen — category tabs on left, item grid, live cart on right]

The layout is a three-panel view:

Left panel — Categories: Your menu categories appear as tabs: Starters, Mains, Breads, Drinks, Desserts, Specials. Tapping a category loads the items for that category in the centre panel instantly — no loading state, no spinner.

Centre panel — Items: Each item shows the name, price, and a quick-add button. Items with variants (small/large, half/full, regular/special) expand inline to show the variant selector before adding to the cart. No extra screen. No navigation.

Right panel — Cart: Items add to the cart in real time. Quantities can be adjusted with + and − buttons. The GST calculation runs automatically — 5% for restaurants under the standard category, with the correct tax code applied based on item type. The cart shows the subtotal, CGST, SGST, and total.

[SCREENSHOT: cart panel with GST breakdown]

A bill can be generated in under 15 seconds from opening the screen. In our training sessions, most staff achieve this by the end of the first hour.

KOT printing is built in. When an order is placed, the Kitchen Order Ticket prints automatically to the kitchen printer — without any extra step from the biller. The biller places the order; the kitchen receives it. The two workflows are synchronised and independent.

Customer Capture — The Database That Builds Itself

When a customer pays, KhanaOS optionally prompts for a phone number. Most systems make this a separate step — a form, a loyalty card, a separate app. KhanaOS makes it part of the billing flow.

[SCREENSHOT: phone number entry during checkout]

The phone number is enough. KhanaOS records the visit, the items ordered, the spend, and the date. Over time — without any additional action from your staff — you build a customer database that knows:

• How many times each customer has visited
• Their total lifetime spend
• Their most ordered items
• Their average order value
• How many days since their last visit

The database builds itself. No separate step. No form. Just billing.

When a repeat customer's number is entered, their profile appears automatically — name (if previously captured), visit count, and any applicable loyalty tier. A returning Gold customer sees a "Welcome back, Priya" acknowledgement on the screen. It takes one second and costs nothing.

This data becomes the foundation for re-engagement campaigns, birthday outreach, and win-back messaging — features that are part of MehmaanOS, the guest relationship management layer launching later this year.

Payment Collection — Every Mode, Split Payments

KhanaOS accepts every payment mode used in Indian food service today.

[SCREENSHOT: payment screen with all modes visible]

• Cash — with change calculation built in
• UPI — QR code displayed on screen; payment confirmation received via webhook
• Card — integrated with major POS hardware; swipe/tap/insert all supported
• Zomato / Swiggy wallet — aggregator wallet settlement recorded for reconciliation
• Credit (house account) — for regular customers with running tabs
• Complimentary — for staff meals, owner guests, or spoilage write-offs, tracked separately

Split payments are fully supported. A bill of ₹1,840 can be paid ₹1,000 by card and ₹840 by UPI. This is a common scenario — two people splitting a bill using different payment methods — and it is handled in a single transaction. No workarounds. No re-ringing.

Staff Management and Access Control

The Staff module in KhanaOS handles both operational access and performance tracking.

[SCREENSHOT: staff list with active/inactive status and role badges]

Creating a staff member takes about two minutes: name, phone number, role, and permissions. Permissions are set page by page, checkbox by checkbox. The permission structure mirrors the navigation — if a staff member cannot see a page in the menu, they cannot access it, even if they know the URL.

Role templates speed this up for common configurations:

• Biller: Billing screen only
• Manager: Billing + Reports + Menu management (no financials)
• Kitchen: KOT display only (for kitchen display systems)
• Owner: Full access

Custom roles can be created for any configuration outside these defaults.

Staff-wise performance tracking runs automatically. Every bill is attributed to the logged-in staff member. The reports module shows, for any date range, how many bills each staff member processed, total revenue billed, average order value, and — where applicable — upsell rate (the frequency with which add-on items appear on their bills).

This is not a surveillance tool. It is a coaching tool. A staff member whose average order value is consistently 20% below the team average may not be aware that asking "would you like a dessert?" once per table is worth approximately ₹2,400 per week in additional revenue.

Menu Management

The Menu module is where you build and maintain your item catalogue.

[SCREENSHOT: menu management screen with category list and item editor]

Categories are created and ordered by drag-and-drop. The order on the menu management screen matches the order on the billing screen — what you see in the back end is what your biller sees.

Items each have:

• Name and description
• Category assignment
• Base price
• Variant groups (optional): size, preparation method, or any other dimension
• Applicable taxes (auto-populated based on HSN code)
• Image (optional — uploaded directly from the device)
• Available / unavailable toggle (for 86'ing an item mid-service without removing it)

Variant pricing handles the most common edge cases cleanly. A Lassi might be ₹80 (regular) and ₹120 (large). A Paneer Tikka might be ₹280 (half plate) and ₹480 (full plate). Variants are set up once and appear correctly on the billing screen, the KOT, and all reports.

Bulk price updates — useful when a supplier price change affects an entire category — can be applied as a percentage increase across all items in a category, with individual items excluded as needed.

Inventory and Recipe Linking

Inventory tracking in KhanaOS operates at two levels.

[SCREENSHOT: inventory dashboard showing current stock levels with low-stock alerts]

Level 1 — Item-level tracking: For packaged goods (bottled drinks, packaged snacks), each sale deducts one unit from stock. Reorder alerts trigger when stock falls below a threshold you set. This is the simplest configuration and works for most QSRs and cafés.

Level 2 — Recipe-linked tracking: For kitchen-prepared items, you link each menu item to a recipe — a list of ingredients and quantities. From the moment a recipe is linked, every sale automatically adjusts stock levels for every ingredient in that recipe.

Sell one Mutton Biryani: 300g mutton, 200g basmati rice, 15g spices, 20ml ghee are deducted from your ingredient stock. No manual entry. No end-of-day stocktake required for those items.

Wastage recording is a separate entry — any ingredient removed from stock that is not attached to a sale (spoilage, breakage, staff meals, tasting) is logged with a reason code. This keeps your theoretical stock (what the system expects) close to your physical stock (what is actually on the shelf), and the variance between the two is visible in the wastage report.

The Dashboard

The Dashboard is the first screen the owner sees after login. It is designed to answer the question: how is the restaurant doing right now?

[SCREENSHOT: owner dashboard with revenue tile, margin tile, orders tile, top item card]

The default view shows:

• Today's revenue — updated in real time as bills are raised
• Today's margin — if recipes are linked, this is the blended food cost % for the day's sales
• Orders today — total bill count
• Top item today — the highest-selling item by quantity, with portion count
• Revenue vs yesterday — a simple comparison that tells you whether today is tracking above or below the previous day at the same time

Below the summary tiles: a revenue sparkline showing hourly billing through the day, useful for identifying peak and trough periods, and an alert feed — any cost threshold breaches, low stock warnings, or system notifications.

The dashboard is read-only. It shows. It does not ask you to do anything. The operational decisions stay with you.

Reports

The Reports module covers everything from a single shift to a full financial year.

[SCREENSHOT: reports screen with date range picker and report type selector]

Available reports:

• Sales Report — total revenue, discount applied, GST collected, net revenue, by date or date range
• Item-wise Report — quantity sold and revenue for every item, ranked by volume or revenue
• Category-wise Report — the same view at category level — useful for understanding whether the dinner rush is being driven by mains or beverages
• Staff-wise Report — bills processed, revenue attributed, average order value, per staff member
• Payment mode Report — breakdown of cash, UPI, card, and other modes for reconciliation
• Wastage Report — all wastage entries with reason codes and cost impact
• P&L Summary — revenue minus ingredient cost (if recipes linked) minus entered fixed costs, giving a gross margin figure for the period

All reports can be exported as CSV or PDF. The PDF format is print-ready — useful for weekly reviews with a manager or accountant.

Who Is KhanaOS Built For?

KhanaOS is designed for food businesses with 1 to 50 outlets operating in the Indian market.

It is a particularly strong fit for:

Cafés and coffee shops: The billing speed and variant handling make it effective for high-volume, low-complexity ordering. The customer capture feature works well in café environments where regulars are a significant part of revenue.

Ice cream parlours and dessert bars: Multiple sizes, flavour combinations, and toppings are handled cleanly through the variant system. Stock deduction for scoops and portions works without manual tracking.

Casual dining restaurants: The full feature set — KOT printing, table management, recipe-linked inventory, MarginMind™ integration — is designed for the operational complexity of a 30–80 cover casual dining restaurant.

Cloud kitchens: Online order integration, multiple-outlet management from a single dashboard, and robust reporting make KhanaOS well-suited to multi-brand cloud kitchen operations.

QSRs and kiosks: The billing-only configuration with a single staff login and minimal permissions works well for fast counter service.

KhanaOS is not designed for enterprise hotel chains, stadium concessions, or operations that require deep integration with property management systems. For those environments, the software complexity requirements are different.

FAQ

How long does setup take?

Most restaurants are fully set up and billing on KhanaOS within 2 hours of signing up. The KhanaOS onboarding team handles the menu upload if you share it in any format — PDF, photo, WhatsApp message. You do not need to type 130 items yourself.

Does KhanaOS work without internet?

Yes. KhanaOS has an offline mode that allows billing to continue when connectivity drops. Bills raised offline sync to the cloud automatically when connectivity is restored. No data is lost. This is critical for restaurants in areas with unreliable connectivity, or for peak-hour situations where network congestion can cause drops.

Can I run KhanaOS on a tablet?

Yes. KhanaOS runs on Android tablets (7-inch and above recommended), iPads, Windows POS hardware, and any modern browser. Most restaurants run it on a 10-inch Android tablet with a Bluetooth printer. Hardware is not bundled — you buy what you have or what we recommend.

What happens to my data if I stop using KhanaOS?

Your data is yours. On request, a full export of all your transaction data, customer records, and menu configuration is provided in CSV format within 48 hours. There is no lock-in and no data retention fee.

Is KhanaOS GST-compliant?

Yes. KhanaOS applies the correct GST treatment based on item type and restaurant classification (AC vs non-AC, alcohol licence status). The GST report is formatted for direct reconciliation with your GSTR-1 filing. For specific compliance questions, we recommend consulting your CA — KhanaOS is a billing tool, not a tax advisory service.