The ECM complexity problem
Electronics contract manufacturing in Singapore is operationally dense. An ECM might be running 20–50 active production orders simultaneously, across 3–8 customer accounts, each with their own BOM, component supply, quality standards, and delivery schedule. Inventory is a mix of company-owned stock and customer-consigned components that must never be confused.
The administrative load is as high as the production load. Component shortages must be flagged to customers before production starts, not after. Yield losses on customer-supplied components must be documented and reported. COCs must be generated per shipment. Engineering changes come in by email and must be tracked against specific production lots.
The five ERP requirements for ECMs
Customer-segregated inventory: the ERP must distinguish between company-owned stock and customer-consigned components at the bin level. Consignment usage must be tracked and reported back to the customer. Surplus must be returnable with an accurate usage report. Standard inventory ERPs do not have a native consignment-by-customer model.
Multi-level BOM with ECO management: BOMs for electronics are typically 3–5 levels deep. Engineering change orders must be traceable to specific BOM versions and must not silently affect in-progress production orders. The ERP must maintain BOM revision history and show which production lots were built to which BOM version.
Shortage analysis: before releasing a production order, the ERP must check component availability across all supply types (own stock, consignment, on-order) and flag shortages. This prevents a production order from starting and failing mid-build due to missing components — one of the most expensive disruptions in electronics manufacturing.
Yield and scrap tracking: component yield on PCBA assembly is never 100%. The ERP must record actual vs planned yield per production run, attribute scrap to a cause code, and distinguish between defective components (vendor claim), process scrap, and customer-induced issues.
Certificate of conformance generation: each shipment must be accompanied by a COC that lists the production order, BOM version, test results, and serialisation (where applicable). This should be generated from the ERP with one click, not compiled manually from multiple records.
Where standard ERPs miss for ECMs
SAP B1 and Odoo both handle multi-level BOM and lot tracking. Neither has a native customer-consignment model that segregates inventory by customer at a structural level. Workarounds — using separate warehouses per customer, or tagging lot records with customer IDs — are brittle and create reconciliation problems.
Generic ERPs also do not generate COCs, handle ECO workflows, or provide a shortage analysis that works across mixed own/consigned inventory. These gaps are not addressable with configuration alone — they require development, which means the off-the-shelf cost saving is quickly eroded.
What a custom build covers for ECMs
A custom ERP built for an electronics contract manufacturer covers: customer-segregated inventory with consignment reporting, multi-level BOM with ECO workflow, pre-release shortage check, yield and scrap recording, COC generation, and InvoiceNow e-invoicing. Build cost for a 30–80 person ECM is typically S$50,000–S$120,000. EDG grants reduce net cost to S$15,000–S$60,000. Build time: 16–24 weeks.
Starting the scoping process
Begin with your current customer-consignment workflow: how do you receive, record, store, use, and report on customer-supplied components today? Document every step, including how you handle disputes and reconciliation. This workflow map is the first section of the ERP requirements brief and drives the most critical design decisions in the system.