A Brooklyn supply business with tight controls
The client was a medical supply business serving clinics, practices and associated distributors in Brooklyn, Pretoria. Their operation handled fast-moving stock, batch-controlled items and repeat orders, with daily pressure to get the right products out on time and keep records clean enough for audit checks. In a regulated environment, a missed quantity or wrong batch can cause more than a delay, so the brief came with very clear expectations.
They needed one system flow for inventory, sales orders, purchasing and fulfilment, rather than a patchwork of spreadsheets and separate records. Their team also had to keep working while the change was being rolled out, which meant a practical plan with limited downtime, careful testing and proper handover to staff who were already busy on the floor.
The brief, constraints and compliance pressure
The main brief was simple to state and harder to execute: control stock better, reduce manual re-keying, and improve visibility across order processing and replenishment. The client also wanted a setup that could cope with load-shedding, avoid data loss, and support users who were split between office work, stock handling and dispatch. Because the business operated in a regulated category, traceability and correction history mattered just as much as speed.
- Stock needed to be tracked by product code, batch and expiry where required
- Order processing had to link correctly to available stock and purchase reorders
- Reporting needed to show movement, shortages and pending orders clearly
- The team needed a system that was practical for day-to-day use, not over-complicated
There was also a strong local requirement for discipline around approvals and record keeping. The client needed a process that worked when the power tripped, when staff were off sick, and when suppliers delivered partial quantities without warning. That meant building controls into the workflow rather than relying on memory or ad hoc checks.
What we supplied and how we configured it
We designed and implemented an ERP structure focused on inventory control, order processing and reporting. The setup included process mapping first, so we could match the software flow to the way the Brooklyn team actually worked. After that we configured the core records, approval steps and integration points needed for a cleaner operation.
The implementation covered data migration from existing records, master data clean-up, user roles and permission settings, and custom reporting for stock movement and open orders. We also linked the workflow to the business systems already in use, so the team would not need to keep switching between disconnected tools.
- ERP implementation for inventory, sales and purchasing
- Process mapping of order intake, picking, dispatch and returns
- Data migration with record cleansing and duplicate removal
- System integration for financial and operational handover
- Custom reporting for stock cover, slow movers and order backlogs
- User training for office staff and warehouse users
Six weeks from scoping to go-live
The project ran over six weeks in a staged rollout. Week 1 was discovery and process mapping, with interviews, sample documents and a review of pain points in stock handling. Week 2 focused on the data set and field mapping, including product codes, supplier records and open order histories. During Week 3 we configured the ERP structure and tested the main workflows against the client’s actual documents.
Week 4 covered integration, report design and exception handling. Week 5 was user training and sign-off testing, with stock and sales users running through real cases. Week 6 was go-live support, with close monitoring through the first trading cycle. The timing worked well because it let the team learn the new process before the busiest dispatch periods, and we kept a short daily check-in schedule so issues could be fixed quickly.
Operational results that held up under pressure
After go-live, the biggest change was visibility. The client could see stock on hand, open orders and replenishment needs in one place instead of piecing together three or four records. That reduced the amount of manual follow-up, cut down on errors from duplicate entry, and gave management a cleaner view of what was actually available for sale. It also made it easier to see where shortages were coming from, whether the issue was supplier lead time, process delay or data quality.
The order-processing team reported faster turnaround because fewer transactions had to be corrected by hand. Warehouse users had clearer picking instructions, and management got more reliable reporting for planning. In practical terms, the business gained tighter control without making the team slower. That matters in a supply environment where every missed line item can create another round of calls and apologies.
- Better stock accuracy across active product lines
- Cleaner order processing with fewer manual corrections
- Improved traceability for controlled items
- Stronger reporting for daily decisions and replenishment planning
- Less time spent reconciling sales, stock and supplier records
Lessons we would carry into another medical-supply rollout
If we were doing a similar project again for a medical or regulated supplier in Pretoria, Johannesburg or anywhere else in South Africa, we would keep the same sequence: map the process first, clean the data early, and only then move into configuration and training. That sequence saved time later because it exposed the weak points before they became live problems. It also gave the client a chance to challenge the workflow while it was still easy to adjust.
We would also keep the user training short, role-based and hands-on. Stock teams need different detail from finance or management, and one long session usually means people forget half of it by the next morning. A practical support window after go-live is just as important, especially in towns and cities where internet stability, load-shedding and busy work shifts can all affect how quickly a team settles in. The project confirmed what we see often: good software helps, but the real gain comes from matching the system to the business process and sticking to it.
Key facts
| Project type | Controlled ERP and order-processing setup for a regulated medical supply business |
|---|---|
| Town | Brooklyn, Pretoria |
| Implementation time | 6 weeks |
| Core scope | ERP implementation, process mapping, data migration and system integration |
| Operational focus | Inventory control, traceability, order processing and reporting |
| Support included | User training, go-live support and initial change management |
