Why supply chains struggle to prove what actually happened at scale

And how that gap quietly drives risk, working capital, and performance

You don’t start the day with data. You start with pressure.

It is 7:40 am, and the day has already begun to take shape. Overnight disruption notes, inventory exceptions, supplier updates, and margin pressures are being scanned in quick succession. Finance is pushing for lower working capital, operations is asking for buffers, sustainability needs evidence, and the board is looking for reassurance that the organisation can withstand further shocks. At the same time, customers expect availability that can be promised with confidence, and there is always the possibility that a regulator, auditor, or brand team may ask for proof at short notice.

By mid-morning, attention turns to a dashboard review. It presents what is commonly described as visibility, a structured view of transactions, movements, and status updates across the network. Yet beneath the surface, there is a shared understanding that the picture is incomplete. The system reflects activity, but not the full lifecycle. Suppliers report one version of events, logistics providers another, and enterprise systems present what should have occurred based on process design. What remains is the ongoing effort to reconcile these fragments into a coherent account of what actually happened.

Later in the day, a project team introduces a proposed solution. It may be positioned as a tactical enhancement or a broader transformation, and while the intent is clear, the reaction is more measured. Interest is tempered by fatigue. There is no shortage of platforms, tools, or integration programmes already in motion. What is sought is not another demonstration, but a clearer answer to a more fundamental question: whether uncertainty can be reduced, capital released, margin protected, and decisions supported with evidence that can be relied upon when it matters.

The system isn’t broken. It just doesn’t hold together.

The constraint is not a lack of intent or investment. Most organisations have already committed significant capital to ERP, WMS, TMS, control towers, and supplier platforms, each designed to optimise a specific part of the value chain. The barrier is more structural: priority competition, change fatigue, and a prevailing belief that these systems, collectively, provide sufficient coverage. In isolation, they do. Planning systems improve forecasts, execution systems capture transactions, and logistics platforms report movement. Yet once a product moves across organisational boundaries, is consolidated, split, or transformed, continuity breaks. The problem is not the absence of data, but the inability to reconstruct, with confidence, what actually happened across the lifecycle. Activity is visible, but sequence is inferred. The system functions, but it relies on interpretation rather than proof.

McKinsey’s 2025 supply-chain survey finding is directly relevant: the “most serious supply chain problem” is lack of awareness of true vulnerabilities, especially beyond tier-one suppliers, and most companies understand risk only up to tier one. In practice, that lack of awareness does not remain abstract. It is absorbed across the system. Uncertainty shows up in inventory, buffers, expediting, write-offs, and claims risk, often without being explicitly measured or governed. The question is not whether this exists. It is where it sits and how much it is costing.

• Where is uncertainty currently being absorbed: inventory, buffers, expediting, write-offs, or claims risk?

• If ERP or ERM provides internal transaction control, what provides product-level truth across organisational boundaries?

• Where is the organisation already spending money to compensate for not having this?

What does success look like?

When lifecycle behaviour can be observed and measured end-to-end, the dynamic changes. Time is no longer an assumed input. It becomes a controllable variable. Delays can be identified at their point of origin rather than after they propagate through the system. Inventory can be reduced with greater confidence because variability is understood rather than buffered. Working capital can be released as uncertainty diminishes, and claims can be supported with evidence grounded in actual events rather than reconstructed narratives.

At that point, the supply chain begins to operate less as a collection of interconnected processes and more as a coordinated system with measurable behaviour across time. Performance is no longer inferred indirectly through outcomes; it can be observed directly through the sequence and timing of events. The organisation moves from absorbing uncertainty to controlling it.

This is not a technology outcome. It is a control outcome. It is the ability to stand behind the lifecycle of what is produced, moved, and sold, particularly when that lifecycle extends beyond organisational boundaries. The real test is not whether the system functions under normal conditions, but whether it holds under pressure, when the demand for certainty increases and decisions cannot rely on interpretation.

At that point, the conversation shifts

• The CEO wants to say: “We know where the risk is, and we can respond.”

• The COO wants to say: “We can see where flow breaks and act before it becomes escalation.”

• The CFO wants to say: “We are not carrying hidden capital because operations cannot trust time.”

• The Head of Sourcing wants to say: “Our claims are defensible, and our supplier base can scale without losing control.”

The question is not whether the information exists. It is whether it can be assembled into a coherent and defensible account without ambiguity.

If you were asked to demonstrate what actually happened across the lifecycle of a product today, would that explanation rely on evidence, or reconstruction?