ERP Selection, South Africa

How South African ERP shortlists usually take shape

Many South African companies start from a Sage-based setup, often the Pastel line their finance team has used for years, or from Xero, with spreadsheets for stock, jobs and approvals around it. That existing setup deserves a fair place on the shortlist, because extending it can sometimes be the least disruptive answer.

Beyond that, the options depend on what the business does:

• Wholesalers, distributors and retailers often compare Odoo, Dynamics 365 Business Central and the broader Sage range, focusing on branch stock, pricing and point-of-sale links.
• Manufacturers may add SYSPRO or another production-focused system to the comparison alongside Odoo and ERPNext.
• Service, mining services and project firms look harder at job costing, timesheets and asset tracking, where Zoho or Odoo can fit alongside the incumbent accounting product.

I keep the shortlist small enough for each option to be tested properly, and every exclusion is recorded with a reason your board can follow. If the real question is whether an ERP is needed yet, my ERP evaluation service starts one step earlier.

Judging implementers and proposals in South Africa

In South Africa, the implementer often decides the outcome as much as the software. Two firms delivering the same product can differ sharply in team depth, industry knowledge and how well they support clients after go-live. I assess each one on the people who will actually do the work, their experience with businesses like yours and what their reference customers say about delivery and support.

Some procurement policies also apply supplier criteria to implementers, including B-BBEE credentials. If yours does, I add that as a scored criterion using the requirements your advisors define, rather than leaving it to a late conversation with procurement.

When proposals arrive, I compare them against the same requirement list and look for scope that is assumed rather than stated:

• interfaces to your bank, payroll provider and any point-of-sale or warehouse devices
• migration effort from your current package, including stock codes and open items
• VAT setup and testing, and who signs it off with your accountant
• support coverage, response commitments and how custom code is maintained

Gaps become written clarification questions before any shortlist is finalized. The approach is explained in more detail on vendor proposal review.

Scripted demos for VAT, imports, payroll and outages

A polished demo rarely touches the cases that cause South African finance teams the most work. So the scripts come from your own paperwork, and each vendor works through the same set. Depending on your business, they may include:

• an import that arrives through a clearing agent, with customs charges, freight and VAT captured and landed cost calculated on the stock item
• a zero-rated export sale next to a standard-rated local sale, with the treatment your accountant confirms
• a credit note against an earlier invoice, showing how the VAT reverses
• importing a payroll journal from your payroll provider into the right accounts and cost centers
• a branch receiving and selling stock while the connection is down, then syncing once it returns
• the figures behind a VAT return, drilled back to individual transactions

Vendors see the material beforehand. Process owners rate how each step went, and I note whether it was standard, configured, handled by an add-on or only possible with custom work. Offline behavior gets particular attention, because a claim that the system works during an outage should be shown, not described. These notes carry straight into gap analysis and later testing.

License currency, hosting, POPIA and contract terms

Many ERP licenses and subscriptions used in South Africa are priced in US dollars or euros, while implementation and support may be quoted in rand. That mix creates exchange rate exposure that is easy to miss when comparing headline prices. I lay out each option's cost drivers with the currency attached, so your financial director can see which parts of the bill could move and decide how much of that risk to accept.

Hosting questions go to every vendor in writing. Where will data be stored, and is a South African data center option available? What does the vendor offer to help you meet POPIA, with the legal reading left to your advisor? What happens to users when a site loses power or internet, and what backups exist if a self-hosted server goes down?

The contract review then checks the points that matter after signing:

• support hours aligned with your trading day and clear response commitments
• ownership of custom reports, integrations and code
• how upgrades and statutory changes are handled and charged
• how you leave, and in what format your data comes back

Cost drivers are explored further under ERP cost estimation.

Running the selection remotely from start to finish

South Africa sits a few hours behind India, which leaves a long shared window for workshops, demos and scoring sessions in your normal business day. I run the whole selection remotely. Recordings help when a session clashes with an outage at your site or when branch managers are on the road, and the scoring workbook is shared so every evaluator can see the evidence. An in-person meeting can be arranged if it would add real value.

The engagement runs in English. Where floor or branch staff prefer another language, a colleague can interpret and note down their feedback, since daily users deserve a voice in the choice.

I have no resale agreements, referral fees or commissions with any vendor or implementer, so I can tell you when your existing package is good enough or when a less familiar option fits better. Once the contract is signed, the work can continue with me as your ERP implementation consultant in South Africa. For wider context, see the South Africa overview and my ERP consultant page for South Africa.