Restaurant Counter Handbook

01Signing in

The app decides which workspace to open from your account — you do not pick it.

1. Enter the email and password issued to you and sign in.
2. The app opens the restaurant workspace automatically. If your account is set up for a retail shop instead, you will get the retail workspace — that is an account setting, changed in the ERP by your owner, not on this screen.
3. The menu button at the top left opens the sidebar. It holds the three places you work: Table Management, Restaurant POS and Sales History, plus Logout.

02Opening a ticket

Every order belongs somewhere before it can hold items. Pick the destination first, then start adding.

The top row of the POS is the ticket row. On the left are the buttons that create a new ticket; after the divider are the tickets and tables that already exist.

Each press of Delivery opens a fresh numbered ticket — Delivery #1, Delivery #2 — so several riders can be out at once. The same is true of Pickup and each aggregator.

Tax works differently on aggregator orders

Menu prices uploaded to Swiggy, Zomato and your own ordering app already include GST. The app knows this and does not add CGST/SGST on top of those tickets. Dine-in, Delivery and Pickup have tax added at billing time as normal. You do not have to do anything — just do not expect the two to total the same way.

03Adding items

1. Make sure the right ticket is selected — its pill is highlighted, and the customer banner at the very top shows who the order is for.
2. Pick a category from the second row, then tap the dish.
3. If the dish comes in sizes, a size window opens. Choose small, medium or large — the price follows your choice.
4. Add-ons and a kitchen note can be attached to the item. Add-ons that carry a charge show their price on the chip, and that charge is added to the line.
5. Tap the cart to review the ticket before you send or bill it.

Tapping the same dish again adds another portion. To take one off, use the minus control — but read section 05 first, because whether that needs a passcode depends on whether the kitchen has already seen it.

Holding a ticket

HOLD CART parks the whole order so you can start another one, and NEXT ORDER leaves the ticket exactly as it is and jumps you to the next free table — nothing is billed, cleared or sent. Use NEXT ORDER when a table is still deciding and you want to serve someone else.

04Firing the kitchen

The KOT is the kitchen's copy. Sending it is what turns a typed list into food being cooked.

1. Open the cart and press PRINT KOT.
2. If more than one printer is set up, choose which one gets it.
3. The kitchen copy prints. The items on it are now marked as sent.

05The passcode rule

One rule, and it is about food that has already been cooked.

Where an item is partly sent — three ordered, two already fired — you can take the unsent one off freely. The passcode only appears when the next one you remove would come out of what the kitchen already has.

06Billing & payment

Print the bill for the guest

PRINT BILL prints the customer's copy. It does not close the sale — the ticket stays open and the table stays occupied. Use it when the guest asks for the bill and you are still waiting to be paid.

Close the sale

PLACE ORDER records the sale, frees the table and posts it to the ERP. Choose how the guest paid — CASH, UPI or CARD — before you press it.

Split across payment modes

When a table pays partly in cash and partly by card or UPI, use SPLIT. Type what came in through each mode; the window shows what is still outstanding as you type and only lets you finish when the parts add up to the total.

07Unpaid orders

Orders that went out before the money came in are held in a floating window so none of them is forgotten.

When a sale is completed without full payment, it goes into the pending list and a red PENDING PAYMENTS pill appears with a count. Tap it to open the list; tap it again to shrink it back out of the way while you serve.

1. Open the pending window and find the order — each row shows the ticket, the guest and the amount.
2. Press the mode the guest actually paid with: CASH, UPI, CARD, or SPLIT to divide it.
3. The sale is posted with that mode and drops off the list.

08Customer accounts

Regulars who settle later are tracked on an account, so the balance is always the app's answer and not a diary's.

Attach a customer to the ticket and the banner at the top of the POS shows their running balance. When an order is left PAY LATER on the account, the amount is added to what they owe; when they come in and pay, record it against the same account and the balance comes down.

09Table Management

The floor at a glance: what is occupied, how long it has been sitting, and what is waiting to be accepted.

Each card is a table or ticket, with a timer showing how long it has been running. That timer is the fastest way to spot a table that has been waiting too long.

Online orders arriving

Orders placed through your ordering app land here and sound the tone. Accept the order to start it, or REJECT ORDER if you cannot make it — rejecting asks for a reason so the customer is told something useful.

Actions on a table

• KOT & BILL — fire the kitchen and print the bill in one press.
• COMPLETE BILL — settle and close the table.
• MARK COMPLETED — close off a pickup or delivery that has gone out.
• SWAP — move a whole order from one table to another when guests change seats. Everything moves with it: items, KOT status and customer.
• NEW TABLE — add a table to the floor plan.

10Sales History

Every completed sale for the day, filterable by order type — dine-in, Delivery, Pickup, App Order, App Pickup and each aggregator — and by who rang it up.

• REPRINT — print a customer's copy again. Reprinting does not create a second sale.
• VOID — cancel a sale that should not have been taken. Needs the passcode, and the voided sale stays visible marked VOIDED rather than disappearing.
• SALESMAN COLLECTION — what each person has collected, for handover at shift end.
• RECEIVE PAYMENT — take money against a bill left on account.

11Cash & expenses

Small cash movements recorded as they happen, so the drawer matches the app at close.

Cash paid out of the till during service — vegetables, gas, a repair — is recorded as an expense. Cash put in is recorded as till cash. Both are cash-only by design: this is about what is physically in the drawer.

1. Open the expenses screen and choose DEDUCT FROM CASH for money going out, or ADD TO CASH for money going in.
2. Enter the amount and a short description of what it was for.
3. Enter the passcode to confirm.

Each entry is recorded against the person signed in, so the day's cash can be reconciled per operator. Entries made with no connection show PENDING SYNC and upload themselves later.

12Printers

Printers are set up once per device, in Printer Settings. Each entry needs three things:

• Name — what you will see when choosing where to send a KOT. Name it after the station: Kitchen, Tandoor, Bar, Counter.
• IP address — the address of the printer on the restaurant's network.
• Port — usually 9100 unless the installer told you otherwise.

With more than one printer set up, sending a KOT asks which station it is for. With one, it goes straight there.

13Offline & multi-device

When the internet drops

Keep serving. Orders, bills and expenses are stored on the device and marked PENDING SYNC. When the connection returns they upload on their own — you do not have to press anything, and you must not re-enter them. A sale that reached the server before the line dropped is recognised and will not be recorded twice.

Several devices on one floor

Tickets are shared between the devices on your network, so a table opened on the counter tablet appears on the waiter's device. Two people should still avoid billing the same table at the same moment — if one device has already billed it, the other will say so rather than taking the money twice.

14Sync & duplicates

A reply that never arrives is not the same as a payment that never landed. What the app does about that, and the one screen where you still have to look before you save a second time.

When you save a bill, an expense or a payment, the app sends it to the server and waits to be told it arrived. On a weak line the entry can reach the server and be written correctly while the reply is lost on the way back. From the app's side that looks exactly like a failure, so it sends the entry again.

Every entry carries a one-time reference, made on the device the moment you pressed save, and the server keeps it with the record. When the same reference turns up a second time the server answers already recorded and writes nothing new. That is why the app is allowed to retry on your behalf: a bad connection costs you time, not money.

A late sale never takes over an open ticket

Ticket names come round again — today's Pickup #1 is tomorrow's Pickup #1. When a sale that was queued offline finally uploads, the app checks whether that ticket still holds the same order before clearing it. If the name has since been reused for somebody else, the current order is left exactly where it is. You can keep working on a reused ticket while an older sale is still waiting to go up.

15Quick reference