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.

Häufig gestellte Fragen

What are ERP tools?

ERP tools refers to the individual modules, specialist programs and add-ons around an ERP system that together form an integrated tools stack. At the core, this includes financial accounting, order processing, warehouse management and reporting; depending on requirements, these are complemented by specialist tools such as APS, PIM, DAM or MES. The term covers both functions that are included directly in the standard ERP and stand-alone programs that are connected via an interface. The umbrella term therefore describes less a single product than the entire ecosystem of tools with which companies digitally map their business processes.

Which ERP tools are mandatory?

There is no legally prescribed mandatory set, but in practice financial accounting, order processing, warehouse management and reporting form the indispensable core of almost every ERP project. Depending on the business model, production planning (PPS), CRM, PIM or EDI are added as soon as manufacturing, sales management or electronic data interchange play a role. Which modules are actually needed depends more on the industry and processes than on company size. It makes sense to start with the ERP core and add specialist tools only once there is a clearly demonstrated need.

What is the difference between a suite strategy and a best-of-breed strategy?

With a suite strategy, all modules come from a single source, for example as an integrated complete package from one vendor, which means a unified data basis, fewer interfaces and only one contract partner. The best-of-breed approach, by contrast, combines the specialised top product for each function — for example an ERP core plus a separate CRM and a separate BI tool. Suites score with lower integration effort and consistent usability but tie you more strongly to one manufacturer (vendor lock-in), while best-of-breed delivers maximum functional depth and flexibility at the cost of more interfaces, contracts and maintenance effort. As a trend, a hybrid composable ERP approach is increasingly establishing itself, combining a stable core with specialised extensions via API-first architectures.

When are specialist tools such as PIM, MES or APS worthwhile?

Specialist tools are worthwhile above all when the functions included in the standard ERP are no longer sufficient for a complex volume or process scenario. A PIM typically becomes relevant in e-commerce with several thousand articles, a DAM with very large image and media databases, and an APS in manufacturing with pronounced capacity bottlenecks and many competing constraints. An MES plays to its strengths mainly in larger plants with real-time requirements for recording and controlling production. As a rough rule of thumb: only when the standard ERP module hits functional or performance limits does the extra effort justify a dedicated specialist tool.

Which tools connect the ERP with other systems?

To connect the ERP to other systems, the main options are iPaaS platforms (Integration Platform as a Service), EDI converters, classic middleware and API gateways. iPaaS solutions such as MuleSoft, Boomi or Lobster_data orchestrate data flows centrally and replace laborious point-to-point connections between individual applications. EDI converters, in turn, translate business documents into standardised exchange formats for data traffic with business partners. A common rule of thumb says that from around five interfaces to maintain, a dedicated integration tool pays off compared with individual direct connections.

Which interface standards should an ERP tool support?

Modern ERP tools should directly support common standards such as REST API, OData and EDI formats (such as EDIFACT) to avoid expensive custom interfaces. Particularly important in German B2B business are the e-invoicing formats XRechnung and ZUGFeRD (from version 2.0.1, as these fulfil the European standard EN 16931), because since 1 January 2025 domestic companies must be able to receive electronic invoices. For issuing, staggered transition periods apply: from 2027, companies with more than 800,000 euros in prior-year revenue must issue e-invoices, and from 2028 the obligation applies in principle to all domestic B2B transactions. Those who already cover these standards in their ERP reduce adaptation effort and secure compliance early.