When component verification becomes operational

Editor’s note: This is the second of a three-part series on manufacturing risk appearing on scmr.com. Part 3 will publish on Tuesday, July 14. You can read part one here.

A production disruption triggered by a component issue. Not a large OEM-scale shipment. A fragmented secondary-market purchase—several lots, each in the tens of thousands of dollars. MLCC capacitors that passed incoming inspection and failed months later in the field. Nothing in the dashboards signaled a problem.

The failure only became visible when return rates started to climb—slowly at first, then fast enough to trigger a full investigation. By that point, the damage was already done.

This is not an unusual case. It is a category of risk that most supply chain systems are not designed to detect.

Most risk frameworks focus on supplier-level metrics: financial stability, delivery performance, certifications, capacity. These are necessary. But they do not guarantee component-level integrity.

A supplier can be reliable. The documentation can be valid. The transaction can be compliant. And the physical component can still be wrong.

In practice, these failures are almost never introduced and detected at the same point. Misrepresented MLCC components typically enter through secondary-market intermediaries—where lots are aggregated, repackaged, and redistributed. They pass through the warehouse intake. They pass through incoming inspection. And they are only identified later—in production anomalies or field failures.

The point of introduction and the point of detection are almost never the same.

Part 1: The hidden supply chain risk no dashboard shows

In the MLCC case, the issue was not a fake component, but a misrepresented one: a lower-grade part sold as higher-grade; a reprocessed component repackaged as new; a lot with compromised storage history presented as compliant. That is precisely why it passed.

What verification looks like in practice

Tuesday morning, warehouse intake. The shift does three things differently from standard receiving:

• Each lot is separated and treated as its own unit—not merged with others from the same supplier
• Documentation is cross-checked against independent sources, not accepted at face value
• Storage history is reconstructed where possible; sampling is adjusted based on source risk profile

This adds friction. It is slower. And it is the only method that consistently catches the category of failure described above—not because it is more sophisticated, but because it operates at the right level.

The three shifts that change outcomes

Organizations that break the pattern do not do so through better technology alone. They make three operational shifts:

• They separate the verification function from procurement. Not organizationally separate, necessarily. But functionally separate—so that the people under pressure to close the purchase are not the same people assessing whether it should close.
• They treat the lot as the unit of risk, not the supplier. A reliable supplier can ship a compromised lot. Treating all lots as equivalent is what allows misrepresented components to pass.
• They apply judgment before testing, not instead of it. Directed verification—based on source risk, supply path complexity, and market conditions—outperforms random sampling for this category of failure.

The trade-off most teams underestimate

Operationalizing component-level integrity adds friction. It slows intake. It requires judgment that cannot be fully automated. It creates exceptions that are uncomfortable to manage under production pressure.

That friction is exactly why most organizations avoid it. And it is exactly why the failures keep occurring.

The speed-versus-visibility trade-off is not theoretical. Every organization that has experienced this category of failure has, in retrospect, identified the moment when process discipline gave way to urgency. Each exception looked justified in isolation. Taken together, they recreated the original exposure.

For supply chain leaders, the real question is no longer whether this risk exists. It is whether their organization operates at the level where the failure actually occurs because the most expensive failures are not the ones that appear in your metrics. They are the ones that pass through them.

About the author

Alexander Litvin is a supply chain executive with 27 years of experience in electronic component distribution. He is an IEEE Senior Member and the originator of the CILM (Component Integrity & Lifecycle Management) methodology. He may be reached at [email protected].

SC
MR