← Back to Field Notes

July 22, 2025 · The Bloomfield Team

Your ERP Vendor Doesn't Care About Your Shop Floor

Your ERP vendor's product roadmap is built around features that sell licenses to the next customer. Shop floor usability, the experience of the machinist or the operator or the quality inspector who interacts with the system eight hours a day, is not a line item on that roadmap. It never has been.

ERP systems were born in accounting departments. MRP, the predecessor to modern ERP, was invented to plan material requirements for production. The fundamental architecture of every ERP system on the market today is built around transactions: purchase orders, work orders, invoices, inventory adjustments. These are accounting events. They happen to involve manufacturing, but the system's DNA is financial, not operational.

The Gap Between the System and the Floor

Walk into any 40-person job shop and watch how the ERP actually gets used on the floor. An operator clocks into a job by navigating four screens, entering a work order number they copied from a paper traveler, selecting their employee number from a dropdown list of 50 people, and clicking a button that was designed by someone who has never stood at a machine. The process takes 90 seconds. They do it 8 to 12 times per day. That is 12 to 18 minutes per operator per day spent interacting with a system that was not designed for them.

Multiply that across 25 floor employees and you have 300 to 450 minutes of daily labor dedicated to ERP data entry on the shop floor. That is five to seven hours per day. One full-time equivalent. Spent typing into a system that gives nothing back to the person typing.

The ERP collects the data. It does not return value to the person who collected it. The operator who clocked into the job does not see their actual vs. estimated cycle time. Does not see whether the material they are cutting has caused quality issues on similar parts. Does not see the setup notes from the last time this job ran. The system takes information from the floor and sends it to the office. The flow is one-directional.

Why Your ERP Vendor Will Not Fix This

ERP vendors serve a market. For the large vendors like SAP, Oracle, and Infor, the market is companies with 500 to 50,000 employees. Manufacturing is one vertical among dozens. The shop floor experience of a 40-person job shop is not a market segment that drives product investment.

For the mid-market vendors like Epicor, JobBOSS, and Global Shop Solutions, the market is closer to your size, but the business model is still built around implementation services and annual licenses. The vendor makes money when you buy the system and when you pay for customization. The vendor does not make more money when your operator's experience improves. The incentive structure does not reward shop floor usability.

Feature announcements from ERP vendors consistently focus on dashboards, reporting, and mobile access. These features serve managers and executives. The person running the CNC mill at 6 AM who needs to know how the last operator fixtured this part gets the same clunky interface they had five years ago, with a new button color and a slightly different menu layout.

What the Floor Actually Needs

Operators need context. When they start a job, they need to see the setup procedure with photos, the critical dimensions to watch, any notes from the last time this part was run, and the quality issues that have occurred on similar geometries. That information exists somewhere in the operation, scattered across ERP records, quality logs, setup sheets, and people's memories. The ERP does not assemble it. The ERP was not designed to assemble it.

Estimators need speed. When an RFQ arrives, they need historical job costs, material pricing, machine availability, and customer history assembled around the specific part in front of them. The ERP stores most of this data. Retrieving it in a useful format requires 30 to 60 minutes of manual searching, cross-referencing, and assembly. The ERP was designed to store transactions, not to deliver operational intelligence at the point of decision.

Quality teams need patterns. Inspection data for individual parts is in the quality system. Job cost data is in the ERP. Machine data is in a monitoring system or on paper. The correlations between material vendor, machine, operator, and defect rate that would prevent quality escapes are invisible because the systems do not talk to each other. The ERP vendor's answer is to buy their quality module. That module stores more data in the same system. It does not connect data across systems.

What to Do About It

Keep your ERP. It does what it was designed to do: track transactions, manage inventory, produce financial reports. Those functions are necessary. The mistake is expecting the ERP to also serve the shop floor, the quoting desk, and the quality department in ways it was never architected to handle.

Build the operational layer on top. A data layer that connects your ERP to your quality system, your quoting spreadsheets, your machine data, and your team's accumulated knowledge. That layer, purpose-built for your operation, delivers the context, the speed, and the pattern recognition that the ERP cannot. It uses the ERP as a data source, not as the sole system of engagement for your entire operation.

The technology to build this layer exists now. It costs a fraction of what your ERP implementation cost. It deploys in weeks, not months. And it is designed for the people who do the work, not the people who sell the software.

Your ERP vendor will continue to add features that serve their market. The gap between what the system does and what your floor needs will continue to grow. The manufacturers who fill that gap with custom tools built on their own data will have an operational advantage that the ERP vendor's next update will never close. For a deeper look at how these integrations work, see our guide to ERP and AI integration.