Six jobs, two of them local
Four jobs are universal. Ring up a sale quickly. Take the money and record it against that sale. Move stock as it goes out of the door. Produce figures somebody can act on.
Two are specific to trading here. The first is offline: a connection that comes and goes is normal, and a system that stops selling during one costs you the day and the stock figures after it. The second is KRA eTIMS, where the invoice has to be signed through a control unit as it is issued, which requires certified software rather than a well-designed receipt.
Systems ported into Kenya usually do the four well and the two badly, which is why a demo looks excellent and the second month does not. The order of evaluation should be inverted: test the two first.
Want to see it running in your own business first?
Sign UpThe six jobs, and how to test each
Half an hour in a real shop with a real device.
- 1
Speed at the counter
Time a basket of ten items, scanned rather than keyed. At the busiest hour the difference between fifteen and forty seconds a customer is the difference between a queue that clears and one that does not.
- 2
Payment recorded against the sale
Take an M-Pesa payment and then try to answer 'which sale was this' from the code alone an hour later. If that takes more than seconds you will be reconciling by hand every evening: M-Pesa at a retail counter.
- 3
Stock moving automatically
Sell, then check the count. Receive a delivery, then check it again. A figure that only changes when somebody types is a spreadsheet with a login: what stock software has to do.
- 4
Selling with the connection down
Drop the data mid-sale, not before opening the app. The sale should complete, stock should move, and nothing should duplicate on reconnect: offline POS.
- 5
A compliant tax invoice from the sale itself
Ask whether the vendor is a certified eTIMS integrator, then check a real receipt for a control unit invoice number and a QR code: connecting a POS to eTIMS.
- 6
Figures you would actually use
Margin per product, what is not moving, what the day took by staff member. A report nobody opens is a feature, not a benefit.
How the choice goes wrong
Evaluating the four universal jobs first
Every system does those competently. The two local ones are where the field separates, and they are the ones left until after the decision.
Buying on the monthly fee
The fee is the smallest number in the comparison: what a POS actually costs.
One shared login at the counter
Then a void, a discount or a missing sale belongs to nobody, and the audit trail that justifies the system does not exist.
Loading the whole catalogue on day one
Start with the lines that move and the lines worth money. A partial catalogue that is accurate beats a complete one that is stale.
Not asking what leaving looks like
Your catalogue, stock history and sales live in it. Ask about an export before you commit a year of data.
A worked example: excellent for six weeks
A minimart in Nakuru chose a well-reviewed system on the strength of a demo: fast, clean reports, staff trained in a morning.
Week seven brought a long outage. The system would not complete a sale, so the shop served from a notebook, and the notebook recorded money without recording items.
Stock was wrong for a fortnight afterwards and two fast lines ran out. Nothing about the software was poor; it had simply been evaluated on the four jobs every system does well, and not on either of the two that decide whether it works here.
Running a shop on memory and paper leaves money on the table: missed sales, stock you cannot account for, and receipts KRA will not accept.
Veira records every sale, tracks stock and keeps you eTIMS-compliant automatically, so the numbers look after themselves.
How Veira handles it
Veira is built around the two local jobs rather than having them added. Selling continues when the connection does not, stock moves in both directions, and eTIMS invoices queue and transmit on reconnect.
Veira is a KRA-certified eTIMS integrator, so the tax invoice is produced by the sale rather than by a second device, and payments are recorded against the sale they paid for.
Each member of staff signs in as themselves, and margin, movement and takings are reported per product, per staff member and per branch rather than as one total.
Frequently asked questions
What separates a POS built for Kenya from one ported into it?
How long should a sale take?
Do I need a barcode scanner?
Can I run a shop on a phone?
How do I verify an eTIMS claim?
What should I load into the catalogue first?
Test the two local jobs before the four universal ones. A system that sells through an outage and issues a compliant invoice from the sale will almost certainly do the rest; one that does the rest beautifully may do neither.
Need help, or want to talk it through first? Chat with us on WhatsApp