Choosing ERP Software in South Africa

Start with the modules you actually need

ERP is a category, not a single product, and the modules that matter differ by business. Common building blocks include stock and warehousing, procurement and approvals, job costing and production scheduling, and finance and management reporting. A workshop needs strong job costing and WIP valuation; a warehouse operation needs bin-level stock control and picking workflow; a professional services firm needs resource planning and budget tracking more than manufacturing modules.

The mistake to avoid is buying a broad suite because it looks complete, then only ever using a fraction of it. It is usually more effective to be precise about the three or four modules that remove real pain, and build or configure around those first.

Integration is where ERP projects succeed or stall

An ERP system rarely lives alone. It needs to talk to accounting packages, payment gateways, couriers, and sometimes lab or production equipment. The FileMaker Data API, OData and general REST integration patterns make it possible to connect an ERP core to these third-party systems without manual re-typing — but this needs to be planned as part of the project, not bolted on afterwards.

Before selecting or building an ERP system, list every system it will need to exchange data with, and confirm each one has a usable API or export format. This single step avoids most of the integration headaches that surface after go-live.

Cloud vs on-premise

Cloud-hosted ERP (including FileMaker Server hosted with WebDirect access, or a Supabase/Postgres backend) reduces the infrastructure your team has to manage and makes remote and multi-site access straightforward. On-premise deployment gives more direct control over data residency and can suit businesses with strict compliance or connectivity constraints.

Many South African businesses land on a hybrid: a hosted server for day-to-day access, with offsite daily backups and a clear disaster-recovery plan, rather than a strict either/or choice.

Inventory management: periodic vs perpetual

Inventory management is usually the module that makes or breaks an enterprise resource planning system. A periodic inventory system updates stock levels at set intervals, typically after a physical count at month-end. It is simple and cheap to run, but between counts nobody knows exactly what is on the shelf. A perpetual inventory system records every receipt, issue and transfer as it happens, so the stock controller always sees live quantities and valuations.

Most businesses that move beyond spreadsheets need a perpetual stock system, especially when they carry consignment stock (goods held on site but still owned by the supplier, or placed at a customer but not yet sold) or run JIT management, where materials arrive just in time for production. Both depend on accurate, real-time numbers. A good warehouse management system adds bin locations, picking lists, barcode scanning and cycle counts on top of that, so the inventory controller can trust the figures without stopping the operation for a full count.

Accounting, invoicing and payroll integration

An ERP rarely replaces your accounting platform; it feeds it. Most small and mid-sized businesses already use accounting software for small business such as Sage Business Cloud, Xero, QuickBooks, Zoho Books or the Wave accounting app. The right approach is usually a Sage Cloud accounting software integration or a Xero software accounting integration over their REST APIs, so invoices, customers and stock movements post automatically instead of being re-typed.

The same applies to invoice billing software and payroll software. If your team already likes Zoho Invoice or a free invoice software tool, the ERP can push billable jobs to it. If job costing lives in QuickBooks, the ERP can send actual labour and material costs for QuickBooks costing reports. Payroll computer software can receive approved timesheets directly. The goal is one source of truth for operations and one for the books, joined by a reliable integration.

Reporting and business intelligence

Once the data is clean and connected, reporting becomes the payoff. Built-in dashboards cover day-to-day needs, but many teams also connect a business intelligence platform such as Power BI software to the ERP database for cross-department analysis: margin by product, stock turn by warehouse, or sales pipeline from the CRM against production capacity. Planning this from the start — consistent codes, dates and categories — is what makes the reports trustworthy.

Off-the-shelf, custom, or both

Off-the-shelf ERP suites bring pre-built modules but often force a business to adapt its process to the software. Custom ERP development — commonly built on Claris FileMaker with Supabase for web-scale or AI features — starts from your actual workflow, at the cost of more upfront design work. Many businesses run a blended approach: a custom core for the workflows that make them different, integrated with standard accounting or payroll software for the parts that do not need to be unique.

Conclusion

Choosing ERP software in South Africa comes down to three questions: which modules actually remove pain, what does the system need to integrate with, and where should it be hosted. Answering these before comparing vendors or platforms makes the rest of the decision much easier.