What Is an ERP? The Definition, Plainly
ERP stands for Enterprise Resource Planning: integrated business software that runs a company's core operational areas — finance and accounting, inventory, procurement, manufacturing, sales, and HR — on a single shared database. The point is one record and one truth: every department works from the same data, in real time.
Why that matters in practice: without an ERP, most growing companies operate on spreadsheet islands. The warehouse keeps one file, finance keeps another, sales keeps a third — and at month-end somebody spends days reconciling all three. An ERP eliminates that parallel data entry: when the warehouse ships a product, the stock level, the invoice, and the general ledger update at the same moment, from the same record.
One distinction worth making early: an ERP is broader than accounting software. Invoicing, ledger, and VAT reporting are the mandatory financial core — the ERP adds the operational layer on top: warehouse, manufacturing, procurement, projects, HR. If a tool only does the first part, it is a bookkeeping system, not an ERP.
There is also a compliance angle that international vendors often underestimate in Central Europe: many EU countries now mandate real-time, machine-readable invoice reporting. Hungary's NAV Online Invoice 3.0 is a strict example — every VAT invoice must be reported in real time via XML. An ERP that doesn't support the local scheme natively is effectively unusable there, and retrofitting it is expensive and fragile. When you evaluate a system, local tax compliance is a first-round filter, not a detail.
10–20 hrs
weekly admin (re-keying, reconciling) at a 20+ person company without an ERP
30–40%
the license share of the true 5-year ERP cost — the rest is implementation, training, operations
5–12 months
realistic timeline for a mid-size ERP implementation
ERP Modules — What Each One Does, and Who Needs It
An ERP is not one monolithic program but a set of modules on a shared database. The good news: you don't deploy them all at once. Most successful projects start with 2–3 modules and expand from there. Here are the main ones, and which company type needs which first:
| Module | What it does | Who needs it first |
|---|---|---|
| Finance & accounting | General ledger, invoicing, VAT and e-invoice reporting, payables/receivables, cash flow | Everyone — this is the mandatory core of any ERP |
| Inventory & warehouse (WMS) | Stock records, goods-in/goods-out, stocktaking, multi-warehouse, barcode/QR | Traders, e-commerce operators, distributors |
| Manufacturing (MES link) | Production orders, bill of materials (BOM), capacity planning, scrap and uptime tracking | Manufacturers — without it the ERP is just an accounting tool |
| CRM & sales | Customer master data, quotes, orders, price lists, sales reporting | Wherever winning revenue is the bottleneck |
| Procurement | Purchase orders, purchase requests, supplier scoring, framework contracts | Companies with many suppliers or raw-material dependency |
| HR & payroll | Employee master data, leave, attendance, payroll integration | Above ~50 employees, or with shift-based operations |
| Reporting / BI | Management dashboards, KPIs, automated month-end close | The leadership team — this is the ERP's "why" |
The warehouse layer is enough of a discipline on its own that at serious logistics volume a dedicated system is worth evaluating — see our WMS warehouse management page for the details. The CRM side is often a separate decision, too: many companies do better with a strong standalone CRM than with their ERP's weaker CRM module — here is how we approach custom CRM development.
SAP vs Odoo vs Custom ERP — Which One Fits You?
In 2026, an SME decision-maker typically chooses between three directions: an international boxed system (SAP Business One, Microsoft Dynamics, NetSuite), an open-core modular system (Odoo), or custom development. All three are legitimate — at different company sizes and different levels of process complexity.
| SAP Business One | Odoo | Custom ERP | |
|---|---|---|---|
| License cost | ~$100 per user/month, or €20,000–38,000 (8–15M HUF) for a 10-user license | ~€39 per user/month (Enterprise) | None — you own the code |
| Implementation cost | €38,000–90,000 (15–35M HUF) | €7,500–60,000 (3–24M HUF), depending on partner and scope | €38,000–200,000 (15–80M HUF); SME scope: €30,000–90,000 |
| Implementation time | 6–12 months | 3–9 months | 5–12 months |
| Customization | Limited and expensive (SDK development) | Good, but upgrading a heavily customized Odoo is painful | Unlimited — built around your process |
| Local tax compliance | Via partner add-ons | Via localization modules | Built in natively |
| Best fit | 30–100 employees with standard processes | 10–50 employees willing to adopt Odoo's logic | Industry-specific processes, 50+ users, or a legacy replacement |
The logic behind the table is simple. A boxed system is cheap as long as your processes fit its template — the moment you need customization, billable consulting hours erode the price advantage fast. Odoo is more flexible, but version-upgrading a deeply customized Odoo is a project in itself. A custom ERP costs more upfront, but there is no license fee, and it does exactly what your company does — nothing more, nothing less.
We have written detailed comparisons of the boxed route: SAP Business One alternatives for SMEs and Oracle NetSuite alternatives — both with concrete 5-year cost breakdowns. If the custom route interests you, our custom ERP development page shows the process and pricing. And for a market-by-market breakdown of systems available in Hungary, see the best Hungarian ERP systems in 2026.
When Does an ERP Pay Off? — 5 Signs
ERP is not a headcount question; it is a pain question. There are 8-person companies that already need one and 40-person companies that don't yet. If three of the following five signs apply to you, it is time to run the numbers:
- You enter the same data more than once. The order goes into the CRM, then manually into the invoicing tool, then into the inventory spreadsheet. Every copy is an error risk and a labor hour — at 10–15 hours per week, that is half a full-time role.
- Stock records regularly disagree with reality. The system says 40 units, the shelf holds 31. So you over-order (dead capital) or under-order (lost revenue) — on €125,000 of inventory, a 5–15% stock-cost gap is thousands of euros a year.
- Month-end close takes days. Finance hunts numbers across three sources, and the management report lands on the 10th — too late for the decisions it was meant to inform.
- Tax reporting and audits are a stress event.If a VAT audit means days of stitching data together, you don't have a single reliable source of truth.
- Growth stalls on admin.A new site, a webshop integration, or a second shift — and it turns out the current spreadsheet system doesn't scale; it just consumes more people.
Size rules of thumb: below roughly €750,000 revenue and 10–15 employees, invoicing + inventory software + a good accountant is usually enough. Between €750,000 and €2.5M, regional SaaS ERPs (implemented for €2,500–12,500) are the typical entry point. Above €2.5M and 30+ employees — especially with manufacturing or multiple sites — you are in the territory of the serious systems (SAP B1, Dynamics, partner-implemented Odoo) or custom development.
Implementation Pitfalls and the Real TCO — What Vendors Don't Mention
Industry research has shown the same picture for years: a large share of ERP projects run over budget or schedule. The pattern is almost always the same five mistakes:
- Underestimating data migration. The data in your legacy systems and spreadsheets is dirty: duplicate customers, stale item masters, missing fields. Cleaning it is 30–40% of the implementation effort — and it is missing from most proposals.
- Bolting software onto broken processes. Put an ERP on top of a chaotic process and you get a chaotic ERP. Half of an implementation is process design, not IT.
- No internal owner.Projects launched on the "IT will handle it" principle die quietly. You need a leader whose own KPI is the rollout's success.
- The customization spiral.With a boxed system, every "can we just adjust this" request is billable consulting. After 20–30 modifications, the boxed system costs as much as a custom one — without the flexibility.
- Skipping training. The system is worth exactly as much as your team actually uses. Without training, everyone drifts back to Excel and you maintain two systems for the price of one — paid twice.
This is why comparing license prices alone is misleading. The honest comparison is the 5-year TCO(total cost of ownership): license + implementation + customization + training + annual maintenance (typically 18–22% of the license price per year for boxed systems) + your own team's invested hours. On that horizon the ranking often flips: what looks cheaper on day one is frequently the more expensive option over 5 years.
Summary and Frequently Asked Questions
How much does an ERP system cost?
Regional SaaS ERPs start around €20–65 per user/month with implementation from €2,500–12,500. Odoo runs about €39 per user/month plus €7,500–60,000 for partner implementation. SAP Business One implementations typically land at €38,000–90,000. Custom ERP development ranges from €38,000–200,000 (15–80M HUF), with SME-scoped builds usually at €30,000–90,000. Licenses are only 30–40% of the real 5-year cost — the rest is implementation, customization, training, and maintenance.
What is the difference between ERP and CRM?
A CRM (Customer Relationship Management) manages your customer-facing pipeline: leads, quotes, and the sales process. An ERP manages your entire operation: finance, inventory, manufacturing, procurement, and HR. CRM can be one module inside an ERP, but many companies run a stronger standalone CRM instead. Rule of thumb: if winning revenue is your bottleneck, start with CRM; if fulfilling and administering it is, start with ERP.
How long does an ERP implementation take?
A simple invoicing/bookkeeping system: 4–8 weeks. A SaaS ERP with full functionality: 3–6 months. SAP Business One or Microsoft Dynamics 365 Business Central at medium complexity: 6–12 months. Custom ERP development: 5–12 months. The longest phase is almost never the software itself — it is data migration from legacy systems and reworking your processes.
Cloud or on-premise ERP — which should I choose?
For SMEs, cloud is the better choice in roughly 80% of cases: fast start, low entry cost, automatic updates, no servers to run. On-premise makes sense when data residency is non-negotiable (NIS2, GDPR, banking or healthcare), when you need deep customization, or when your monthly cloud bill stays above ~€2,500 — at that point self-hosting can win on a 5-year horizon.
What does the abbreviation ERP stand for?
ERP stands for Enterprise Resource Planning. It refers to integrated software that runs your company's core operational areas — finance and accounting, inventory, procurement, manufacturing, sales, and HR — on a single shared database. One record, one truth, visible to every department in real time.
Does a 10-person company need an ERP?
Not automatically. Below 10 people, an invoicing tool plus inventory tracking plus a good accountant is usually enough. ERP starts paying off when weekly administration (re-keying data, reconciling spreadsheets, chasing errors) reaches 10–15 hours, when stock records regularly disagree with reality, or when revenue passes roughly €750,000 (300M HUF) and multiple locations, a webshop, or manufacturing enter the picture.
When is custom ERP development worth it instead of an off-the-shelf system?
In three typical cases: (1) your processes are industry-specific and don't fit a boxed template (MES integration in manufacturing, project-based billing); (2) at 50+ users your SaaS license bill grows to €38,000–100,000 per year — over 5 years a custom system can be 50–70% cheaper; (3) your current system is legacy and the vendor is gone. Custom ERP starts at €38,000–200,000 (15–80M HUF) and takes 5–12 months to deliver.
If several of the signs above sounded familiar, the next step is not watching software demos — it is getting your own numbers straight. Start with the ERP TCO calculator — or book a free 30-minute consultation: we review your processes and tell you whether a boxed system or custom development is the better fit — including when the honest answer is neither, yet.
