Billing, khata and books for a shop with staff.
Every sale, refund and payment carries the name of whoever made it, undoes for 5 minutes, and sits behind 157 permissions — with refunds, voids and price overrides off until you switch them on.
- 157
- permissions
- 19
- businesses live
- 13
- FBR Annexure C columns
The drawer is uncounted. Tally the notes to close the shift.
Counted minus expected. Past PKR 100 either way, the shift goes to review instead of closing.
Tap to count the drawer
“We switched from Excel last year. Reconciliation that used to eat the morning now happens before chai is finished, and our customers check their balances on their own phones.”
Everything in the quote is shipped product: one payment settling the oldest unpaid bills first, 50 bills locked at a time so nothing is counted twice; split payments across cash, card, bank transfer, cheque; receivables aged into Current, 1–30, 31–60, 61–90 and 90+ days; and the customer app where they check their own balance.
What Polaris will not let you do.
Most software lists what it allows. These are the writes the product refuses, and the reason each one fails.
Tap a rule to see the attempted write, the refusal it hits, and what gets written instead.
- Close the day while a till is still open.
- End-of-day submission is refused while any shift is unclosed. Expected cash is read from dated ledger entries, not from bill totals that can still change.
- Approve your own stock transfer.
- The person who requests a branch transfer cannot be the person who approves it. On approval the oldest batches drain at the source and are rebuilt at the destination carrying their purchase price, supplier, lot code and expiry.
- Close a drawer that does not add up.
- Counted cash more than PKR 100 away from expected does not close the shift. It moves to review, and only an account holding the shift-review permission can clear it.
- Post a journal entry that does not balance.
- Debits must equal credits or the entry is rejected, and a database constraint makes it physically impossible for one line to carry both a debit and a credit.
- Send a walk-in out with a part-paid bill.
- A sale booked against the walk-in customer must be settled in full at the counter. Separately, a no-receipt return with no customer on it cannot be paid out as store credit — it has to be cash.
- Reach a screen your role was never granted.
- A request hitting an endpoint that never declared which permission it needs is refused outright rather than run. And production will not start at all if the database role could read another shop’s rows.
Every document, generated from the same ledger.
Every output carries your branding, your tax setup, your terms — generated in under a second, sent in one tap.
- My records are in Excel and a hand-written ledger — how do they get in?
- Our team enters your customer list, supplier list, and stock with you as part of free setup. Direct importers from Tally or QuickBooks are not yet built; we do it manually together.
- My staff aren’t technical. Can they run it?
- Yes. The interface is built around the screens a Pakistani shop owner already knows: bill, ledger, stock, customers. WhatsApp support is there for the rough edges.
- Who can see what? I don’t want everyone seeing purchase prices.
- Access is organisation-scoped with 157 distinct permissions, so a counter login sells without seeing costs. A new cashier starts with refunds, voids, price overrides and ledger access switched off. Two-factor sign-in, and a full audit trail with before and after balances.
- How fast can I start?
- A guided 5-step wizard takes you from sign-up to your first invoice — shop, customer, product, bills, then a ready screen. Tax settings sit inside the bills step. Every step is skippable, and progress is saved on the server, so you can start on the counter machine and finish on your phone.