JTL-Wawi and Microtech are two DACH-built SMB ERP options with strong followings in German online retail and small-business operations. Both have multi-decade history serving the German market with native German features. The comparison is unusual because both are deeply DACH-focused and rarely appear in non-German selections. This comparison covers the practical differences for German SMB buyers evaluating both.
Vendor and product positioning
JTL-Wawi: built by JTL-Software GmbH in Hueckelhoven, Germany. Originally an e-commerce-back-end for JTL-Shop, evolved into broader inventory-and-ERP system for online retailers. Strong free-tier offering (JTL-Wawi Community Edition with paid commercial scaling). Approximately 70,000 active users in DACH SMB online retail. Microtech: built by Microtech GmbH in Hargesheim, Germany. Long-established mid-market ERP for trade and small manufacturing operations. Several product lines including bueromaster, ERP-Master, Mid-Markets-Solution. Approximately 30,000 customers in DACH SMB. Both target German SMB with native German features and DATEV integration.
Functional comparison
JTL-Wawi strengths: deep e-commerce-focus, marketplace integration (Amazon, eBay, Otto, Kaufland), JTL-Shop tight integration, multi-channel order-management, customer-friendly free-tier. Microtech strengths: broader ERP scope including production-light manufacturing, longer mid-market history with established business-process patterns, stronger DATEV integration depth, broader DACH partner network. Where JTL wins: online retail, marketplace-heavy operations, free-tier accessibility. Where Microtech wins: trade and wholesale operations, light-manufacturing scenarios, broader-scope SMB operations with mixed business models.
Architecture and platform
JTL-Wawi: traditional Windows-based client-server architecture with SQL Server. Strong DACH-installed-base. Cloud-hosted variants emerging but core remains on-premises-style. Microtech: Windows-based client-server architecture similar to JTL. Microtech Cloud variant available for managed-hosting deployment. Neither product is fully cloud-native in the modern SaaS sense; both retain rich-client deployment models with cloud-hosting options. For SMB operations prioritising cloud-native architecture, modern alternatives (weclapp, Xentral, Business Central) may fit better.
Selection guidance
JTL-Wawi for: online retail SMBs (under 50 employees), JTL-Shop ecosystem operations, marketplace-heavy multi-channel operators, cost-sensitive operations valuing the free Community Edition. Microtech for: trade and small-wholesale operations, mixed business models including light manufacturing, established DACH SMB with broader operational scope than pure e-commerce. For modernisation: organisations outgrowing either product typically migrate to weclapp, Xentral, or Microsoft Dynamics 365 Business Central.
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, company 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 a must 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.
Which cloud options do the two systems offer?
Cloud availability, multi-tenancy and SaaS models often differ significantly. 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, company 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 rapid innovation cycles. Specific functions 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 UI for back-office staff.
