Mining & Industrial Supply in Southern Africa: Site Stores, Spares and Contractor Custody
The businesses that supply and service mines run the hardest inventory problem in the region — critical spares nobody can quantify, consumables issued without paperwork, and tools that walk off site with a contractor. What actually works, and the honest line on where an operations system stops and mine planning or maintenance software begins.
The Copperbelt, the Bushveld, Selebi-Phikwe and the corridors between them are served by a category of business that rarely appears in software marketing: the supplier, fabricator, contractor and service company whose entire operation exists to keep somebody else's plant running. They hold stock nobody else wants to hold, at sites nobody visits casually, issued to people who are not their employees, against a purchase order that arrived by WhatsApp.
Their operational problem is not complexity in the ERP sense. It is custody, distance and the fact that stopping to do paperwork costs more than the item is worth — until the day it does not.
Four problems, and only one is about software
Every supply and service business in this sector recognises these. Most have solved the first two with heroics and none of them survives an audit or a growth spurt.
- Critical spares you cannot quantify. The item that costs a hundred dollars and stops a plant if it is missing sits in the same store as the item that costs ten thousand and turns over twice a year. Ordinary reorder logic treats them the same, which is how one of them is always out.
- Consumables issued without a record. Grease, filters, welding rod, bits, gloves. Individually trivial, collectively the difference between a healthy gross margin and an unexplained one, and almost never captured at the moment of issue.
- Tools and equipment in someone else's hands. A contractor takes a torque wrench to a site four hours away and the record of that lives in a supervisor's memory. Nobody notices until demobilisation.
- Site stores that are effectively a separate company. The remote store keeps its own book because head office's system is unreachable and unreliable from there. Two truths, reconciled monthly, disagreed with constantly.
Only the fourth is genuinely a systems problem. The other three are capture problems, which is a more encouraging diagnosis than it sounds — capture problems are fixed by making capture easier than not capturing, not by buying more features.
Segmenting stock by what failure costs
The single highest-return change in this sector is refusing to manage all stock the same way. Classify by consequence of a stockout rather than by value, and let the classification drive different rules.
| Class | What it is | How it should be governed |
|---|---|---|
| Plant-critical spares | Failure stops production somewhere | Named minimum on hand, physically segregated, counted monthly, issue requires an authorised requisition naming the equipment it went to |
| Standard spares | Failure delays but does not stop | Reorder points with real lead times, including the customs and road leg — not the supplier's quoted lead time |
| Bulk consumables | Cheap, high volume, invisible | Issued against a job or cost centre every time, no exceptions. This is where margin quietly leaves the business |
| Tools and equipment | Returnable, and frequently not returned | Not stock at all — an asset with a named custodian, an expected return date and a verification history |
| Fuel and lubricants | Measured rather than counted | Treated as consumption against equipment or job, reconciled to deliveries, with variance investigated rather than absorbed |
The classification most businesses skip
Tools are not inventory. Treating a returnable torque wrench as a stock item means it is "issued" and gone; treating it as an asset with a named custodian means the system can tell you who has it, where it went, when it was due back and when it was last physically verified. The distinction costs nothing to make at setup and is nearly impossible to retrofit once three years of issues are recorded the wrong way.
The site store problem
A store four hours from head office, on a mine site with restricted access and unreliable connectivity, is where most systems in this sector quietly fail. The store keeper does the sensible thing — keeps a book — and within a quarter the system holds a fiction.
The fix is not better discipline. It is making the system usable from where the work happens, which means capture that does not require a connection at the moment of the transaction.
-
The store is a location in the system, not a spreadsheet
It holds its own stock position, receives transfers from the main warehouse, and issues against jobs. One system, several locations — not several systems.
-
Transfers show goods in transit
Stock that has left the main warehouse and not yet been confirmed received belongs to neither location. This one behaviour removes most of the monthly argument between the two stores.
-
Capture works offline
Receipts, issues and counts recorded on a phone at the store, queued locally, and synced when the device reaches a signal — each operation carrying its own identifier so nothing arrives twice.
-
Issues name the job or the equipment
Not "issued to workshop". Issued against the job number or the equipment reference, which is what makes consumable cost visible per contract afterwards.
-
Counts happen on a rhythm, not after an incident
Monthly on plant-critical spares, quarterly on the rest. A count only triggered by suspicion is an accusation; a count on a calendar is a control.
Procurement gates that survive an urgent order
Every governance framework in this sector dies the same death: a breakdown at 03:00, a supervisor who buys the part, and a purchase order raised three days later to make the paperwork agree. Do that eleven times and the control no longer exists — everyone has learned that the approval is decorative.
The answer is not stricter rules. It is an emergency path that is legitimate, visible and reviewed.
If the purchase can wait
The normal gate
Requisition, approval against a threshold that refuses rather than warns, purchase order to the supplier, goods received against the order, invoice matched three ways. Slow by design, and the design is the point.
If production is down
A named emergency path
A defined route with a smaller approver list, a value ceiling and a mandatory reason — recorded as an emergency purchase at the moment it happens, not reclassified afterwards. It is still governed; it is simply governed faster.
If it happened anyway
The retrospective, counted
Someone bought without either path. Record it as what it was and report the count monthly. A business that knows it had nine retrospective purchases last month can fix the cause. One that quietly regularises them cannot.
A control that bends for every emergency is not a control. A control with a legitimate fast path, and a monthly count of the times it was bypassed anyway, is.
Contractor custody, which is where the losses are
Assets in the hands of people who are not on your payroll behave differently from assets issued to staff. There is no HR process at the end to catch them, demobilisation is often abrupt, and the person who authorised the issue may have left the project before the equipment does.
The register has to carry the relationship, not just the item: who holds it, where, under which contract, due back when, and verified physically at some point since it was issued. Recording custody is a thirty-second action at issue and an archaeology project six months later — the whole discipline turns on doing it at the counter.
The general version of that discipline, including labelling and verification rhythm, is in asset tracking and custody, and the maintenance-record boundary in maintenance records that actually get kept.
The straight answer for this sector
What AWRA OpsHub does today
- Multi-location stock with governed transfers, including in-transit visibility between a main warehouse and remote site stores.
- Item classification, batches, reorder points and variance reporting against physical counts.
- Requisition, approval, purchase order, goods receipt and three-way matching, with thresholds that refuse rather than warn.
- Asset registers with named custody, expected return dates, movement history, physical verification records and barcode or QR labelling with optional GPS capture on checkout, return, transfer and verification.
- Job and project tracking so issues and purchases can be costed to the contract they were consumed on.
- Offline capture on mobile with a device register, queued operations, duplicate-safe sync and a conflict view — which is what makes a remote site store viable at all.
- Landed cost from freight, duty, clearing and inland transport, allocated onto the receipt.
What it does not do
- No mine planning, geology, survey or production scheduling. Nothing in this product touches the orebody or the plan.
- No maintenance management system. There is no preventive-maintenance scheduler, no service interval per asset, no meter or engine-hours tracking, and no work orders with labour and parts booked against them. A maintenance trip is recorded as a movement, not a job card.
- No automatic cost roll-up per asset. Repair invoices live in purchasing and expenses; tying spend to a specific machine is a coding convention you enforce, not a total the register computes.
- No fleet telematics or fuel-card integration. Fuel is recorded as consumption and reconciled to deliveries; it is not read from a pump or a vehicle.
- No weighbridge, SCADA or plant-control integration.
- No transmission to any Southern African revenue authority, and no maintained statutory payroll outside Kenya.
The maintenance line is the one that most often ends a conversation, and it should. If your core need is planned maintenance with meters, intervals and work orders, buy a maintenance system and let it own that — then connect the two so parts consumption and purchasing stay in one place. A supplier who tells you an operations system covers maintenance management is describing a movement log with an optimistic label.
What is not built for Southern Africa today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in Southern Africa. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a revenue authority pipeline, a bank or mobile money feed, a statutory return format or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Tax pipelines and return output
Return output in the shape your revenue authority expects and electronic invoicing against any prescribed interface, with retries, a failure queue and a reconciliation report.
Banks, EFT and card acquirers
Bank statement feeds, EFT and debit-order files and card acquirer settlements pulled into the Payments Register so receipts match invoices without re-keying.
Payroll and statutory returns
Payroll tax and social security schedules produced in the layout your filing body expects, generated from live payroll records rather than rebuilt each month.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedWhere to go next
The regional buying context is in operations software for Southern African SMEs and, for the three markets specifically, ERP for Zambian, Zimbabwean and Botswana businesses. If import currency is squeezing your margins on spares, the discipline is in multi-currency in kwacha, pula and a redenominated dollar.
Continentally, asset management software for African organizations covers custody and verification at wider scale, and inventory management software for Africa covers the stock half.
Our take
Classify stock by what a stockout costs, not by what the item costs. Move tools out of inventory and into an asset register with named custody before you record a single issue. Make the remote site store a location in one system with offline capture, not a book that gets reconciled. Give emergencies a legitimate fast path and count the times it was bypassed anyway. Then buy maintenance management separately, from someone who builds it — because we do not.
See governed site stores and contractor custody
Multi-location stock with in-transit transfers, offline capture that works at a remote store, procurement gates that refuse, and an asset register that knows which contractor still has your equipment.
Explore asset trackingFrequently asked questions
Is this a mining ERP?
No, and the distinction matters. We do not touch mine planning, geology, survey, grade control or production scheduling, and we are not a maintenance management system. What we run is the supply and service business around the mine: stock across a main warehouse and remote site stores, procurement with approvals that refuse, contractor custody of tools and equipment, and job costing so consumables land on the contract they were used on. If you are the mine rather than the supplier, we are one component of your stack, not the stack.
Can a store on a site with no connectivity actually use it?
Yes, and this is the capability that decides whether a remote store stays in the system or reverts to a book. Receipts, issues, transfers and counts are captured on a phone or tablet offline, queued locally, and synced when the device reaches a signal — each queued operation carries a client-side identifier so the same receipt cannot arrive twice, and conflicts are surfaced for an administrator rather than resolved silently. Administrators see a device register showing which devices are behind, what is queued and what failed.
Do you track engine hours or schedule preventive maintenance?
No. There is no meter or engine-hours field, no service interval per asset and no due-for-service reminder based on time or usage. Maintenance appears as recorded movements — sent to maintenance, returned from maintenance — alongside assignments, transfers and verifications, with a maintenance status on the asset so availability reporting is honest. If planned maintenance with intervals and work orders is core to your business, buy a maintenance system for it; we would rather connect to one than pretend.
How do we stop losing tools to contractors?
Stop treating them as stock. A tool issued as inventory is consumed and gone; a tool issued as an asset has a named custodian, a location, an expected return date, a movement history and a physical verification record, and can carry a barcode or QR label so a return is a scan rather than a form. Optional GPS capture on checkout and return records where the transaction physically happened. None of that recovers a wrench by itself — but it turns "somebody has it" into a name and a date, which is what actually changes behaviour.
How should we handle emergency purchases at three in the morning?
Give them a legitimate, named path rather than pretending they will not happen. A defined emergency route with a shorter approver list, a value ceiling and a mandatory reason keeps the transaction inside the system and inside the record. What destroys governance is the retrospective purchase order raised days later to make paperwork agree — so record those as what they are and report the monthly count. A business that can see it had nine last month can fix the cause; one that regularises them silently cannot.
Does it handle fuel?
As consumption and reconciliation, not as a fuel management system. Fuel issues can be recorded against equipment or a job and reconciled against delivery records, with variance visible rather than absorbed. There is no pump integration, no fuel-card feed and no telematics connection, so the discipline is manual capture at the point of issue. For most supply and service businesses that is enough to find the leak; for a large mixed fleet it may not be, and a dedicated fuel system is the honest recommendation.
Can we cost consumables to a specific contract?
Yes, provided the issue names the job at the moment it happens. Issues can be recorded against a project or job, and purchases can carry a project reference, so contract profitability includes the grease and welding rod rather than just the invoiced labour and major parts. The system cannot infer this after the fact — "issued to workshop" is unrecoverable — so the whole benefit depends on a store discipline that takes about five extra seconds per issue.
