Distribution brief from a Durban operations team
The client was a mid-sized distributor in Durban serving retail and trade accounts across KwaZulu-Natal and beyond. Their main concern was simple: orders were coming in quicker than their systems could process them, and stock updates were not reaching the right people fast enough.
They asked us to improve the flow from sales order through to picking, dispatch and invoicing. The business had several moving parts, including live inventory, back orders, credit checks and delivery scheduling, so the solution had to fit real operations not just a clean demo. The team also wanted something staff could learn quickly, because a lot of the work happened under pressure during peak trading hours.
- Site type: distribution business in Durban
- Scope: ERP integration and dispatch workflow improvement
- Primary goal: faster order processing with less manual handling
- Operating pressure: busy daily order volumes and time-sensitive deliveries
What was holding the process back
The biggest constraint was the amount of manual re-entry between systems. Sales staff were capturing orders one way, the warehouse was checking stock another way, and dispatch was relying on printed lists and phone calls. In a busy Durban environment, with traffic delays and weather disruptions in some areas, that kind of setup quickly starts costing time.
There was also a practical hardware issue. The business had mixed-age devices on site and a few users working off a limited internet connection during load-shedding. We kept the design lean, with data checks and error handling built in so the team could keep working if a connection became unstable for a short period.
- Manual rekeying between sales, stock and accounts
- Late visibility on order status and available stock
- Mixed user devices across office and warehouse teams
- Need for sensible handling during power interruptions
Systems we supplied and how they were linked
We implemented ERP integration around the client’s core order and stock processes, then mapped the data flow so each step had a clear owner. Sales orders fed into stock allocation, dispatch picked up the correct release status, and invoicing reflected the actual goods moved. We also set up custom reporting so supervisors could track what was pending, what had shipped and what was waiting on approval.
Key functions included process mapping, data migration support, workflow automation and user training. Gerhard Pienaar led the integration architecture, while Zulfa Rhoda handled the ERP configuration side with a focus on usability for the operations team. Mpolokeng Tshabangu managed delivery in weekly phases so the client always knew what was going live next.
- Order capture to dispatch status integration
- Stock visibility across warehouse and sales teams
- Custom reports for cut-off times and pending orders
- Automated task handoffs for approvals and invoicing
Timeline, testing and go-live control
The project ran over 8 weeks from discovery to go-live support. The first two weeks covered process mapping and current-state reviews. Weeks 3 and 4 focused on the integration build and data clean-up. Weeks 5 and 6 were used for testing with real order scenarios, including partial stock, urgent dispatches and credit hold cases. The final two weeks were dedicated to training, cut-over and support during live use.
We kept the test set practical. Instead of only checking perfect orders, we worked through the messy cases that usually create problems on the floor. That included split deliveries, incorrect item codes, out-of-stock substitutions and reprints for dispatch notes.
- Total duration: 8 weeks
- Testing included real order exceptions
- Go-live was scheduled around dispatch cut-off times
- Support coverage continued after launch for stabilisation
Results seen after the first month
After go-live, order processing moved faster because staff no longer needed to copy the same information into multiple places. Dispatch had clearer release status, and the warehouse could see what was approved without chasing down confirmations. The result was less back-and-forth and fewer delays before trucks left the yard.
The client also reported better decision-making because reporting was now based on the same live data used by operations. That made it easier to spot bottlenecks, track backlog and manage daily priorities. For a distributor working in a tight margin environment, that kind of visibility matters.
- Shorter order-to-dispatch turnaround
- Fewer manual errors from duplicate entry
- Cleaner stock and order reporting
- Better control over pending and urgent orders
What we would repeat for another Durban distributor
If we were doing a similar project again, we would use the same approach: start with process mapping, keep the scope tight, and test against real warehouse scenarios before launch. That is especially important for Durban distributors dealing with busy routes, mixed customer requirements and pressure around same-day fulfilment.
We would also keep change management practical. Rather than overloading users with theory, we would train around actual tasks like releasing stock, handling exceptions and confirming dispatch. Muneeb Ismail and Thembisa Mabandla are both valuable on this kind of work because the support and adoption phase often determines whether the project settles in well or not.
- Start with actual process mapping, not assumptions
- Test exception cases before cut-over
- Train users on daily tasks, not just system screens
- Keep support close during the first trading cycle
Key facts
| Client type | Mid-sized distribution business |
|---|---|
| Town | Durban |
| Project duration | 8 weeks |
| Core scope | ERP implementation and system integration |
| Key functions | Order processing, stock visibility, dispatch control |
| Team lead | Oupa Mabuza, Managing Director |
