Hedge, Monitor, or Accept? What to Do With a Supply-Chain Dependency
August 31, 2026
Altsets
Research by Altsets Research
Turn dependency analysis into a portfolio decision by separating relationships that deserve active risk reduction from those that need monitoring or should be accepted as part of the investment thesis.
Data used:Altsets Supply Chain Intelligence: 90k+ entities, 400k+ relationships, 20+ years of history.
Key findings
- The correct response to a dependency depends on economic importance, replaceability, catalyst proximity, and portfolio overlap rather than the existence of concentration alone.
- A strategically valuable relationship can be worth accepting when it improves demand visibility, while repeated or catalyst-sensitive dependencies can justify active risk reduction or tighter monitoring.
Finding a supply-chain dependency is only the beginning of the investment decision. The useful question is what to do with it. Some dependencies deserve a smaller position, some deserve a catalyst alert, some deserve deeper research, and some should simply be accepted because they are part of what makes the business valuable.
A practical framework is to classify a dependency into one of three responses: hedge it, monitor it, or accept it. The choice depends on economic importance, replaceability, catalyst proximity, portfolio overlap, and whether the dependency is already central to the investment thesis.
Hedge when one dependency can damage several parts of the portfolio at once
A dependency becomes a stronger candidate for active risk reduction when it is economically important and repeated across multiple holdings. The investor is no longer dealing with one company-specific vulnerability. One outside event can reach several positions through the same customer, supplier, manufacturing node, or regulatory channel.
Hedging does not have to mean buying an options contract against the dependency. It can mean reducing one position, lowering the combined weight of a cluster, choosing a new holding with a different dependency map, or temporarily carrying less exposure through a known catalyst.
The objective is to reduce portfolio damage if the shared node becomes the source of volatility.
Monitor when the dependency matters but the failure mechanism is uncertain
Many relationships are important enough to watch but not strong enough to justify a portfolio change. A customer may be economically meaningful while demand remains healthy. A supplier may be difficult to replace but operationally stable. A structural relationship may identify a plausible event path without providing enough economic evidence to size it.
In those cases, monitoring is the better response. The investor can attach earnings dates, product launches, regulatory decisions, contract milestones, capacity announcements, and relevant filings to the relationship and wait for evidence that the risk is strengthening or weakening.
This prevents the portfolio from being churned every time a meaningful dependency is discovered.
Accept when the dependency is part of the reason the company is attractive
Some concentrated relationships create strategic value. LG Energy Solution's Tesla relationship is a good example of why a dependency can be both a risk and a source of visibility. The supplied Altsets data makes Tesla economically important to LG Energy Solution, while the companies' public product context ties the relationship to Tesla energy-storage systems and planned U.S. production.
An investor may decide that the relationship improves the thesis because it connects LG Energy Solution to a growing customer and a specific product roadmap. The concentration still needs to be monitored, but eliminating the exposure would also eliminate part of the opportunity.
Accepting a dependency is therefore not the same as ignoring it. It means the investor understands the risk and still wants the economic exposure.
Replaceability changes the answer
A large relationship can be less dangerous when substitutes are readily available and more dangerous when qualification, technology, scale, or capacity make switching difficult. The percentage alone cannot answer that question.
This is why financial materiality and operational criticality need to remain separate. A relatively small supplier can still be critical to production, while a large customer relationship can be easier to replace than the headline number suggests.
The action should follow the failure mechanism, not the visual size of the graph edge.
Catalyst proximity determines whether the decision is urgent
The same dependency can move between the three categories over time. A relationship that normally belongs in the monitoring bucket can become a short-term hedging problem when a major earnings report, regulatory deadline, contract renewal, or product transition approaches.
After the catalyst passes, the investor may decide the relationship is stable enough to accept again. Dependency management should therefore be dynamic rather than a permanent label attached to a company.
This is especially useful for portfolios that want to stay invested through long-term themes while controlling shorter windows of event risk.
Portfolio overlap matters more than the dependency in isolation
One customer relationship can be perfectly acceptable in a portfolio with little exposure to that customer and much more concerning in an account where several holdings already depend on the same company.
That is why the response cannot be determined from company data alone. The investor needs to know whether the dependency is repeated elsewhere in the portfolio and how much capital is already sitting behind that shared node.
A moderate company-level dependency can become a major portfolio-level concentration once overlap is included.
An investing agent can keep the decision current
This framework works well with an agent because the underlying decision does not need to be remade from scratch every day. The investor can define why a relationship is currently being hedged, monitored, or accepted, and the agent can watch for evidence that would move it into another category.
The agent might flag a new customer concentration disclosure, a supplier qualification problem, a product delay, a contract extension, or a relationship change. The value is not the agent deciding the trade. The value is keeping the assumptions behind the risk decision visible.
The conclusion is a response, not a score
Supply-chain data becomes much more useful when every important dependency leads to a decision. The investor should be able to say why the relationship is being hedged, why it is only being monitored, or why it is being accepted as part of the thesis.
That is a better outcome than collecting a long list of dependencies and treating all of them as generic risk. The point of dependency awareness is not to eliminate dependence. It is to know which dependence deserves action.
The position-sizing guide explains how dependency can change capital allocation. The pre-earnings de-risking guide applies the same logic to a known external catalyst.
For relationship definitions and evidence limits, read the Altsets methodology.