Restaurant, Tea Shop, Bakery & Bar

For any food business: a restaurant or hotel with table service, a cloud kitchen, a tea shop over a fast counter, a cake shop, or a bar. Dine-in orders are taken at the table and printed as KOTs to the kitchen; takeaway and delivery bill at the counter; the kitchen display shows what to cook next; the register opens and closes in shifts.

Trade presets: Restaurant / Hotel (food.restaurant), Cloud Kitchen / Takeaway (food.cloudKitchen), Tea Shop (food.teaShop), Cake Shop / Bakery (food.bakery), Bar / Wine Shop (food.bar). Business category 20 - every food and drink trade shares one category, and the preset carries what separates a bar from a bakery.

Where it is in the app

Waiters can take orders on their own phones with the SKS Waiter app connected to the shop's local server; the same table screen is also under Sales > Waiter POS on the POS page for other categories that serve food. See Companion Apps.

Service flow

flowchart TD
    subgraph Dine["Dine-in"]
        T[Tables / Captain: tap a table] --> O[Order: menu items · add-ons · notes]
        O --> K[KOT printed to kitchen station]
        O --> OH[(The table’s open order)]
        OH --> KDS[Kitchen Display: cooking timer · bump when ready]
        O -->|more rounds| O
        O --> B[Bill the table
merge · split · discount]
        B --> S[(Counter sale voucher)]
    end
    subgraph Take["Takeaway / delivery"]
        C[Takeaway / Counter] --> C1[Items · parcel charge · token no]
        C1 --> S
        C1 --> K
    end
    R[Shift / Register: open float] --> Dine & Take
    S --> R2[Day close: count · variance]
    P[Kitchen Purchases] --> ST[(Stock: ingredients)]
    ST -.->|recipe / raw to finished| M[Menu Items]

Screens

Tables / Captain

The dining floor by room: free, occupied, billed. Tap a table to take or add to its order; items print as KOTs to the kitchen printer of their group (kitchen, bar, tandoor). Move or merge tables, and bill from the table when the guests ask.

Kitchen (KDS)

Live orders across tables with elapsed cooking timers, item notes and add-ons, and one-tap bump actions per station. Run it on a kitchen tablet or TV.

Takeaway / Counter

The counter sale with a token number, parcel or delivery charge, and the delivery address when needed. Cloud kitchens live here entirely.

Dining Layout

Rooms and tables: names, seats, order. Add a table from the quick action when the floor grows.

Shift / Register

Open the register with a float, close it with a count; the variance against expected cash is kept per shift. See Shifts.

Menu Items and Add-on Groups

Menu items are products with a food type (veg / non-veg), KOT group and printer, and an availability schedule. Add-on groups (toppings, sizes, extras) attach to items with min/max selections and print on the KOT. Ingredient items and raw-to-finished conversions track kitchen stock when you want it.

Purchases and staff

Kitchen Purchases buys ingredients from vendors (Advanced plan). Waiters are staff contacts; attendance is marked from the Management group.

Where the money lands

flowchart TD
    A[Dine-in table] --> D[Bill settled]
    B[Takeaway counter] --> D
    C[Delivery order] --> D
    D --> E{Tender}
    E -->|cash| F[Register drawer]
    E -->|UPI / card| G[UPI or POS account]
    E -->|aggregator| H[Receivable on the platform]
    F --> I[Shift close: count · variance]
    G & H --> J[Settlement into the bank]
    I & J --> K[Day Book · Profit and Loss]
    K --> L[Owner reads: covers · average bill · food cost]

Settings & permissions

Relevant settings: Settings > Master (add-on groups, dining rooms), Settings > Transaction (counter sale, token numbers, KOT), Settings > Invoice Print (KOT printer per group, bill layout), shifts under Transaction settings. Waiter and cashier permissions come from the ordinary sales and payment permissions.

Reports

Day Book, Expenses, Income, Profit & Loss under Reports; Sales Register, Sales by Product, Add-on Sales, Product Summary and the shift reconcile via the POS report menu.