Best POS & Inventory System for Kenyan Retail (2026)
What Kenyan retailers should demand from a POS and inventory system in 2026 — eTIMS on every receipt, shrinkage visibility, multi-branch control, and a straight answer on what happens when the line drops — plus how to evaluate the options, including us.
Retail in Kenya runs on thin margins and fast stock. The difference between a shop that grows into three branches and one that quietly bleeds out is rarely the location or the products — it is whether the owner can answer three questions any evening: What did we sell today? What is it worth? And where did the difference go? A good POS-and-inventory system answers all three without being asked. Most setups in the market answer none.
Why POS and inventory must be one system
A till that only prints receipts is a calculator. The value is in the link: every sale should move stock in the same instant, so the stock card is always current and shrinkage has nowhere to hide. When POS and inventory live in separate apps, the gap between them becomes the place where miscounts, theft, and "boss, the system was down" accumulate.
The non-negotiables for Kenya
1. eTIMS compliance from the normal sale
Compliant electronic receipts must come out of the ordinary selling flow — including credit notes and returns, which is where manual processes break. If eTIMS means re-entering sales into a separate portal at closing time, it will stop happening by February. Our compliance features guide covers what to verify.
2. Offline-first selling
Connectivity drops are a fact of Kenyan retail life. The till must keep selling offline and sync transactions — including queued eTIMS transmissions — when the network returns. A till that stops selling when Safaricom hiccups trains staff to sell outside the system, and that habit never reverses.
3. Shift and drawer discipline
Cash, M-Pesa, and card takings reconciled per shift, with variances attributed to the person on the drawer. Anonymous shortages are permanent shortages; named shortages end within a month.
4. Multi-branch from day one
Even if you have one shop today, the growth pattern in Kenyan retail is branches — and retrofitting branch visibility is painful. Head office should see sales, stock, and reconciliations across every counter live, with governed transfers between locations. Our guide on multi-branch retail goes deeper.
5. Purchasing connected to selling
Reorder decisions belong on data: what sells, what sits, what margins each supplier really gives you after negotiating. When POS, inventory, and procurement share one dataset, replenishment becomes arithmetic instead of instinct.
Comparing what's on the market
| Option | Strengths | Where retailers get hurt |
|---|---|---|
| Standalone POS apps | Cheap, quick to start | No real inventory link, no purchasing, eTIMS often bolted on, branch view missing |
| Imported retail suites (USD) | Feature-rich | Dollar pricing, no eTIMS, support in another timezone |
| Custom-built systems | Fits your exact flow… initially | One developer is your single point of failure; compliance updates are your problem |
| AWRA OpsHub | POS + inventory + procurement + finance in one suite, eTIMS built in, KES pricing | Selling needs a connection — offline queueing is mobile-only and covers stock movement, not sales. Weigh that against the demand above |
The evaluation checklist
Make every vendor demonstrate, not describe
- A sale, a return, and a credit note — with the eTIMS transmission shown for each.
- The till selling with WiFi off, then syncing when it returns.
- A shift close where cash + M-Pesa + card reconcile against system takings.
- The stock card updating the instant a sale completes.
- A transfer between two branches, with approval and in-transit visibility.
- The daily report an owner sees: sales, margins, variances, stock alerts — on a phone.
Then apply the commercial filter from our 10 questions for choosing a provider, and pressure-test the three-year cost. For AWRA's answer to all of the above, see the POS system for Kenya and retail POS & inventory pages.
What AWRA OpsHub does today
- Sales at a counter bound to a warehouse, with availability enforced before a sale — no overselling and no override.
- Cash sessions with opening float, expected cash, counted cash, cash drops and a variance, attributed to a named cashier.
- Offline capture for four operations — stock transfers, inventory check-out and check-in, and asset movements — with a sync queue and conflict codes. Selling and counting are not among them.
- eTIMS fiscalisation on sales, which is a real integration and Kenya-only.
- M-Pesa collection via STK push.
- Stock shared with the rest of the system — a POS sale depletes the same stock procurement replenishes.
More we can add to your workspace
- The blind cash count is a discipline, not an enforced lock, unlike the inventory count where blind entry is enforced with a permission to reveal. Every till variance figure depends on the cashier not seeing expected cash first.
- Discounts have no approver field, so a till discount is attributable but not gated by approval.
- Queued eTIMS transmission during an outage. Fiscalisation happens at sync today, which is what makes a long outage a compliance question worth planning for.
- An offline card or mobile-money authorisation.
This is one of the strongest clusters for us and the caveats are narrow. The one to act on is the blind count: the field exists on the inventory side and not on the cash side, so if till variance matters to you, make the count sheet a physical discipline until that changes.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsSee a full retail day, end to end
Sales with enforced availability, eTIMS on the receipt, cash sessions with a named cashier and a valued variance, and stock shared with the rest of the system.
See AWRA for retailFrequently asked questions
What does a POS system cost in Kenya?
Standalone POS apps run from a few thousand shillings monthly; integrated POS-plus-inventory platforms priced locally typically start higher but replace two or three tools. Compare the three-year total including eTIMS compliance, support, and the branch you plan to open — not the first month's price.
Do I need special hardware?
Usually not — modern systems run on Android devices, tablets, or existing PCs with standard receipt printers. Beware vendors whose pricing anchors on proprietary hardware; the lock-in outlives the hardware.
Can one system handle both retail and wholesale counters?
Yes, if it supports price lists per customer type and credit sales alongside cash-and-carry. Ask to see a wholesale invoice on credit and a retail cash sale from the same item list.
How long does switching take for a running shop?
For a single shop: item list and prices imported, one training day, then go-live at the start of a stock-count cycle so opening quantities are verified. A week from decision to first live shift is realistic; branches follow one at a time.
