Case study
MbuiTech POS: Retail Deployment
How we built and deploy MbuiTech POS: the engineering behind offline-tolerant tills, live multi-branch stock and staff accountability in Kenyan retail conditions.
The challenge
Kenyan retail runs in conditions generic POS software often ignores: internet interruptions at the worst moment, month-end queues, cash-and-M-PESA mixed payments, and branches whose stock records drift apart. Shops needed a till that keeps serving customers offline and an owner's view that reconciles every branch by morning.
Our approach
We designed around the worst network day, not the best. The till is a fast client application against a local store, with a sync layer that queues transactions when connectivity drops and replays them safely when it returns. Conflict rules are explicit and idempotent, the same sale can never be applied twice.
Stock truth lives server-side; tills hold a working copy. Reporting consolidates branches nightly and on demand, so the owner's dashboard reflects the whole business, not whichever branch synced last.
Implementation
The platform pairs a responsive till interface with a PHP/MySQL backend. Barcodes, receipt printing and cash-drawer control are integrated at the till. Staff accounts carry shift and role context, so every sale, discount and void is attributable. M-PESA payments are recorded against the sale with reconciliation to till cash-up.
Deployment is per-shop: catalogue import, hardware setup, cashier training and a supported go-live day. Updates are staged so tills in different branches can run the same version window.
Technology and integrations
- PHP and MySQL backend with queued, idempotent sync
- Local-first till application with offline tolerance
- Barcode, receipt and cash-drawer hardware integration
- M-PESA payment recording and cash-up reconciliation
- Multi-branch consolidation reporting
Outcome
The product is in active use as our retail platform: tills stay usable through outages, stock reconciles across branches, and owners get a single morning report instead of branch-by-branch phone calls. Every deployment feeds engineering improvements back into the product.
MbuiTech POS is presented in full on its product website and on the MbuiTech POS product page.
Lessons learnt
- Offline tolerance is a design decision, not a feature. Building it from day one was far cheaper than bolting sync onto an online-only till.
- Accountability changes behaviour. Attributable discounts and voids reduced till variance more than any policy memo.
- Training day is go-live day. Cashiers adopt software in the first two hours; everything after is reinforcement.
Services used on this project
Building something similar?
If your organisation faces a comparable challenge, we can apply the same engineering approach to your context, starting with a free consultation.