How to Choose Software for a Shop in Pakistan: A Buyer's Checklist

A mobile shop owner in Peshawar sells ten phones a week — six for cash, four on qist. His register holds the cash sales fine. The qist sales are the problem: four customers, four different due dates, two guarantors, one customer who paid half and promised the rest next Friday. By the third month he cannot say, without an hour of flipping pages, who owes what. That is the moment most owners start looking for software — and the moment most of them buy the wrong kind.

The wrong kind is bought backwards: the owner watches a flashy demo, likes the dashboard, pays — and only then discovers the system has no per-customer khata, no WhatsApp reminders, and no way to record a guarantor. The right way round is the opposite. First write down, in one page, what your shop actually does every day. Then check every system against that page.

Most Pakistani shops fall into three kinds, and each kind needs different things from software. A cash-only kiryana store needs fast billing and stock counts. A shop that sells on udhaar or qist needs customer records, due dates, reminders and a defaulter list. A mixed shop needs both, in one place, without paying for two systems. Before you read a single feature list, answer this: which kind is yours, and what does a normal day look like — how many credit customers, how many due dates, how many reminders? That one page is your buying checklist. The ten points below turn it into questions you can put to any seller.

If you already sell on qist and want the buyer's view of that market first, our guide to qist software in Pakistan walks through what a shop actually needs from it, day to day.

Run every system you consider through these ten checks. A system that passes all ten on a trial with your own shop's data is worth buying. One that fails three or more will cost you more in lost collections and daily friction than it ever saves.

1. A per-customer khata — not one long list

Every customer needs their own record: name, phone, address, and every rupee they owe or have paid, in one place. If the system only keeps one long list of transactions, you will spend your evenings hunting for one customer's balance. Ask the seller to open one customer and show you the full history in five seconds.

2. Qist schedules with guarantor and CNIC

If you sell on installments, the system must split a price into monthly qist with fixed due dates, and link the guarantor's name, CNIC copy and phone number to the same customer. When a buyer disappears, the guarantor's details must sit on the same screen as the balance — not in a drawer, not on another page.

3. Automatic WhatsApp reminders

Most late payments are not fraud; people simply forget. The system should send a polite WhatsApp reminder before each due date, with the customer's name and the amount due — and let you send a manual reminder to anyone already late, straight from the recovery list. If reminders depend on someone remembering to send them, they will not happen.

4. Offline working for load-shedding

Your shop does not stop when the power or internet drops, and the software must not either. You should be able to keep recording payments while offline, with everything syncing once you are back online. Ask the seller the direct question: at 8pm on a busy evening, with the internet down, what still works?

5. Stock that knows what is on the shelf

Software that only records sales is half a system. It should tell you what is in stock, what is running low, and what you sold this week — so you order before the shelf is empty, not after. For a kiryana or mobile shop, this one check alone pays for the system.

6. A printed receipt for every payment

Every payment a customer makes should produce a printed receipt with the amount, the date, and the remaining balance. Receipts end arguments — "you never wrote my payment down" stops being a sentence anyone can say. If the system cannot print a clear receipt, it is not built for a real counter.

7. Daily and monthly reports you actually read

At day's end you should see, in one screen: how much was collected today, how much is still due, and who recovered the most. At month's end: the same picture for the whole month, and one defaulter list sorted by amount overdue. If the reports need a spreadsheet and an hour of your evening, they will never be read.

8. Your data stays yours

Your customer list and their balances are your business. You must be able to take them out any time, in a file you can open — and you must know, before you pay, what happens to your data if you ever stop paying. A seller who cannot answer this clearly is a seller to avoid.

9. Setup help — someone puts your shop in

Software fails at setup more than anywhere else: your customers, their balances and your stock have to be inside before the first working day. Ask who does that work — you, alone, at midnight, or the seller's team, with you. If the answer is "you do it yourself, it is easy," ask how long it takes for a shop with two hundred credit customers.

10. Support in your language, on WhatsApp

When the system stops on a busy day, you need help on WhatsApp in plain words — not a ticket form, not an email that answers tomorrow, and not English-only support your staff cannot use. Ask the seller: if I message at 11am on a working day, when does a human reply? Then check the answer during your trial.

The ten checks above are the test. This table is how to run it: ask the question in the left column, and listen for which kind of answer you get. A weak answer is not always a reason to walk away — but three weak answers together are.

Running a shop like this? See the system free on WhatsApp →

One more thing the table cannot show: how the system feels at speed. A demo on the seller's data always looks smooth. The real test is your data, your customers, your busiest hour — which is why the next section matters more than this table.

Five questions, asked of every seller, in the same words. Write the answers down. The seller whose answers stay the same in writing and in the trial is the one to trust.

1. Can I try it with my own shop's data first?

A demonstration shows you their shop; a trial shows you yours. Ask for a trial that runs on your real customers, your real balances and your real stock — across a full busy week, not a quiet afternoon. If the seller offers no trial at all, say so in your decision, and lean harder on the other four questions.

2. What is the full monthly cost — everything included?

Not the starting figure: the full figure, with every feature you need, for your shop, every month. Ask for it in writing, with the exact words "everything included." If the answer changes when you ask about reminders, reports or a second user, the starting figure was never the real one.

3. If I stop paying, do I keep my data?

This is the question most owners never ask until it is too late. Your customer list, their balances and your stock records are your business. Get the answer in writing: can I export everything, any time, in a file I can open? If the seller hesitates, the data is not really yours.

4. Who puts my customers and balances in at the start?

Two hundred credit customers, each with a balance, a phone number and a due date, is a full day of careful entry — and one wrong balance becomes a customer argument. Ask who does this work, how long it takes, and what happens if a balance is entered wrong. The honest sellers have a real answer; the rest change the subject.

5. When the internet or power goes down, what still works?

Ask it exactly like that, and ask to see it: switch the internet off during the demo and record a payment. If the screen freezes, you have learned more in thirty seconds than in an hour of slides. A system built for Pakistani shops is built for this evening — it is not a surprise.

Watch a one-minute walkthrough of the Rahnivo retail system — an installment sale from customer profile to printed receipt. This is the same daily routine the ten checks above are testing: profile, schedule, reminder, receipt.

Want the full tour? Explore the retail system.

Buy now if your register already costs you money — missed due dates, customers whose payments nobody recorded, a month-end total you cannot trust. Every month you wait is a month of collections that depend on memory. Run the ten checks, take the trial on your own data, and decide on what you saw working, not on what you were told.

Wait if your shop is still small enough that one person knows every customer and every balance by heart — a handful of credit customers, all paying on time, all in one head. Even then, write the checklist down now: the day the second person starts handling collections, or the day the customer list passes fifty, is the day to buy.

The two-week test. Whatever you choose, judge it the same way: put your real customers in, run it through your busiest week, send real reminders, print real receipts, and close a real month. If, after two weeks, your staff reaches for it without being told, you chose well. If they reach for the register instead, the software failed the only test that matters — and no feature list will save it.