ERPSMEsBusiness softwareCustom software
What is an ERP system? A plain-English definition, modules, examples and when you need one
11 min read
An ERP system (enterprise resource planning) is business software that keeps a company's core operations in one shared database: purchasing, inventory, sales, invoicing, accounting and, depending on the business, manufacturing, projects or HR. Its value fits in one sentence: information entered once is available to every department, with no retyping and no spreadsheet in between.
Most pages answering this question are written by ERP vendors and end with their product. This one explains what an ERP is, what it does and does not do, how widely it is used, what it costs to put in place, and the signs that a growing business needs one, or does not.
The definition in plain English
Picture a business that sells equipment. Without an ERP, a salesperson builds a quote in a spreadsheet, someone in the office types the order into the invoicing tool, the warehouse tracks stock in another file, and the bookkeeper copies invoices into the accounts. Every handover is a chance for an error or a delay, and nobody has the same version of the numbers.
With an ERP, the order is entered once. It reserves the stock, triggers picking, produces the delivery note and then the invoice, and the invoice posts itself to the ledger. Every department looks at the same record at the same time.
Three features define an ERP:
- one database shared by every module;
- modules that each cover a function (sales, purchasing, inventory, finance) and pass information to each other without retyping;
- end-to-end processes: order to cash, and purchase request to supplier payment.
Where the term comes from
ERP grew out of two manufacturing ideas: material requirements planning (MRP) and then manufacturing resource planning (MRP II). According to Wikipedia (checked on 7 November 2026), the research firm Gartner popularised the acronym in the 1990s to describe systems that went well beyond the factory floor. That heritage is why many ERP systems are still at their strongest on inventory and physical flows.
The main ERP modules
| Module | What it handles | Who uses it |
|---|---|---|
| Sales and order management | Price lists, quotes, orders, deliveries, invoices, credits | Sales, order administration |
| Purchasing | Purchase requests, purchase orders, goods received | Buyers |
| Inventory and warehousing | Items, locations, stock counts, picking, shipping | Warehouse, logistics |
| Manufacturing | Bills of materials, routings, work orders, planning | Production |
| Finance and accounting | Ledger, bank reconciliation, cash, collections | Finance |
| Projects and services | Time tracking, jobs, progress billing | Engineering, services firms |
| HR and payroll | Employees, leave, payroll (often a separate product) | HR |
| Customer relationship | Contacts, opportunities (usually lighter than a dedicated CRM) | Sales |
No business uses every module. A distributor lives in sales, purchasing and inventory; an engineering consultancy in projects and billing; a manufacturer in production planning.
Examples by industry
- Wholesale and distribution: customer-specific pricing, multi-warehouse orders, replenishment, lot traceability.
- Manufacturing: bills of materials, work orders, requirements planning, actual cost per unit.
- Construction and trades: costs per job, progress billing, subcontractors, margin per project.
- Professional services: timesheets, fixed-fee or time-based billing, profitability per client.
- E-commerce: stock synced with the online store, orders, returns, shipping.
These specifics are where ERP products differ. A general ERP covers them through configuration; an industry-specific one ships with them built in.
Types of ERP
| Type | How it works | Keep in mind |
|---|---|---|
| General purpose | One product for every industry, adapted through configuration | Broad coverage, configuration can get heavy |
| Industry-specific | Built for one sector (construction, food, distribution) | Close to your trade, fewer vendors to choose from |
| Cloud (SaaS) | Hosted by the vendor, paid by subscription | Updates included, dependence on the vendor |
| On-premise | Installed on your servers, licence plus maintenance | Control over the environment, you run it |
| Open source | Open code, often with a paid edition | No licence for the core, implementation still to fund |
| Custom or hybrid | A custom core for your process, connected to packaged tools | Fits your business, design and maintenance to fund |
The cloud versus on-premise choice is covered in SaaS vs on-premise, and a popular open source option in Odoo vs custom software.
What an ERP is not
- Accounting software. That records transactions; the ERP runs the operations that create them. Many smaller businesses keep their accounting package and connect it to the ERP.
- A CRM. A CRM tracks leads and deals before the sale; the ERP takes over at the order. See ERP vs CRM for the details.
- A business application. A business application solves one specific problem (field service, scheduling, technical quotes) and can plug into the ERP. See what is a business application.
How widely ERP is used
ERP is now standard in larger companies and common, but far from universal, in smaller ones. According to Eurostat (published 20 May 2026, 2025 data, EU enterprises with 10 or more employees), 41% of small enterprises use an ERP, against 89% of large ones. The need grows with order volume, item count and the number of people touching the same data.
Benefits and drawbacks, without the sales pitch
What an ERP gives you:
- one version of the numbers, shared by everyone;
- no more retyping between sales, inventory and finance;
- end-to-end traceability, useful in disputes and audits;
- reliable indicators: margin per order, real stock, customer balances.
What it asks in return:
- a demanding rollout: processes must be decided before they can be configured, and that is where most projects slip;
- rigidity: the ERP imposes its logic, and every deviation costs configuration, custom development or a workaround;
- dependence on the vendor or implementation partner for changes;
- recurring cost: subscription or maintenance, support, upgrades.
Signs your business needs one
- The same information is typed into two or three tools.
- Stock on the shelf and stock in the system never match.
- The margin on an order or a job is worked out by hand, after the fact.
- Month-end close takes days of reconciliation.
- One key person owns the spreadsheet the business runs on.
- Growth is adding sites, warehouses or legal entities.
If three of these sound familiar, the question is worth asking. If your main pain is one central spreadsheet, our article on replacing Excel with a custom application describes an intermediate step.
E-invoicing is raising the bar
A growing number of countries are making structured electronic invoices mandatory between businesses, so an ERP or invoicing tool increasingly has to produce machine-readable invoices and exchange them through approved networks or platforms. Rules and dates differ by country. If you trade with France, our guide to the French e-invoicing mandate shows what one such mandate means for your software.
How an ERP project unfolds
- Map current and target processes, from order to cash, with their exceptions.
- Choose the route: packaged ERP, industry-specific, open source, custom or hybrid.
- Configure or build in phases, starting with the flow that pays back the most.
- Migrate the data: items, customers, suppliers, stock, open balances. It is the most underestimated workstream, covered in legacy data migration.
- Test with real users on real cases before go-live.
- Go live, ideally at the start of an accounting period, with a rollback plan.
What an ERP costs
A packaged ERP costs licences or subscriptions, an implementation partner for configuration, data migration, training and yearly maintenance. As a reference point, Microsoft's Business Central pricing page listed the Essentials plan at 80 US dollars per user per month, paid yearly (checked on 6 November 2026), before any implementation services. Licences are often only part of the total.
To compare a packaged ERP with one built around your business, read custom ERP vs off-the-shelf ERP, then custom ERP development cost for the budget lines.
Five questions to answer before talking to vendors
- Which flow hurts most today: order to cash, purchasing, stock, production or month-end close?
- Which system owns each piece of data: customers, items, prices, invoices?
- What makes your business different from the standard process, and is that difference worth protecting?
- Which tools must stay, such as your accounting package or e-commerce platform, and do they offer an API?
- What does success look like in a year, in numbers you can check?
Written answers to these five questions make vendor demos far easier to judge, and they are the backbone of any requirements document.
The most common mistakes
- Choosing on a demo rather than on your processes written down.
- Rebuilding the old system as it was, workarounds included.
- Launching everything at once instead of flow by flow.
- Neglecting data migration, then going live with wrong stock.
- Forgetting the exit: data export, commitment period, termination terms and, for a custom build, rights to the code defined case by case in the contract.
When an ERP is not the answer
A full ERP is not always necessary. A small services firm can run perfectly well on connected invoicing, accounting and one business application. A company whose core process looks like no ERP on the market may prefer a custom core for what makes it different, connected to a packaged accounting system. What matters is that every piece of data has one system of record.
See it before you choose
The hardest part of an ERP project is picturing how the business will run before committing. For the part that is specific to you (an order entry screen, job tracking, a margin dashboard), we build a free prototype and present it on a video call within 5 business days. You judge real screens before any development, as explained in see your software before you pay for it.