The brief from a busy Soweto trading yard
The client was a long-standing building supply merchant serving contractors, homeowners and local stokvel buyers in Soweto. Trading was healthy, but stock counts did not always match the shelves, purchasing was handled in different ways by different staff, and management could not always see what was on hand before placing the next order. In a business where cement, fasteners, plumbing fittings and hardware move quickly, that caused lost sales and too much money sitting in slow stock.
The brief was straightforward: put proper controls in place for buying, receiving, stock issues and reorder levels, while keeping the system simple enough for counter staff to use during peak trade. Load-shedding also had to be considered, because the branch needed clear procedures when power was unstable and the team had to work with limited downtime.
- Location: Soweto, Gauteng
- Business type: community hardware and building supply merchant
- Primary need: stock accuracy and purchasing discipline
- Key pressure points: high-volume counter sales, multiple suppliers, seasonal demand spikes
What made the project tricky
The biggest challenge was not the software itself, but the way the business had grown. A few products were bought by habit, some lines had old item codes, and receiving notes did not always match what had actually arrived. There were also practical site issues such as staff changing shifts, noisy counters and limited time to stop trading for long training sessions. We had to keep the rollout tight and realistic, not perfect on paper but unusable in the yard.
We also had to cater for supplier lead times that changed from week to week. Some items came from local wholesalers in Johannesburg while others arrived on mixed pallets from further afield. When delivery quantities varied, the stock system needed to show the shortfall quickly so the buyer could act before a job was delayed.
- Working environment: active trading floor with limited downtime
- Operational issue: mixed stock coding and inconsistent receiving
- Control requirement: reorder visibility by item and supplier
- Rollout constraint: staff had to keep serving customers during the changeover
The ERP and integration work we supplied
Bizmatics scoped the business, mapped the purchasing flow and put in a practical ERP structure around the items that matter most to a building supply merchant. We defined stock groups, supplier records, approvals, reorder points and user roles. We also set up system integration so that the buying, receiving and stock movement records spoke to one another instead of sitting in separate files and paper notes.
Custom reporting was added for the manager and buyer, with daily and weekly views for fast-moving stock, aged inventory, supplier fill rates and items that had dropped below minimum levels. The reporting pack was kept simple enough to read over a cup of coffee before the first rush of the day, but detailed enough to support real purchasing decisions.
- ERP implementation for stock, purchasing and supplier control
- Process mapping for receiving, returns and stock adjustments
- Data migration for item masters, supplier details and opening balances
- Custom reporting for reorder points, slow movers and stock variances
How we handled data, people and go-live
The rollout ran over 6 weeks. Week one was discovery and process mapping, week two was data cleanup, and week three focused on configuration and migration planning. In week four we tested the key workflows with the buyer and counter team. Week five covered user training, while week six was go-live support and close monitoring. That pace gave the staff time to get comfortable without dragging the project out for months.
Training was done in short sessions by role, because a cashier does not need the same detail as a buyer or manager. We also prepared simple reference guides for common tasks such as receiving stock, correcting a quantity and checking a reorder list. A few minor mistakes were picked up early and sorted before they became habits, which saved a lot of backtracking later.
- Project duration: 6 weeks
- Training format: role-based, short sessions with practical examples
- Go-live support: on-site and remote check-ins during the first trading cycle
- Controls introduced: approvals, stock checks, exception reporting
Results after the first trading cycle
Once the new controls were in use, the business had a much clearer picture of what was in store and what needed to be ordered next. Stock variances reduced because receiving was captured properly and item codes were standardised. The buyer could see shortages before they affected the counter, and management had better visibility of where money was being tied up in slow stock. In practical terms, that meant fewer surprises and less time spent chasing missing figures.
The staff also gained confidence. The counter team knew where to look for the correct item, and the manager could review activity without walking the whole yard every time. That matters in a busy Soweto trading environment where customers expect quick service and no one wants to stand around while someone hunts for a price or a code.
- Improved stock accuracy across key product lines
- Faster purchasing decisions from clearer reorder reports
- Less time spent correcting manual errors
- Better visibility for management and the buying team
Lessons we would carry into another hardware-merchant rollout
We would approach a similar hardware merchant project in much the same way: map the actual trade process first, clean the item master before migration, and keep training short but hands-on. That combination worked because it respected the pace of a real South African trading floor. There is no point installing controls that nobody uses when customers are waiting at the gate.
We would also keep the focus on exception handling. In a business like this, the main value is not in making everything complicated, but in showing the buyer where the problems are before they become shortages or dead stock. If we did it again, we would still keep the system practical, the reports short and the support close during the first few weeks after go-live.
- Best practice: map the real process before configuring anything
- Best practice: clean stock data before migration starts
- Best practice: train by role and by daily task
- Best practice: keep exception reports simple and visible
Key facts
| Client type | Community-focused hardware and building supply merchant |
|---|---|
| Town | Soweto, Gauteng |
| Project duration | 6 weeks |
| Core scope | ERP implementation, stock control and purchasing discipline |
| Main outputs | Data migration, reporting, workflow setup and training |
| Result | Better stock accuracy and clearer purchasing decisions |
