ERP Systems — the comprehensive overview for DACH mid-market buyers
An ERP system (Enterprise Resource Planning) integrates the operational and financial processes of a company in a single coherent system. It records every order, every shipment, every invoice, every stock movement and every accounting entry in a shared data model, so that the business runs from one source of truth rather than from a constellation of disconnected tools. For the German Mid-Market, the ERP is the backbone system on top of which CRM, e-commerce, manufacturing and HR processes are organised.
This page is the cornerstone overview. It covers what an ERP system is and is not, where the concept came from, what the modules cover, which deployment models exist, how the vendor landscape is structured and how to run a credible selection process. Each section links to a deeper guide for buyers who need detail.
Definition: what an ERP system is
An ERP system is an integrated software platform that supports the operational and administrative processes of a company across functional boundaries. The technical hallmarks are a shared data model (customers, suppliers, products, accounts, transactions all live in one schema), workflow orchestration across functions (a customer order updates inventory, triggers procurement, schedules production, posts to accounting) and a consolidated reporting layer that draws from the same data.
What an ERP system is not: a CRM (customer relationship management) on its own; an accounting package on its own; a shop system on its own; or a collection of best-of-breed tools tied together by manual exports. Each of those covers a slice of the ERP scope but none of them, individually, qualifies as an ERP. The defining property is integration across the operational backbone, not the breadth of features in any single module.
Modern ERP systems increasingly extend beyond the classical core into CRM, project management, HR, e-commerce, supply-chain analytics and even light manufacturing execution. The boundary between ‘ERP’ and ‘business platform’ is intentionally blurred by the major vendors; for buyers, the practical question is what the system needs to cover end-to-end.
A short history of ERP
The lineage runs from MRP (Material Requirements Planning, 1960s – production planning from bill of materials and inventory data) via MRP II (Manufacturing Resource Planning, 1980s – MRP plus capacity planning and master scheduling) to ERP proper (1990s – financials, sales, procurement, manufacturing and HR in one system). The 1990s consolidation around SAP R/3, Oracle Applications, JD Edwards, PeopleSoft and Baan defined the modern enterprise-grade ERP category.
The 2000s and 2010s saw two parallel developments: industry verticalisation (Mid-Market-specific products for discrete manufacturing, plant engineering, food production, automotive, pharma, fashion) and the cloud transition (NetSuite as the early SaaS-native ERP, followed by Workday for HR, then Salesforce, then the major suites with their own cloud editions). The 2020s have shaped the next generation: composable ERP, AI-native ERP and the gradual end of on-premises as the default deployment model.
The history matters because the historical generation of an ERP product still shapes its architecture and pricing model. A late-1990s on-prem product retrofitted to the cloud behaves differently from a cloud-native product built in the 2010s, even when both vendors describe their offering as ‘cloud ERP’.
Modules of an ERP system
The classical module scope of a mid-market ERP covers eight functional areas. Financial accounting handles general ledger, accounts receivable, accounts payable, fixed assets and the German-specific GoBD-compliant audit trail; DATEV export is standard. Controlling covers cost-centre accounting, internal orders, profit-centre accounting and product costing. Sales and distribution handles quotes, orders, deliveries and invoicing, including credit-note and cancellation flows that satisfy UStG requirements. Procurement covers supplier orders, goods receipt, invoice matching and supplier-master management.
Inventory and warehouse management covers stock tracking at bin or shelf level, stocktake, picking and packing, carrier-label generation. Production planning covers BOMs, routings, work orders, capacity planning and shop-floor data collection — the core domain for discrete and process manufacturing. CRM covers contact management, opportunity tracking and customer-service workflows; many mid-market ERPs ship a serviceable CRM module, others integrate to dedicated CRM products. HR covers employee master data, time tracking, leave management; payroll is usually a dedicated DATEV or HR product integrated to the ERP rather than a native module.
On top of the core, modern ERP systems add modules for project management, service management, quality management, plant maintenance, supply-chain planning, business intelligence and increasingly e-commerce / marketplace integration. The right module scope depends on the business model; very few mid-market companies need all of them.
Deployment models
Four deployment models dominate the 2026 market. Public cloud SaaS — multi-tenant SaaS hosted by the vendor on hyperscaler infrastructure. Fast to start, low operational burden, fixed update cadence, restricted customisation envelope. The reference products are SAP S/4HANA Cloud Public Edition, Oracle NetSuite, Microsoft Dynamics 365 Business Central, Workday.
Private cloud SaaS — single-tenant dedicated deployment, usually still vendor- or partner-hosted. The reference products are SAP RISE Private Edition, Infor CloudSuite (dedicated tier). More customisation freedom, higher cost, more customer-side operational responsibility than public SaaS.
Hosted on-premises — the traditional on-prem product deployed by a hosting partner on customer-dedicated infrastructure. The standard cloud path for the German Mid-Market specialists (proAlpha, abas, oxaion, ams.erp, SelectLine). Full customisation freedom, customer controls upgrade cadence, infrastructure is outsourced.
On-premises — the traditional model with customer-owned infrastructure. Decreasingly common for new deployments but still operational at many established Mid-Market companies. Companies that consciously choose new on-prem deployments today typically have strict data-sovereignty or air-gap requirements.
The 2026 DACH market organises into four tiers. Tier-1: SAP S/4HANA and Oracle Fusion Cloud cover the upper enterprise and complex multi-entity Mid-Market. Upper mid-market: Microsoft Dynamics 365 (F&O and Business Central), Infor CloudSuite, IFS Cloud and Oracle NetSuite cover ambitious mid-market companies that want suite-class capability without tier-1 implementation effort.
Mid-Market ERP: the heart of the German market. proAlpha, abas ERP, oxaion, ams.erp, PSI Penta, Asseco APplus, Comarch ERP Enterprise, SoftENGINE, godesys and others serve discrete manufacturing, plant engineering, project business and other German-specific verticals with deep industry templates and high customisation freedom.
Cloud-native SMB / Mid-Market: myfactory, weclapp, Haufe X360, scopevisio, BMD, Sage Business Cloud, Lexware Office, JTL-Wawi, Xentral, Pickware, plentyOne, Billbee and similar products cover SMB and lower mid-market segments with subscription pricing and faster implementation.
Detail per category lives in our ERP programs overview.
Mid-market vs enterprise
The choice between mid-market and enterprise ERP is rarely about company size alone; it is about process complexity, multi-entity footprint and customisation appetite. A 500-person service business with a single legal entity and standardised processes can run a mid-market product comfortably; a 250-person specialty chemicals manufacturer with 8 legal entities and complex regulatory reporting may need an enterprise-grade product despite the headcount.
The honest mid-market positioning of the German Mid-Market specialists is competitive against enterprise products for companies whose differentiator is industry process depth rather than multi-country footprint. The honest positioning of the enterprise products is competitive when the company actually consumes the multi-entity, multi-country, multi-GAAP capability that the enterprise product is built to deliver. Mismatches go in both directions and produce expensive over-buying or under-buying.
Selection process
A credible mid-market ERP selection runs in five phases over 6–10 months. Phase 1 — requirements (8–14 weeks): business workshops, requirements document, MoSCoW prioritisation. See our requirements document template and the worked example. Phase 2 — long-list (2–4 weeks): 8–15 vendors filtered down to a structured long-list, RFP issued with the requirements document. The mechanics live in our ERP RFP process playbook. Phase 3 — short-list and demos (4–8 weeks): 3–5 finalists, scripted demo days against the customer's own use cases, reference-customer checks. Phase 4 — commercial negotiation (4–8 weeks): licence and services pricing, contract terms, SLA, exit clauses, implementation-partner selection. Phase 5 — due diligence and signature (2–4 weeks): security review, data-residency review, final business-case validation.
The cost overview that anchors the business case is in our ERP cost overview. The compare-systems methodology is in our compare ERP systems guide.
An ERP system is software that connects all key areas of a company (accounting, warehousing, sales, production, HR) on a shared data basis — instead of running them in separate programs. In practice, the exact shape varies with the industry, size class and customising depth of the specific ERP setup. A well-founded answer always requires looking at the company's individual business processes and strategic IT roadmap.
Which ERP systems are available in the DACH region?
Over 300 vendors — from SAP S/4HANA and Microsoft Dynamics 365, Oracle NetSuite, proAlpha, abas and Sage through to weclapp, Xentral, myfactory and open-source options such as Odoo or ERPNext. Together, the vendors named cover over 70 % of the relevant DACH market, but leave specialised industry solutions aside. For industry-specific requirements, it is worth looking at industry specialists such as ams.erp (mechanical engineering), CSB-System (food) or Comarch (energy).
How long does an ERP implementation take?
SMEs with cloud ERP: 3–6 months. Mid-market: 6–12 months. Corporate groups with a greenfield migration: 18–36 months.
What does an ERP system cost?
30,000–150,000 EUR (SME, over 5 years) up to several million euros (corporate group). Cloud subscriptions from 50 EUR/user/month. Licence fees typically account for only 25-35 % of total project costs; the remaining 65-75 % arises from implementation, customising, training and data migration.
Which ERP is the best in 2026?
There is no single best — the choice depends on industry, size and strategic goals. Top cloud options: weclapp, NetSuite, MS BC. Top for corporate groups: SAP S/4HANA.
How quickly does an ERP pay for itself?
Realistically 3-5 years. Clearly defined ROI drivers are important: efficiency gains, fewer manual errors, faster processes. In practice, the exact shape varies with the industry, size class and customising depth of the specific ERP setup.
What is composable ERP?
A modular architecture built from best-of-breed tools instead of a monolithic suite. More in the glossary entry on composable ERP. In practice, the exact shape varies with the industry, size class and customising depth of the specific ERP setup.
