
Uganda
A POS built for how Uganda actually pays
Most of your customers reach for a phone, not a wallet — MTN Mobile Money and Airtel Money settle the majority of retail payments in Uganda, and the two do not talk to each other.
So the day ends with a MoMo statement, an Airtel statement, a cash drawer and a notebook, and you reconcile all four by hand to find out what you actually sold.
Then URA wants an EFRIS invoice against it, with the line detail to match.
What you get
How Uganda pays
MTN Mobile Money
Uganda's largest rail. Record it against the sale at the counter, so the MoMo total and the day's sales agree without you reconciling two statements.
Airtel Money
The second rail, and rarely the same customers. Both land in the same day's takings rather than two separate books.
Cash, with change
Still a large share of duka and market trade. The till does the arithmetic in shillings so a busy counter does not.
Card and bank transfer
For the corporate and NGO buyers who will not pay any other way, recorded against the same invoice.
EFRIS, and what sell.ke holds for it
URA requires VAT-registered businesses to issue invoices through EFRIS — the Electronic Fiscal Receipting and Invoicing Solution. The filing needs the detail of the sale, not just its total: each line item, quantity, unit price, the tax treatment, and the buyer's TIN where one is given.
sell.ke records every sale at that level of detail as a matter of course, because that is also what stock control and margin reporting need. When you file, the underlying data is already there and already itemised, rather than being reconstructed from a till roll at the end of the month.
sell.ke does not submit to EFRIS on your behalf. Kenya's KRA eTIMS is the one revenue-authority integration the platform ships today; in Uganda the platform is the record, and the filing stays yours.
- Line-level detail on every sale — item, quantity, unit price, tax treatment
- Buyer details captured at the counter when the customer needs an invoice
- Exportable sales and tax reports for the filing period
- Per-branch totals, so a multi-shop business files from real numbers
What you get
What that means for your shop in Uganda
Priced in shillings, reported in shillings
No mental conversion and no spreadsheet doing FX. Stock values, margins and day-end totals are all in UGX.
Keeps selling when the network drops
Upcountry connectivity is not a given. The till runs offline and syncs the backlog when the line returns — nobody waits at the counter.
Kampala stock, upcountry stock, one view
Branch-level stock and per-branch takings, so a second or third shop does not mean a second or third set of books.
Staff who see only their own lane
Cashiers see prices and stock; margins, supplier costs and reports stay with the owner and managers.
Your trade in Uganda
The same platform, written for how your trade actually works here.
Supermarket POS (Uganda)
Two rails at every till, thousands of SKUs, and an EFRIS filing that wants the lines.
Pharmacy POS (Uganda)
Batch and expiry under NDA licensing, dispensing by strip, and EFRIS on the invoice.
Restaurant POS (Uganda)
Orders to the kitchen, recipes that deduct stock, and a MoMo split bill that still reconciles.
Hardware shop POS (Uganda)
Contractors on credit, cement by the bag, and a B2B invoice that needs a TIN on it.
The two things that decide it
The revenue authority and the rail your customers actually pay on, each at the depth they deserve.
EFRIS and your POS (Uganda)
Every sale held at the line detail a URA e-invoice needs, before you go to file it.
MTN MoMo at the till
Every MoMo payment attached to the sale that earned it, instead of a statement you read at night.
Airtel Money at the till
The second rail is a third of your takings and usually a separate book. It should not be.
The features this leans on
Each one goes deeper than this page does — start with the first.
Selling at the counter
Split payments, held orders, manager-gated discounts and a drawer count that reconciles.
Stock you can trust
Batch and expiry, serial numbers, reorder levels, stock takes and the formulas behind them.
Reports and real accounting
Double-entry books — trial balance, P&L, balance sheet — not a CSV export to somebody else's software.
Branches, staff and control
Shared catalogue, separate stock, transfers that are movements, and permissions per branch.
Questions
Questions from Uganda
Does sell.ke work with MTN Mobile Money and Airtel Money in Uganda?
Both are recorded against the sale at the counter, so your MoMo and Airtel takings reconcile against the day's sales instead of sitting in two separate statements. Ugandan businesses run sell.ke on both rails today.
Can sell.ke file my EFRIS invoices with URA?
No — sell.ke does not submit to EFRIS on your behalf. What it does is hold every sale at the line-item detail an EFRIS filing needs, and export it for the period, so the filing is a transfer of data you already have rather than a reconstruction. KRA eTIMS in Kenya is currently the only revenue-authority integration the platform ships.
Is sell.ke priced in Ugandan shillings?
Your shop runs in UGX — prices, stock values, margins and reports. Subscription billing is quoted in KES; talk to the team about settlement in shillings.
Will it work outside Kampala?
Yes. The till is offline-first: it keeps taking sales with no connection and syncs when the network returns, which matters more upcountry than it does in Kampala.
Can I use it for more than one shop?
Yes. Branches share one product catalogue but hold their own stock, so a transfer between them is a recorded movement rather than a re-count. Reports run per branch or across all of them, and staff permissions are set per branch — a Kisumu supervisor does not need to see Nairobi's margins.
Do I need internet?
Not to keep selling. Offline mode lets the till take sales, print receipts and reserve stock while the connection is down, then syncs everything when it returns. You do need connectivity for the parts that are inherently online: an M-Pesa STK push, an eTIMS submission and the online shop all need a live link.
How long does setup take?
A single-counter duka is usually selling the same day. The work is the product list, not the software: import a CSV or let Amina create products from a supplier invoice or a photo of your price list. A multi-branch business with thousands of SKUs, opening stock counts and an eTIMS enrolment should plan a week and run the old system in parallel for a fortnight.
Try it in your Uganda shop
Fourteen days, no card, no hardware to buy. Your prices, stock and reports all run in UGX.