The Pinetown brief: replace a tired system without stopping the floor
The client was a mid-sized supplier in Pinetown serving retail and trade customers across KwaZulu-Natal. They were still relying on a legacy platform for purchasing, stock control and basic reporting, but the system had become difficult to maintain and even harder to trust. Approvals were stuck in message, stock counts were often out by a few cartons, and the team had no clean view of what needed re-ordering each week.
The brief was straightforward on paper: replace the old system, keep the business running, and make purchasing and replenishment easier for a small team that could not afford long downtime. They also needed cleaner controls for sign-off, better visibility across multiple stock locations, and reporting that managers could use without waiting for someone to export and tidy up a spreadsheet.
- Client type: wholesale supplier with purchasing, warehousing and dispatch functions
- Location: Pinetown, with service reach into Durban and the wider KZN corridor
- Main pain points: slow approvals, weak stock visibility, manual re-keying and unreliable reports
- Goal: replace the legacy setup with a practical ERP process that staff would actually use
What had to be handled before cutover
The biggest constraint was continuity. The business could not pause ordering for a week while data was being cleaned, and there was no appetite for a risky switchover on a busy month-end. The site also had mixed connectivity in parts of the building, so the new process had to be stable even when the connection dipped. In KZN, load-shedding was another reality, so the client wanted a process that could be recovered quickly after an outage without double entries or missing approvals.
There was also a systems challenge. Stock records were spread across the old ERP, a few local spreadsheets and some staff knowledge that lived in people’s heads. Supplier lead times were not always recorded in one place, which made replenishment planning messy. In practice that meant the team needed more than software installation. They needed process mapping, data cleansing, workflow design and a proper handover that matched how the warehouse actually worked.
- Legacy data needed to be checked for duplicate items, inactive codes and incorrect units of measure
- Approval rules had to reflect who could sign off by value and by category
- Reports had to work for purchasing, stores and management, not just one department
- Training had to be short, practical and timed around day-to-day operations
How we structured the replacement project
We ran the work over 8 weeks, starting with process mapping and ending with go-live support. Our team from Centurion worked with the client’s operations lead, warehouse supervisor and finance contact to map the full order-to-replenishment flow. That covered purchase requests, approval steps, stock issue checks, goods received entries and exception handling for short deliveries or price variances.
Once the workflow was agreed, we set up the ERP structure around the business rather than forcing the business to fit the software. We configured approval routes, item masters, supplier records and replenishment triggers. Data migration was staged in batches so the client could test records before final cutover. We also built a few tailored reports, including low-stock alerts, open purchase order status and a weekly purchasing summary for management.
To keep the rollout practical, we split the work into clear phases:
- Weeks 1 to 2: process mapping, system review and data audit
- Weeks 3 to 4: configuration, approval workflow setup and field mapping
- Weeks 5 to 6: data migration, report build and user testing
- Weeks 7 to 8: training, cutover, go-live support and issue resolution
The ERP and integration work we delivered
Our scope covered ERP implementation and business-systems integration, with enough flexibility to fit the client’s purchasing habits. We did not try to overcomplicate the setup. The aim was to remove repeat typing, make approval paths visible, and keep stock data current enough for the team to make sensible decisions before a line ran dry. That meant linking the new ERP flow to existing sales and finance processes where possible, and reducing the number of manual handoffs.
We also introduced controls that made stock replenishment easier to govern. Minimum stock levels were set per item group, approval thresholds were tied to buyer roles, and exception reports flagged items that were moving faster than expected. A few items had different pack sizes and the old system was muddling units, so we standardised those records during migration. The result was cleaner purchasing data and fewer surprises when receiving stock.
- ERP implementation with item, supplier and approval setup
- Process mapping for purchasing, stores and replenishment
- Data migration from the old system and spreadsheets
- Custom reporting for stock, purchasing and management review
- User training with follow-up support after go-live
Results after go-live in Pinetown
After go-live, the client had a single purchasing process with less chasing between departments. Approvals moved faster because the right people could see pending requests in one place instead of digging through inboxes. Stock visibility improved as well, which helped the team plan replenishment earlier rather than reacting when something had already run out. The warehouse team also reported fewer errors caused by re-keying the same information into multiple places.
From a management point of view, the weekly reports became useful again. Instead of working from several versions of the truth, the team had one set of figures for open orders, low stock and supplier follow-up. The change did not remove every manual task, but it cut a lot of waste out of the process. Most importantly, staff were comfortable using the system because it matched the way they already worked, just with better controls.
- Faster purchasing approvals with fewer follow-up messages
- Better replenishment planning from cleaner stock data
- Reduced manual re-entry between departments
- Improved confidence in weekly purchasing reports
What we would repeat on the next supplier project
If we were doing the same type of project again, we would follow the same order: map the process first, clean the data early, then test with real users before cutover. That sequence matters on supplier sites, especially where buying, warehousing and dispatch all depend on the same records. It also helps to keep training short and role-based, because people remember what they use that day, not a long session full of features they may never touch.
We would also keep a close eye on power and connectivity risk from the start. In South Africa, especially on sites that are running during load-shedding, a practical recovery plan is part of the project, not an extra. For businesses in Pinetown, Durban and the surrounding industrial areas, that kind of planning is often the difference between a smooth Monday morning and a backlog that takes all week to clear.
- Keep the migration staged instead of moving everything at once
- Test approval paths with actual order values and real user roles
- Build reports that match daily decisions, not just month-end needs
- Plan for outages and delayed sign-off from day one
Key facts
| Project town | Pinetown, KwaZulu-Natal |
|---|---|
| Client type | Mid-sized supplier |
| Timeline | 8 weeks |
| Core focus | Legacy-system replacement for purchasing approvals and stock replenishment control |
| Services used | ERP Implementation, Process Mapping, Data Migration, Workflow Automation, Custom Reporting, User Training, Go-Live Support |
| Delivery team | Oupa Mabuza, Zulfa Rhoda, Gerhard Pienaar, Mpolokeng Tshabangu, Muneeb Ismail and Thembisa Mabandla |
