The problem we saw on the ground
Most SMEs in Angola manage inventory in spreadsheets, notebooks, or generic systems that don't reflect operational reality. Stock losses, undetected stockouts, and gut-feel decisions are the norm. When we visited over 15 businesses across Luanda and Benguela, we found clear patterns: no multi-store visibility, zero alert automation, and teams spending hours reconciling data manually.
StockFlowPro design principles
We defined three principles before writing a single line of code. First, simplicity — if the warehouse manager can't use the tool within 10 minutes, we've failed. Second, offline-first — connectivity across much of Angola is intermittent, so sync needs to work when the network returns. Third, affordable pricing — African SMEs operate on tight margins, so the pricing model had to be proportional to the value delivered.
Technical architecture
StockFlowPro is a progressive web app (PWA) built with React on the frontend and Node.js on the backend, with a PostgreSQL database. The sync layer uses an event-sourcing model that resolves conflicts when multiple stores update data in parallel. The REST API serves both the web dashboard and the future mobile app. We host on servers with a CDN to minimise latency across the SADC region.
Features that solve real problems
Real-time stock control with a visual dashboard. Automatic alerts when stock reaches user-configurable thresholds. Multi-store sync in real time — the manager sees inventory across Luanda, Benguela, and Cabinda on a single screen. Operational reports showing movements, trends, and restocking forecasts. Existing inventory import via CSV, so migration doesn't halt operations.
Concrete results
A retail chain with 4 stores in Luanda reduced inventory losses by 34% in the first 3 months. Time spent on manual reconciliation dropped from 12 hours per week to under 1 hour. Restocking decisions shifted to data-driven, eliminating frequent stockouts that were costing an estimated $8,000 USD per month in lost sales.
Lessons learned
Building software for SMEs in Africa requires closeness to the customer. Field feedback shaped 60% of the features we released in the first year. In-person training remains the most effective adoption method — more so than video tutorials. And the ongoing support model is as important as the product itself.