The till total never quite matches the books
When POS is a separate product that exports a daily figure, the difference between the drawer and the ledger becomes a monthly write-off nobody can explain.
Solution
Retail & supermarket
Multi-counter selling with barcode, schemes, loyalty and gift cards, closing each shift with a cash handover that reconciles.
What we hear
The problems that bring people to us
Retail margin is thin enough that small leaks matter: a scheme priced by hand, a discount nobody approved, a drawer that is short and cannot be attributed. Penahak makes the counter fast, then makes the shift accountable.
Stock on the shelf does not match stock in the system
Without vouchered movements, shrinkage, breakage and unaccepted transfers all look identical at year end — a gap with no cause.
Promotions cost more than they earn
Discounts typed in at the counter cannot be analysed afterwards, so nobody can say what a promotion actually cost in margin.
A shortage cannot be attributed
Shared logins and open-ended shifts mean a shortfall belongs to everyone, which means it belongs to no one.
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.
Cashier opens a shift with a counted float
Barcode selling, schemes and loyalty applied automatically
Delivery received against the purchase order, landed cost allocated
A return is processed against the original invoice
Shift closed, cash declared, variance recorded, handover signed
Sales, refunds and settlement already sit in the ledger
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.
Retail POS
Touch-first point of sale with a modern UI, hardware printing and a cashier shift model that ends in a real cash handover — not a guess.
- Modern touch and desktop POS UI with barcode, product browse and keyboard shortcuts
- Split payments: cash, card, bank, QR, wallet and gift card in one bill
- Sales return and replacement directly from the counter
- Loyalty policy, loyalty adjustment policy and points redemption
Explore module
Retail 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, adjustments and physical counts
- Serial-number and batch tracking with expiry and breakage handling
- Landed-cost allocation across purchase documents
Explore module
Inventory & Stock
Sales & Purchase
Full order-to-cash and procure-to-pay cycles with challans, dispatch, returns and outstanding tracking at every stage — so you always know what is quoted, ordered, delivered, billed and unpaid.
- Sales quotation, order, challan, dispatch, invoice, return and replacement
- Purchase quotation, order, challan, invoice and return
- Outstanding tracking at quotation, order and challan level
- Bill term, discount and tax term engines shared with POS and hospitality
Explore module
Sales & Purchase
Accounting & Finance
A double-entry core with a real chart of accounts, cost centres, fiscal-year control and immutable posting. Every sale, folio, payroll run and stock movement in Penahak resolves to a source document here.
- Chart of accounts with multi-level groups, sub-ledgers and general-ledger IDs
- Journal, day book, receipts, payments, contra and cash/bank vouchers
- Credit notes, debit notes and approved reversal paths — posted documents are never edited in place
- Cost centres, classes, areas, agents and user-defined fields for dimensional reporting
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.
- Every counter sale posts to the ledger with its own tax and settlement treatment — nothing to reconcile
- Shrinkage becomes a document with a reason instead of a year-end surprise
- Scheme and loyalty cost is reportable, so you can tell which promotions worked
- Cash variance is attributable to a named cashier on a named terminal
- A second branch is a configuration change, not a second disconnected system
Reporting
The reports you will live in
Every total drills down to the source document behind it.
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.
Other industries
Not quite your business?
Built for Retail & supermarket
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.