Business

What a Retail POS Has to Do in a Kenyan Shop

K By Kev 5 November 2026 Updated 7 November 2026 12 min read
Share
Business guide

A retail POS is judged on six jobs, and the ones built elsewhere fail the same two: selling when the connection is gone, and issuing a KRA tax invoice as part of the sale. This sets out what each job actually involves in a Kenyan shop, which ones are negotiable, and the half hour of testing that tells you more than any feature list.

Key takeaways
  • Six jobs: speed, payment, stock, reporting, offline and eTIMS. The last two decide it here.
  • Drop the connection mid-sale during the demo, not before opening the app.
  • A stock figure that only changes when someone types it is a spreadsheet with a login.
  • Certified integrator status is a fact with a yes or no answer; ask for it in writing.
  • The monthly fee is the smallest number in the real comparison.
On this page▾
  1. Six jobs, two of them local
  2. The six jobs, and how to test each
  3. How the choice goes wrong
  4. A worked example: excellent for six weeks
  5. How Veira handles it
  6. Frequently asked questions

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 Up

The six jobs, and how to test each

Half an hour in a real shop with a real device.

  1. 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. 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. 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. 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. 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. 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

Worked example

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.

Business impact

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?
Two jobs: selling through an outage and issuing a KRA-compliant tax invoice as part of the sale. Almost every system handles speed, payments, stock and reporting competently; those two are where the field separates, and they are usually tested last.
How long should a sale take?
Time a ten-item basket, scanned rather than keyed. At the busy hour the gap between fifteen and forty seconds per customer decides whether the queue clears, and it is a layout and hardware question as much as a software one.
Do I need a barcode scanner?
Not to start, but it is usually the cheapest speed improvement available once the catalogue is loaded. Keying item codes is the single slowest thing most Kenyan counters do.
Can I run a shop on a phone?
For one counter, yes, with the caveats of battery through a full shift, screen brightness in daylight and a separate thermal printer. Beyond one or two counters a dedicated device earns its place.
How do I verify an eTIMS claim?
Ask whether the vendor is a certified integrator and which control unit route they use, then run a real sale and check the receipt for a control unit invoice number and a QR code. Those exist only if the invoice actually passed through a control unit.
What should I load into the catalogue first?
The lines that move and the lines that are worth money. Trying to load everything is what stalls most rollouts, and a partial catalogue that is accurate is more useful than a complete one nobody trusts.

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

Keep reading

See all Business guides

Veira for your business

Browse Veira by business type · Who we serve