How batch complexity quietly outgrows the systems that were built to manage it, and the questions worth asking before it becomes a structural problem.
There's a moment in most process manufacturing operations when the ERP stops being the source of truth. It doesn't announce itself. It shows up as a spreadsheet someone built to track formula revisions, because the system couldn't handle version control cleanly. Then another one for lot genealogy reconstruction at audit time. Then a shared folder where quality holds get documented, because the ERP workflow was too cumbersome to trust.
A year later, those spreadsheets are load-bearing. Nobody planned it that way. And the cost of that drift isn't only operational. It's the weekend rushes to hit ship dates, the quiet dread before an audit, and the Sunday-night check of a spreadsheet that should have been the system's job. The workarounds don't just slow the business. They wear out the people running it.
The Pattern Shows Up the Same Way Every Time
Batch-based, formula-driven manufacturing introduces complexity that compounds over time. New SKUs. Formulation changes. Yield variability that affects costing. Compliance requirements that tighten as the business scales, especially in regulated food and beverage and consumer packaged goods environments. Each of these is manageable in isolation. Together, they stress the architecture of a system that was never designed to absorb sustained, variable operational complexity.
The early indicators are consistent: lot genealogy that requires manual reconstruction, formula revisions tracked outside the ERP, inventory discrepancies driven by yield variance that can't be reconciled inside the system, and quality documentation that lives in a parallel workflow because the supply chain module is too slow or too rigid to trust in production.
These aren't edge cases. In food and beverage, 48% of suppliers still rely on manual spreadsheets, and 39% report data entry errors as a recurring operational problem. The ERP is present but not primary.
Why Growth Makes It Worse, Not Better
The instinct is to assume that as the business grows, the system will grow with it. ERP vendors sell scalability. But scalability on a feature list is different from architectural depth: the ability to absorb more batch complexity, more traceability requirements, and more compliance pressure without requiring your team to compensate manually. This is exactly the gap worth probing when you compare ERP platforms.
Process manufacturing exposes that gap faster than almost any other operational context. The average food recall carries an estimated $10 million in direct expenses, and that figure assumes you can isolate the affected lot quickly. When traceability lives in spreadsheets, you can't. Recall scope grows because the system can't surface clean answers under pressure.
Businesses relying on disjointed systems lose up to 20% of operational efficiency to manual reconciliations. In process manufacturing, that efficiency loss isn't abstract. It's the hours your team spends reconstructing lot genealogy before an audit, reconciling WIP to the general ledger at month-end, verifying formula revisions across locations, and rebuilding in Power BI the quality and yield reporting that should already live in one place.
The Three Questions Most Process Manufacturers Haven't Asked Yet
In most ERP evaluations, the questions are about features. Does the system handle lot tracking? Can we manage formulas? How does it handle regulatory documentation? These are reasonable questions. But they're questions about what the ERP can do today, not about whether it will hold up as complexity increases.
The questions that tend to surface ERP fit, or the lack of it, are different:
- Where will your batch complexity be in three years? Not today's SKU count and formulation volume. Where is it heading, and does the system architecture you're evaluating absorb that trajectory?
- What does your ERP do when it doesn't know the answer? Every system has limits. Good architecture fails gracefully and surfaces the gap. Bad architecture forces manual intervention, often through brittle custom integrations, that becomes permanent.
- Who is accountable for how the system performs at year three, not at go-live? The partner who implements the system should have an opinion about its long-term health, not just its launch-day configuration.
What Honest Answers to These Questions Reveal
Most process manufacturers who work through these questions discover one of three things: their current system is already past its architectural limits and they're managing it with workarounds; their current system is fine for now but won't absorb the complexity they're building toward; or they're about to evaluate a new ERP and they're asking the wrong questions in that process. For teams still running an aging platform, this is often the moment a NAV to Business Central move moves from "someday" to "now."
None of these is a comfortable realization. But all of them are better surfaced before a commitment than after one. ERP implementations that fail almost always fail not because the software didn't work, but because the architectural fit was wrong for where the business was heading. Industry data puts the failure rate at 73%, with average cost overruns exceeding 215% in manufacturing.
Built for Batch: What Long-Term ERP Stability Looks Like
In our Built for Batch session, Western Computer and Yaveon walk through exactly this: what it looks like to evaluate ERP fit against your operational complexity trajectory rather than a feature checklist. We use Dynamics 365 Business Central, configured with Yaveon's process manufacturing framework, as the demonstration environment. Not because it's the only answer, but because it's the one we've seen hold up in batch-based, formula-driven environments years after go-live, from finite capacity scheduling operators actually trust to traceability that survives an audit without a spreadsheet in sight.
If your team is living the spreadsheet accumulation problem, or you want to make sure you're asking the right questions before your next ERP conversation, this is the session worth watching.
With nearly 40 years and 1,750+ implementations behind us, the questions we're asking aren't theoretical. They're the ones that show up in every post-implementation debrief where something went wrong.
Watch the Built for Batch on-demand session to see what long-term ERP stability looks like for process manufacturers. When you're ready to map it to your own operation, talk to a process manufacturing expert or get a pricing estimate for a move to Business Central.
.png)
