What Is ERP? A Plain-English Explanation

ERP stands for Enterprise Resource Planning. That doesn't tell you much. Here's a more useful definition:

An ERP is one database that the whole business works from. Sales, purchasing, the warehouse, production and finance all record what they do in the same place, so a sales order, the stock it consumes, the delivery and the invoice are all linked to each other.

That's it. Everything else (the modules, the dashboards, the AI features vendors like to talk about) sits on top of that single shared record.

What an ERP replaces

Most businesses don't buy an ERP because they want "enterprise resource planning". They buy one because something hurts. Usually it's a mix of these:

• An accounting package such as QuickBooks, Xero, Tally or Sage
• A few spreadsheets that track stock, open orders or production
• An eCommerce platform that doesn't really talk to anything
• Email threads standing in for purchase approvals
• One person who "just knows" where everything is

Each of these works fine on its own. The trouble is in the gaps between them. Someone types the Shopify order into the accounting system. Someone else updates the stock sheet, or forgets to. At month-end, finance spends three days working out why the numbers don't agree.

An ERP closes those gaps by making each step update the next one automatically.

The modules you'll hear about

Vendors package ERP functionality into modules (Odoo calls them "apps"). The names vary, but the core set is pretty consistent:

You don't need all of them on day one. A distributor might start with sales, purchasing, inventory and accounting and never touch manufacturing. A services firm might care most about projects, timesheets and invoicing.

How do you know you need one?

There's no revenue threshold. These are the signs we look for when someone asks us whether it's time:

1. The same data is typed in more than once. Orders, customer details or stock adjustments get re-keyed between systems.
2. Nobody trusts the stock figure. People walk to the shelf to check before promising a delivery date.
3. Month-end takes too long. If closing the books takes more than a week because of reconciliation, the operational data isn't flowing into finance properly.
4. Growth is adding admin headcount. Doubling orders shouldn't mean doubling the people who process them.
5. You can't answer simple margin questions. "What did we actually make on that customer last quarter?" should take minutes, not a project.

If two or three of these sound familiar, an ERP is probably worth looking at. If none do, you may be fine with what you have, and that's a perfectly good answer.

Cloud, on-premise, open source

Three questions come up early:

Cloud or on-premise? Most new implementations are cloud-hosted, either as SaaS from the vendor or on a server you rent. On-premise still makes sense in a few cases, such as sites with poor connectivity or strict data residency rules. We cover this properly in cloud ERP vs on-premise ERP.

Proprietary or open source? Open-source ERPs such as Odoo Community and ERPNext don't charge licence fees. You still pay for implementation, hosting and support. See our open-source ERP guide for where that trade-off works.

Off the shelf or custom? Almost always off the shelf, with configuration and a small amount of custom work. Building an ERP from scratch is rarely justified. We explain why in custom ERP vs off-the-shelf ERP.

What an ERP won't do

It's worth being honest about this part. An ERP won't fix a process nobody has agreed on. It won't clean your data for you. And it won't make people use it. Those are all project problems, not software problems, and they are where most implementations succeed or fail. The ERP implementation guide goes into that side in detail.

Where to go from here

If you're early in the process, read how to choose an ERP system next. If you already have a shortlist and want a second opinion, a short ERP consultation with someone who has implemented a few is usually the cheapest way to avoid an expensive mistake.