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.
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. 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, quality documentation that lives in a parallel workflow because the ERP version is too slow or too rigid to trust in production.
These aren't edge cases. According to research from 2025, 48% of suppliers in batch-based environments still rely on manual spreadsheets — and 39% of those teams 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, more compliance pressure without requiring your team to compensate manually.
Process manufacturing exposes the gap between those two things faster than almost any other operational context. The average recall event in 2025 carried $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, verifying formula revisions across locations, and reconciling quality data that should be in one place but isn't.
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? 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 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.
None of these is a comfortable realization. But all of them are better surfaced before a commitment than after one. ERP implementations that fail — and the failure rate sits at 73%, with average cost overruns exceeding 215% — almost always fail not because the software didn't work, but because the architectural fit was wrong for where the business was heading.
What We're Working Through on June 18
On June 18, Western Computer and Yaveon are walking through exactly this: what it looks like to evaluate ERP fit against operational complexity trajectory rather than a feature checklist. We'll 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.
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 showing up for.
With 35+ years and 1,250+ ERP implementations behind us, the questions we're asking on June 18 aren't theoretical. They're the ones that show up in every post-implementation debrief where something went wrong.
Register for Built for Batch: What Long-Term ERP Stability Looks Like for Process Manufacturers — June 18, 2026.
.png)
