ERP explained: what an enterprise resource planning system does

An ERP is a single business system that brings your finance, stock, purchasing, sales, production and reporting together on one shared database. The acronym stands for enterprise resource planning, and in French-speaking markets the same thing is called a progiciel de gestion intégré (PGI). If you have ever re-typed an order from one tool into another, or waited for someone to rebuild a spreadsheet before you could answer a simple question about margin or stock, you have felt the problem an ERP is designed to solve.

This guide gives a plain definition of an ERP, explains how it works, sets it apart from accounting software and a CRM, and describes who needs one and when. It is written for owners, finance directors and IT leaders at small and mid-sized UK companies who are weighing up whether to take the step.

ERP definition: what is an ERP?

An ERP is an integrated suite of business applications built around one central database. Each application, called a module, covers a function of the company: accounting, inventory, sales, purchasing, manufacturing, projects, human resources and so on. Because every module reads from and writes to the same database, an event recorded once is visible everywhere it matters.

Take a customer order. In an ERP, the sales order checks available stock, reserves it, triggers a purchase if something is short, schedules production if you make the item, produces the delivery note, raises the invoice and posts the accounting entries. Nobody re-keys anything. The finance team sees the same order the warehouse is picking.

That is the core idea behind a progiciel de gestion intégré: the word "integrated" refers to the shared data and the shared logic, not simply to a set of tools that happen to sit side by side.

The single database principle

The defining feature of an ERP is the single source of truth. A customer, a product, a supplier or a price list exists once, and every department uses that same record. This removes the usual symptoms of fragmented systems: duplicate customer files, stock figures that differ between the warehouse and the website, and invoices that do not match what was shipped.

It also changes how reporting works. Instead of exporting data from several tools and stitching it together, you query one database. Margin by product, ageing of debtors, stock value, order backlog and cash forecast all come from the same figures, so they agree with one another.

ERP, PGI and enterprise resource planning: the same thing

You will see several labels for the same category of software. "ERP" is the standard international term. "Enterprise resource planning system" is the full name. "Progiciel de gestion intégré" and its abbreviation "PGI" are the French equivalents you may meet in documentation from European vendors or in international groups. Some suppliers also say "business management software" for smaller products. The differences between these labels matter far less than the differences between the products themselves, which vary widely in scope, depth and cost.

The main modules of an ERP

Modules are the building blocks of an ERP. You rarely need all of them on day one; most companies start with a core and add more as the business grows. The exact names vary between publishers, but the typical set looks like this.

Core modules versus optional modules

Finance, sales, purchasing and inventory form the heart of most deployments. Manufacturing, project accounting, e-commerce connectors, quality management and advanced warehouse functions are usually added when the activity requires them. A good integrator will help you sequence these so that you go live with a coherent core rather than attempting everything at once.

Configuration, customisation and integration

Two ideas are worth separating. Configuration means adjusting the standard product through settings, workflows and fields, without changing the code. Customisation means developing something new. Configuration is cheaper to maintain and upgrade; heavy customisation can make later upgrades harder. Integration means connecting the ERP to other systems you keep, such as a payment provider, an e-commerce platform, a bank feed or a specialist piece of equipment.

How an ERP differs from accounting software, a CRM and spreadsheets

People often ask whether they really need an ERP when they already run accounting software and a CRM. The answer depends on how many things you are now stitching together manually.

ERP versus accounting software

Accounting software records money. It handles the sales and purchase ledgers, bank reconciliation, VAT returns and statutory accounts, and for many small businesses that is all that is needed. An ERP contains an accounting engine too, but it also records the operations that generate the money: the stock moves, the production orders, the timesheets and the deliveries. Each of those posts to the ledger automatically.

If your accountant spends part of the month rebuilding figures because stock is held in one file and sales in another, the gap between accounting software and an ERP is exactly the work you are doing by hand.

ERP versus CRM

A CRM, short for customer relationship management, focuses on the front of the commercial cycle: prospects, contacts, opportunities, quotations and follow-up. An ERP focuses on what happens once an order exists: availability, fulfilment, invoicing, collection and the effect on your accounts. The two overlap on quotations and customer records, and many ERP products include a basic CRM. Companies with a demanding sales operation sometimes keep a dedicated CRM and connect it to the ERP so that won deals flow into orders without re-entry.

ERP versus spreadsheets and a patchwork of tools

Spreadsheets are flexible and familiar, which is why they spread. Their weakness shows up when several people depend on them. Versions multiply, formulas break unnoticed, access cannot be controlled properly, and there is no audit trail of who changed what. A patchwork of specialist tools has a similar problem at the seams: each tool works, but the links between them rely on exports, imports and people's memory.

An ERP replaces those seams with controlled workflows, user permissions and a complete history of transactions.

What does an ERP do for a business?

The benefits are practical rather than abstract. They usually fall into a handful of areas.

• One version of the truth. Everyone works from the same customers, products and figures, so meetings are about decisions rather than about whose spreadsheet is right.
• Less manual re-entry. Data entered at the source flows through to the next step. That cuts errors and frees staff from repetitive typing.
• Better visibility of stock and cash. You see what you hold, what is on order and what is owed, in close to real time, which supports better purchasing and credit control.
• Faster month end and reporting. Because transactions post as they happen, closing the books involves checking rather than assembling.
• Control and traceability. Approval rules, role-based access and audit trails make it easier to demonstrate sound control to auditors, lenders and investors.
• Scalability. A system that can add users, entities, currencies and sites lets the company grow without rebuilding its tooling every time.
• Compliance support. Modern ERPs help with VAT, with digital record-keeping and with e-invoicing obligations. For the UK picture, see our guide to ERP and e-invoicing.

None of these benefits arrives automatically. They depend on clean data, clear processes and staff who are trained and willing to use the system, which is why implementation quality matters as much as product choice.

Who needs an ERP?

An ERP is not reserved for large corporations. Smaller companies increasingly adopt one because cloud delivery has lowered the barrier to entry. What matters is the complexity of your operations rather than your headcount.

Typical profiles

• Manufacturers that need bills of materials, production planning, costing and traceability. See ERP for manufacturing.
• Wholesalers and distributors managing large product ranges, multiple warehouses, supplier terms and customer-specific pricing. See ERP for wholesale and distribution.
• Online sellers that must keep website, marketplace and warehouse stock aligned. See ERP for e-commerce.
• Professional services firms that bill by time, milestone or retainer and need project profitability. See ERP for professional services.
• Construction, healthcare, food and drink and logistics businesses, each with specific needs around job costing, compliance, traceability or fleet and warehouse flows. Our sector pages cover them.

Small businesses

A small company does not need the most powerful product on the market, and over-buying is a common mistake. The right question is which processes cause the most friction today and which modules would remove it. Our guide to ERP for small business goes into the trade-offs in more detail.

Signs it is time to adopt an ERP

Few companies decide to buy an ERP in a calm moment. The trigger is usually a growing sense that the current set-up is holding the business back. These are the signals we hear most often.

1. The same data is entered in several places. Orders, customers or products are typed into more than one tool, and mistakes creep in.
2. Nobody trusts the stock figure. The warehouse, the website and the accounts disagree, and the true position needs a manual count to confirm.
3. Month end is slow and stressful. Closing relies on a few key people and a chain of spreadsheets.
4. Reporting takes days. Simple questions about margin by customer or product need a mini project each time.
5. Growth is adding complexity. You are opening a site, adding a subsidiary, trading in another currency or launching a new sales channel.
6. Customers or auditors expect more. Traceability, approval trails or digital records are being asked for and you struggle to provide them.
7. Key-person risk is rising. Critical know-how sits in one person's spreadsheet or in their head.
8. Your current software is reaching its limits. Licences are costly for what they deliver, upgrades are no longer supported, or the product cannot follow your processes.

If several of these ring true, the discussion is probably about when and how rather than whether. A structured requirements document is the best first step; our ERP requirements template gives you a framework to build on.

Cloud, on-premise and open-source ERP

Deployment is one of the first choices you will face. A cloud ERP runs on the publisher's or a partner's infrastructure and is accessed through a browser, with upgrades handled for you. An on-premise ERP is installed on your own servers or in a private hosting environment, which gives more control but also more responsibility for maintenance, security and backups. Many mid-sized companies now favour cloud, though sectors with specific constraints sometimes prefer to host themselves.

The trade-offs are covered in our comparison of cloud and on-premise ERP. Separately, some products are open source, meaning the source code is available and the licence model differs from traditional software. Our guide to open-source ERP explains what that does and does not change in practice.

The ERP products you will meet

The market is broad, and no single product suits every company. The five below are the ones most often shortlisted by the businesses we help, presented in a neutral order.

• Odoo is a modular business suite, available as open-source software and as a hosted service, and often chosen by small and mid-sized companies that want to start with a few applications and add more. See our page on Odoo integrators.
• Microsoft Dynamics 365 Business Central is a cloud business management product from Microsoft aimed at small and mid-sized organisations, closely tied to the wider Microsoft ecosystem. See Business Central.
• Sage is a long-established UK software publisher with products ranging from accounting to fuller ERP offerings, which makes it a familiar name for many British finance teams. See Sage.
• Oracle NetSuite is a cloud ERP suited to growing and multi-entity businesses that want finance, operations and commerce in a single platform. See Oracle NetSuite.
• SAP Business One is SAP's ERP for smaller companies and subsidiaries, with a strong footprint in trading and manufacturing. See SAP Business One.

We are not affiliated with any publisher, and we do not sell software. If you want to see how two of them stack up, our comparisons set them side by side, for example Odoo versus Business Central.

What is involved in adopting an ERP?

Choosing the software is only part of the work. An ERP project changes how people do their jobs, so it needs to be treated as a business project rather than an IT purchase.

The usual stages

1. Define the need. Map your processes, pain points and priorities, and agree what success looks like.
2. Shortlist and compare. Match products and integrators to your sector, size and budget. Our guide on how to choose an ERP sets out a method.
3. Scope and plan. Agree modules, data to migrate, integrations, responsibilities and a timetable with the integrator.
4. Configure and build. The integrator sets up the system, adapts workflows and develops any agreed extensions.
5. Migrate data and test. Customers, suppliers, products, open orders and balances are cleaned, loaded and checked.
6. Train and go live. Users are trained on their own processes, and the cut-over is planned carefully around a quiet period.
7. Support and improve. After go-live, the system is tuned, extended and kept up to date.

The details of each step are in our guide to ERP implementation. If you are replacing an existing system, read the notes on ERP migration too.

The role of the integrator

An ERP integrator is the firm that configures, adapts and deploys the software for your business, trains your team and often supports you afterwards. The quality of this partner has a major influence on the outcome, perhaps more than the product itself. That is why choosing an ERP integrator deserves as much attention as the software choice.

ERP Integrator is a free service. You describe your project, and we introduce you to a certified integrator suited to your sector, size and chosen software. The integrator then scopes and delivers the project. You can read more about how the service works.

What does an ERP cost?

Costs vary widely and depend on the product, the number of users, the modules, the amount of customisation and the effort needed for data migration and training. Costs typically include software subscriptions or licences, implementation services, integrations, training and ongoing support. We do not quote figures here because any number without context would mislead you. Our guide to ERP cost explains the components so that you can compare quotes on a like-for-like basis.

Common mistakes to avoid

Most ERP projects that struggle do so for reasons that have little to do with the software. The usual causes are unclear requirements, too much customisation, poor data quality, weak sponsorship from the leadership team, and insufficient training. Setting priorities early, keeping the scope realistic and involving the people who will use the system every day all help. Our article on ERP project mistakes goes through them in detail.

Summary

An ERP, or progiciel de gestion intégré, is a set of integrated modules that share one database so that finance, sales, purchasing, stock, production and projects work from the same information. It differs from accounting software because it manages the operations behind the figures, and from a CRM because it covers fulfilment, control and finance rather than prospecting. Companies usually need one when duplicated data, unreliable stock, slow reporting or growing complexity begin to cost more than a structured system would.

If you are at that point, a short conversation with an integrator can clarify which modules, which product and which approach fit your situation. You can start with our overview of ERP software or go straight to a request through ERP Integrator.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.