← Back to Field Notes

July 14, 2025 · The Bloomfield Team

8 Things Your ERP System Will Never Tell You

Your ERP is a transaction engine. It records what happened: job opened, material issued, hours logged, parts shipped, invoice sent. That is valuable. But transactions describe the past in structured fields. They do not capture the context, the judgment calls, or the knowledge that determined how those transactions actually played out on the shop floor.

Here are eight categories of information that your ERP will never surface, no matter how well it is configured.

1. Why a Job Actually Went Over Hours

The ERP says Job 4872 was estimated at 16 hours and clocked at 24. The variance report shows a negative 8 hours. What the ERP cannot tell you is that the first setup required three attempts because the fixture design from 2019 does not accommodate the updated material thickness, and the operator spent 90 minutes on the phone with the tooling supplier resolving a compatibility issue with the new insert grade.

The variance is a symptom. The cause lives in the heads of the people who dealt with it. For a broader view of how to extract value from the data your ERP already holds, see our guide to ERP and AI integration.

2. Which Customers Are About to Leave

Your ERP tracks order volume by customer. It does not track the tone of the last three emails from their purchasing manager. It does not know that their lead engineer mentioned at a trade show that they are qualifying a second source. It does not register that their order frequency dropped from monthly to quarterly over the past six months because you missed two delivery dates in Q1.

By the time the ERP shows a customer's revenue at zero, the relationship has been deteriorating for a year.

3. The Real Reason Your Best Estimator Quotes Differently

Two estimators use the same ERP data and the same costing formulas. One consistently produces quotes that win at higher margins. The ERP cannot explain why, because the advantage lives in 20 years of judgment: which tolerances to flag as risk factors, which customers negotiate hard on price, which material suppliers are reliable enough to quote at standard lead times.

That knowledge is worth hundreds of thousands of dollars annually. The ERP has no field for it.

4. What Your Setup Sheets Are Missing

The ERP stores the routing: Op 10 mill, Op 20 turn, Op 30 grind. It might store a setup time estimate. What it does not store is that Op 10 requires a specific clamping pressure to hold tolerance on the thin wall section, that the part tends to chatter at the programmed feed rate on the Haas but runs clean on the Mazak, or that the deburr on the ID bore takes twice as long as the standard time if the operator uses the wrong tool.

These details determine whether a job runs in 4 hours or 7. The ERP sees the number. The operator lives the difference.

5. Where Your Scheduling Assumptions Break

ERP scheduling modules work from standard times: setup hours, run hours, queue time between operations. Those standards were set at some point in the past and rarely updated. The ERP schedules based on those numbers with perfect confidence. The shop floor knows that Machine 7 runs 15% slower on Inconel than the standard suggests, that the grinding department is a two-day bottleneck every time aerospace work spikes, and that the heat treat vendor's actual lead time is eight days despite the five days entered in the system.

The schedule in the ERP and the reality on the floor diverge a little more each month.

6. The Workarounds Your Team Has Built

Every manufacturing operation runs on a layer of informal workarounds that no system captures. The purchasing manager who checks steel prices on a supplier's portal every Monday morning because the ERP pricing data is three months stale. The quality inspector who keeps a personal log of which customer specs differ from the drawing. The production planner who maintains a shadow schedule in Excel because the ERP's scheduling module does not handle split operations.

These workarounds exist because the ERP does not do what the team needs. They also represent knowledge and process that will disappear when the people maintaining them leave.

7. Which Parts Are Actually Profitable

The ERP can calculate margin on a job by comparing quoted cost to actual cost. What it cannot calculate is the fully loaded cost of producing that part including the quoting time that went into winning the job, the engineering review that caught a drawing error before production, the quality hold that delayed shipment by a day, and the customer service time required to manage the account.

A job that shows 22% margin in the ERP might carry 8% true margin when all costs are allocated. The ERP reports the number it can calculate. The number it cannot calculate is the one you need.

8. What Happens When Key People Leave

The ERP will continue to function perfectly after your most experienced machinist retires. Every job record will remain intact. Every routing will still show the correct operations. And the new operator running those jobs will have no way to access the 30 years of context that made those routings work: which fixtures to trust, which programs to modify, which material batches to watch, which customer specs to double-check.

An ERP without the knowledge of the people who built the data inside it is a filing cabinet. Organized, accessible, and missing everything that mattered most.

Filling the Gaps

The ERP is not broken. It does what it was designed to do: manage transactions. The gap is between transactional data and operational knowledge. Bridging that gap requires a system that captures context alongside transactions, connects data across sources that the ERP was never built to integrate, and makes the combined knowledge available at the point of decision.

That is the category of tool that did not exist five years ago. It exists now. The manufacturers who recognize what their ERP cannot do are the ones positioned to build the layer of intelligence on top of it.