Restaurant & POS

POS (cashier screen)

Route: Restaurant › POS — /rest/pos (full-screen kiosk)

Purpose: the main order-taking screen, built for fast touch. Use it for every sale: dine-in tickets sent to the kitchen, takeaway sales paid on the spot, and delivery orders tied to a customer. It runs full-screen (kiosk); the cashier leaves only via the Logout button on the bottom bar.

Screen layout

Order types and what each one needs

The modifiers dialog

Tapping an item that has modifier groups opens a chooser before it lands in the cart:

• A group marked Required (min ≥ 1) must have a selection — Add to order refuses otherwise.
• A group showing Choose up to N caps the selections; in a single-choice group, tapping another option replaces the previous one.
• Options with a surcharge show +amount; the button’s price updates live (item price + selected surcharges).
• The same item with different modifier combinations makes separate cart lines.

Discounts (permission-governed)

1. With items in the cart, tap Discount on the toolbar.
2. Pick a preset chip: 5% · 10% · 15% · 25% · Comp 100% (Comp = free of charge).
3. A discount / comp reason becomes mandatory — pick a preset (hospitality, staff, customer complaint, marketing offer, management comp) or type your own. The order cannot be placed without it.
4. If your user lacks the discount authority, placing the order returns “Manager approval required” — a manager types their username and password in the dialog and the order goes through. The approval is recorded with the order.

VAT is scaled down in proportion to the discount, so tax is charged on what is actually paid.

The “More” menu (order attributes)

Hold, recall, and adding items to an open ticket

An order saved without payment (Hold or Send to kitchen) keeps status Open. Recall it into the POS from the Orders screen (recall icon), or by tapping its table on the floor plan. The recall dialog shows the ticket and offers actions by status:

Add items (append mode): a banner shows “Adding to ORD-xxxxx”, the ticket’s existing items are listed read-only with the current total, and the cart collects only the new items. The totals strip shows the new-items total and the order total after adding. Tap Add to order to save (new lines also print to the kitchen), or the × on the banner to leave without saving. Order-level discount and “More” attributes are hidden while appending — they belong to the whole ticket, not to an append.

Split payment (several tenders, one ticket)

1. Tap Split (takeaway/delivery ticket with items in the cart).
2. Tap a payment method (the station cash box, banks/cards…) — it becomes the active tender.
3. Key its amount on the numpad. C clears, ⌫ backspaces, and the Remaining key fills the tender with everything still unpaid.
4. Repeat for the next method. Each tender can be removed with its ×. Amounts are capped so tenders never exceed the total.
5. Pay enables only when Remaining = 0.00 — the order is settled and posted with all tenders recorded.

Example — total 115.00: tap Card, key 80 → tap Cash, press Remaining → 35.00 fills in, remaining shows 0.00 → Pay.

The payment receipt dialog

After Pay, a thermal-style preview of the Simplified Tax Invoice opens. The preview scrolls while the buttons stay pinned at the bottom of the dialog. It shows: company logo and name, VAT No., city, order number/date/type, table, delivery customer (name, phone, address), waiter, guests, call name, every line as qty × unit price — modifiers, then subtotal, discount, service charge, extra charge, VAT, tip and the total, and the configurable footer line.

• Amount tendered — a cashier aid under the preview: type what the customer handed over and the change due is computed (tendered − total). It is not printed.
• When the print agent is up and the station has a network printer, the receipt prints automatically and the dialog notes “Printing to: <printer> (network printer)”. The Print button reprints; without an agent it opens the browser print dialog (80 mm layout).

Shifts: open, X-Report, cash movements, close

1. Open shift: with a station selected, tap Open shift and enter the opening float (cash). While a station is selected and no shift is open, selling is blocked — the open-shift dialog appears instead.
2. Cash movement (money-bill icon): record a Paid in (drawer top-up) or Paid out (supplies, bank deposit, petty expense) with an amount and a mandatory reason. Presets are offered.
3. X-Report (chart icon): the same shift summary read mid-shift, without closing — sales so far, payments breakdown and drawer expectation.
4. Close shift: requires the REST.Shifts.Close permission (otherwise the bar shows “Closing is a supervisor action”). Enter the counted cash physically in the drawer — the Z-report opens (and auto-prints to the network printer when the agent is up).

Offline mode

• The menu, tables, waiters and tenders are cached locally — the POS keeps rendering and selling if the server drops.
• Orders placed while disconnected are queued locally: a red badge shows “Offline — selling continues locally”; once the connection returns the badge turns amber (“Awaiting sync (n)”) and the queue sends automatically.
• Tap the badge to open the queue: each parked order shows type, items count, time and total, with Sync now and a per-order discard button. A client reference guarantees a replay never duplicates an order.

Worked example — a dine-in table, start to finish

1. Station CASH-01 selected, shift open. Tap Dine-in, choose table T-05 and waiter Ahmed.
2. Tap Grilled Chicken (27.00). The modifiers dialog opens — in the “Sauces” group pick Hot sauce +3.00 → Add to order. The line lands at 30.00; press + on the cart line → qty 2, line total 60.00.
3. Tap Family Salad (28.00) — no modifiers, added directly.
4. Totals: subtotal 88.00 · VAT 15% 13.20 · total 101.20. Tap Send to kitchen (the button shows 3 items and 101.20).
5. Order ORD-00045 is created with status Open: table T-05 turns red on the floor plan, the card appears on the kitchen display, and kitchen tickets print on the category printers.
6. The guests order a juice later: on the floor plan tap T-05 (or Orders → recall icon) → Add items → tap Orange Juice (12.00) → Add to order. New items 12.00 + 1.80 VAT = 13.80; order total after adding: 115.00.
7. The guests want to pay 60/40: Orders screen → split-bill icon on ORD-00045 → checks: 2 → assign the two chickens to check 1, the salad and juice to check 2. Live totals: check 1 69.00 (60%), check 2 46.00 (40%) → confirm. Check 1 stays as ORD-00045; check 2 becomes a new open order (e.g. ORD-00046).
8. Settle check 1: recall ORD-00045 → Pay → 69.00 goes to the station cash box and the receipt opens. The guest hands 70.00 — type it in Amount tendered → Change due 1.00.
9. Settle check 2 the same way: total 46.00, tendered 50.00 → change 4.00. Table T-05 turns green again.

Worked example — a shift day with a 500 float

1. 09:00 — pick station CASH-01 → Open shift → opening float 500.00. Shift SH-00012 shows in the shift bar.
2. 11:30 — buy kitchen supplies from the drawer: Cash movement → Paid out · 150.00 · reason “Buy supplies”.
3. 15:00 — X-Report to see sales so far. The drawer stays open.
4. 23:00 — the day ends with 42 orders: net sales 3,000.00 + VAT 450.00 = gross 3,450.00; payments: cash 2,150.00, card 1,300.00.
5. A supervisor taps Close shift and counts the drawer: 2,495.00.
6. The Z-report opens: expected cash = 500.00 (float) + 2,150.00 (cash sales) − 150.00 (paid out) = 2,500.00; counted 2,495.00 → variance −5.00 shown in red (a shortage). The report lists the payments breakdown and every cash movement with its reason, and auto-prints when the agent is connected.

FAQ

Kitchen display

Route: Restaurant › Kitchen — /rest/kitchen

Purpose: the cooks’ live queue. Every open order sent from the POS appears as a card; the kitchen works it, ticks lines off, and bumps the order when done. Runs on any networked screen or tablet — no printer needed. Refreshes itself every 15 seconds.

1. A new card appears (within at most 15 seconds of the POS sending it).
2. The cook ticks each line as it is plated.
3. Ready → the card disappears; the order number moves to the pickup board’s “Ready” column, and a delivery order shows the Ready badge on the dispatch board.

FAQ

Pickup board

Route: Restaurant › Pickup Board — /rest/pickup (customer-facing)

Purpose: a wall/kiosk screen customers watch while waiting. Two columns of big order numbers: Ready for pickup (green) and Preparing (amber), with the company name and a live clock in the header. Refreshes every 10 seconds; a number that just turned ready pulses to catch the eye.

• The big number is the numeric tail of the order number (ORD-00091 shows as 91).
• If a call name was set on the order, it shows under the number.
• “Ready” lists the orders the kitchen bumped in the last 30 minutes — collected orders drop off by themselves, no extra taps.

FAQ

Dispatch board (delivery)

Route: Restaurant › Dispatch Board — /rest/delivery

Purpose: the dispatcher’s screen. Three columns follow each delivery order’s life — Ready to dispatch → Out for delivery → Delivered — plus a driver strip on top that tracks each rider’s cash accountability in real time. Refreshes every 15 seconds. Driver records (code, name, phone, active) are managed in Delivery Drivers — /rest/drivers.

Worked example — a COD delivery, end to end

1. POS: order type Delivery → Delivery customer → type phone 0551234567; no match, so enter name “Mohammed Al-Harbi” and address “Al-Nakheel district, King Fahd St.” → Done (the customer is saved to the book with the order).
2. Add Margherita Pizza 35.00 and Cola 5.00 → subtotal 40.00 + VAT 6.00 = 46.00.
3. Cash on delivery → tap Hold (open). The order stays Open (unpaid) and its kitchen tickets print. (If the customer had already paid by card, you would tap Pay instead.)
4. The card appears in Ready to dispatch with the Preparing badge; when the kitchen bumps it, the badge flips to Ready.
5. Dispatch with driver → pick Saad. The card moves to Out for delivery; the strip shows Saad: 1 out, carrying 46.00.
6. The customer confirms receipt → tap Delivered. The card moves to Delivered showing the trip minutes; it is still unpaid, so Settle cash stays on it.
7. Saad returns and hands over 46.00 → tap Settle cash. The payment is booked at the till (journal posted), the badge turns Paid, and the strip shows Saad: carrying 0.00 · settled today 46.00.

FAQ

Orders

Route: Restaurant › Orders — /rest/orders

Purpose: the central log of every ticket. Columns: order no, date, type (Dine-in / Takeaway / Delivery), table, subtotal, VAT and total (with column sums), and status. Use the table’s filters to search by any column. Holders of REST.Orders.ViewAll get a My orders / All cashiers toggle; the all-cashiers view adds a Cashier column showing who created each ticket.

Row actions (by status)

Split bill (separate checks by item)

1. Tap the split-bill icon on an Open order.
2. Set the number of checks (2–6) with − / +.
3. Every line starts on check 1 — tap a check number next to each line to assign it. Live per-check totals show at the bottom.
4. Confirm (enabled once at least one line sits on a check other than 1). Check 1 stays on the original order; each other check becomes a new open order, each payable separately.

FAQ

Floor plan

Route: Restaurant › Floor Plan — /rest/floor

Purpose: the live state of the dining room. The header counts Free and Occupied tables (with a manual refresh button). Each tile shows the table name and seats; an occupied tile adds a running occupancy timer, the open order’s number and its current total.

• Tap a free (green) table → the POS opens with a new dine-in ticket pre-selected on that table.
• Tap an occupied (red) table → the POS opens with that table’s order recalled (add items / pay / cancel).

Table operations (buttons on an occupied tile)

FAQ

Menu (items, categories, modifiers)

Route: Restaurant › Menu Items / Categories / Modifier Groups

Purpose: everything the cashier sells is defined here — sections, dishes, and the option sets (modifiers) that pop up when ordering.

Menu categories — /rest/categories

Menu items — /rest/menu

Modifier groups — /rest/modifiers

FAQ

Operations setup: waiters, stations, printers

FAQ

How printing works

Purpose: understand which paper comes out of which printer, and why — before blaming the hardware.

Two printer roles

What prints when

The local print agent

• Browsers cannot open raw TCP connections, so a tiny KEMTOVA ERP Print Agent runs on the cashier PC (local address 127.0.0.1:18731) and relays print jobs straight to the network printers (IP:port) — no Windows print dialogs.
• The POS probes the agent about every 20 seconds — the printer icon next to the search box is green when connected.
• Agent down or no printer configured → receipts fall back to the browser print dialog (80 mm layout). Kitchen tickets require the agent — lines whose category resolves to no printer are skipped silently.
• One kitchen printer failing never blocks the other printers or the sale.

Permission-gated operations

Purpose: the sensitive POS actions and who may perform them. Anything money-negative (discounts, voids, refunds) is either permission-gated or requires an on-the-spot manager approval.

Troubleshooting