The supplier your
dashboard can't see

A nexus supplier is deceptively simple to define: it's a supplier whose criticality comes not from how much you buy from them, but from how many relationships, information flows, and coordination dependencies run through them. Mid-tier by spend. Often missing from your ERP entirely. Remove them and three or four other relationships stop functioning correctly within days.

The reason these suppliers stay invisible is almost embarrassingly mechanical: enterprise procurement systems only track suppliers with active purchase orders. No PO, no visibility. Nexus suppliers live in that gap. A regional logistics coordinator managing the handoff between your contract manufacturer and your freight forwarder. A quality testing lab that four of your Tier 1 suppliers rely on before shipping to you. A small software vendor whose API connects two systems that would otherwise require manual intervention at scale. None of these appear important in a spend cube. All of them are irreplaceable in practice.

Apparent diversification is the real trap. Why does sourcing from three separate Tier 1 suppliers feel like risk management when all three draw from the same Tier 2 component supplier in the same geography? It doesn't add resilience. It adds procurement complexity while the concentration sits below the line of visibility, invisible in your risk register until something breaks. At that point, the nexus supplier becomes visible in the worst possible way: as the single point of failure your entire escalation process is now organized around.

Spend-based tiering wasn't a bad call. Ten years ago it was, for most teams, the fastest and least painful proxy available: limited data, limited time, and top-50-by-spend was the version of risk management you could actually execute in a quarter. Nobody chose badly. But the world underneath that shortcut has moved and the shortcut hasn't. Supply networks are more decentralized than they were a decade ago, disruptions compound faster, and AI now makes it practical to work from the actual dependency structure instead of the proxy that stood in for it. Keep using spend as the entry criterion for risk attention and the blind spot doesn't shrink. It just gets easier to justify.

McKinsey's 2025 Supply Chain Risk Pulse found that only 42% of organizations have meaningful visibility past their direct suppliers, even as 95% report confidence in their Tier 1 view. The majority are managing risk on a map that covers, at best, the first layer of a multi-tier network. The rest is inference and assumption. And Resilinc's 2025 data shows disruptions climbing 38% year over year, with a growing share serious enough to force teams into ad hoc, reactive response. That is not a risk management strategy.

Sources: McKinsey Supply Chain Risk Pulse, 2025 (Tier 2+ visibility); Sphera, 2025 survey of 500 senior supply chain decision-makers (sub-Tier 1 risk origin)

The financial argument is not abstract. Industry lead-time benchmarking from 2025 puts average raw material lead times at roughly 81 days, up about 25% from pre-pandemic norms of around 65 days. Take a hypothetical manufacturer with a €50M annual COGS base operating on that lead time: a single 10-day production halt works out to approximately €1.4M in lost output, before expediting costs and air freight premiums. In my experience running these numbers with finance teams, the expediting cost alone on a 10-day halt frequently lands in the 3–5x range of the direct disruption cost once freight premiums are added (a rule of thumb worth stress-testing against your own freight contracts rather than taking as given).

The subtler hit is on working capital. Teams without nexus visibility compensate with safety stock. They hold buffer across the network because they can't predict where the next failure originates. Rational given incomplete information. Expensive regardless. A €10M inventory base carrying 20% more buffer than necessary due to unresolved network opacity ties up €2M in cash that earns nothing and ages on the shelf. Fix the map and you have a credible case for releasing that buffer, improving ROCE, and reducing carrying cost drag on the P&L. I've watched that conversation with a CFO go very differently once you can show the visibility gap is the direct cause of the overstock, not just a general hedge against uncertainty. It's usually a fifteen-minute conversation, not a full re-forecast, but it's the fifteen minutes that decides who owns the next buffer-reduction decision.

When you ask the right questions in a supplier conversation, nexus suppliers identify themselves. I've run network mapping exercises where the breakthrough came not from a sophisticated graph analysis tool but from a single question to a Tier 1 supplier's operations lead: "If you had to stop production for two weeks, which three suppliers would cause you the most pain to replace?" The answers are almost never the ones at the top of their own spend reports. They name a logistics coordinator, a specialist testing lab, a single-source component maker with a six-month lead time that nobody upstream ever thought to flag.

The information exists. It lives in the heads of people we rarely think to ask. I've seen teams spend months building supplier risk surveys for their top 50 by spend and miss every single actual critical dependency in the process. A handful of structured conversations with the right mid-tier suppliers, framed around operational dependency rather than compliance, is worth more than any dashboard built on spend data alone.

The part I can't cleanly separate is whether that blindspot is an information problem or an incentive problem. The operations lead at your Tier 1 supplier knows exactly which sub-supplier would sink them. But your procurement team is measured on cost and on-time delivery from Tier 1. Nobody's scorecard rewards them for digging two tiers deeper. So the question I keep coming back to: how many of the nexus suppliers sitting invisibly in your network are invisible not because the data doesn't exist, but because nobody's job description currently includes finding them?