Skip to content
SAP, DATEV and Dynamics experts

ERP Integration for the Manufacturing Industry

Industrial companies deliver configurations, bills of materials and spare parts for machines with a twenty-year service life. We map this complexity — from BOM resolution through spare part identification to Kanban-driven restocking of C-parts.

ERP integration from 6,900 € net BOMs, spare parts and Kanban SAP, Dynamics and proAlpha connected

two-way

real-time sync

50+

integration projects

99.8%

uptime

15+

ERP systems connected

Fixed prices · net plus VAT

from 6,900 € fixed price net
  • Standard ERP connection: articles, stock, prices and orders synced bidirectionally
  • Spare parts shop with machine assignment via serial number
  • Kanban control loops and product configurator added on a time basis
  • Binding fixed price after a free system analysis

SAP Business One integration from 9,900 €, Microsoft Dynamics 365 Business Central from 6,900 €, DATEV accounting connection from 1,490 € per link. BOM, configurator and Kanban logic on a time basis — project day 990 € net (hourly rate 119 € per hour). Ongoing connector licenses are itemized separately. All prices net plus VAT. The project day is a package price for a reserved working day and therefore deliberately not a multiple of the hourly rate — the rationale is on the pricing overview.

Manufacturing places unique demands on shop integration. It is not about simple product catalogs with images and prices, but about technical products with hundreds of attributes, bills of materials with nested assemblies, spare parts identified by machine serial numbers and Kanban control loops that trigger reorders automatically when stock drops below a threshold. The connection between online shop and ERP must fully map this industrial complexity, otherwise the shop remains a foreign body that neither your customers nor your sales team will accept.

Industrial projects usually combine several integration building blocks: if SAP runs in the background, SAP integration describes the technical routes, for Microsoft systems Dynamics 365 shop integration. Where no suitable standard interface exists, it is built in API development; many parallel data flows are decoupled by a middleware. Spare part and accessory assortments are connected via inventory system integration, accounting via DATEV integration. Related scenarios are described on the wholesale and electronics and technology pages.

Integration Project Timeline: From System Analysis to Go-Live

Integration project timeline
From system analysis to spare parts shop go-live
An industrial project in six phases — first data flows go live early, BOMs and Kanban follow step by step. Illustrative representation — values are examples.
Week 1–2 · done
System analysis & interface inventory
ERP modules, available APIs (REST, SOAP, RFC) and business-critical data flows captured. Binding fixed price set.
Week 3–4 · done
Data model & mapping
Field mapping for articles, BOMs, prices, customers and orders. Cross-referencing of number ranges defined.
Week 5–9 · in progress
Middleware & BOM representation
Connector built, multi-level BOM as a navigable tree, real-time stock. First data flows already in production.
Week 10–12
Configurator & Kanban loop
Rule-based variants, reorder-point automation and serial-number spare part search connected.
Week 13
Load & contract test
End-to-end test against the ERP test system, load test with real article volumes, breaking-change detection.
Week 14 · go-live
Go-live & hypercare
Phased activation, monitoring of all sync processes, guided first weeks of operation.
First data flowsfrom week 4in production
Spare parts shop live10–14 weeksarticle sync + order flow
Fixed pricefrom 6,900 €after system analysis
Week 5–9Middleware running · first syncs live
Fixed priceERP integration from 6,900 € net
An industrial project in six phases — first data flows go live from week 4, the spare parts shop goes live after 10 to 14 weeks. Illustrative representation.

BOM Integration: From ERP to Shop

In manufacturing, products are not sold individually but as parts of assemblies, plants or systems. A machine spare part only makes sense when the customer knows which assembly it belongs to and which other parts are also needed for the replacement. The bill of materials (BOM) is the central document describing these relationships, and it must be navigable in the shop just as it is in the ERP.

Our integration reads multi-level BOMs from your ERP system and presents them in the shop as navigable tree structures. The customer sees the assembly, can navigate into individual parts, add required components to the cart and sees real-time availability and prices throughout. When a BOM changes in the ERP, for instance because a component is replaced by a successor model, the shop display updates automatically. Discontinued items are flagged as such, and the replacement part is recommended.

Spare Parts Shops with Machine Assignment

Spare parts sales are a high-margin business for many industrial companies, but they only work when the customer can quickly find the right part. In traditional sales processes, the service technician calls, provides the machine number and has the part looked up. A digital spare parts shop must replicate this process: the customer enters the serial number and immediately sees the associated BOM with all available spare parts.

We integrate machine master data from your ERP into the shop so that every delivered machine is linked with its configuration, BOM and service history. The customer logs into the portal, sees their installed base, navigates to the affected machine and orders the spare part in a few clicks. The service history shows which parts have already been replaced and when the next maintenance is due. All this data comes from the ERP and is synchronized in real time.

One data flow from ERP to cart

Serial number instead of phone call

The service technician enters the machine serial number and sees the associated configuration with all spare parts within seconds. Cross-referencing translates between your article numbers, manufacturer and OEM numbers, so the right part is found even when the customer only knows a foreign number.

  • Machine master data from the ERP in the customer portal
  • Service history and next maintenance date visible
  • Discontinued parts with automatic successor recommendation
Serial number SN-2014-7731
Cross-referencing
Match: 42 pcs available
Number ranges15+art-no · maker · OEM
Time saving68 %vs. phone ordering
Installed base3 activein the portal
Machine master data and service history from the ERP
Next maintenance date and suggested parts visible
Discontinued part detected — successor DS-77N recommended
Illustrative representation — values are examples.

Integration Areas for Industrial Companies

BOMs and Assemblies

Multi-level BOM structures from the ERP as navigable product hierarchies in the shop. Automatic updates on BOM changes, discontinuation notices and successor recommendations.

Product Configurators

Rule-based variant configuration directly in the shop. The configurator validates combination rules against manufacturing parameters stored in the ERP and generates valid BOMs for production.

Kanban Order Automation

Integration of Kanban control loops for C-parts: when the customer's stock reaches a defined threshold, the system automatically triggers a reorder. Connection to barcode scanners and IoT sensors.

Spare Part Identification

Part search by machine serial number, exploded view or article attributes. Cross-referencing between manufacturer part numbers, OEM numbers and your own article designations.

Maintenance Planning and Service Portals

Digital maintenance schedules in the customer portal with automatic reminders and suggested spare parts lists. Integration with CMMS systems for preventive maintenance.

Technical Documentation

Linking products with technical data sheets, drawings, certificates and safety data sheets from the DMS. Customers find all documents directly with the product in the shop.

Kanban and Automated Reordering

Kanban-driven reordering of C-parts, consumables and standard parts is a proven principle in manufacturing that digitizes excellently. The customer defines a reorder point and standard order quantity for each article. When stock reaches the threshold, whether through manual entry, barcode scan or IoT sensor, the system automatically generates an order and passes it to the ERP integration.

For the customer, this means: no manual reordering, no forgotten orders, no production interruptions due to missing small parts. For your company, it means: predictable order volumes, stronger customer retention and reduction of phone orders. The integration ensures that Kanban orders go through the same ERP process as manual orders: availability check, price calculation, picking and dispatch.

The Kanban control loop as a digital process

From reorder point to ERP order

Every article has a reorder point and a standard order quantity. When stock drops below the threshold, the system automatically creates an order and hands it to the ERP integration, where it follows the same process as a manual order. Capture happens by hand, barcode scan or IoT sensor.

  • No forgotten orders, no production stops due to small parts
  • Predictable order volumes and fewer phone orders
  • Same checks as manual orders: availability, price, dispatch
Kanban control loop
Reorder point per articleCapture: hand · barcode · IoTAuto order without approvalERP check: availability & pricePicking & dispatchStock updated
Manual orders0no reordering
Production stopsavoidedno missing C-parts
Checklike manualsame ERP process

What the Kanban connection triggers in the warehouse

Threshold per article

Reorder point and standard order quantity are stored per C-part and location. The loop reacts to shortfalls without anyone having to keep stock levels in mind.

Capture at the shelf

Barcode scanners and IoT sensors report consumption directly from production. Manual capture in the portal is also possible when no hardware is in place.

Order to dispatch

The triggered order runs through the same availability check, price calculation and picking in the ERP as a classic order from sales.

Technical Attributes and Product Data in Manufacturing

Industrial products are not differentiated by color and size but by technical attributes: torque, rated voltage, sealing class, material, tolerance class, certification. A ball bearing has twenty relevant attributes, a pneumatic cylinder thirty, a frequency converter fifty. These attributes must be filterable in the shop so the buyer finds the right product, and they must be correctly synchronized from the ERP or PIM.

Our integration supports importing structured attribute sets from ERP and PIM systems. Attributes are transferred with units, value ranges and filter categories and made searchable via Elasticsearch faceted filtering. Technical drawings, CAD files, certificates and safety data sheets are synchronized as linked documents and are available for the customer to download directly from the product view.

The ERP Landscape in Manufacturing

Industrial companies frequently use industry-specific ERP systems that are not reachable via standard connectors. Beyond the major systems like SAP and Microsoft Dynamics, we regularly encounter proAlpha, abas, PSIpenta, INFOR and industry-specific niche solutions. Many of these systems have been extended over years with custom modifications that must be considered during integration.

We begin every industrial project with a detailed analysis of ERP interfaces: which APIs are available? Which data can be queried in real time, which only as batch export? Are there documented webhooks or do we need to implement polling mechanisms? Based on this analysis, we design the integration architecture and select the optimal technical path for each data flow.

What happens when a BOM changes in the ERP

  1. 1

    Change in the ERP

    A component is replaced by a successor model, an assembly is extended or an article is set to discontinued. Maintenance stays where it belongs: in the leading system.

  2. 2

    Sync detects the delta

    The integration compares state and ERP data and transfers only the changed nodes of the multi-level BOM instead of replicating the full tree every time.

  3. 3

    Shop updates the display

    The navigable tree, availability and prices are updated in the shop. Discontinued items receive a notice and the successor part is recommended automatically.

  4. 4

    Contract test guards the interface

    Automated tests detect breaking changes on the ERP API early, so we can react before a production update and keep synchronization stable.

Project Approach for Industrial Integrations

Long-Term Support for Industry Integration

An ERP-shop integration in manufacturing is not a completed project but a permanent connection that must keep pace with updates from both systems. Our maintenance packages include proactive monitoring of all synchronization processes, timely adaptation to API changes and quarterly reviews of data quality and performance. Through automated contract tests, we detect breaking changes early and can react before production updates. This long-term perspective ensures your integration works reliably not only today but also in two years, keeping pace with your growing requirements.

Industry-Specific Challenges in Manufacturing

Integrating ERP and shop in the manufacturing industry brings specific challenges that are less pronounced in other sectors. Bill of materials integration for configurable products, connectivity to production planning systems for realistic delivery dates, capacity queries for custom manufacturing and synchronization of technical product attributes according to industry standards like ETIM and eclass require deep understanding of both ERP logic and shop architecture. Our project experience in manufacturing encompasses exactly these scenarios and enables us to avoid typical pitfalls from the start and deploy proven solution approaches.

Our maintenance packages for industry integrations include monitoring of all synchronization processes, adaptation to ERP and shop updates, and quarterly reviews of data quality, performance and error rates. This long-term support ensures your integration works reliably even with growing requirements and changing system landscapes.

For industrial companies needing comprehensive technical support for their shop alongside ERP-shop integration, we offer combined maintenance and integration packages. A single contact for the entire technical infrastructure reduces complexity and ensures all system components remain coordinated.

BOMs, spare parts and Kanban in one system

Bring your installed base, service history and automatic reordering into a shop fed from your ERP. In a technical workshop we review your interfaces and sketch the integration path.

Frequently Asked Questions About ERP Integration in Manufacturing

For a deeper look at the blog: PIM Integration describes the product data pipeline for technical articles, EDI Integration explains EDIFACT coupling with key accounts, and Automating Drop Shipping shows supplier integration without own stock.

By submitting you consent to the processing of your details to handle this request. Details in our privacy policy.

Related industries and regions