An ERP system — enterprise resource planning software, also called a company management system — is one application and one database that holds a business’s main records: who you quoted, what you ordered, what is in stock, what was produced, what you owe, what you are owed, and who is employed to do all of it. The point is not the software. The point is that every record is connected to the one before it.
What an ERP replaces
Most growing companies start with a quotation spreadsheet, an accounting package, a folder of purchase orders, an attendance export from a fingerprint machine and a messaging app where approvals actually happen. Each tool is fine on its own. The trouble is the gaps between them: the same price is typed three times, nobody can say which purchase order is still waiting for goods, and “who approved this?” has no reliable answer six months later.
An ERP closes those gaps. A quotation becomes a sales order, a sales order generates buy requests, a purchase order generates a goods receipt, the receipt moves stock, and the invoice and payment close the loop — without anyone re-typing anything.
The modules that matter
Different businesses weight the parts differently, but most ERP systems are built from the same building blocks:
- Commercial — quotations, sales orders, invoicing, customers and delivery. See the Commercial workspace.
- Procurement — purchase orders, goods receiving, vendor management and payment approvals. See Procurement.
- Operations — production, bill of materials, inventory and, for service companies, inspection and job records. See Operations.
- Finance — chart of accounts, receivable and payable, vouchers and expenses. See Finance.
- People — employees, attendance, payroll and leave. See People & payroll.
Why generic ERP can fit physical-work businesses badly
Big suites are designed around selling things off a shelf. Engineering, inspection and fabrication work produces different data: a tolerance, a fitness status, a pressure rating, a rejected quantity and the reason for it. When the software has no place for those fields, teams keep a spreadsheet beside the ERP — which defeats the purpose. The best fit is an ERP whose fields were written for the work. Read more about ERP by industry.
Signs you have outgrown spreadsheets
- You cannot tell, without asking someone, whether a quotation has become an order, been bought and been delivered.
- A supplier has been paid twice, or paid for goods that never fully arrived.
- Payroll takes days because attendance is re-keyed by hand.
- Stock counts differ between the store, the spreadsheet and the books.
- Approvals are given by phone call or chat message and cannot be shown to an auditor.
- Tax invoices have to follow a regulator’s format — for example ZATCA e-invoicing in Saudi Arabia.
Where to start
You do not have to switch on everything on day one. A sensible first phase is the chain that moves money — quotation, order, purchase, delivery, invoice — plus whichever of stock, payroll or service jobs hurts most. Add the rest when the first phase is working. Read the ERP implementation checklist before you begin, and ten questions to put to any ERP vendor.