The Operational Brief in Kempton Park
The client was a mid-sized logistics business in Kempton Park handling local distribution, line-haul coordination and ongoing customer reporting. Their teams were working across separate systems for delivery status, cost capture and management updates, which made it hard to see the real margin on each job. Finance, operations and dispatch were all doing parts of the same work twice, and that slowed decisions down.
The brief was straightforward on paper: connect the moving parts, reduce manual re-keying and make the daily reporting usable by supervisors and management. In practice, that meant bringing together delivery records, costing rules, customer account data and approval steps without disrupting live operations. They needed something practical that could cope with busy warehouse hours, late vehicle returns and data coming in from more than one site.
What Made the Project Tricky
Kempton Park is a strong logistics base, but the pace can expose weak processes quickly. The business had to keep dispatch moving during load shedding windows, manage staff across different shifts, and work around older spreadsheets that were still being used by some supervisors. Coastal humidity was not an issue here, but the site still had the usual warehouse realities: printed notes going missing, vehicles leaving before full sign-off and cost changes arriving after the delivery had already gone out.
We also had to keep the changeover sensible for users who were used to informal workarounds. The new process had to be clear enough for operations staff, yet detailed enough for management reporting and month-end checks. There was no point building something clever if the team could not use it on a busy Friday afternoon, so we focused on practical steps and clean handovers.
- Multiple live workflows running at once
- Inconsistent costing fields across departments
- Manual reporting copied from spreadsheets
- Need for limited downtime during rollout
How We Structured the Integration Work
Bizmatics started with process mapping to trace the full job cycle from delivery booking through to final management reporting. That let us see where information was entering the business, where it was being duplicated and where approvals were getting stuck. From there we set up the ERP structure around the client’s actual operating flow, not an idealised version of it.
We then handled data migration for the essential records, including customer profiles, delivery history, pricing rules and selected master data. The integration layer linked the ERP to the systems used by dispatch and finance so that updates could move in both directions. Custom reporting was added for daily volume, cost-to-serve, outstanding exceptions and job profitability. A small typo in some old source files meant we had to clean entries carefully, but that sort of thing is normal on real projects.
- Process mapping across operations, finance and management
- Data migration for core customer and job records
- System integration for delivery and costing updates
- Custom reports for daily and month-end review
Delivery Timeline and Go-Live Support
The project ran over 10 weeks from discovery to stabilisation. The first two weeks were used for process mapping and requirements confirmation, followed by configuration, data preparation and report build. Testing took place with live scenarios from the Kempton Park team, including split deliveries, partial costs and amendments after dispatch. That testing stage mattered, because it showed where users needed clearer prompts and where approvals should be tightened.
Go-live support was handled on site and remotely during the first operating cycle. We worked with the client through the first reporting cut-off, then supported fixes to make sure the figures matched what operations and finance expected. The change management plan included user training, quick-reference notes and supervisor walkthroughs so the team could settle in without a long dip in productivity.
Results Seen After the Rollout
Once the new structure was in place, the business had a cleaner view of each delivery and the cost attached to it. Supervisors could check exceptions earlier, finance had less manual rework and management received reports that were ready to use instead of needing another round of checking. The biggest gain was not just speed, it was confidence in the numbers.
The client also found that customer queries could be handled faster because dispatch and cost data were easier to trace. Month-end close became more manageable, and the team had fewer arguments about which spreadsheet was current. It is not glamorous work, but it changed the way the business ran day to day and gave management better control over margins.
- Fewer manual handovers between departments
- Clearer job-level costing and reporting
- Faster review of delivery exceptions
- Better visibility for supervisors and management
What We Would Do Again on a Similar Site
If we were starting the same kind of project again in Pretoria, Johannesburg or elsewhere in Gauteng, we would use the same approach: map the full process first, clean the master data early and test with real operational examples before go-live. That sequence saves time later and avoids forcing staff into a system that does not match their daily work.
We would also keep the training practical and role-based, especially where teams work across dispatch, finance and management. In our experience, the best results come from simple screens, clear ownership and reporting that tells the truth without extra admin. For a logistics business, that usually matters more than having every option switched on from day one.
Key facts
| Project type | Operational ERP integration for logistics |
|---|---|
| Location | Kempton Park, Gauteng |
| Timeline | 10 weeks from discovery to stabilisation |
| Core scope | Delivery, costing and management reporting |
| Services used | Process mapping, data migration, integration, reporting, training |
| Primary outcome | Better control of job data and margins |
