A 200-person PCB assembly house often runs the same generic ERP used by a mechanical parts shop or a cosmetics manufacturer down the road. Six months in, the penny drops: the system cannot handle a BOM revision index without rebuilding the entire structure from scratch, it cannot trace component date codes across batches from the same supplier, and the RoHS compliance declaration for each finished product lives in a manually maintained Excel file outside the system entirely.
Electronics manufacturing — OEMs, EMS (Electronics Manufacturing Services) providers, PCB assemblers, cable harness manufacturers — places demands on an ERP that most general-purpose platforms simply do not meet natively. This guide maps those demands, analyses the solutions built for this sector, and proposes six concrete selection criteria.
Why Electronics Manufacturing Breaks Generic ERPs
NPI and Revision Control: the Engineering Change Order Wall
In electronics, products never stand still. Engineering modifies a resistor (value, package, or approved supplier), adds a decoupling capacitor, corrects a schematic after prototype validation. Every change generates an ECO (Engineering Change Order) or ECN (Engineering Change Notice) that must propagate through the entire chain: bill of materials, routing, test instructions, inventory of affected components.
An ERP without a native ECO/ECN workflow handles these changes through manual deletion and re-creation of items and BOMs. The result: production sometimes works from an obsolete BOM revision because the process engineer has not yet “re-created the item in the system.” The quality crisis that follows costs more than the ERP itself.
NPI (New Product Introduction) is the end-to-end sequence from engineering quote through prototype, pre-production, and series launch. An ERP designed for electronics models this workflow with milestone validation gates and a clear distinction between items in development and items in production. Without this, the transition from pre-production to full series creates a risk window where both versions coexist in the system.
Multi-Level BOMs and Real-Time Component Substitution
An electronics product BOM is multi-level (boards → components → materials) and includes components with multiple approved sources (Approved Manufacturer List, AML). When a primary supplier goes on allocation, the ERP must instantly identify which approved alternative is in stock or on order.
The 2021–2024 semiconductor shortage made this capability critical. Assemblers without component alternative management in their ERP resorted to manual Excel tracking with undocumented substitution errors. By 2026, the ability to manage alternative BOMs and dynamic ATP (Available To Promise) across substitution components has become an eliminating criterion in ERP RFPs from European EMS providers.
RoHS and REACH Compliance: Substance Traceability in the ERP
RoHS 2 Directive (2011/65/EU) — the 10 Restricted Substances
The RoHS 2 directive (2011/65/EU) restricts the use of ten substances in electrical and electronic equipment placed on the European market:
- Lead
- Mercury
- Cadmium
- Hexavalent chromium
- Polybrominated biphenyls (PBB)
- Polybrominated diphenyl ethers (PBDE)
- DEHP (bis(2-ethylhexyl) phthalate)
- BBP (benzyl butyl phthalate)
- DBP (dibutyl phthalate)
- DIBP (diisobutyl phthalate)
The four phthalates were added by delegated directive 2015/863, applicable from 22 July 2019 for most product categories.
The ERP implication: every component entering a finished EEE product’s BOM must have a RoHS compliance declaration attached in the system. When a supplier changes its formulation and issues an updated declaration, the ERP must alert the quality team and block new deliveries until revalidation is complete. An ERP that stores supplier documents in a disconnected document management system cannot enforce this automatically.
REACH SVHC: the 0.1% Threshold and the Supplier Cascade
The REACH regulation (EC 1907/2006) requires notification to customers and ECHA (European Chemicals Agency) when an article contains a substance from the SVHC (Substances of Very High Concern) candidate list above 0.1% by weight. The SVHC candidate list, published on the ECHA website, now runs to several hundred substances.
In electronics manufacturing, this calculation is complex: the concentration of a substance across every component (solder, coating, connector, housing) at every BOM level must be summed, then the total concentration in the finished article calculated. A purpose-built ERP automates this cascade calculation from supplier Safety Data Sheets (SDS) and REACH declarations.
Without this capability, the quality manager recalculates manually in a spreadsheet after every component change. For a 500-component product with frequent revision cycles, this is a permanent source of error and market delays.
Supplier Declarations and SDS: Centralising in the ERP
RoHS/REACH compliance rests on a document chain: each supplier provides a RoHS declaration and/or SDS for its components. These documents have an expiry date (a supplier may change its formulation), a scope (single component or an entire family), and an internal validation status.
The ERP must manage this document lifecycle natively: expiry alerts, revalidation workflow, automatic blocking of items with expired or missing declarations. ERPs that outsource this to a disconnected PLM or document system create a grey zone where non-compliant components can enter production.
Component Shortage and Obsolescence Management
EOL Alerts and Distributor Integration
Component obsolescence is a permanent reality in electronics. A semiconductor manufacturer announces EOL (End of Life) for a component with 12 to 24 months’ notice. Without an alert system, the EMS discovers the end-of-life when its last stock is exhausted — with no time to build a last-time buy reserve or validate an alternative.
Purpose-built electronics ERPs integrate obsolescence data feeds from major distributors (Arrow, Avnet, Digi-Key, Mouser) via API. As soon as a component in an active BOM is flagged as EOL or NRND (Not Recommended for New Design), an alert is generated in the ERP for engineering and procurement, listing affected finished products and available alternatives according to the AML.
Substitution Strategies and Dynamic ATP
When a component is on allocation or EOL, the ERP must allow purchasing to switch instantly to the approved alternative without creating a new BOM or a new item number. The substitution must be traceable (who approved it, when, and why) and must not modify the product’s reference BOM — only the BOM of the specific manufacturing order in question.
Dynamic ATP management for substitution components is the decisive test: can the ERP calculate the possible delivery date for a customer order taking into account a mix of primary and substitute components, with their respective lead times? Generic ERPs rarely answer yes without custom development.
ATE Testing and Quality Traceability: the ERP as Results Hub
Test Data Flow into the ERP: AOI, ICT, FCT and IPC Standards
In a PCB assembly shop, multiple test types are applied to every board in production:
- AOI (Automated Optical Inspection): automated visual inspection post-soldering
- ICT (In-Circuit Test): electrical testing of individual components
- FCT (Functional Circuit Test): functional test of the board in a near-production configuration
- X-ray: inspection of hidden solder joints (BGA, QFN)
Each test system generates a results file per board tested (pass/fail per test point, defect coordinates). The ERP must import these results and link them to the board’s serial or lot number, enabling calculation of DPMO (Defects Per Million Opportunities) by line, equipment, or component supplier. The IPC-A-610 standard defines acceptability criteria for electronic assemblies — the ERP must allow the applicable quality level (Class 1, 2, or 3) to be referenced per product.
Without this integration, test results remain siloed in the ATE equipment’s proprietary software, inaccessible for trend analysis or customer traceability documentation.
CAPA and Non-Conformances in the Electronics Context
When a defect is detected in testing or reported by a customer, the CAPA (Corrective and Preventive Action) process must engage. In electronics, complexity comes from the number of potential root causes: a soldering defect may originate from solder paste, reflow oven settings, PCB warpage, or an out-of-tolerance component.
The ERP must allow a non-conformance to be linked to a precise root cause (component, supplier, process parameter, operator), track corrective actions with deadlines and owners, and close the CAPA with evidence of effectiveness. For a deeper look at ERP QMS configuration, our ERP quality management and CAPA guide covers the reference setup in detail.
ERP Comparison: Solutions Built for Electronics Manufacturing
IFS Cloud — Strengths in Lifecycle Management and Mission-Critical Maintenance
IFS Cloud is particularly well-suited to EMS providers manufacturing complex equipment with long lifecycle and maintenance requirements (industrial equipment, defence, civil aerospace). Its Engineering Change Management module is native, BOM revision management is robust, and its regulatory compliance module covers RoHS and REACH. IFS Cloud deployment is typically justified for EMS providers with over 300 employees, high-value-add products, and demanding documentation requirements.
Epicor Kinetic — Job-Shop Discrete Manufacturing Heritage, EMS Track Record
Epicor Kinetic (formerly Epicor ERP) is one of the rare mid-market ERPs with a meaningful track record among North American and European EMS providers. Its discrete job-shop production management, NPI workflow, and multi-level BOM configuration with AML are genuine differentiators. Epicor Kinetic targets manufacturers with 100 to 1,500 employees. For a side-by-side comparison with IFS and Infor on the mid-market industrial segment, see our mid-market manufacturing ERP comparison.
abas ERP — European Mid-Market, SME EMS 50–300 Employees
abas ERP is a German specialist in discrete manufacturing with strong presence in continental Europe (DACH, Benelux, France). Its strength for electronics: flexible BOM management, a native lot/serial traceability module, and an available MES interface. Its natural target is the EMS provider with 50 to 300 employees that cannot afford SAP or IFS but needs a more robust platform than a generic SME ERP.
SAP S/4HANA — Large EMS Groups and Major Equipment Manufacturers
For EMS providers with over 500 employees or equipment manufacturer groups with multi-entity consolidation requirements, SAP S/4HANA remains the reference. SAP offers RoHS/REACH compliance modules (SAP EHS — Environment, Health and Safety) with automatic SVHC concentration calculation per item. The deployment weight (18 to 36 months, significant budget) is justified for organisations with high volumes, multi-country presence, and integration requirements with existing MES and PLM systems. Integration with third-party PLM (Siemens Teamcenter, PTC Windchill) is critical at major equipment manufacturers — SAP provides certified connectors for these scenarios.
Summary Table
| ERP | Target Profile | Native NPI/ECO | RoHS/REACH Compliance | Implementation Partners |
|---|---|---|---|---|
| IFS Cloud | EMS 300+, complex equipment | Yes | Dedicated module | Yes (IFS regional offices) |
| Epicor Kinetic | EMS 100–1500, job-shop | Yes | Via extensions | Select partners |
| abas ERP | SME EMS 50–300 | Partial | Quality module | Reseller network |
| SAP S/4HANA | Groups 500+, multi-site | Yes (with PLM) | SAP EHS native | Extensive |
Deployment budget ranges vary significantly depending on functional scope, infrastructure, and integration complexity. Request benchmarks from electronics-specialist implementation partners.
5 Pitfalls to Avoid During ERP Deployment in an EMS
1. Underestimating the MES–ERP interface. In an EMS, the MES orchestrates production across SMT and CMS lines. If the ERP interface is not precisely specified at design stage, inventory discrepancies between the two systems become a daily event. The interface must cover at minimum: manufacturing order transfer, component consumption, test results, production declaration. Budgeting 20 to 30% of the project for interfaces is a sound rule of thumb.
2. Overlooking component date code complexity. The same component ordered from the same supplier can carry different date codes depending on the manufacturing batch. The ERP must manage these sub-lots, as electrical properties can vary slightly between date codes, potentially affecting product conformance. Failing to plan for this during configuration creates a permanent non-conformance risk.
3. Delegating regulatory compliance to a disconnected external tool. Managing RoHS/REACH in an Excel file outside the ERP, updated manually, is an operational liability. A supplier change not reflected in the REACH declaration is enough to expose the EMS to prosecution for placing non-compliant products on the market. The connection between the ERP and the compliance document base must be systemic, not manual.
4. Neglecting training for methods and quality teams. ECO/ECN, alternative BOM, and CAPA workflows are complex. If methods and quality teams are not trained on the specific ERP chosen, these modules will not be used — and the EMS will continue running Excel files in parallel. Change management typically represents 15 to 20% of the project budget in an EMS.
5. Selecting an ERP without validating ATE equipment integration. Test machines (Keysight, Teradyne, ATG) generate proprietary formats. Before signing, validate that the ERP can import these formats or that a connector is available. Discovering this gap post-deployment means a custom development project with variable cost and uncertain timeline.
6 Electronics-Specific Selection Criteria
Before shortlisting solutions, evaluate each ERP candidate on these six non-negotiable criteria for an EMS:
- Native ECO/ECN workflow: are BOM revisions managed through a traced validation process, without item deletion and re-creation?
- Alternative BOM and dynamic ATP: does the ERP calculate availability taking substitution components from the AML into account?
- Integrated RoHS/REACH compliance: is SVHC concentration calculation automatic from supplier documents stored in the ERP?
- Date code and sub-lot management: does lot/serial traceability extend down to the component date code level?
- ATE results import: does the ERP accept results file formats from your test equipment (AOI, ICT, FCT) without custom development?
- Documented MES interface: is there a standard connector for your MES, or a documented REST API enabling integration without bespoke work?
To connect the ERP to the MES and IIoT equipment on the shop floor, our guide ERP and IIoT: connecting the shop floor in real time covers the reference architecture.
Download our ERP evaluation scorecard — 30 criteria across 100 points to benchmark three vendors side by side, including a dedicated section for electronics manufacturing and EMS sector constraints.
