Picture the shopkeeper at 9pm, locking up, trying to figure out why the till is short by 1,400 rupees and which of three cashiers rang up the wrong price. That nightly guessing game is usually a software problem, not a staff problem. A good point-of-sale system answers those questions before you even ask them. A bad one just gives you another screen to fight with.
Choosing one is a decision you'll live with for years, so it's worth slowing down. Here's what actually matters when you're shopping for a POS in Pakistan, based on the questions retailers keep running into after they've already signed up.
Start with FBR, because everything else is negotiable and this isn't
If a vendor can't show you live FBR Digital Invoice submission today, walk away. "We'll add it soon" tends to mean never, and you don't want to be the customer who finds out during an audit.
When you do get a demo, push on the details. Ask which FBR scenarios are supported — you want all 28, SN001 through SN028, not a convenient subset. Ask whether submission happens in real time or in batches, and what the system does when FBR's servers go down (they do). And ask whether a rejected invoice can be retried cleanly. The right answer to all of this is that the system submits quietly in the background, so your cashier never stands there waiting on a government API while a queue builds up behind them.
Inventory that knows where your stock actually is
If you run more than one branch, or even a shop plus a back storeroom, you need stock tracked per location in real time. The system should let you move stock between locations, track purchases against the branch that received them, and set location-specific pricing if your Clifton outlet charges differently from your Saddar one.
Tied to that is purchasing. WhatsApp orders and an Excel sheet work until they don't, usually right when a supplier disputes what you owe. A proper POS gives you purchase orders that move from draft to approved to received, Goods Received Notes that update stock the moment goods arrive, supplier aging so you know who's owed what, and a place to record vendor payments. None of this is glamorous. All of it saves you a bad afternoon.
The khata, but it stops "growing legs"
Every traditional shopkeeper keeps a khata — the credit ledger for regular customers. A digital version should do everything the paper book did and a few things it couldn't: enforce credit limits, show a running ledger of every charge and payment, store a buyer's NTN or CNIC for FBR-registered sales, and handle loyalty points if you run a rewards scheme. The difference is that a digital ledger doesn't get smudged, lost, or quietly edited.
Reports you'll actually open
Most POS reports go unread because they're noise. The handful worth checking regularly are sales by product (so you stop reordering the stuff that sits on the shelf), sales by cashier (which doubles as your shift-end reconciliation), live inventory valuation (what your stock is worth right now), and an FBR tax summary that lines up with your monthly returns. If the system includes accounting, a real profit-and-loss view rounds it out.
That accounting piece is worth pausing on. The better systems include built-in double-entry bookkeeping, so every sale, purchase, and expense posts proper journal entries automatically. You get a real-time balance sheet instead of a shoebox of receipts you hand your accountant in July. ClearRing builds this in rather than charging for it as an add-on, which is the model I'd look for generally — bookkeeping shouldn't be an upsell.
It has to work when the internet doesn't
This one is non-obvious until the fibre line gets cut down your street. A cloud-only POS that freezes the moment connectivity drops will, sooner or later, stop you from selling during your busiest hour. Insist on offline capability: the till keeps ringing, and everything syncs once you're back online.
Who can do what
You don't want every employee seeing your margins or issuing refunds on a whim. Look for custom roles — cashier, manager, admin — with permissions set per feature, and an audit log that records who did what and when. The audit trail matters more than people expect; if staff can delete a record without leaving a trace, you've got a hole in your books and no way to find it.
Cloud or on-premise?
For most Pakistani retailers, cloud wins, and it isn't close. On-premise means buying hardware and software upfront, leaning on your own IT to keep it patched, and manually updating it every time FBR changes a rule. Multi-location gets genuinely painful. Cloud flips all of that: a predictable subscription, vendor-managed maintenance, automatic updates including FBR compliance changes, and easy expansion to new branches. The one thing on-premise traditionally did better — running fully offline — is solved by any cloud POS worth buying through local caching. So pick cloud, just confirm that offline mode is actually there.
The red flags
A few things should make you put the pen down. A vendor who promises FBR compliance "soon." No offline mode. No way to export your own data. Hardware lock-in that forces you onto specific tablets and printers. And no audit trail. Any one of these is a reason to keep looking.
Questions to ask before you sign
Bring this short list to every demo:
- Do you support all 28 FBR DI scenarios?
- Does it work offline, and how exactly does sync work?
- Is accounting included, or is it a paid add-on?
- Can I export my data whenever I want?
- What happens to my data if I cancel?
- Is there real support in Urdu and English?
The honest answers tell you more than any feature list.
A POS should make the 9pm lock-up boring — till balanced, FBR filed, stock counted, nothing to puzzle over. Try the free trials, run them in your actual shop with your actual staff, and don't commit until one of them has survived a real Saturday rush.