Walk into most shops in Pakistan and the owner’s phone is on the counter with WhatsApp open. Orders arrive there. Payment screenshots arrive there. “Bhai, kitna balance hai?” arrives there. Email is for the bank. WhatsApp is where the business actually happens.
Most business software treats this as an afterthought. You generate a PDF, download it, open your file manager, find it, then attach it in a chat. Four steps, mid-transaction, with a customer waiting. In practice nobody does it, and the software quietly stops being used for anything the customer needs to see.
The counter test
We apply a simple test to features: can you do this at the counter, with a queue, without apologising to the next customer? Emailing a PDF fails the test. Sharing it straight from the bill screen passes. That test shaped where WhatsApp sits in Polaris — not in a settings page, but on the screens where work happens. Finish the bill, tap share, pick the chat. The customer has the invoice before they have their change.
What shares over WhatsApp today
- Of the 13 documents Polaris generates, 5 send straight from the app — sales invoice, quotation, refund, customer statement and supplier ledger — with your branding already on them.
- The customer statement carries a running balance and aging buckets at Current, 1–30, 31–60, 61–90 and 90+ days. When a customer asks what they owe, you send the statement instead of reading numbers off a register.
- Payment reminders go out over WhatsApp. A receivables campaign reaches every customer carrying a balance; the aging report is what tells you who to chase, and the 90+ column is the one worth reading as a call list.
- Every message lands in the communication log alongside SMS, email, and calls, so whoever is at the counter can see what was already sent and when.
It is not only the retail counter. A wholesaler quoting a retailer sends the quotation from the same screen it was made on, and the supplier ledger goes to a supplier the same way when a balance needs settling. The document types differ; the movement is the same — made in Polaris, sent in the chat where that relationship already lives.
Some customers will install the app and check their khata themselves — they sign in with their phone number, a password and your shop’s code, so one phone can hold accounts at several shops. Many never will, and that is fine. A WhatsApp message needs nothing installed, nothing explained, and nothing changed about how your customers already behave. The app is there for the customers who want it; WhatsApp is the floor that works for everyone.
Support lives there too
Our own support runs on WhatsApp at +92 335 070 6014, with same-day replies on business days. This is not a cost-saving trick. A shop owner with a stuck bill does not want to file a ticket and describe the problem in writing — they want to send a screenshot and a voice note. So that is what support looks like. The channel we ask customers to use is the channel we answer on.
Bolted on versus built in
Bolted on means the software exports a file and the rest is your problem. Built in means the share happens from the bill screen, the send is logged against the customer, and the reminder logic reads the same ledger the statement does. The difference sounds small in a feature list, and it never shows up in a comparison table. At the counter, it is the difference between a feature that gets used every day and one that gets demonstrated once during the sales call and never touched again.
If you want to see it working, message us on the number above. It is also how we prefer to talk.