CRM, inventory, order and stock management
Africa Business System Development | Multiple currencies, multiple entities, cash and credit together
The usual financial pattern is local-currency collection, USD settlement, cash and credit running in parallel, and significant exchange-rate movement. Systems must handle all of these and still allow invoicing when the network is down, synchronising once connectivity returns.
Scope of Business System Development
The activities below are the ones we own on this type of project, delivered in phases and confirmed item by item. Where third-party hardware or licences are involved, the procurement list, licensing requirements and responsibility split are set out at solution stage.
Approval workflows, contracts and financial reconciliation
Multi-store, multi-warehouse, multi-currency and multi-entity accounting
Integration with ERP, payment, logistics and tax systems
Reporting dashboards and operational analytics
Deliverables
Every item is archivable and transferable, so an internal team or a third party can maintain the system later.
- Current-state and target process maps
- Data model and permission matrix
- System source code, database scripts and migration plan
- API documentation and third-party integration records
- Training materials and acceptance report
Typical technology stack
Selected against the existing environment and the capabilities of your team, with maintainability and future extension in mind.
Implementation phases
Each phase produces a confirmable output and an acceptance record, so issues are resolved within the phase.
Phase 01
Process review
Map existing spreadsheets, legacy systems and manual steps; identify where duplicate entry and reconciliation cost the most
Phase 02
Scope and model
Confirm first-phase modules, role permissions and data migration boundary
Phase 03
Build and parallel run
Bring core modules live first, then validate data through a parallel run
Phase 04
Cutover and support
Retire the old system, archive data and provide a supervised stabilisation period
Compliance considerations in Africa
For Business System Development, the requirements below directly affect data structures, page behaviour and deployment. We confirm each item during solution design; formal legal advice should be confirmed with a local adviser.
Protection of Personal Information Act (POPIA)
POPIA has been fully enforced since July 2021, requiring lawful processing conditions, purpose limitation, notification duties, data subject rights and security measures, with conditions attached to cross-border transfer. An information regulator oversees compliance and handles complaints.
Data Protection Act (NDPA 2023)
The 2023 Act replaced the earlier regulation, established the Nigeria Data Protection Commission, and sets processing principles, data subject rights, cross-border transfer conditions and penalties. Businesses processing large volumes of user data are expected to designate a data protection officer.
Data Protection Act (DPA 2019)
Registration as a data controller or processor is required, together with consent, notification of purpose and rights, and evidence of adequate protection for cross-border transfer. The Office of the Data Protection Commissioner supervises compliance.
Personal Data Protection Law (Law 151/2020)
The law sets requirements for consent, purpose limitation, data subject rights and cross-border transfer, with special licences required for certain data categories. Implementing regulations and enforcement timing follow the competent authority’s publications.
PDPA 2022 / Data Protection Act 843
Tanzania’s 2022 Personal Data Protection Act requires registration and compliance audits; Ghana’s Data Protection Act requires processing registration, consent and security measures. Both set conditions for cross-border transfer.
Mobile wallets and local payment compliance
Mobile wallets fall under local financial regulation, and businesses that collect or disburse funds on behalf of others usually need to work with a licensed institution. We confirm fund flows and the business model before deciding the technical approach, so compliance exposure is not created at the design stage.
Africa cases involving this service
The following projects involve Business System Development. Each shows how the challenge was scoped and what was delivered.
Road project cost and progress system, Lagos
Client: Chinese engineering contractor in Lagos (roads and municipal works)
Challenge
Projects were spread across several states and consolidated by weekly reports. Diesel, bitumen and aggregate consumption was recorded on site, so over-consumption surfaced late. Equipment utilisation was unclear, and hired and owned equipment costs were mixed together.
What we delivered
- Work item progress reporting with site photographs and location data attached
- Material and fuel ledgers consolidating consumption by machine and by work item
- Equipment management covering owned and hired machine hours, maintenance and cost
- Cost dashboard comparing budget and actual, with over-consumption alerts
Outcome
Material over-consumption is identified mid-project rather than settled at completion. Equipment cost consolidates by project, giving quotations a basis, and progress records with photographs answer client enquiries quickly.
Mine site materials and workforce system, Tanzania
Client: Chinese mining services company in Dar es Salaam (site materials and logistics)
Challenge
Sites are far from the city and replenishment cycles are long, so a missing item stops work. Workforce entry and hours were recorded on paper, producing payroll disputes. Fuel and spare parts consumption was unclear.
What we delivered
- Material inventory with safety stock alerts generated against replenishment cycles
- Workforce entry and hours registration, with attendance data captured offline
- Fuel and spare parts issue ledgers consolidated by team and by machine
- Site dashboard covering stock, headcount on shift and daily consumption
Outcome
Stockout stoppages decreased. Hours data is traceable, reducing payroll disputes, and fuel and parts consumption now has a comparison baseline so anomalies are visible.
Multi-currency wholesale inventory system, Lagos
Client: Chinese trade wholesaler in Lagos (building materials and household goods)
Challenge
Purchasing in USD and selling in naira while the rate moved daily meant quotations frequently ran at a loss. Credit was widespread and receivables were kept in a notebook. Warehouse and store stock did not agree.
What we delivered
- Multi-currency purchasing and sales with exchange-rate snapshots and gain/loss accounting
- Customer credit limits and payment terms, with automatic order blocking on overdue balances
- Shared stock between stores and warehouse, with transfers and stock counts
- Receivables dashboard by customer, salesperson and ageing
Outcome
Exchange gain and loss is separately visible, so quotations can compute a floor price. Receivables are traceable with a basis for collection, and a single stock basis reduced overselling.
Building materials factory and dealer ordering, Nairobi
Client: Chinese building materials manufacturer in Nairobi (roofing and wall materials)
Challenge
Dealers ordered by phone and WhatsApp and orders were transcribed by hand. Production scheduling ran on experience, so some specifications were out of stock while others piled up. Delivery and collection were tracked separately.
What we delivered
- Dealer ordering app with ordering by specification and visibility of stock and in-transit quantities
- Production scheduling generating proposals from orders and stock
- Delivery and receipt with driver confirmation and electronic proof of delivery
- Collection management reconciling order, dispatch and payment three ways
Outcome
Orders moved from chat history into the system, reducing missed orders. Scheduling now has a basis, cutting both stockouts and overstock, and collection can be matched to dispatch, making follow-up precise.
Agro-processing intake and settlement system, Tanzania
Client: Chinese agro-processing company in Tanzania (maize and oilseed)
Challenge
During harvest, growers delivered in concentrated volumes and queued for weighing and settlement. Moisture and impurity testing was recorded by hand, causing price disputes. Large volumes of cash settlement did not match documentation.
What we delivered
- Automatic weighbridge capture with tickets bound to grower records
- Quality metric entry with grade-based pricing and on-the-spot settlement printing
- Grower records and delivery history supporting advance deduction
- Intake dashboard covering daily volume, average price and quality distribution
Outcome
Settlement moved from hours of queuing to an on-the-spot document. Quality data is recorded, reducing price disputes, and daily intake is visible the same day, making cash planning easier.
Port clearance and inland transport coordination, Mombasa
Client: Chinese logistics company in Mombasa (clearance and inland transport)
Challenge
The chain from port to inland destination is long and shippers could not see live status. Clearance documents and transport documents were disconnected. Demurrage occurred regularly without clarity on which stage was responsible.
What we delivered
- Document and transport linkage managed by shipment, with automatic milestone timestamps
- Vehicle scheduling and in-transit tracking with abnormal-stop alerts
- Customer portal for status and estimated arrival by shipment number
- Demurrage and detention cost attribution analysis
Outcome
Shippers check status themselves, reducing repeat enquiries. Milestone timestamps make responsibility traceable, so demurrage disputes have evidence, and scheduling is more balanced with less empty running.
Mobile money agent network management, Nairobi
Client: Chinese mobile money agent operator in Nairobi (community agent network)
Challenge
Agents are dispersed and cash did not reconcile against electronic balances. Commission settlement was checked manually. Device and training status across the network was unknown.
What we delivered
- Agent records and device management, including training and compliance status
- Daily reconciliation comparing cash, electronic balance and transaction records three ways
- Commission calculation and settlement statements generated by agent and period
- Anomaly and limit monitoring with threshold alerts
Outcome
Reconciliation moved from manual checking to a discrepancy list. Commission settlement is automated, raising agent confidence, and anomalous transactions are identified promptly.
Restaurant and food delivery system, Johannesburg
Client: Chinese restaurant and food delivery business in Johannesburg (central kitchen plus delivery)
Challenge
Delivery routes from the central kitchen to stores and direct customers were not optimised, and food arrived below temperature. Orders arrived by phone, WhatsApp and platforms and were easily missed. When power failed, the POS could not issue orders.
What we delivered
- Order aggregation pooling phone, messaging and platform orders into one queue
- Delivery scheduling and route optimisation allocated by time window and area
- Offline order entry with synchronisation on recovery, covering power and network loss
- Temperature and timeliness records with automatic overdue alerts
Outcome
Missed orders fell noticeably. Routes became more efficient, reducing late and temperature complaints, and trading continues during power cuts.
Case note: client names are anonymised under confidentiality agreements; cases are presented to explain implementation approach and delivery boundaries, and specific figures are subject to project acceptance records.
Business System Development FAQ
The first three answers are general; the last two address conditions specific to Africa.
Can you extend an existing ERP?
Often, yes, but it is worth assessing first. Where the ERP exposes standard APIs we build peripheral systems and integrate; where only source modification is possible, we assess upgrade risk before committing.
Will data migration lose records?
We take a full backup and build a field mapping table, then run a trial migration and reconcile totals and sampled records. The legacy database stays read-only on cutover day until sign-off.
Will it cope with concurrent users?
Sizing follows expected concurrency. With sound indexing and caching, typical SME systems handle tens to hundreds of concurrent users; peak or bulk-entry scenarios are load tested as part of the plan.
How are timelines and meeting times arranged for Business System Development in Africa?
Meetings and confirmation points follow the working hours common in Africa (UTC+1 to UTC+3, 5–7 hours behind Chengdu). Requirements and solution design include a written progress update every week; development delivers a runnable build every two weeks. For cross-timezone work, key confirmations are placed inside the overlap of both working days, so progress never stalls waiting on a reply.
Which local compliance requirements should be confirmed in advance for Business System Development in Africa?
Projects in Africa typically involve Protection of Personal Information Act (POPIA), Data Protection Act (NDPA 2023), Data Protection Act (DPA 2019). These requirements directly shape data structures, page behaviour, hosting location and data retention, so each is confirmed at solution stage and recorded in the delivery documentation. Formal legal advice should be confirmed with a local adviser.
Other services in Africa
Most projects combine two or three services, for example a website followed by a business system, or AI capabilities added after a system goes live.
Mobile App Development
An app must complete core actions on low-end phones and weak networks
Website Development
A corporate site has to establish credibility before it looks impressive
AI Application Development
AI first where it removes labour, not where it impresses
IoT Development
Power and network loss are the default, not an exception
System Operations & Maintenance
Remote maintainability matters more than on-site support