AsaanHisab
Asaan Hisab Desktop
The full shop on your computer, kept in step with the cloud.
The complete counter app: billing, khata, stock, purchases and reports, signed in with your Asaan Hisab account. It talks to the same account as the web and the phone, so a sale rung up here shows on every screen. It also updates itself whenever a new version is published.
v0.1.9
99.0 MB
31 Aug 2026
Auto-updates
- Signs in with your Asaan Hisab account — same shop, same data
- Billing counter, khata, stock, purchases and reports
- Syncs with the web portal and the Android app
- Updates itself — no reinstalling for each new version
- Prints to thermal and A4 printers attached to the PC
Download Desktop v0.1.9
Windows 10 or 11 (64-bit) · 4 GB RAM · internet connection for sign-in and sync
How to install & use it
1
Download the installerClick Download. Windows may warn that the file is from the internet — choose Keep, then More info → Run anyway if SmartScreen asks.
2
Install itRun the .exe and follow the prompts. It installs for the current user, so no admin password is needed on most machines.
3
Sign inOpen Asaan Hisab Desktop and sign in with the same email or mobile number you use on the website.
4
Start billingYour products, customers and khata appear automatically. Connect your printer from Settings → Printing.
All versions (5)
Invoices Monitoring Feature
In This release, you can see all possible invoices of current register.
Offline Mode
1. Pairing (no internet needed)
Admin downloads Metadata.zip from the website (Users Management) and imports it on the desktop app.
The zip carries the shop key, user, business info, and full product/menu dataset — verified by a checksum so it can't be tampered with.
The app is now "offline-paired": no server session, but fully usable for selling.
2. Selling offline
Every order (open/edit/complete/cancel) is saved locally and added to an upload queue (state.queue) — nothing touches the server yet.
Opening a register offline creates a local register (register.local = true) tracked entirely on-device.
3. Closing a register
Closing bakes that session's sales into a LocalRegisterRecord (opening/closing balance, items sold, and which queued tasks belong to it) and lists it on the Register Sell page, marked unpublished.
4. Publish (the part we just built)
Pressing Publish on a closed register sends its register data + queued tasks directly to the server (register/publish), instead of exporting a zip file.
The server verifies the shop key, rejects duplicates (by a unique export id), then replays each task through the normal order-create/confirm logic — creating a real cash_registers row (open → sales → close) and real sales, exactly as if they'd happened online.
On success: register marked "Published" and its tasks drop out of the local queue. On failure: the exact reason is shown in a highlighted red message so it's obvious something needs attention.
5. Timezone correctness
The desktop always exports true UTC timestamps. The importer converts the register's open/close time and each sale's actual time into the business's configured timezone (Asia/Karachi etc.) before saving — so the times shown on the website match what the desktop showed locally, both for the register and for each sold item's date, instead of showing the moment it happened to be published.
Third Release
Service Types and Key issue resolve.
Online Device Activity Log
First Release