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.
Solution
Restaurant management software for Nepal
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 queues every kitchen ticket so a printer fault delays it instead of losing it, and puts recipe consumption behind every dish.
Kitchen stock never matches sales
Without recipes behind the menu, ingredient stock is a monthly guess from purchases rather than from what was actually sold.
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.
Table opened from the floor map, first round sent
Items route by product group to hot kitchen, tandoor and bar
Recipe ingredients leave the store when each bill is posted
A resident guest charges dinner to their room folio
Bills split, settled, cash shift closed and declared
Item mix, void audit and table performance in the restaurant reports
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.
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.
- 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
- Kitchen and bar ticket routing by product group to the right station
Explore module
Restaurant POS
Inventory & Stock
One inventory engine serves retail, restaurant, hotel minibar and manufacturing. Movements are vouchered, costed and reconcilable back to accounting.
- Products, groups, sub-groups, units, bundles and product targets
- Multi-godown stock with transfers, issues and stock adjustments
- Serial-number and batch tracking with expiry and breakage handling
- Landed-cost allocation across purchase documents
Explore module
Inventory & Stock
Production
Light manufacturing that consumes real stock and produces costed output, with a production journal you can audit line by line.
- Bill of materials with raw materials, fixed costs and by-products
- Production journal entries against production orders
- Raw materials leave stock when the journal is approved at the quality check
- Finished-goods costing rolled up from materials and fixed costs
Explore module
Production
Accounting & Finance
A double-entry core with a real chart of accounts, fiscal-year control and logged corrections. Every sale, folio, payroll run and stock movement in Penahak resolves to a source document here.
- Chart of accounts with multi-level groups and sub-ledgers
- Journal, day book, receipts, payments, contra and cash/bank vouchers
- Credit notes, debit notes, returns and same-day cancels; approved and reconciled documents are locked
- Projects or business units, classes, areas, agents and user-defined fields on documents
Explore module
Accounting & Finance
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
- Ingredient stock follows what was billed, through each dish’s recipe
- Voids and comps carry a reason and appear in the Void / Comp Audit
- 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
Many totals open the document behind them.
Compliance
Nepali obligations handled in the core
IRD-ready fiscal invoicing
Fiscal invoice behaviour is built into the sales invoice and POS paths themselves rather than added on top, with IRD synchronisation, VAT customer and vendor summaries, and an audit trail written as you trade rather than reconstructed afterwards.
Nepali fiscal year and dates
Bikram Sambat fiscal-year control, business-date close and dual-date handling throughout documents and reports.
Payment methods
Cash, card, bank transfer, QR and wallet payments are recorded against the bank account you choose. Penahak does not move the money.
English and Nepali
English and Nepali in the accounting, inventory, retail POS, HR and report screens. The hotel, restaurant and CRM screens are in English.
Controlled corrections
With IRD on, saved invoices cannot be changed: they are corrected by returns or same-day cancels. Approved, reconciled and locked documents cannot be edited, and edits are logged.
Role-based security
Granular roles and permissions, sign-in by listed IP addresses, account lock after wrong passwords, user activity logging and account start and end dates.
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 methods, checked before the first live day.
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, new releases, and the help centre’s step-by-step guides.
Help centre
Where your team starts
The guides your staff use after go-live, written from the Penahak screens.
How a check moves from the table to the books
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 booksSend an order to the kitchen and reprint a KOT
Send 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 KOTWhat leaves stock when a bill is posted
Stock leaves the store when the bill is posted, not when the order is sent. A dish with a recipe takes its ingredients out; a combo takes its parts out.
What leaves stock when a bill is postedOpen and close the cash shift
A 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 shift
Other industries
Not quite your business?
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.