Why Custom Fields Are Destroying Your ERP Data Trust
Custom fields feel like flexibility. In practice, they're the #1 cause of ERP data degradation. Here's what happens when every department gets to 'just add a field.'
Every ERP vendor sells "flexibility." What they're really selling is rope.
Custom fields feel like a feature. In practice, they're the single biggest contributor to ERP data degradation in manufacturing environments. Here's how it happens, why it compounds, and what the alternative looks like.
The Lifecycle of a Custom Field
Month 1: Sales needs a field to track customer preferred shipping method. IT adds x_preferred_ship_method to the Customer table. Takes 20 minutes. Everyone's happy.
Month 6: Finance needs to report on shipping cost by method. They discover the field has 47 unique values because there was no validation. "UPS Ground," "UPS ground," "Ground UPS," and "GND" are all in there. The report is useless.
Month 12: Purchasing creates their own field, x_vendor_ship_preference, which tracks almost the same thing. Now there are two fields with overlapping purpose and no shared vocabulary.
Year 3: 200+ custom fields across 40 tables. Nobody knows what half of them mean.
Year 5: The company decides to migrate. The migration team finds 200 fields that don't exist in any standard module. Each one requires a manual decision. Many of the people who created them are gone.
The Math
| Cost Category | Per Field | 100 Fields |
|---|---|---|
| Creation and testing | $250 | $25,000 |
| Maintenance per upgrade cycle (3 upgrades) | $150 | $45,000 |
| Data quality remediation (annual) | $100 | $50,000 |
| Migration mapping and decision | $200 | $20,000 |
| Integration overhead (per connected system) | $500 | $25,000 |
| Total | $1,650 | $165,000 |
The Alternative
What if the answer to "can we add a field for X?" was: "If it's useful to manufacturers, we'll add it to the core for everyone. If it's not useful to manufacturers, you probably don't need it in your ERP."
That's the position Yggdrasil takes. Zero custom fields. One shared data model. Every tenant runs the same schema, the same validation rules, the same API contracts.
This isn't a limitation — it's a design choice that preserves data trust over time.
Mimir Labs builds Yggdrasil ERP — a manufacturing platform with zero custom fields. Learn more or schedule a conversation.