Start with a branch rollout scope that matches the business
Before the first branch goes live, define exactly what must be standardised and what may vary by site. For a growing SME in South Africa, that usually means one chart of accounts, one item master, one customer record structure and one set of approval rules, with local differences only where they are truly needed. If your sites are in Johannesburg, Pretoria, Durban, Cape Town or Gqeberha, also note branch specific factors like delivery lead times, local stock holding and municipal trading hours.
A proper scope prevents last minute arguments about pricing, stock codes and who may approve purchases. It also keeps the rollout from turning into a once-off project with no follow through. Decide early whether you are rolling out finance only, or finance plus sales, purchasing, warehousing and service. That decision drives timeline, testing and training effort.
- List every branch, warehouse and satellite office in scope.
- Set the go-live order, for example head office first then one branch at a time.
- Confirm which processes must be identical across all sites.
- Record local exceptions, including courier cut-offs and after-hours support needs.
Clean the data before you move stock, customers and suppliers
Most branch problems start with poor data. Old item codes, duplicate customers and incomplete supplier details cause stock errors, slow invoicing and messy reporting. A rollout works better when the data is cleaned before migration, not after staff have already started using the new system.
Work through customer records, item masters, price lists, opening balances and stock quantities branch by branch. Make sure units of measure are consistent, batch and serial rules are defined, and tax settings align with South African requirements. If a branch carries fast moving stock in a hot or humid area, such as Durban or Gqeberha, check whether shelf life, storage location and reorder triggers need to be tighter.
- Remove duplicate records and agree on the naming format.
- Verify opening stock counts by branch and warehouse.
- Check outstanding orders, backorders and credit notes.
- Test tax, discount and approval rules before migration day.
It is also worth doing a system audit before rollout so hidden gaps do not surface when the first branch starts processing live transactions. That small step can save a lot of rework later on.
Build one reporting structure that all branches can trust
Branch managers need numbers they can trust every morning. That means the rollout must define reporting from the start, not as an afterthought. Decide which reports are standard across the business and which need branch level filters for sales, stock movement, gross margin, ageing debtors and supplier performance.
Use one reporting calendar for month end, stock take and management packs. If each site closes on different dates, the group view becomes weak and decision making slows down. Consistent reporting also helps with load-shedding planning, since teams can schedule uploads, reconciliations and backups around stable power windows.
Strong branch reporting usually includes:
- Daily sales by branch, department and cashier or user.
- Stock on hand, stock variances and slow movers.
- Outstanding customer balances and overdue supplier accounts.
- Branch budget versus actuals, with comments on major variances.
Where branch managers need their own views, keep the structure the same and only change the filters. That way head office can compare sites fairly, and each branch still sees the numbers relevant to its own targets.
Roll out in phases so each site settles before the next one opens
A phased rollout lowers risk and gives the team time to settle. Start with a pilot branch that has enough transaction volume to test the real process, but not so much complexity that every issue becomes urgent. Once the pilot is stable, move to the next branch with the lessons already captured.
For each phase, plan a clear sequence: data load, user acceptance testing, training, go-live, and post go-live support. Give each branch a cutover checklist and a named owner. This avoids confusion when the warehouse, finance team and sales staff all need different actions on the same day.
Use the same phase pack for every branch:
- Confirmed branch master data and opening balances.
- User list, roles and approval rights.
- Testing sign-off for sales, purchasing, stock and finance.
- Go-live timetable with freeze periods for changes.
- Support contacts for the first week after launch.
Keep the time between branches short enough to maintain momentum, but long enough to fix issues properly. That balance matters in South Africa where teams may already be managing overtime, transport delays and power interruptions.
Train branch teams on the process, not just the screens
Training works best when it follows the real branch process from start to finish. Staff need to know what to do when a customer order arrives, when stock is short, when a supplier delivery is late, and when a document has to be reprinted for audit. Screen-by-screen training alone leaves gaps.
For each role, define the daily actions, the approval chain and the exception handling rules. A cashier, warehouse clerk, sales rep and branch manager do not need the same depth of training. Keep sessions short, practical and tied to actual transactions. If the team can practice with live examples, adoption improves quickly.
- Prepare role based checklists for every branch.
- Train on standard work instructions, not memory alone.
- Include backup users for leave, sickness and shift changes.
- Test what happens if power or internet goes down mid process.
Change management matters here too. Some staff will be used to manual logs, spreadsheet stock counts or informal approvals. Give them time to adjust and explain why the new controls protect the branch as well as head office.
Protect the first 30 days after go-live with tight support
The first month after go-live is where branch rollout either settles or slips. Plan daily check-ins, issue logs and clear escalation for stock errors, posting problems, failed integrations and user access issues. A support retainer gives branches a clear point of contact while the team gets used to the new process.
During this period, focus on three things: transaction accuracy, stock integrity and report confidence. If a branch cannot trust its stock balances or month-end figures, the rollout is not finished yet. Keep a short list of open issues and review it with branch leadership each week until the numbers hold steady.
Useful controls for the first 30 days include:
- Daily reconciliation of sales, receipts and stock movements.
- Exception reports for negative stock, duplicate entries and failed uploads.
- Back-up access for key users in case of leave or emergencies.
- Weekly review of open support tickets and root causes.
Once the branch is stable, move into upgrade planning, refresher training and periodic system audits so the process stays clean as the business grows. A rollout that is maintained properly will keep paying back long after go-live.
