Skip to content
Penahak now runs hotels, restaurants and retail on one ledger.
Penahak
Solution

Restaurant, café & bar

Floor map service, station-routed kitchen tickets, KDS and cash shifts, with recipe stock consumption behind every plate.

What we hear

The problems that bring people to us

Service fails in small, expensive ways: a ticket that never printed, a bill split badly, a bar stock count nobody trusts. Penahak takes printing out of the browser and puts recipe consumption behind every dish.

Lost kitchen tickets

Printing straight from a browser means an offline printer, an empty paper roll or a closed tab loses the order outright, and the table simply waits.

Nobody knows the real cost of a dish

Without recipe consumption, food cost is a monthly guess derived from purchases rather than from what was actually served.

Bar stock walks

Pour variance is invisible when sales and stock live in different systems that are reconciled by hand, if at all.

Voids and comps are untraceable

If a cancelled item leaves no record, the difference between a genuine mistake and a habit cannot be seen.

A day on Penahak

One chain of documents, start to finish

Each step below creates or references a real document. Nothing is retyped between them, and every figure at the end traces back to the action that caused it.

Read the step-by-step guides

Table opened from the floor map, first round sent Service
Items route by product group to hot kitchen, tandoor and bar Service
Recipe ingredients issue from the kitchen store as dishes are served Service
A resident guest charges dinner to their room folio Evening
Bills split, settled, cash shift closed and declared Close
Item mix, void audit and food cost ready the next morning Overnight
Typical setup

The modules most businesses like yours run

A starting point, not a fixed bundle. Add or drop modules once we have seen how you operate.

What changes

What you should expect to be different

Not features — outcomes. If these are not true six months after go-live, something has been configured wrongly and we want to hear about it.

  • A printer fault delays a ticket instead of losing it — jobs retry until acknowledged
  • Food and beverage cost derives from what was served, not from what was bought
  • Voids, comps and discounts carry a user and a reason, and appear in the exception reports
  • Restaurant revenue lands in the same ledger as every other outlet
  • Charge-to-room works without anybody retyping the bill
Reporting

The reports you will live in

Every total drills down to the source document behind it.

  • Outlet sales
  • Item & category mix
  • Void & discount audit
  • Cash shift summary
  • Raw material consumption
  • Table turn performance
Compliance

Nepali obligations handled in the core

IRD-ready fiscal invoicing

IRD-approved, with fiscal invoice behaviour in the central SalesBill and POS paths, IRD sync, VAT customer and vendor summaries, and an audit trail built for inspection rather than reconstructed after the fact.

Nepali fiscal year and dates

Bikram Sambat fiscal-year control, business-date close and dual-date handling throughout documents and reports.

Local payment providers

eSewa, Khalti, Fonepay, card, bank, QR and wallet adapters, with verification evidence required before a provider goes live. Cash stays simple: no merchant ID, no callback URL.

English and Nepali

Interface translations and a localisation layer in both the web application and the reporting engine.

Immutable audit trail

Every posting command carries an idempotency key. Corrections go through approved reversal or credit paths; posted truth is never edited in place.

Role-based security

Granular roles and permissions, IP address whitelisting, two-factor authentication, user activity logging, time-based account expiry, and stage-based setup gates that block posting until configuration is safe.

Getting there

How a go-live actually runs

01

Discovery

We map your outlets, books, stock locations and statutory obligations, and agree what go-live means.

02

Configuration

Chart of accounts, tax and bill terms, document numbering, godowns, roles and payment providers, all checked against the setup gates before anything posts.

03

Migration

Masters, opening balances and opening trial imported and reconciled against your closing figures.

04

Training

Role-based sessions for owners, cashiers, front desk, kitchen, storekeepers and accounts, using your own data.

05

Go-live

One full test cycle end to end, then supervised go-live with a support engineer on hand.

06

Aftercare

Ongoing support, statutory updates, new-release rollout and periodic health checks.

Built for Restaurant, café & bar

Book 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.