ERP Tools — the modules and adjacent software around the ERP
The ERP is the backbone, but the operational stack around it is broader. ERP tools in everyday usage covers the modules inside the ERP, the add-ons that vendors sell or that partners build, and the adjacent software that sits next to the ERP and integrates with it. This page maps the most relevant categories for the DACH mid-market and links into the dedicated articles for each.
Modules inside the ERP
The classical modules — financial accounting, controlling, sales, procurement, inventory, production planning, CRM-light, HR-light — ship as part of the ERP itself in most mid-market products. The boundary between ‘module’ and ‘add-on’ depends on the vendor's pricing model; some vendors package broadly with a high base licence, others sell module by module. The economic effect of the two pricing models converges in the steady state, but the negotiation dynamics during selection differ.
Industry modules — variant management, project controlling, configure-to-order, batch and serial tracking, recipe management, plant maintenance, service management — are sometimes included and sometimes priced as add-ons. The German Mid-Market specialists (proAlpha, abas, oxaion) tend to bundle industry modules into their packaged offers; the major suites (SAP, Dynamics 365, NetSuite) sell them as add-on modules or as industry editions.
Business intelligence and reporting
Native ERP reporting covers the operational reports that the business needs day-to-day. Strategic reporting and analytics increasingly run on dedicated data warehouse or lakehouse infrastructure with a BI tool on top — Power BI, Tableau, Qlik or Looker. The realistic mid-market pattern is to use the ERP's native reports for transactional reporting and a BI tool for cross-system analytics, executive dashboards and ad-hoc analysis.
Vendors that try to deliver all analytics inside the ERP itself routinely lose mid-market deals on the BI flexibility question. The honest answer is that ERP-native BI works for some companies and a separate BI stack is the right choice for others; the volume and complexity of the analytics workload drives the decision.
Warehouse management and MES
A WMS (warehouse management system) is the dedicated software for warehouse operations — chaotic storage, system-directed put-away, pick path optimisation, integration with conveyors and sorters. Mid-market ERPs ship light WMS modules; dedicated WMS products (e.g. Körber WMS, Manhattan, JDA, ProLogistics, viadat) are the answer above roughly 5,000 daily order lines or when automation enters the warehouse.
A MES (manufacturing execution system) sits between the ERP and the shop floor, capturing machine data, work-instruction execution, quality data and lot tracking. Mid-market manufacturers often start with an MES-light layer integrated into the ERP and move to a dedicated MES (Forcam, MPDV Hydra, iTAC, GFOS, Industrie Informatik cronetwork) as production volume and complexity grow.
PIM, DAM and product-related tools
A PIM (product information management) is the dedicated system for managing rich product data across many output channels — the ERP holds the commercial master data (SKU, price, stock), the PIM holds the marketing master data (descriptions, attributes, translations, images, channel-specific variants). The major DACH PIMs are Akeneo, Contentserv, censhare, Stibo and SAP Product Master Data Governance.
A DAM (digital asset management) manages images, videos and design files. Many mid-market companies start with the ERP's native asset handling, outgrow it during e-commerce expansion and migrate to a dedicated DAM (Bynder, Brandfolder, Frontify, Cloudinary).
DMS, e-invoicing and compliance tools
A DMS (document management system) handles document storage, indexing, workflow and GoBD-compliant archiving. The major DACH DMSs are ELO, d.velop, DocuWare, Kyocera Enterprise Information Manager (formerly Optimal Systems) and ecoDMS. The DMS sits alongside the ERP rather than inside it, with deep integration for invoices, contracts and HR documents.
E-invoicing tools cover the issuance and receipt of ZUGFeRD 2.x and XRechnung documents. Most modern ERPs include native e-invoicing capability; companies with complex e-invoicing requirements (Peppol, country-specific tax-authority reporting) often add a dedicated platform such as B2BRouter, Pagero or Edicom.
Integration platforms and iPaaS
The integration layer around the ERP increasingly runs on a dedicated iPaaS rather than on point-to-point custom code. The major platforms used in the DACH mid-market are Workato, Boomi, Microsoft Azure Logic Apps, MuleSoft, Lobster_data, SEEBURGER and the open-source ESBs (Apache Camel, n8n).
Mid-market companies should expect to make an iPaaS investment as part of any modern ERP project; the total integration count for a typical Mid-Market company is between 10 and 30 production interfaces, well above the threshold at which point-to-point code becomes unmanageable.
Related Topics
Frequently Asked Questions
Is BI a part of the ERP or a separate tool?
Both patterns are valid. Operational reporting belongs in the ERP; strategic analytics and cross-system reporting belong in a dedicated BI tool with its own data warehouse layer. The decision boundary is the volume and complexity of the analytics workload and the need to integrate non-ERP data sources (web analytics, CRM, marketing platforms).
Do we need a separate WMS at our size?
Below roughly 5,000 daily order lines or 200,000 SKUs the ERP's warehouse module typically suffices. Above either threshold, or when conveyors, sorters or goods-to-person automation enters the warehouse, a dedicated WMS is the realistic answer. Many mid-market mail-order companies hit the threshold during a peak season and underestimate the operational consequences until they do.
What is the difference between PIM and DMS?
A PIM manages structured product data (attributes, variants, translations, channel-specific content) for downstream publication to shops, marketplaces and catalogues. A DMS manages unstructured documents (invoices, contracts, drawings, HR files) for storage, workflow and archiving. They are complementary; a mid-market company with both an e-commerce business and a manufacturing operation typically runs both alongside the ERP.