The problem ERP exists to solve
Most businesses do not start with software. They start with a book, then a spreadsheet, then a billing package, then a second spreadsheet for stock because the billing package does not do stock properly. By the time there are twenty staff there are usually five systems and one person who understands how they connect.
The cost of that is not the software licences. It is the hours spent making numbers agree, the orders that get typed twice, and the argument at month-end about which figure is right. ERP is the idea that those systems should have been one system all along, sharing one set of records.
ERP stands for Enterprise Resource Planning, which is a phrase from 1990s manufacturing and tells you almost nothing. Ignore the name. What matters is the shared database underneath.
What an ERP actually contains
ERP products are sold as modules, and the list varies by vendor. These are the ones almost every product has, and what each is for.
| Module | What it handles |
|---|---|
| Inventory / stock | Items, batches, warehouses or godowns, stock movements, reorder levels, physical counts |
| Sales | Quotation, sales order, invoice, delivery, credit notes — and in India, GST and e-invoicing |
| Purchase | Material requests, RFQs, purchase orders, goods receipt, vendor bills |
| Accounting | Ledgers, journals, receivables, payables, trial balance, statutory returns |
| Manufacturing | Bills of material, production orders, operations and routing, job work |
| HR and payroll | Attendance, leave, salary processing, statutory deductions |
| CRM | Leads, opportunities, customer history, field visits |
| Projects | Tasks, timesheets, billing rates, project profitability |
What makes it an ERP rather than several apps
This is the part that matters, and it is easy to miss when comparing feature lists. In a genuine ERP, raising a document in one module changes the others automatically and immediately.
A goods receipt increases stock and creates a payable. An invoice reduces stock, posts revenue and creates a GST liability. A production order consumes components and produces finished goods. Nobody re-enters anything, and there is no nightly sync that can fail quietly.
A suite of well-integrated separate apps can get close to this, and for many businesses close is enough. But the failure mode is different: separate apps disagree, and somebody has to notice.
When a business actually needs one
Not every business does, and a good vendor will tell you so. The honest signals that it is time are operational rather than financial.
- The same information is typed into more than one place, routinely.
- Stock on the system and stock on the shelf disagree often enough that people have stopped trusting the system.
- Month-end close takes longer than a week because figures have to be reconciled before they can be reported.
- Somebody has to be asked a question because the answer is not visible to the person who needs it.
- You are turning down work, or hiring, because nobody can see capacity or availability.
What an ERP will not fix
It will not fix a process nobody follows. If the storekeeper does not record issues today, buying software does not make them record issues — it makes the gap visible, which is useful but is not the same thing.
It will not fix bad data. Opening stock that was wrong in your old system is wrong in the new one on day one.
And it is not a quick project. An honest implementation for a small business is weeks, not days, and most of that time is yours, not the vendor’s: deciding item codes, agreeing who approves what, and reconciling opening balances.
In short
- ERP means one shared set of records across operations, not a particular feature list.
- The test of an ERP is whether a document raised in one module changes the others without anyone re-typing.
- You need one when information is being entered twice, or when nobody trusts the stock figure.
- It will expose bad process and bad data rather than fix them.