Skip to content
Penahak now runs hotels, restaurants and retail on one ledger.
Penahak
Sign in Talk to sales Request a demo
Module

Restaurant POS

Table service built around a floor map, station-routed kitchen tickets and durable print jobs that survive a printer going offline mid-service.

Demo Restaurant POS Read the guides
The problem

Floor, kitchen and bar working off the same order.

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 takes printing out of the browser entirely. The backend creates durable print jobs and a local bridge delivers them, retrying until they are acknowledged.

Who uses it

  • Servers, who open tables, take rounds and settle
  • Kitchen and bar staff, who work from station tickets or the KDS
  • Cashiers, who close the shift and reconcile
  • Managers, who watch item mix, voids and table turn
How it works

The workflows you will actually use

Not a feature list — the sequences your team runs day to day.

Table service, end to end

  1. Select the table on the floor map. A session opens.
  2. Add items and send the round. Items route to the station configured for their product group.
  3. Durable print jobs are created; the bridge prints them and acknowledges.
  4. Add later courses as further rounds against the same session.
  5. Settle the bill — cash, card, QR, or charge to a guest room.

Splitting a bill

  1. Open the table session.
  2. Split by item or by cover.
  3. Each resulting bill settles independently.
  4. The split is recorded rather than being an invisible edit.

A ticket did not print

  1. Check the bridge is running on the machine the printer is attached to.
  2. Check the print job state: not created means routing, pending means the bridge, failed means the printer.
  3. If no job exists, check the item has a product group and that group maps to a station.
  4. Fix the cause and reprint from the order — no re-entry needed.
Capabilities

11 capabilities ship with this module

Everything listed here posts through the central accounting engine rather than keeping its own separate records.

  • Interactive floor map and floor-plan editor with table sessions
  • Order panel and bill panel built for fast, repeated service
  • Kitchen Display System (KDS) and pass display for expo
  • Customer-facing display (CFD) at the counter
  • Kitchen and bar ticket routing by product group to the right station
  • Durable print jobs with acknowledge/fail retry — a dead printer does not lose a ticket
  • Station-to-printer mapping handled by the local bridge, not the browser
  • Table reservations calendar
  • Cash shift control and sales return
  • Split, merge and transfer table sessions
  • Charge-to-room handoff into Hospitality folios
Connected, not integrated

What it shares with the rest of the platform

These are not integrations between separate products. They are modules on one ledger, one party master and one product catalogue.

Hospitality

A diner staying with you can charge the bill to their room folio, with the outlet and session recorded on the line.

Inventory

Recipe consumption issues ingredients from the kitchen store as dishes are served.

Accounting

Outlet sales and shift cash post with their tax and settlement treatment.

Production

Central kitchen output can be produced once and issued to outlets.

Every module posts into one ledgerEight Penahak modules arranged around a central accounting ledger. Each module sends source documents inward to the ledger, and the ledger feeds a single reporting layer. One ledger immutable Retail POS Restaurant POS Hospitality CRM Inventory HR & Payroll Production Sales & Purchase
Reporting

What you get out of it

Every total drills down to the source document that produced it, and exports to Excel, CSV or PDF.

  • Outlet sales
  • Item & category mix
  • Station throughput
  • Cash shift summary
  • Void & discount audit
  • Table turn performance
Questions

About Restaurant POS

Yes, 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.

Explore

The rest of the platform

Sales & Purchase

Quotation to invoice to settlement, with nothing falling between.

Sales & Purchase

Retail POS

A counter that keeps selling, then reconciles to the rupee.

Retail POS

See all ten modules

See Restaurant POS running on your data

Book a walkthrough and we will demo the modules that match how you actually trade — not a generic slide deck.

Request a demo Talk to sales

No obligation. Typically 30–45 minutes.