The retail brief from Pretoria
The client was a growing multi-store retailer in Pretoria serving walk-in customers, trade buyers and seasonal demand spikes. They had separate point-of-sale records, branch stock counts and head-office financial reports, but no reliable way to see the full picture on the same day.
The brief was practical: reduce stock shrinkage, improve replenishment decisions, and make branch performance visible without waiting for month-end. They also wanted a system that could cope with load-shedding, patchy connectivity in some areas and the realities of a busy trading floor where staff turnover can be high.
- Client type: multi-store retail SME
- Location: Pretoria with branch activity across Gauteng
- Core need: one source of truth for sales, stock and finance
- Working constraint: keep trading live during rollout
What was getting in the way
Before the project, each branch was working a little differently. Some teams captured adjustments in spreadsheets, others used manual stock sheets and head office had to reconcile variances after the fact. That made it hard to spot losses, over-ordering or pricing errors early enough to act.
The client also needed better controls around user access, approval steps and item master data. In retail, a small pricing mistake or a duplicate stock code can affect every branch within hours, so the system had to be cleanly structured from the start. The reporting requirement was more than pretty charts, it had to support actual buying decisions.
ERP and integration scope
We mapped the core processes first, then configured the ERP around the way the business really traded. The solution linked point-of-sale, purchasing, inventory and finance so branch activity flowed into central reporting without double entry. We also set up workflow rules for approvals and exception handling.
- Point-of-sale integration for branch sales and returns
- Stock visibility by branch, category and product line
- Head-office financial posting and daily reconciliation
- Custom reporting for sales, margin and stock movement
- User access controls by role and branch
- Workflow automation for approvals and replenishment triggers
The implementation included data migration from existing stock lists and transaction files, plus cleanup of product codes, supplier records and pricing fields. This part took patience because retail data is never neat on the first pass, especially where branches have grown at different speeds.
How we delivered it in 10 weeks
The project ran over 10 weeks from discovery to go-live support. Week 1 and 2 covered process mapping and data review, week 3 and 4 covered system design and master data cleanup, then configuration and integration testing followed. User training and branch sign-off happened before cutover, with support on site during the first trading days.
To keep trading stable, we phased the rollout and used a branch-by-branch cutover plan. That reduced disruption and gave the team time to adjust their working habits. We also built in fail-safe procedures for periods when electricity or connectivity became an issue, so daily operations could still continue and catch-up reconciliations stayed manageable.
- Discovery and process mapping: 2 weeks
- Configuration and integration testing: 4 weeks
- Training, cutover and go-live support: 2 weeks
- Stabilisation and post go-live support: 2 weeks
Results after go-live
After go-live, branch sales started feeding into the financial view far more consistently, which gave management a clearer picture of daily performance. Stock variances became easier to trace because the system kept a cleaner record of movement, adjustments and approvals.
The retailer also gained better buying control. Reorder decisions were based on actual movement rather than guesswork and branch managers had less time spent on manual admin. The finance team could reconcile faster, which helped with cash flow control and reduced the month-end scramble. In short, the business got better visibility without asking staff to do more duplicate work.
- Faster branch-to-head-office reporting
- Improved stock accuracy and traceability
- Cleaner daily reconciliation
- Less manual admin for branch teams
What we would do again
We would use the same approach again for any Pretoria or Gauteng retailer with several outlets and different levels of system maturity. Start with process mapping, clean the master data early and treat training as part of the project not an afterthought. That saved time later and made adoption easier for the branch teams.
We would also keep the rollout phased and insist on proper reporting definitions before go-live. If a retailer wants quick wins, the best place to focus is usually stock control and daily sales visibility. Once those are stable, the rest of the finance and operations picture becomes much easier to manage.
Project facts at a glance
For this Pretoria retailer, the main deliverable was not just software setup but a workable operating model that could support growth across branches. The project had to fit a busy trading environment, handle real stock movement and give head office the numbers it needed without extra chasing.
The strongest outcome was practical control. Managers could see what was selling, what was moving slowly and where adjustments were happening. That meant better decisions on replenishment, pricing and staffing, with less reliance on end-of-day guesswork.
Key facts
| Project type | Multi-store retail ERP and systems integration |
|---|---|
| Client location | Pretoria, Gauteng |
| Rollout timeline | 10 weeks |
| Core systems linked | Point-of-sale, stock, purchasing and finance |
| Primary outcomes | Daily visibility, tighter stock control and faster reconciliation |
| Support included | Training, go-live support and post-launch stabilisation |
