Dependency Risk: When Supplier Control Becomes Customer Exposure

Many supplier-agreement disputes that appear to concern intellectual property ownership are really about dependency risk. A customer may not need to own every process, software component, design tool, or item of know-how used to make a product. It does, however, need a credible path to continue manufacturing, supporting, repairing, and selling the product if the supplier relationship ends or the supply chain is disrupted. 

Dependency risk arises when technology essential to the product remains under the supplier's control, but the agreement does not give the customer sufficient rights or practical access to operate without that supplier. The dependency may involve embedded software, manufacturing processes, tooling, drawings, test methods, quality records, source materials, or other technical information. The issue is not simply whether the supplier owns those assets. The issue is what happens when the customer needs them most. 

The risk often hides in otherwise familiar drafting. A definition of Supplier Technology may sweep in all improvements, including product-specific changes. A license may permit the customer to use the delivered product but omit the right to make or have it made. Rights may expire with the supply agreement, prohibit sublicensing to an alternate source, or fail to transfer with the relevant business. Tooling may be customer-funded but remain at the supplier's facility without meaningful retrieval rights. Transition assistance may be described generally, without identifying the records, materials, timing, or cooperation required for an actual transfer. 

These gaps may not matter while performance is stable, but they become critical when a supplier stops supplying, increases prices beyond expectations, experiences financial distress, loses a key subcontractor, encounters an IP claim, or simply cannot meet demand. At that point, a narrow license or incomplete technical package can leave the customer with a contractual remedy but no practical way to preserve the product line. Damages or a refund may compensate for a breach, but they do not necessarily keep products moving to customers or support units already in the field. 

The strongest agreements address dependency as an operational problem, not merely an ownership problem. If the supplier retains its background technology, the customer should consider whether it needs durable rights to make, have made, modify, repair, use, sell, and import the affected products. The real test is whether the license continues to work when the supply relationship breaks down. The license should survive termination, transfer with the business, permit use by affiliates and contractors, and allow the customer to transition production to an alternate source. Depending on the transaction, continuity protections may also include access to tooling, drawings, specifications, software materials, quality files, approvals, inventory, and defined transition support. 

This does not mean every customer should demand ownership of the supplier's platform. Overreaching ownership language can create a different problem by capturing reusable supplier technology and making the negotiation unnecessarily adversarial. A more balanced structure often allows the supplier to retain its platform while giving the customer the rights and materials needed to protect continuity. Ownership and operating freedom are related, but they are not the same thing. 

A useful drafting test is straightforward: if supply ended tomorrow, could the customer continue producing, supporting, and selling the product through another qualified source? If the answer depends on the supplier's continued consent, cooperation, or discretion, the agreement may contain a dependency gap. Identifying that gap before signing is usually far easier than trying to solve it during a disruption. 

Key takeaway: The goal is not to eliminate supplier ownership. It is to ensure that supplier-controlled technology does not leave the customer without a workable continuity plan. The agreement should pair clear IP boundaries with durable licenses, access rights, and transition mechanics that preserve the customer's ability to operate throughout the product lifecycle.