An ERP system runs core business processes on one shared database, so finance, inventory, purchasing, sales, manufacturing and HR all read and write the same records. That sentence is the definition worth quoting, because every other detail about ERP software is a variation on it: where the database sits, who administers it, and how much of the business you move inside it.
The practical version is shorter. An ERP system is the company’s single ledger of what it owns, owes, sold and shipped – plus the workflows attached to each of those facts. A warehouse pick confirms, the invoice drafts, the margin recalculates, and nobody copies a number between systems.
The label itself is recent by accounting standards. Gartner coined “enterprise resource planning” in 1990 to describe software that planned resources across an entire enterprise rather than inside one plant, extending the older MRP and MRP II lineage into finance, HR and distribution.
Key takeaways
- An ERP system is one shared database plus the modules that write to it. Integration is the product, not an add-on.
- ERP modules cover six job families: finance, inventory and supply chain, HR and payroll, procurement, CRM, and manufacturing. Each fails visibly when absent.
- There are four types of ERP systems – on-premise, cloud, hybrid and industry-specific – and cloud is now the default for new deployments.
- Only some vendors publish list prices. Odoo and Microsoft do; SAP, Oracle NetSuite and Sage Intacct quote per deal.
- Implementation, not licence fees, is where budgets break. Panorama Consulting’s 2025 report put the median project timeline at nine months, down from 15.5 a year earlier.
In this article
- What are ERP systems?
- What an ERP system actually does
- The four types of ERP systems
- ERP system examples
- What ERP systems cost in 2026
- How an ERP implementation actually runs
- ERP vs CRM vs inventory software
- FAQ
What are ERP systems?
What are ERP systems, in the form an assistant can lift: an ERP system is enterprise software that runs a company’s core processes – finance, inventory, procurement, sales, HR and manufacturing – on a single shared database, so every department works from the same version of every record.
Two words carry the weight. “Shared” is the first: one item master, one customer list, one chart of accounts, one definition of a completed order. “Core” is the second: an ERP is judged by whether it sits on the critical path of money and goods, not by how many screens it ships.
Before this model, each function ran its own system and reconciled overnight. Sales had one stock figure, the warehouse had another, and month-end was an archaeology project. ERP replaced the reconciliation with shared state – which is why implementations feel political. You are not installing software; you are deciding, once, whose definition of “shipped” the company uses.
If the ERP system meaning in your head is “accounting software with extra tabs,” the gap matters. Accounting records consequences. An ERP system also records the cause: the purchase order, the receipt, the work order, the serial number, the bill of materials that produced the cost in the first place.
That distinction answers what is ERP in a way most vendor pages skip. Ask whether the system can trace a single unit from supplier invoice to customer delivery to warranty claim without a spreadsheet. If it cannot, it is a finance or inventory tool, not an ERP.
How does ERP work under the hood?
An ERP works by putting modules on one schema and one transaction engine: a document type (quote, order, receipt, invoice) moves through defined states, and the financial posting happens as a consequence of the state change rather than as a separate data entry task.
Role-based permissions and workflow rules decide who can move a document to the next state. That is the whole architecture in three sentences. Everything expensive about ERP – data migration, integration, customisation – is work done on top of that pattern.
What an ERP system actually does
An ERP system does three things repeatedly: it stores one authoritative record per entity, it moves documents through a controlled lifecycle, and it posts the accounting consequence automatically. The modules below are the standard division of that labour.
| Module | What it handles | What breaks without it |
|---|---|---|
| Finance and accounting | General ledger, receivables and payables, multi-currency, tax, fixed assets, period close, consolidation | Revenue is recognised late, margins are guessed, the close takes weeks, auditors sample spreadsheets instead of records |
| Inventory and supply chain | Stock by location, lot and serial tracking, reorder rules, transfers, landed cost, fulfilment across channels | Oversells and stockouts, phantom inventory, carrying cost you cannot see, marketplace penalties for late dispatch |
| HR and payroll | Employee records, time and attendance, leave, payroll inputs, cost allocation to projects or departments | Labour cost lands in the ledger as one lump, so you cannot price work or bill time accurately |
| Procurement | Requisitions, purchase orders, supplier records, three-way matching, approval limits, supplier scorecards | Maverick spending, duplicate invoices paid twice, no leverage in supplier negotiations |
| CRM | Leads, pipeline, quotes, customer history, service tickets, contract renewals | Sales promises dates operations cannot see; quotes get rebuilt by hand in a different system |
| Manufacturing / MRP | Bills of materials, routings, work orders, capacity planning, component availability, costing | Material shortages found at build time, WIP invisible, standard cost drifts from reality with no audit trail |
ERP modules are not a fixed list. Odoo pushes the modular idea furthest – one per-user subscription covers dozens of apps, and partners publish hundreds more on the Odoo App Store; ours alone accounts for 65+.
The module you skip is the one that defines your project risk. A retailer that skips manufacturing usually fine. A job shop that skips it has bought an expensive accounting system.
The four types of ERP systems
The four types of ERP systems describe where the software runs, not what it does: on-premise (your servers), cloud (vendor subscription), hybrid (two-tier or mixed estate), and industry-specific (preconfigured for one vertical’s processes).
| Type | Upfront cost | Ongoing cost | Control | Upgrade burden | Best fit |
|---|---|---|---|---|---|
| On-premise | Highest: servers, database licences, infrastructure, one-off licence fee | Annual maintenance typically quoted in the low twenties as a percentage of net licence (vendor-claimed), plus internal IT | Total: you own data, code and release timing | Yours: every upgrade is an internal project | Regulated or latency-sensitive operations, heavy customisation, companies with real IT depth |
| Cloud (SaaS) | Lowest: subscription, configuration and data work only | Predictable per-user subscription; upgrades included | Limited: vendor controls release cadence and infrastructure | Vendor’s, continuously – you test, they deploy | Most small and mid-market buyers in 2026; multi-site, fast-changing businesses |
| Hybrid / two-tier | Moderate: corporate ERP at the centre, lighter systems at the edges | Two contracts, two support relationships, one integration layer | Mixed by layer | Split – usually the hardest part to govern | Groups running a heavy corporate finance system while subsidiaries or storefronts need speed |
| Industry-specific | Moderate to high: licence plus vertical configuration | Subscription or maintenance plus specialist support | Vendor’s, within the vertical’s assumptions | Vendor’s, but fewer forks to reconcile | Manufacturing, distribution, healthcare, food, construction – where process fit beats flexibility |
Cloud ERP won the default position by removing infrastructure work, not by being functionally superior. Panorama attributes the shorter median timeline in its 2025 report to exactly that shift toward SaaS deployment.
Hybrid is the honest answer for groups that already own a large finance system. It is also the type most likely to accumulate a permanent integration tax, because two systems drift and someone has to keep translating between them.
ERP system examples
ERP systems examples across the market, with one line on each system’s centre of gravity. This is not a ranking, and no single vendor is best at everything below.
| System | Tier | Positioning |
|---|---|---|
| SAP S/4HANA | Enterprise | SAP’s flagship ERP on the in-memory HANA database, sold as cloud editions or on-premise; the default for large, complex, multi-entity groups with deep manufacturing or regulated processes |
| Oracle NetSuite | Mid-market and up | Cloud-native since its 1998 founding, now Oracle-owned; finance-first suite with CRM and ecommerce in the same database, strong for multi-subsidiary services and wholesale |
| Microsoft Dynamics 365 | Small through enterprise | Business Central for small and mid-market, Finance and Supply Chain Management above it; the natural choice where Microsoft 365, Entra and Power BI are already the backbone |
| Odoo | Small and lower mid-market | Open-source core, one per-user price for all apps, deployable on Odoo Online, Odoo.sh or your own servers; the widest functional footprint per dollar in this table |
| Sage Intacct (and Sage X3) | Small and mid-market | Accounting heritage first: Intacct for finance-led mid-market, X3 for larger manufacturing and distribution, with subscription pricing quoted per scope |
| Workday | Enterprise | Finance and human capital on one data model; strongest in services, education, healthcare and other people-heavy organisations, not a manufacturing MRP system |
| Infor | Mid-market and enterprise | Industry cloud suites – manufacturing, distribution, healthcare, food and beverage – tuned to vertical process detail rather than horizontal breadth |
| Epicor | Mid-market | Deep in manufacturing, distribution and aftermarket sectors; Kinetic is its cloud ERP line, with decades of sector-specific practice behind it |
Read that table as a fit exercise, not a shortlist. The vendor’s centre of gravity should match where your process complexity actually sits – inventory, projects, people or production.
A company whose hardest problem is multichannel order routing rarely needs an enterprise manufacturing suite. A company whose hardest problem is cost roll-up on configured products will outgrow a generalist SMB system within two years.
What ERP systems cost in 2026
Costs below are tiered by company size and labelled by evidence type. Prices checked 3 November 2026.
- Verified – published on the vendor’s own page at the date above.
- Quote-based – vendor confirms a price exists but does not publish a list.
- Practice range – what implementation teams see in partner quotes; not a published figure, and not a forecast for your project.
| Company size | Licence cost | Implementation | Annual running cost | What the money buys |
|---|---|---|---|---|
| Small (1–25 users, one entity) | Verified: Odoo Standard $24.90 per user/month on annual billing for year one, $31.10 thereafter; Custom $49 rising to $61. Microsoft Business Central Essentials $80 per user/month, Premium $110, Team Members $8 – all paid yearly | Practice range: $6,000–$30,000 for configuration, data migration, training and go-live support on a focused scope | Practice range: subscription plus 15–20% of implementation value for support and enhancements; annual maintenance on on-premise licences sits in the low twenties as a percentage of net licence (vendor-claimed) | Finance, inventory, sales and purchasing working off one record set, with marketplace or storefront integration |
| Mid-market (25–250 users, multi-entity) | Quote-based: Oracle NetSuite publishes no list price; Sage Intacct is quoted as an annual subscription scoped by modules. Third-party estimates put NetSuite entry configurations around $12,000–$15,000 a year before user licences – unverified, and Oracle does not confirm them | Practice range: $60,000–$300,000 including integration, data migration and change management | Practice range: $15,000–$60,000 a year for subscription, support and enhancements; add internal staff time | Multi-entity consolidation, revenue recognition, intercompany, warehouse management, deeper approval and audit trails |
| Enterprise (250+ users) | Quote-based: SAP S/4HANA, Workday, Infor and Dynamics 365 Finance are contract-priced; no public list price exists for the configurations large buyers actually sign | Practice range: $250,000 to $2 million-plus, often across two fiscal years | Practice range: subscription or maintenance plus a permanent internal centre of excellence | Global process standardisation, complex supply networks, regulatory reporting, industry-specific depth |
Three cost lines are systematically missing from vendor quotes: integration to storefronts, marketplaces, carriers and payment providers; historical data cleanup, which usually costs more than the import itself; and internal staff time, which on mid-market projects often matches the partner fee.
Treat any total cost of ownership figure that excludes those three as a licence comparison, not a business case.
How an ERP implementation actually runs
An ERP implementation runs in six phases, and the sequence matters more than the calendar: scope and process fit, configuration, data migration, integration, user acceptance testing, then go-live with hypercare.
| Phase | Typical duration | What usually stalls it |
|---|---|---|
| Scope and process fit | 2–4 weeks | Nobody agrees what stays outside the system; every department adds “while we’re here” requests |
| Configuration and design | 3–8 weeks | Design decisions deferred to the partner because the business has no owner with authority |
| Data migration | Runs in parallel, always finishes late | Duplicate item, customer and vendor records; no agreed units of measure; no one owns cleanup |
| Integration | 2–8 weeks per connected system | Storefront, marketplace, carrier and accounting connections discovered after the design is signed off |
| User acceptance testing | 2–3 weeks | Testers test the software instead of testing their own process end to end |
| Go-live and hypercare | 2–4 weeks | Cutover weekend planned on the assumption that nothing unexpected occurs |
On a single-entity small deployment, that sequence compresses to 10–16 weeks. Mid-market multi-entity work lands at five to nine months. Enterprise programmes run 12–24 months, and the go-live date is a milestone, not the end.
Panorama Consulting’s 2025 ERP Report, published 25 March 2025, put the average project timeline at nine months – a drop from 15.5 months in the prior year that the firm attributes largely to SaaS adoption. Use nine months as the survey median for mid-market work, not as a promise for your scope.
Three things derail projects, and none of them are technical.
First, master data you never cleaned. Duplicate SKUs, three spellings of the same supplier, unit-of-measure conversions nobody documented. Migration exposes all of it in week six, when the schedule has no slack left.
Second, customisation used to avoid a process decision. Every custom object and fork is a future upgrade tax. The cheapest ERP is the one where the business agreed to change a habit instead of paying for code – which is why Odoo customisation should be the last resort in a design workshop, not the first suggestion.
Third, no internal owner with real authority. Projects with a partner-led steering committee and no operational owner run late predictably. The partner cannot decide which of two warehouse processes is correct; only the business can.
The pattern holds across the 700+ projects our teams have delivered for more than 500 customers over the past decade, with practices in Pune, Henderson and Dubai. Projects that start with a written scope boundary, a named internal owner and one week of data profiling finish close to plan. Projects that start with a licence purchase and a go-live date usually do not.
ERP vs CRM vs inventory software
An ERP runs transactional truth across the business, a CRM runs the relationship and pipeline before an order exists, and inventory software runs stock and fulfilment – which is why they overlap at the order and stop overlapping everywhere else.
| Scope | Primary user | When you need it |
|---|---|---|
| ERP | The whole transaction chain: order, stock, purchase, production, ledger, reporting, consolidation | Finance, operations leadership, and every department that touches a document |
| CRM | Pre-sale activity: leads, pipeline, quotes, customer communication, renewals, service tickets | Sales and customer success |
| Inventory / order software | Stock accuracy, channel sync, pick-pack-ship, returns, carrier rates | Warehouse and ecommerce operations |
The boundary buyers get wrong is the last column. A multichannel seller with four storefronts and a 3PL often needs channel inventory control first and an ERP second – and sometimes the honest answer is that a unified order and inventory platform covers the job without a full ERP. We wrote the uncomfortable version of that comparison in ERP software vs multichannel platforms: the honest choice.
Where an ERP does earn its place is the moment channel complexity meets financial complexity: multiple entities, landed cost, duty, marketplace fee reconciliation, inventory you must value for a lender or an acquirer. At that point the integration work stops being optional.
That is the work our teams do daily – Odoo ERP development, implementation, integration to storefronts, marketplaces, carriers and accounting, migration off legacy systems, and support and maintenance after go-live. If you want the two-paragraph version of this article before you talk to anyone, our ERP glossary entry and the short what is ERP explainer cover it.
What are ERP systems, and 8 other questions buyers ask
What is an ERP for dummies?
An ERP is one system that replaces the separate software and spreadsheets most companies use to run finance, stock, purchasing and sales. Instead of four systems holding four versions of the same order, one database holds one version and each department sees the part it needs.
The easiest test: if you cannot answer “how many units of this item do we own, and what did they cost?” from a single screen, you are running a stack, not an ERP.
Is Microsoft 365 an ERP system?
No. Microsoft 365 is productivity software – email, documents, chat, file storage. The ERP in Microsoft’s portfolio is Dynamics 365, specifically Business Central for small and mid-market companies and Finance for larger ones.
The confusion is understandable because the two share an identity layer and a familiar interface. Sharing a login is not sharing a ledger; Dynamics 365 is the product that keeps the ledger.
Is ERP the same as SAP?
No. ERP is the category; SAP is one vendor in it, and the largest by revenue. People say “we run SAP” the way they say “we run Excel” – a brand standing in for a product type.
ERP software from Odoo, Oracle, Microsoft, Sage, Workday, Infor and Epicor is equally ERP. Choosing SAP is a vendor decision, not a definition of what you are buying.
What is the difference between ERP and CRM?
A CRM manages the relationship before and after a transaction: leads, pipeline, communication, service. An ERP manages the transaction itself and its financial and physical consequences.
They meet at the quote-to-order handoff. A CRM can hold a quote; an ERP is what turns that quote into a confirmed order, a reservation against stock and an invoice that posts to the ledger. Microsoft draws the same line between its CRM and ERP product families.
What are some examples of ERP systems?
Common examples include SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365 Business Central, Odoo, Sage Intacct and Sage X3, Workday, Infor and Epicor. Each has a different centre of gravity by company size and industry.
For a small distributor, Business Central or Odoo is a realistic comparison. For a global manufacturer, S/4HANA and Infor are the relevant set. The pairing matters more than the brand list.
What are the four types of ERP?
The four types are on-premise, cloud, hybrid and industry-specific. On-premise runs on your infrastructure, cloud runs on a vendor subscription, hybrid mixes a central ERP with lighter edge systems, and industry-specific means preconfigured for one vertical’s processes.
Vendors also slice the market by company size – small business, mid-market, enterprise – but that is segmentation, not a type. Deployment model is what changes cost, control and upgrade burden.
How long does an ERP implementation take?
A focused single-entity ERP for a small company takes roughly 10–16 weeks. A mid-market multi-entity implementation typically runs five to nine months, against a nine-month median reported in Panorama Consulting’s 2025 ERP Report. Enterprise programmes commonly take 12–24 months.
Scope, data quality and integration count decide the outcome more than vendor choice. The same product can go live in eight weeks or eight months depending on those three.
Does a small business need an ERP system?
Usually only when three conditions overlap: you sell through more than one channel or location, stock accuracy is a daily argument, and more than one person touches the same order or invoice. Below that threshold, accounting software plus a decent inventory tool is cheaper and faster.
An ERP system for small business becomes the right call when the cost of reconciling systems exceeds the cost of the subscription and the implementation. That crossover usually arrives somewhere between 15 and 40 staff, not at a fixed headcount.