High-mix low-volume (HMLV) manufacturing is the dominant production model for Singapore SMB manufacturers. Precision engineering job shops make hundreds of different part numbers per month, often single-digit quantities each. Specialty packaging makes one-off runs for new customers. Electronics contract manufacturers produce limited revisions for OEM clients.
Standard ERP systems are not designed for this. They are designed for repeat production where you set up a product once and make it many times. When every order is different, the standard ERP setup overhead — define the SKU, build the BOM, define the routing, calculate the standard cost — becomes a tax on every transaction.
Where Standard ERP Breaks
1. SKU explosion. A high-mix manufacturer can easily accumulate 5,000-50,000 SKUs over time. Many are one-off — created for a single customer order and never produced again. Standard ERP item masters become bloated with inactive records that slow down search, reporting, and master data maintenance.
2. BOM setup overhead. Standard ERP requires a structured BOM before a production order can be created. For a one-off product, building the BOM from scratch consumes more time than the production itself. Most HMLV manufacturers end up using "generic" BOMs or skipping the BOM entirely — undermining the system's value.
3. Routing variation. Each product may follow a different routing through the shop floor. Standard ERP assumes routings are defined per product (or per product family). When the routing varies per order, the routing setup becomes manual per order — defeating the system's scheduling capabilities.
4. Standard cost modelling. Standard cost requires historical data to set the baseline. A product produced once has no historical data. Variance reports against standard cost are meaningless when the standard cost is itself a guess. Without reliable variance reporting, job costing becomes opaque.
5. Engineer-to-order coordination. Many HMLV operations involve engineering work before production — design changes, customer-specific configurations, regulatory approvals. Standard ERP does not model this engineering loop; the workflow stays in email and CAD systems.
What HMLV Manufacturers Actually Need
Template-based SKU creation. New SKUs should be created from templates, not from scratch. The system should auto-populate common fields (category, default routing, default supplier) so creating a new SKU takes seconds, not minutes.
Order-driven costing. Every production order is an opportunity to capture actual cost — material consumed, labour hours, machine time, subcon charges. Order-driven costing replaces standard cost: the cost of "this job" is what was actually spent, not a pre-set standard.
Engineer-to-order workflow. The system supports the engineering phase explicitly — design status, customer approvals, drawing revisions, regulatory checks — before production starts. The engineering output becomes the production input.
Customer-configuration preservation. When customer A orders a custom variation, the configuration is stored against the order. If customer A orders the same variation again, the configuration can be recalled — turning a one-off into a repeatable pattern over time.
Flexible routing per order. Each production order can override the default routing for the product. The scheduler handles per-order routings without requiring product master maintenance.
SKU lifecycle management. Inactive SKUs (not produced in 18 months) are archived from active views but retained for historical reporting. The item master stays clean.
Why Custom Often Wins for HMLV
For HMLV manufacturers, a custom-built system can be designed around the order-driven, template-based, engineer-to-order pattern from the start. The system models how the business actually operates rather than forcing the business to fit a repeat-production model.
The alternatives:
- Standard ERP (SAP B1, Odoo, Syspro) — works for the 20% of products that are standard repeat items. Breaks for the 80% that are one-off or low-repeat.
- MRP-focused SaaS (Katana, Cin7) — handles inventory and BOM well but assumes standard products. Same breakage pattern.
- ETO-specialised ERP (DELMIAworks, Plex, IFS) — handles engineer-to-order well but at enterprise pricing (S$200k+) and 12-month implementations.
The custom-build approach for HMLV typically scopes:
- Template-based item creation flow
- Order-driven costing module
- Engineering workflow integration
- Per-order routing flexibility
- Customer-specific configuration storage
- SKU lifecycle management
For most SG SMB HMLV manufacturers, this build runs S$18,000-S$28,000 — at the higher end of the standard build band because of the workflow complexity. The 5-year TCO comparison vs ETO-specialised ERP is dramatic (S$25k vs S$300k+).
Diagnostic Signals
Your operation is high-mix low-volume if:
- You add 50+ new SKUs per quarter, many for single customer orders.
- Your top 20% of products represent less than 60% of revenue (the long tail dominates).
- Production planning involves significant per-order setup (routing decisions, BOM creation, customer-specific configuration).
- Your existing ERP setup involves heavy workarounds — generic items, copy-paste BOMs, manual routings.
- Job costing is your primary financial visibility need (not standard cost variance).
If 3+ of these are true, a standard ERP will struggle. Start Canyon scopes HMLV-friendly custom systems as a recognised pattern. The free diagnostic at startcanyon.com/diagnostic captures the HMLV signals as part of the assessment.