Table service built around a floor map, station-routed kitchen tickets and durable print jobs that survive a printer going offline mid-service.
In a busy service the failure that hurts is a lost ticket: the table waited, the kitchen never knew, and nobody can prove what happened. Penahak queues every ticket on the server and a desktop app or cloud printer prints it. If a printer is off, the ticket waits and prints when it is back.
Not a feature list — the sequences your team runs day to day.
Everything here works on the same customers, products and books as the rest of Penahak.
These are not integrations between separate products. They are modules on one ledger, one party master and one product catalogue.
A diner staying with you can charge the bill to their room folio, with the outlet and session recorded on the line.
With recipe stock switched on, a posted bill takes each dish’s ingredients out of the branch’s default store.
Outlet bills post as sales invoices with their tax and payments; the cash shift is a count, not a posting.
Central kitchen output can be produced once and issued to outlets.
Many reports open the document behind a row, and export to Excel or PDF.
The same guides your team uses after go-live, written from the Penahak screens.
One picture of the whole job, and where each setting lives: on the restaurant screens, in Accounting, in Administration.
How a check moves from the table to the booksAdd dishes from the menu, choose the options, add notes, and check the order before you send it to the kitchen.
Take an orderSend KOT / BOT turns the draft order into tickets at each station. The cash shift must be open. A lost ticket is reprinted from Sent KOTs.
Send an order to the kitchen and reprint a KOTOpen the bill, check it, choose how the guest pays, and confirm. The bill is posted, printed, and the table is marked for cleaning.
Bill the table and take paymentSplit the payment of one bill between guests: equally, by the dishes each had, or by amounts you type. The bill stays one invoice.
Split the bill between guestsA cashier opens a shift with the cash in the drawer and closes it by counting. The screen compares the count with what the bills say should be there.
Open and close the cash shiftYes, and in a small kitchen that is normal. The ticket header still shows which station it was routed for.
No. The KDS shows the same routed orders on a screen per station, with a pass display for the expediter. You can run paper, screens, or both.
The financial engine every other module posts into.
Accounting & FinanceStock truth across every godown, counter and kitchen.
Inventory & StockQuotation to invoice to settlement, with nothing falling between.
Sales & PurchaseA counter that keeps selling, then reconciles to the rupee.
Retail POSBook a walkthrough and we will demo the modules that match how you actually trade — not a generic slide deck.
No obligation. Typically 30–45 minutes.
