What you are actually buying
The phrase describes the operating system and nothing else. An Android POS is a computer running Android, the same system on most phones in Kenya, in a case shaped for a shop counter: a touchscreen, a barcode scanner, a thermal printer, a battery, and usually a SIM slot. The hardware is the least interesting part of the decision.
What decides whether it works for you is the software on it. Two identical-looking terminals from the same factory can run completely different applications, and the application is what handles your stock, your prices, your staff logins, your eTIMS transmission and your reports. A shop that buys on hardware specifications and takes whatever software comes bundled has chosen the wrong half of the product.
The reason Android won this category in Kenya is convergence. A traditional setup is a till for cash, a card machine from the bank, a phone for M-Pesa, and an ETR device for tax. Four devices, four things to reconcile at close, four things that can disagree. On a handheld Android terminal the sale, the payment prompt, the receipt and the tax transmission are one sequence, and there is nothing to reconcile because nothing was ever separate.
Battery matters more than the spec sheet suggests. Kenyan power is not uniformly reliable, and a terminal that runs a full trading day on one charge keeps selling through an outage that would stop a desktop till. This is also why the offline behaviour of the software is not a nice-to-have, which is the next section.
One clarification worth making, because sellers blur it: Android POS is not the same as a payment terminal. A payment terminal takes money. A POS records the sale, decrements the stock, prices the item, identifies the cashier and produces the tax record. Some devices do both. Many do only the first while being sold as though they do both.
Want to see it running in your own business first?
Sign UpBuy the software and let it tell you which hardware it runs on. Buying the hardware first is how shops end up with a good terminal running a bad till.
What to check before you pay
In the order that matters. The first three eliminate most of what is being sold in Nairobi at any given time.
- 1
Make it sell with the internet switched off
Ask the seller to turn off the WiFi and mobile data, then ring up three sales and print the receipts. A system that cannot do this will stop your shop every time the network drops, which in most of Kenya is weekly rather than yearly. Watch what happens when the connection returns, too: the queued sales should transmit by themselves, without anyone re-keying anything.
- 2
Ring up a sale end to end, with a real M-Pesa payment
Not a demonstration of screens. An actual sale: scan an item, take payment by M-Pesa prompt, print the receipt, and check the receipt carries proper eTIMS details and a QR code. Every step that needs a person to do something manually is a step your cashier will skip on a busy Saturday.
- 3
Ask who writes the software and how you get updates
Hardware is commodity; software is the relationship. Find out whether the application is maintained by the company selling you the box, how updates arrive, and what happens when KRA changes something. A terminal running abandoned software is a terminal with a expiry date nobody told you about.
- 4
Check you can get your data out
Ask to see an export of sales and stock. If the answer is that reports can only be viewed on the device, your business history is trapped on a piece of hardware that will eventually break or be stolen. Any serious system exports to a spreadsheet in a couple of taps.
- 5
Test it with your actual catalogue, not a demo one
Bring twenty of your real products, including the awkward ones: items sold by weight, items in cartons and singles, items with similar names. Demo catalogues are curated to look easy. Yours is not.
- 6
Find out what happens when the device breaks
Ask directly: if this dies on a Friday, what do I sell on? A system where the same account works from a phone while a terminal is repaired is worth more than a marginally better screen. A system that exists only on that one device is a single point of failure for your entire shop.
- 7
Check the staff model before you buy, not after
Each person who serves customers should have their own login. Shared logins mean no cashier is accountable for anything and your variance reports cannot tell you who was on. This is a software question and it is usually the one nobody asks in the shop.
- 8
Total the first year, not the sticker
Add the device, the monthly software, the receipt rolls, the support and anything charged per transaction. A terminal that is free upfront and expensive monthly can cost more by month eight than one that is the other way round. Do the arithmetic once, on paper, before you decide.
- 9
Buy one before you buy five
Run a single terminal in your busiest shop for a month. If it survives your worst day, buy the rest. Nobody has ever regretted this order; plenty have regretted the reverse.
Android terminal versus the traditional setup
| Android POS terminal | Till + card machine + phone + ETR | |
|---|---|---|
| Devices to manage | One. | Three or four, each with its own failure mode. |
| End-of-day reconciliation | Nothing to reconcile; one record of the sale. | Match the till, the M-Pesa statement, the card settlement and the ETR. |
| Tax record | Filed as part of the sale. | A separate step somebody has to remember. |
| Power cut | Runs on battery. | The till and the ETR stop. |
| Moving around the shop | Handheld; sell from the aisle or the table. | Fixed to the counter. |
| What it costs to get wrong | Software you cannot export from. | Devices that disagree, and no single version of the day. |
Where money gets wasted
Choosing the hardware and inheriting the software
The commonest and most expensive mistake. The box is the part you can hold, so it dominates the decision, and then you live with whatever till application came on it for the next three years.
Believing "it works offline" without testing it
Almost every seller says this. Far fewer systems queue a sale, print a valid receipt and transmit on reconnect. The only way to know is to switch the network off in the shop and watch.
Buying a payment terminal that was described as a POS
If it takes money but does not track your stock, price your items or produce your reports, it is a card machine with a bigger screen. Useful, but not the thing you were sold.
Ignoring where the data lives
A terminal is dropped, stolen or drowned eventually. If your entire sales history lives only on it, that event costs you the business records you need for a loan application or a tax question.
Rolling out to every branch at once
Five terminals with a problem is five times the problem and five times the disruption. Prove it in one shop first.
A minimart that bought twice
A minimart in Kasarani buys a cheap Android terminal from a stall in town because the price is a third of everything else quoted. It scans, it prints, and for six weeks it is fine.
Then the connection drops on a Friday evening and the till refuses to complete a sale. The owner serves the queue on paper and spends Saturday morning entering forty transactions by hand, guessing at two of them. A month later he wants a stock report by supplier and discovers the application does not produce one and cannot export anything. There is nobody to call, because the stall sold him hardware, not software.
He replaces it, and the second purchase takes a different shape: he tests offline selling in the shop before paying, watches a real M-Pesa payment and a real eTIMS receipt, and asks to see a spreadsheet export. The device he ends up with is not dramatically better hardware. The difference in what he gets is entirely the software, which is what he was actually buying both times.
Trading without eTIMS-compliant tax invoices risks KRA penalties, blocked VAT input claims for your customers, and receipts a business buyer cannot expense.
Veira signs every sale to KRA eTIMS automatically, so each receipt is compliant the moment it prints, with no separate device to reconcile.
One device, one record of the day
Veira runs on Android handheld terminals and on the phone you already own, so a sale, an M-Pesa prompt, a printed receipt and an eTIMS filing are one sequence rather than four devices to reconcile at close.
It keeps selling when the connection drops. Sales queue on the device and transmit on reconnect, so a network outage is a delay in transmission rather than a stop in trading.
Your data lives in your account rather than on the hardware, so a broken or stolen terminal costs you a device and not your business history. Staff sign in with their own roles, which means your reports can tell you who rang up what.
Frequently asked questions
What is an Android POS?
Is an Android POS the same as a payment terminal?
Can I use my own Android phone as a POS?
Does an Android POS work without internet in Kenya?
Can an Android POS file eTIMS?
How much does an Android POS cost in Kenya?
What happens if the terminal breaks?
Do I need one terminal per till point?
Is a more expensive terminal always better?
Should I buy the hardware or the software first?
An Android POS is a good default for a Kenyan business, but the phrase describes the operating system rather than the product. What you are choosing is the software: whether it sells offline, files eTIMS as part of the sale, lets your staff sign in as themselves, and hands your data back when you ask for it. Test those four things in your own shop with your own products before you pay, and buy one before you buy five.
Need help, or want to talk it through first? Chat with us on WhatsApp