How a shop tool became Polaris POS
Real problems in the shop
We built our own fix
Years of daily use & iteration
Proven in real operations
Other owners asked for it
Polaris POS today
Revenue was growing. The business wasn't.
On paper, Mars Kitchen Essentials looked healthy. Money came over the counter every day. But the harder question — are we actually better off? — was almost impossible to answer honestly.
We could see sales. We couldn't see profit. Stock went missing with no way to trace it. Expenses were scattered across notebooks and memory. Reports meant sitting down with a calculator at the end of the month and hoping the picture was roughly right. Nobody was accountable for the numbers, because nobody could see the numbers.
Then we closed one branch. Counting what was left exposed how much stock had quietly walked out the door — and how little our existing way of working could tell us about it. That was the moment it became undeniable: we were flying blind, and it was costing us real money.
The everyday problems that pushed us to build.
No real profit view
We knew what we sold, never what we truly made.
Inventory losses
Stock disappeared with no trail back to a cause.
Scattered expenses
Costs lived in notebooks, receipts and heads.
Thin reporting
Answers took a calculator and a hopeful guess.
Manual everything
The same work, re-done by hand, every day.
No accountability
"Someone" gave the discount. No name attached.
Little operational insight
Which hour, which product, which channel? Unknown.
Growth that didn't add up
Busier every year, but not meaningfully ahead.
So we built our own.
We didn't want another imported system priced in dollars, dead without internet, built for a business that works nothing like ours. So we built the tool the shop actually needed — starting at the till, where money moves and the truth is hardest to hide.
There was one rule: every feature had to earn its place by solving a problem we were genuinely having. Nothing went in because another POS had it. If it didn't help us run the shop better, it didn't ship.
Years of daily use, feedback, and improvement.
Polaris POS wasn't designed in one go. It grew the way a good tool should — one real problem at a time, tested on a live shop floor.
-
The starting point
Selling in the dark
A growing kitchenware business running on notebooks, memory and month-end guesswork. Sales visible; profit, stock and expenses were not.
-
The trigger
Closing a branch exposed the losses
Reconciling what was left revealed how much stock had gone missing — and how blind we'd been to it. The decision to build was made here.
-
First build
A till that told the truth
We started where money moves: fast checkout, real cost and margin on every sale, and a record of who did what. For the first time, the numbers weren't a guess.
-
Built for here
It had to work when the power didn't
Load-shedding and dropped connections are normal, not exceptions. So the system was built to keep selling offline and reconcile when the network returned — never a frozen counter, never a lost sale.
-
Years of iteration
One real need at a time
Inventory alerts after a stockout cost us a sale. Expense tracking when revenue alone kept lying to us. Reports because we wanted answers, not spreadsheets. Staff roles and audit logs so accountability didn't slow the team down. Each feature has a scar behind it.
-
Today
Polaris POS — and the platform it's growing into
What proved itself in one shop is now Polaris POS, used by other businesses across East Africa — and the foundation of Polaris, the connected platform for how African business really runs.
Then people started asking for it.
We never advertised it. But customers, neighbouring shop owners and friends would come in and notice: checkout was fast, the shelves were organised, the reports were real, the whole place ran calmer.
The question kept coming back — "Can we use the same software?"
That demand is what turned an internal shop tool into Polaris POS. Not a market opportunity we chased. A tool that worked, that other people wanted for the same reasons we built it.
Lessons we built into the product.
Revenue is not profit
A busy shop can still go backwards. Until you can see cost, margin and expenses together, you're guessing — so we made the real number impossible to hide.
Reliability beats features
A feature that needs perfect internet is useless here. If it doesn't work during load-shedding, on the phone you already own, it doesn't count. Working always comes first.
Accountability without friction
You can't manage what you can't attribute. Every sale, discount and refund carries a name — and it never slows the counter down.
Build only what you need
Every feature earned its place by solving a problem we actually had. Nothing was added to match a competitor's checklist — and it keeps the product honest.
Enter it once
Re-keying the same information into three places is where errors live. One sale should update stock, books and reports on its own — so it does.
Someone has to stay
Tools built for a handover die on handover. We run our own business on this — so it's maintained, supported on WhatsApp, and improved for the long term.
It solved our business first. Let it look at yours.
Book a walkthrough and we'll show you Polaris POS with your kind of business in mind — the same tool that fixed ours. No pressure, just a real conversation about how your shop runs.