Comarch ERP Enterprise and APplus are both DACH mid-market manufacturing ERPs with similar target customer profiles. Both serve 100-500 employee discrete-manufacturing operations with variant complexity. The comparison frequently arises in DACH mid-market evaluations alongside abas, proALPHA and godesys. This comparison covers the practical differences shaping selection.
Vendor positioning
Comarch ERP Enterprise: Polish-headquartered company (Cracow) with substantial DACH presence (Munich, Dresden offices). Approximately 3,000 customers globally including substantial DACH manufacturing customers. APplus: developed by asseco Solutions Germany (formerly Cosmos), part of Asseco Group. Approximately 1,500 customers predominantly DACH mid-market manufacturing. Both target similar customer profiles; positioning and ecosystem alignment differ slightly.
Functional comparison
Both products cover comprehensive mid-market manufacturing scope. Comarch strengths: integrated BI and DMS modules, multi-language and multi-country capabilities, broader ERP scope including distribution depth alongside manufacturing. APplus strengths: deeper manufacturing-focused capability with native variant configuration and integrated APS, stronger project-business support. Functional parity: core financials, basic manufacturing, multi-entity capabilities, DACH compliance requirements. Differentiation lives in specific functional depths and ecosystem orientation.
Deployment and architecture
Both products operate primarily as on-premises deployments with cloud-hosted options (Comarch Cloud, APplus Cloud). Customer-friendly customisation depth is similar; both retain customisation capability at the cost of upgrade complexity. For organisations prioritising cloud-native delivery, modern alternatives (Microsoft Dynamics 365 F&O, SAP S/4HANA Cloud) may fit better than either. Within the DACH mid-market manufacturing segment, both products remain credible.
Selection considerations
Practical differences for DACH mid-market manufacturing selection. For manufacturing-focused operations: APplus typically delivers better native manufacturing depth, integrated APS, and project-business capability. For broader operations combining manufacturing with distribution: Comarch's broader scope may fit better. For international expansion: Comarch's multi-country capability is somewhat stronger given international vendor footprint. Both should be evaluated alongside abas, proALPHA, godesys in DACH mid-market manufacturing selections to identify the best operational fit.
Implementation considerations
Implementation considerations beyond pure functional fit. Partner-network depth: the implementation partner often matters more than the product within a peer set. Both products typically have multiple credible DACH partners; evaluating partner-specific team CVs and project references matters substantially. Reference customers: speak to at least two customers per vendor in your specific industry segment. Industry-specific operational patterns reveal which product fits better in real operations. Total Cost of Ownership: compare 5-year TCO including software subscriptions, implementation services, ongoing support, infrastructure (where applicable) and internal effort. Cost differences typically 20-40% across comparable proposals; the absolute cost matters less than the operational outcome. Roadmap orientation: evaluate the vendor's investment trajectory and ecosystem strategy. Products with strong roadmap investment and growing ecosystem deliver better long-term value than products in maintenance mode despite functional parity at selection time.
Long-term operational considerations
Three additional patterns matter for long-term operations. (1) Upgrade and update model: cloud-SaaS products receive automatic updates; on-premises products require customer-managed upgrade projects. The cumulative cost-and-effort of upgrades over 5-10 years matters substantially. (2) Customisation discipline: products with constrained-customisation (clean-core) reduce long-term maintenance burden at the cost of operational flexibility. Products with flexible customisation enable operational specificity at the cost of upgrade complexity. Match the discipline to organisational capability. (3) Skills and talent: products with larger user-bases have larger pools of available IT-skilled professionals. Specialist products with smaller installed bases produce talent-acquisition friction over time. Selection should reflect not just current capability but long-term sustainability of the operations model.
Costs depend heavily on the number of users, module selection and deployment model. A 5-year TCO calculation should be carried out in any case — see the ERP cost overview. The exact configuration depends on the industry, size class and customizing depth of the specific ERP setup.
Which system has the better interfaces?
Both systems now offer REST APIs and common accounting connectors as standard. The depth of marketplace and e-commerce integrations varies — see the comparison table above for details. Standardised interface protocols (REST API, OData, EDIFACT, ZUGFeRD) are mandatory today and should be supported out of the box.
Which industries are a better fit for which system?
Industry fit is a key selection criterion. You will find a specific industry recommendation for each vendor in the main comparison section above as well as in the industry overview. Industry specialists offer preconfigured master data structures and compliance modules that drastically reduce customizing effort.
What cloud options do the two systems offer?
Cloud availability, multi-tenancy and SaaS models often differ considerably. See the main section above for the comparison — general cloud strategies are covered under cloud computing for ERP. The exact configuration depends on the industry, size class and customizing depth of the specific ERP setup.
Which system offers more AI/automation features?
The vendors' current AI roadmaps (SAP Joule, Microsoft Copilot, Oracle CloudWorld) show fast innovation cycles. Specific features vary by release — the vendor can confirm the current status. AI modules with practical relevance today include demand forecasting, predictive maintenance, invoice OCR and conversational UIs for back-office staff.
