I grew up watching business happen in ways that most software companies completely ignore.
Not boardrooms. Not e-commerce dashboards. Not SaaS analytics suites. I mean the woman who wakes up at 5am to open her provision shop before the school rush. The man running a hardware store from a single room, keeping every credit transaction in a notebook he's had for three years. The shop owner who knows every customer by name but couldn't tell you, right now today, how much stock she has left or how much she's owed.
That's retail in Ghana. Millions of small businesses, moving real money, completely invisible to the tools that claim to serve them.
Part of why this felt so personal is that I've been on the other side of the counter. I worked as a shopkeeper myself. I know what it's like to track credit in a notebook, to guess at stock levels, to count the cash at closing and still not be sure if the day was profitable. That experience never left me.
What I Kept Seeing
The more I paid attention, the more I noticed the same friction everywhere.
A customer asks for a product. The shopkeeper checks a shelf, then a storeroom, then maybe a second notebook. They're not sure if they have it. Sometimes they guess wrong. They say yes, only to discover they sold the last one yesterday and didn't write it down.
A regular customer buys on credit, which is completely normal in local commerce. The shopkeeper writes it in a ledger. Two weeks later, the customer comes back to settle up. The shopkeeper flips through pages trying to find the entry. If the notebook gets wet, torn, or lost, that debt is gone.
At the end of the day, the owner wants to know: how did we do? They count the cash in the drawer, subtract what was there this morning, and that's it. No breakdown by product. No sense of what sold well or what's been sitting there collecting dust for two months.
It's not that these shop owners aren't smart or capable. They're running businesses with zero margin for error, juggling suppliers, staff, and customers every single day. They just never had a tool built for the way they actually work.
The Existing Options Didn't Fit
I looked at what was out there. There are POS systems. Plenty of them.
Most require a Windows PC or a tablet stand bolted to a counter, a setup that doesn't fit a shop that's six feet wide. Others are priced for mid-size retailers and come with subscription tiers, per-user fees, and support contracts that small shops simply can't absorb. Some require constant internet, but connectivity in Ghana is inconsistent enough that building a business-critical tool on a live connection is a design flaw, not a feature.
And then there's the interface problem. A lot of these systems were designed by engineers who've never been inside a provision shop in Kumasi. The UI assumes a certain kind of user: someone with time to be trained, patience for complexity, a large screen. The shop owners I had in mind are often handling a customer with one hand and their phone with the other.
None of it fit.
The Moment I Decided to Build
There was no single dramatic moment. It was more of an accumulating weight.
I'd been building apps for several years: fintech, logistics, on-demand platforms. I knew what it took. And I kept coming back to this gap. The people who most needed reliable business software were the ones being skipped.
Having worked in a shop myself, I couldn't keep watching the problem and doing nothing about it. At some point I stopped waiting for someone else to build it and started writing the first lines of Trader POS.
The constraints were clear from day one:
- It had to work on an Android phone. That's what's in every pocket.
- It had to work offline. Network is a bonus, not a requirement.
- It had to be fast enough that a cashier could ring up a sale in under ten seconds.
- The credit system had to be first-class, not an afterthought.
Everything else (the backend, the admin dashboard, the iOS app) came after those four things were solid.
The Problems I Set Out to Solve
Invisible inventory. A shopkeeper should know at a glance what they have, what's running low, and what's been moving. Not by memory. Not by counting shelves. The system should track it automatically with every sale and every restock.
Untracked debt. Credit is part of how local commerce works. Refusing it means losing customers. But informal credit is a leakage point. Trader POS gives every customer a ledger: what they owe, what they've paid, and a full history of every transaction.
Zero visibility into daily performance. Was today a good day or a bad day? Which products drove it? Owners deserve answers to those questions without doing mental arithmetic at 9pm.
No paper trail. A thermal receipt printer is cheap. Giving customers a receipt builds trust and reduces disputes. Trader POS supports Bluetooth printers out of the box. If there's no printer, it stores the receipt digitally.
Multi-person shops. Most provision shops aren't solo operations. There's an owner, maybe a manager, and one or two cashiers. They all need different levels of access. The owner shouldn't have to share their full business view with a new cashier, and a cashier shouldn't be able to edit prices or delete records.
Who This Is For
Trader POS isn't for everyone. It's not trying to be.
It's for the shop owner who currently runs everything from a notebook and a memory. It's for the retailer who's been burned by stockouts they didn't see coming. It's for the business that extends credit to loyal customers but has no way to systematically track who owes what.
It's for the kind of businesses that built economies long before any software company noticed them.
I think that's worth building for.
If you want to see what it became: traderpos.app