A condition in which a customer becomes dependent on a specific vendor’s products, services, or technical standards such that switching to an alternative entails substantial economic, technical, contractual, or organizational costs—causing the vendor to obtain durable control over future terms of supply or service.

Principle

Lock‑in arises when switching costs (migration effort, data conversion, retraining, termination penalties) plus network or compatibility effects exceed the expected gains from switching; therefore vendors can capture quasi‑rents and customers face reduced bargaining power unless mitigated by interoperability, contractual safeguards, or competition policy.

Demonstration

Illustrative scenario → Situation: A firm adopts a proprietary database with custom extensions. Recognition: Data formats, APIs and internal workflows depend on vendor‑specific features. Action: To move to a different system the firm must convert data, refactor applications and retrain staff. Consequence: The firm postpones migration despite higher vendor fees, effectively conceding pricing and upgrade terms to the vendor.

Misapplication

Calling any preferred or long‑term supplier a lock‑in: a vendor preference is not lock‑in unless switching imposes material, enduring costs or contractual barriers that make alternatives impractical within the customer’s planning horizon.

Consequence

Vendor lock‑in causally reduces customer bargaining power, can raise long‑run costs, slow adoption of superior alternatives, and distort investment toward vendor‑dependent architectures; it also shapes strategic vendor behaviour (pricing, feature roadmaps) because customers face elevated exit costs.

Reversal

Open standards, data portability, modular architectures, multi‑vendor strategies, explicit contractual exit clauses, or effective regulatory intervention can materially reduce or eliminate lock‑in; conversely, strong network effects or legally binding exclusivity can entrench it further.

Boundary

Clearly within: durable dependency created by high, hard‑to‑recover switching costs (technical, contractual, organizational) tied to vendor‑specific products or standards. Boundary case: temporary switching costs that are significant but diminish over a foreseeable time horizon. Clearly outside: mere vendor familiarity or short‑term contracts without substantive exit barriers.

Semantic Tension

Customization ↔ Interoperability — deep customization increases value but tends to create lock‑in, while interoperability reduces lock‑in but may limit product differentiation and tailored performance.

Synthesis

Vendor lock‑in is not merely a commercial relationship but an economic state produced by a combination of technical, contractual and network features; managing it requires design choices (standards, contracts, architecture) rather than only negotiation.