manufacturing operations

The daily cost of not improving in manufacturing and distribution

Manufacturing consulting in South Africa rarely closes the gap between ERP visibility and real operational improvement. Here's what that gap actually costs.

by Danie Grobbelaar, Verbeter 8 min read · 5 February 2026

Your ERP is live. Reports are running. The data is flowing across your operations. And the problems you had before the implementation are still there.

This is the experience that catches a lot of manufacturing and distribution businesses off guard. They invest in systems expecting improvement. They get visibility instead. Visibility into how often the schedule slips. Visibility into how much inventory variance exists. Visibility into which quality issues keep recurring. But not the improvement itself.

Understanding why this gap exists, and what it actually costs, is the starting point. It’s also the lens through which any manufacturing consulting engagement in South Africa should be evaluated.

What data visibility doesn’t solve

Enterprise systems are designed to integrate information across an operation. When they work well, you can see order status, inventory levels, production output, and financial performance from a single platform. That integration is genuinely useful.

What it doesn’t do is address the underlying processes that produce the numbers.

Research on ERP implementation outcomes is more sobering than the sales conversations that precede them. Roughly half of implementations fail to deliver expected results on the first attempt. Projects regularly run over budget and over timeline. And when systems go live, operations typically experience a temporary productivity decline before gradually recovering, as teams learn to work in new ways while maintaining output. In many cases, the expected operational improvements materialise slowly or not at all, because the system records what operations produce rather than changing how they produce it.

A distribution business that reconciles inventory weekly, or a manufacturer that does shift-end data entry, is working from information that lags reality by hours or days. By the time a planner sees that a component is missing or a machine is down, the window for intervening has often closed. The ERP captured the event accurately. The operation still had to react.

The patterns that cost most

In manufacturing and distribution businesses that are running without structured improvement programmes, specific problems tend to recur regardless of which systems they’re using. These aren’t random occurrences. They’re the predictable output of operations where the underlying processes haven’t been improved.

Inventory variance that doesn’t converge

When inventory variance is measured consistently, many operations notice that it persists despite regular cycle counting and reconciliation. The counts reveal discrepancies. Adjustments are made. The variance reappears.

This is almost never a counting problem. It’s a process problem: receiving procedures that allow unverified items to enter the system, scanning discipline that’s inconsistent across shifts, master data with errors that create structural variance on every transaction. Cycle counting discovers the symptoms. It doesn’t address the causes. The result is excess safety stock held as a hedge against unreliable data, working capital tied up in inventory that shouldn’t be there, and planners making decisions with numbers they don’t fully trust.

Schedules that slip despite planning tools

The three problems that production schedulers consistently describe as their most difficult are labor shortages, unplanned downtime, and rush orders. These are structural, not accidental. They reflect the gap between what planning systems assume and what operations actually produce.

Planning tools are built on assumptions: materials are available when the system says they are, machines run when they’re scheduled to run, labour shows up as planned. When any of those assumptions is wrong, the schedule becomes a starting point for reactive decisions rather than a plan the operation can follow. Overtime, changeovers that weren’t planned, partially completed orders, work-in-progress accumulating between stations: these are the waste patterns that scheduling failures produce.

Quality issues that repeat

Corrective action and preventive action processes exist specifically to prevent quality issues from recurring. In many manufacturing operations, they produce compliant paperwork without changing what happens on the floor.

When root cause analysis is conducted primarily to satisfy an audit requirement rather than to understand why a defect occurred, the corrective actions tend to address the most proximate cause, the last step where the problem was detected, rather than the upstream conditions that created it. The next time production runs under similar conditions, the same defect appears. The CAPA is reopened. The cycle continues.

Maintenance that reacts rather than prevents

Estimates of reactive maintenance prevalence in manufacturing typically put it above 60% of facilities: most of the time, most operations are waiting for things to break before fixing them.

The cost of this is not just the repair. When equipment fails unexpectedly, it disrupts the production schedule, often requiring overtime or resequencing to recover. Emergency repairs typically cost three to five times what planned maintenance costs. And the failure can produce quality defects in the output that ran before the breakdown was detected. In operations with tight margins, even a handful of unplanned stoppages per month represents a meaningful impact on the business.

What structured improvement adds

The pattern that distinguishes operations that improve from those that don’t isn’t the systems they use or the size of their team. It’s whether they have a defined, disciplined way of identifying problems and addressing their causes.

In operations that have this in place:

Inventory variance is treated as a signal of process failure, not just a counting problem. Root causes are identified and addressed. Over time, variance converges.
Production scheduling is built on realistic assumptions about capacity, and when reality deviates from plan, the deviation is used to improve the planning model.
Quality corrective actions are tracked to effectiveness, not just to closure. If the action didn’t prevent the issue from recurring, the root cause analysis is reopened.
Maintenance is planned around equipment criticality, not just around failure. Planned downtime is scheduled. Unplanned downtime is investigated.

None of this requires a particular system. It requires a practice: a disciplined way of working that addresses root causes and sustains the changes made.

The question to ask before engaging a manufacturing consultant

Manufacturing operations have specific, tangible improvement opportunities. The question isn’t whether improvement is possible. It almost always is. The question is whether the engagement is designed to produce lasting change or to produce a project outcome.

Before engaging any manufacturing consultant or improvement programme, ask what changes in the operation’s processes and capabilities by the end of the engagement. If the answer describes deliverables, outcomes like reports, recommendations, or trained cohorts, ask what happens to the problems that produced those deliverables.

The test of a manufacturing improvement engagement is whether the operation is running better twelve months after the consultant leaves than it was when they arrived. Not because the consultant is still there, but because the operation learned to improve itself.

The cost this article describes isn’t a crisis. Inventory that doesn’t reconcile, schedules that slip, quality issues that repeat, maintenance that reacts: these aren’t exceptional events. They’re what the operation produces every day that structured improvement isn’t in place.

If you want to understand which of these patterns is costing the most in your operation, and what’s actually driving them, start with a diagnostic conversation.

Danie Grobbelaar

Verbeter

Danie Grobbelaar is an industrial engineer whose career has been built inside South African manufacturing and distribution operations. He brings practitioner credibility earned across hundreds of operational environments: the kind that comes from having seen what sustains and what does not once the consultant leaves.

Frequently asked questions

Why do manufacturing operations still have the same problems after ERP implementation?

ERP systems integrate information across an operation. They don't change the processes that produce that information. When an operation has inventory variance, scheduling failures, or quality issues before go-live, the system records those problems with greater accuracy. It doesn't address the underlying process failures that cause them. Operational improvement requires a structured approach to identifying root causes and changing the processes, which is separate from the system implementation itself.

What causes persistent inventory variance in manufacturing?

Inventory variance that doesn't converge over time is almost never a counting problem. It's a process problem. Common causes include receiving procedures that allow unverified items to enter the system, scanning discipline that varies across shifts, and master data errors that create structural variance on every transaction. Cycle counting reveals the discrepancies but doesn't address the causes. Until the underlying processes are improved, the variance reappears after every reconciliation.

Why do production schedules keep slipping despite using planning tools?

Planning tools are built on assumptions: materials available when the system says, machines running as scheduled, labour showing up as planned. When any assumption is wrong, the schedule becomes a starting point for reactive decisions rather than a plan the operation can follow. The three problems schedulers consistently report as most difficult are labour shortages, unplanned downtime, and rush orders. These are structural, not accidental. They reflect the gap between what the planning system assumes and what operations actually produce.

What is the test of a good manufacturing improvement engagement?

The test is whether the operation is running measurably better twelve months after the consultant leaves than it was when they arrived. Not because the consultant is still involved, but because the operation developed the capability to identify problems and address them. An engagement designed to produce reports, trained cohorts, or a set of recommendations is a project. An engagement designed to change how the operation works is structured improvement.

← Back to Thinking