Solutions, organised by the job you need finished.

Why these pages are organised this way

Software is usually sold by module, and bought by problem. Nobody wakes up needing an inventory module. They wake up having sold something they did not have, or having discovered expired stock on a shelf.

So each page here starts from a problem in the words a buyer would use, says what changes, walks through how it actually works, and then names the system that does it. If you already know which system you want, the product pages are the shorter route.

Choosing between them

FBR digital invoicing and billing without a connection are both point of sale, and most shops need both. The first is about a legal requirement, the second about the condition the requirement has to be met in. Read the second one if your counter has ever stopped selling.

Payroll you can defend is the one to read if the problem is not calculation but explanation: figures that are right and cannot be traced.

Fee collection and marks to result cards are the two halves of a school year. Schools almost always adopt because of the first and stay because of the second.

Stock, batches and expiry applies to any counter holding perishable or dated goods, which in practice means pharmacies, food retail and much of distribution.

What a solution page will not do

It will not claim a capability the product does not have. Every step described on these pages is one you can point at in the software, which is why some of them include limits: card authorisation still needs a network, two offline registers can both sell the last unit, and a school above 200 students is quoted rather than listed.

That restraint is deliberate. A page that promises more than the demo shows costs more than the sale is worth.

Where the price sits

Solutions are not licensed separately. Each one is part of the system it runs on: PKR 1,000 a month per point of sale register, PKR 1,000 a month for a school of up to 200 students, PKR 15 per employee per month for payroll. Nothing on these pages is an add-on with its own line on an invoice.

If you are not sure which problem you have

That is common, and usually means the symptom you have noticed is downstream of the cause.

"Our stock is always wrong" is normally a receiving discipline problem, or a units problem, or sales recorded on paper during an outage and typed up later. Three different pages, three different fixes.

"Payroll takes a week" is usually attendance arriving as a spreadsheet rather than as data, not the calculation itself.

"Parents complain about fees" is almost always the defaulter list being stale rather than the amounts being wrong.

The fastest way through this is twenty minutes with your own numbers rather than more reading. Bring the thing that is actually annoying you and we will tell you which of these pages describes it, including if the answer is none of them.

What these pages have in common

Each one names a limit as well as a capability. That is not hedging: a page that lists only what works is a page you cannot plan around. If card authorisation needs a network, you need to know that before an outage rather than during one.

Each also states what it costs, because a solution page that avoids the question wastes the reader's time. Nothing here is licensed separately from the system it belongs to.