ERP System Examples — what real DACH mid-market deployments look like

Vendor case studies tend to be marketing artefacts. This page collects four anonymised but realistic mid-market ERP deployments drawn from the DACH market — an automotive supplier on SAP S/4HANA, an e-commerce SMB on Xentral, a professional-services agency on weclapp and a mechanical-engineering Mid-Market on proAlpha. The point is not to recommend a specific product but to give buyers a calibrated sense of what comparable companies actually run and how their projects unfolded.

Example 1: automotive supplier on SAP S/4HANA

Profile: Tier-2 automotive supplier in Bavaria, 850 employees, EUR 220m revenue, two production sites, customers include three OEMs plus tier-1 integrators. System: SAP S/4HANA on RISE Private Edition since 2024, migrated from SAP ECC running since 2009. Modules in scope: Financials (FI/CO), Sales (SD), Materials Management (MM), Production Planning (PP), Quality Management (QM), Plant Maintenance (PM), Warehouse Management (EWM-light). Implementation: 22 months from project kickoff to second-site go-live, brownfield conversion path with selective re-implementation of customisations. Budget: EUR 4.8m total, including custom-code remediation. Implementation partner: a mid-tier SAP partner specialising in automotive. What worked: the brownfield conversion preserved more than 70 % of the customisation portfolio that had become process-critical, and the parallel-site go-live model limited business disruption. What did not: the EDI integration with one of the OEMs required a substantial additional effort that was not in the original scope, adding 4 months to the timeline.

Example 2: e-commerce SMB on Xentral

Profile: D2C cosmetics brand based in Hamburg, 28 employees, EUR 14m revenue, sales through own Shopware shop, Amazon, eBay and three EU marketplaces. System: Xentral Cloud since 2023, migrated from JTL-Wawi after outgrowing it at roughly 15k orders / month. Modules in scope: order management, multi-channel inventory, picking and packing, carrier integration (DHL, DPD), accounting export to DATEV, returns workflow. Implementation: 5 months from contract to stable go-live. Budget: approximately EUR 90k total, of which EUR 35k licences over the first 18 months, EUR 45k partner-led implementation and EUR 10k internal change-management. What worked: the marketplace integration package handled the four channels out of the box, eliminating the manual reconciliation cycle that had cost the previous setup. What did not: data migration from JTL took longer than scoped (4 weeks vs planned 2), particularly the supplier and product master data with its inconsistent attribute population.

Example 3: professional-services agency on weclapp

Profile: Digital agency in Berlin, 65 employees, EUR 9m revenue, project-based services billing model with retainer mix. System: weclapp Cloud since 2022, replacing a spreadsheet-plus-Lexware-plus-Trello setup that had reached its breaking point. Modules in scope: CRM, project management, time tracking, invoicing, accounting integration to DATEV, expense management. Implementation: 3.5 months from contract to go-live, partner-led with 50 % internal effort. Budget: approximately EUR 40k total over the first 18 months. What worked: the project-to-invoice workflow eliminated the 8–14 day delay between project close and invoice issue, materially improving cash flow. What did not: the time-tracking adoption took longer than expected — consultants resisted the granular tracking that the new system enabled, and full adoption needed an additional 4 months of internal coaching after go-live.

Example 4: mechanical-engineering Mid-Market on proAlpha

Profile: Specialist machine builder in Baden-Württemberg, 320 employees, EUR 95m revenue, project-based and configure-to-order business model, customers across Europe and the United States. System: proAlpha ERP on-premises since 2018, with a hosting transition to a certified hosting partner in 2024. Modules in scope: financials, project controlling, configure-to-order, production planning, variant management, service management, project-related procurement, CRM. Implementation: the original 2018 project ran 18 months; the 2024 hosting transition ran 6 months. What worked: the deep variant-management capability handled the complex configure-to-order model that off-the-shelf trade-focused ERP could not. What did not: reporting for the US subsidiary's tax filings was under-scoped at original go-live and was retrofitted over the following 12 months. Why proAlpha: the combination of mid-market price point, machine-building industry depth and German engineering process fit was decisive against the comparison list, which included Microsoft Dynamics 365 F&O, abas ERP, oxaion and IFS Cloud.

What the examples show

Three patterns recur across the four examples and the dozens of similar deployments the editorial team has reviewed. Timeline slippage clusters around data and integration, not around the core software. Three of the four cases above slipped on the same two workstreams. Implementation-partner choice matters more than vendor choice within a given product tier — the same SAP S/4HANA deployment can succeed or fail depending on the partner, even with identical product scope. The vendor selection question is rarely binary; mid-market buyers typically have two or three credible options after a proper RFP, and the decision usually comes down to partner ecosystem and contract terms rather than to a feature gap.

Buyers preparing their own project should look for these patterns in their reference checks — not the marketing wins, but the timeline slippages, the under-scoped workstreams and the partner-related friction.

Häufig gestellte Fragen

Which ERP system is the best example for SMEs?

In the SME segment, cloud-native all-rounders such as weclapp and Xentral are regarded as typical reference examples, because they cover merchandise management, order processing and accounting without any in-house IT infrastructure. For pure e-commerce scenarios with your own shop and marketplaces, JTL is a frequently cited example; for the classic financial accounting and merchandise management needs of small businesses, SelectLine or Lexware. Which system actually fits depends on industry, channel structure and the desired degree of automation, not on headcount alone. There is no universal “best” system — only the one with the best coverage of your own core processes.

What are the best-known ERP systems in Germany?

The best-known ERP vendors in the German market include SAP, Microsoft and Sage, complemented by accounting specialists such as Lexware and DATEV, which strictly speaking are financial accounting rather than full ERP solutions. Measured by revenue and by presence in the large-enterprise segment, SAP is regarded as the market leader in the DACH region; by the sheer number of installed seats, SMB-focused vendors such as Lexware or DATEV hold large shares. While SAP S/4HANA shapes primarily large companies and corporate groups, Lexware and SelectLine are more widespread among micro and small businesses. The precise market share figures vary considerably depending on the survey method (revenue, users or installations) and the source.

Which ERP systems serve as examples for mechanical engineering?

In machinery and plant engineering, proAlpha, abas ERP, IFS and ams.erp are regarded as typical industry examples, because they deeply cover variant manufacturing, bills of materials, project processing and production planning (APS/MES). proAlpha is tailored to the manufacturing mid-market and integrates production, finance, warehousing and CRM in one solution, while abas ERP is traditionally strong in variant and one-off manufacturing and ams.erp specialises in make-to-order and one-off production in special-purpose machine building. Large corporate groups also frequently run SAP S/4HANA or Microsoft Dynamics 365. The concrete fit depends on manufacturing depth, lot sizes and the need for fine-grained production control.

What distinguishes open-source ERP examples from proprietary systems?

Open-source examples such as Odoo, ERPNext, Apache OFBiz, iDempiere or Tryton make their source code openly available, so companies can adapt the software, host it themselves and avoid licence costs. The models differ, however: ERPNext is fully licensed under the GPL and delivers all modules freely, while Odoo follows an open-core model in which the Community Edition is licensed under the LGPL v3 and many advanced features are only available in the paid Enterprise Edition. Proprietary systems such as SAP, Microsoft Dynamics or Sage score instead with a dense partner network, vetted updates and mature DACH localisation. Taken as a whole, open source often shifts costs from licences towards implementation, hosting and internal know-how.

Which ERP system is a good example for e-commerce and online retail?

For online retail, Xentral, JTL, plentyOne and weclapp are regarded as common practical examples, because they consolidate orders from your own shop, marketplaces and brick-and-mortar sales in one system. Xentral is designed for multichannel scenarios in which retailers sell in parallel through their own shop and platforms such as Amazon or Otto and want to automate processes. JTL has established itself as a merchandise management system with strong shop and fulfilment integration, particularly in the e-commerce mid-market, while plentyOne (formerly plentymarkets) stands out with an especially large number of marketplace and shop integrations. Decisive for the selection are the number of sales channels, the order volume and the required interfaces to shop systems and shipping providers.

What do successful and failed ERP examples from practice show?

Practical examples show that project success depends less on the software itself than on process design. Successful implementations usually use the changeover to modernise workflows and align with the system standard, rather than replicating old processes one to one. Failed or heavily delayed projects frequently result from runaway customising, which drives total cost of ownership (TCO) well beyond plan and stretches implementation times. Realistic schedules, staying close to the standard and clean data management are therefore regarded as recurring success factors across all industries and size classes.