Häufig gestellte Fragen
Which requirements must an ERP for automotive suppliers necessarily fulfil?
An automotive ERP must above all map the OEM supply chain technically: EDI connectivity to the customer plants, processing of delivery schedules according to VDA or EDIFACT standards, and their clean propagation into demand and materials planning. Added to this are Just-in-Time and Just-in-Sequence capability, container and empties management, and quality management that supports the requirements of IATF 16949 and the relevant VDA volumes. Also central is end-to-end traceability at batch and serial-number level, so that affected parts can be clearly identified in the event of a complaint or recall. Functions that are optional in the general mid-market belong to the mandatory scope here.
What is the difference between Just-in-Time (JIT) and Just-in-Sequence (JIS), and does the ERP have to support both?
With Just-in-Time, parts are delivered directly to the assembly line precisely on time and usually several times a day, ideally without buffer stock, in sync with the production cycle. Just-in-Sequence goes one step further and is a further development of JIT: parts arrive not only on schedule but also in the exact installation sequence, each part assigned to a specific vehicle on the line, which is why OEMs demand very high sequence accuracy here and generally measure mis-sequences in the ppm range. JIS typically concerns variant-rich modules such as cockpits, seats, doors or front ends, where customer-specific equipment affects the sequence. An ERP for suppliers with such orders should master both procedures, since OEMs specify different call-off models depending on the component and plant.
Which EDI standards and message types must an automotive ERP support?
In Europe, EDIFACT and the VDA standards dominate, while in US business ANSI ASC X12 and in some cases Odette are common, which is why a capable automotive ERP should handle several formats in parallel. Among the message types, the most relevant are the DELFOR as a longer-term delivery schedule or forecast, the DELJIT as a short-term precise call-off for day-specific quantities, and the DESADV as a despatch advice. The forecasts are planned in the ERP via materials planning and exported to a system-specific format (with SAP, for example, IDoc), which the EDI solution then converts into the respective OEM format and transmits. Since each manufacturer maintains its own mappings and conventions, the vendor's experience with the specific customer standards is an important selection criterion.
Do I need IATF 16949 certification for an automotive ERP?
IATF 16949 is a quality management standard for the automotive industry that concerns the company and its processes, not the ERP software itself, which is therefore not certified. However, numerous OEMs and Tier-1 customers require the certification from their suppliers, making it practically indispensable for admission into global supply chains. The certificate is valid for three years and must be confirmed during this time by annual surveillance audits from IATF-recognised auditors, before a full recertification audit is due at the end of the cycle. The ERP supports compliance by cleanly documenting and making auditable standard-compliant processes such as traceability, initial sampling (EMPB in the PPF procedure according to VDA Volume 2 or PPAP according to AIAG) and complaints management.
What does an automotive ERP cost?
Realistic total costs for an automotive ERP in the mid-market are usually in the high six- to seven-figure range over the first three to five years, depending on the number of users, number of sites and customising depth. Tier-1 suppliers with JIS/JIT requirements tend to be higher, because OEM-specific EDI mappings and extensive quality management modules are added. With on-premise models, annual maintenance and update fees additionally apply, while cloud subscriptions are billed per user per month. A reliable estimate only emerges from a requirements specification with concrete requirements; more on this in our guide ERP costs.
How long does implementing an automotive ERP take?
Mid-market ERP implementations in the manufacturing environment typically take around 6 to 18 months, with automotive projects tending towards the upper end of this range because of EDI links, JIS/JIT connectivity and IATF-compliant QA processes. Larger multi-site implementations for several OEM customer plants can run considerably longer and sometimes take two years or more, including the connection of the respective EDI links per site. Experience shows that a large part of the project duration goes to conception, customising and data migration, with the remainder for testing, training and productive roll-out. You will find structured preparation in our ERP implementation checklist.
What does Catena-X mean for ERP selection?
Catena-X is an open, collaborative data ecosystem for the automotive industry whose governing association was founded in 2021 and which is intended to enable standardised, secure data exchange along the entire supply chain. End-to-end traceability of components is considered a key field of application, alongside which CO2 transparency and supply chain resilience play a central role. Several major OEMs are already activating their suppliers and in some cases make participation a requirement in their purchasing terms, so for many suppliers the connection is increasingly becoming a prerequisite for remaining part of the supply chain. When selecting an ERP, suppliers should therefore check whether the vendor can demonstrate a viable Catena-X roadmap or corresponding interfaces.