One System for All Your Branches: Stop Juggling Spreadsheets Across Nairobi, Mombasa and Kisumu
Learn how a single POS, inventory and ERP system can replace five spreadsheets, cut manual work and keep your branches in sync.
Orwan Consulting27 August 20269 min read
One System for All Your Branches: Stop Juggling Spreadsheets Across Nairobi, Mombasa and Kisumu
Open
Morning routine in Nakuru
It is Tuesday morning in Nakuru. The owner of a small retail chain checks the WhatsApp group where branch managers post daily sales figures. One manager sends a photo of a handwritten tally sheet, another forwards an M-Pesa statement, and the third calls to say the internet went down again, so the offline sales book is still at the shop.
Time spent reconciling numbers
By 10 a.m. the owner has spent an hour reconciling numbers, updating a master Excel file, and worrying about whether the KRA eTIMS invoices printed yesterday match the cash collected. This scene repeats in many Kenyan towns where businesses run on spreadsheets, paper books and WhatsApp chats instead of a single system.
Impact on owner’s day
Consider the owner’s routine after the WhatsApp check: they hop on a motorbike to visit the Nakuru outlet, glance at the shelf to see if the popular maize flour is running low, then jot down a quick note on a scrap of paper before heading back to the office to enter the observation into the master sheet. This back-and-forth eats up valuable time that could be spent negotiating with suppliers or training new cashiers.
The problem
Admin burden and time cost
Running multiple branches with separate spreadsheets costs time, money and trust. Each morning managers spend 30-45 minutes copying sales from paper or phone into a central sheet, a task that adds up to over 10 hours a month per outlet.
Errors and stock issues
Errors creep in – a missed M-Pesa transaction, a duplicated stock entry – leading to stock-outs or excess inventory that ties up cash.
Impact on decision‑making
When the owner needs a quick view of performance across Nairobi, Mombasa and Kisumu, the data is stale, forcing decisions based on guesswork.
Security and compliance risks
Limited internal IT capacity means no one can maintain five different tools, and the reliance on WhatsApp for updates creates security risks and makes it hard to prove compliance during a KRA audit. The result is lost sales, higher admin costs and frustration for staff who would rather serve customers than reconcile numbers.
Staff demotivation
Beyond the immediate admin burden, these errors translate into real-world missed opportunities. A duplicated stock entry might show twenty packets of tea in the system while the shelf actually holds only five, causing the shop to turn away customers who ask for their favourite brand. Conversely, a missed M-Pesa payment can leave the till short, prompting the owner to dip into personal funds to cover the day’s expenses, which erodes trust and strains cash flow. Staff who spend their mornings reconciling sheets often feel demotivated, knowing that the same effort could be redirected toward arranging attractive displays or learning about new product lines that could boost sales.
How it works in Kenya
Unified POS, inventory and ERP
A unified system brings together POS, inventory and ERP functions that work online and offline. Sales made at the till – whether cash, M-Pesa STK push, Lipa Na M-Pesa or bank card – are recorded instantly in the POS. The inventory module deducts stock in real time; if the branch loses connectivity, the app continues to capture sales and stock changes locally, then syncs when the network returns, guaranteeing zero data loss. The ERP layer handles invoicing that is automatically eTIMS‑compliant, sends the XML to KRA and stores a copy for your records. All branches feed into a central dashboard that shows sales by outlet, stock levels and cash flow, updated every few minutes. Because the system is built for Kenya, it integrates directly with Safaricom Daraja, Airtel Money and major bank APIs, so reconciliation matches what appears in your M-Pesa statement. Staff use the same interface on a tablet or phone, reducing the need for multiple tools and training.
Offline capability and sync
When the device goes offline, sales are stored in an encrypted local database that timestamps each transaction. As soon as the SIM detects a 3G or 4G signal, the app initiates a secure sync, pushing the batch of sales to the cloud and pulling down any updated price lists or promotional offers that may have been pushed from headquarters.
eTIMS invoicing and QR code
The eTIMS module automatically generates the required XML file, attaches a QR code for easy verification by KRA officers, and archives a PDF copy for internal audit trails. This seamless flow means that even during a sudden downpour that knocks out the tower near a Kisumu outlet, no sale is lost and the owner still sees an accurate picture of stock levels across all outlets the moment connectivity is restored.
Integration with payment gateways
Because the system is built for Kenya, it integrates directly with Safaricom Daraja, Airtel Money and major bank APIs, so reconciliation matches what appears in your M-Pesa statement.
Real-time dashboard
All branches feed into a central dashboard that shows sales by outlet, stock levels and cash flow, updated every few minutes.
Where businesses go wrong
Patchwork of separate apps
First, many try to patch together separate apps – a website for orders, a WhatsApp group for communication, a spreadsheet for inventory – and expect them to talk to each other. This creates duplicate work; a sale entered on the website must be manually copied into the stock sheet, costing roughly two hours a day per branch.
Reliance on constant high‑speed internet
Second, they choose software that requires constant high-speed internet. Outside Nairobi’s core, connections drop several times a day, causing the app to lose unsold sales data and forcing staff to revert to paper.
Overlooking payment reconciliation
Third, they overlook payment reconciliation. Without built-in M-Pesa matching, the finance team spends an extra day each month tracing missing transactions, which can lead to under-reported revenue and penalties during KRA filing.
Ignoring offline capability
Fourth, they ignore offline capability, assuming the cloud will always be reachable, which leads to missed sales during network outages.
Systems that cannot scale
Finally, they purchase a system that cannot scale; adding a new branch means buying another license and re-training staff, instead of simply adding a new outlet to the existing platform.
Illustrative patchwork workflow
In practice, the patchwork approach often looks like this: a manager receives a customer order via Facebook Messenger, writes the details on a notebook, then later enters the same information into a Google Sheet for inventory, while the sales figure is also copied into a separate Excel file for daily takings. Each step introduces a chance for a typo or a transposed digit, and the manager ends up spending the better part of the afternoon just keeping the three sources in sync. When the rains intensify and the mobile network flickers, the offline sales book piles up, and the manager must stay late to re-enter everything once the signal returns, delaying the next day’s ordering cycle and leaving shelves under-stocked.
The path forward
Illustrative case: Kisumu boutique before and after
Before: A boutique in Kisumu uses three spreadsheets – one for sales, one for stock, one for M-Pesa receipts – updated each evening by the shop owner. After a busy weekend, the stock sheet shows 20 units of a popular dress, but the shop floor actually has only five, leading to a lost sale and a disappointed customer.
After: The same boutique installs a POS system that runs on a low-cost Android tablet. Sales are entered via the touchscreen, stock deducts automatically, and the device stores data offline until the evening when the Wi-Fi at the shop reconnects and syncs with the cloud. The owner sees a live dashboard showing Kisumu stock at five units, triggers a reorder from the Nairobi warehouse, and the dress is back on the shelf before the next customer arrives. The tablet also prints a receipt with a QR code that links to the eTIMS invoice, giving the customer proof of purchase and the owner an instant audit trail.
Step 1: Map one branch’s daily workflow
Map one branch’s daily workflow – write down how sales are recorded, how stock is counted and how M-Pesa is reconciled.
Step 2: List the three biggest pain points
List the three biggest pain points you notice (e.g., time spent on spreadsheets, stock‑outs, internet dropouts).
Step 3: Identify a staff champion
Identify a staff member who can act as a system champion during the initial rollout, responsible for answering quick questions and logging any issues.
Step 4: Book a free discovery session
Book a free discovery session with Orwan Consulting in Nairobi – we will review your map, show a fixed‑scope proposal for a POS, inventory and ERP system that works offline, integrates with M-Pesa and eTIMS, and can be rolled out to all branches.
What it costs
Basic POS system pricing
A basic POS system with inventory tracking starts at KES 80,000.
ERP module pricing
Adding an ERP module for invoicing, purchase orders and basic accounting brings the range to KES 200,000–500,000 depending on the number of branches and modules.
Mobile app and website add‑ons
A mobile app for field staff or customers can be added from KES 150,000, and a responsive website from KES 50,000 (complex sites up to KES 300,000).
Hosting fees
Hosting is from KES 2,000 per month.
Fixed‑scope pricing
These are fixed‑scope prices; you know the total before any work begins.
Basic POS package contents
The basic POS package typically includes a touchscreen tablet, a Bluetooth receipt printer, a cash drawer, a barcode scanner, and a user guide that walks staff through opening and closing shifts, processing returns, and running end‑of‑day reports.
Training and support
Training is delivered on‑site, with a focus on practical exercises such as processing an M-Pesa STK push, checking real‑time stock levels, and generating an eTIMS invoice for a sample sale. Ongoing support is provided via a dedicated help desk that can be reached by phone or WhatsApp, ensuring that any question about syncing or reporting is answered promptly.
Common questions
Will the system work if my branch has poor internet?
Yes. The POS and inventory apps store data locally and sync automatically when connectivity returns, so no sales are lost.
Do I need to replace my existing website?
Not necessarily. The new system can link to your current site for online orders, or we can build a simple, mobile‑first site from KES 50,000 if you need one.
How long does implementation take?
A typical rollout for three branches – POS, inventory and ERP – takes six to eight weeks, with weekly increments you can test and approve.
What happens to my data if the device is stolen or damaged?
All data entered on the device is encrypted and backed up to the cloud the moment a connection is available. If the device is lost, you can remotely wipe it through the management console and restore the latest backup on a replacement tablet, ensuring that no sales records are compromised.
Close
Next steps
If you are tired of chasing numbers across spreadsheets and want a single system that keeps your branches in sync, talk to us. Book a free discovery session with Orwan Consulting in Nairobi — we map your processes and show you exactly what we would build, as a fixed‑cost proposal. Starting with a pilot branch lets you see the benefits in action before expanding to the rest of your network.
