{ "schema_version": "core-reviewed-term-ai-handoff-v1", "version": "core-reviewed-term-ai-handoff-v1", "contract_status": "preview", "distribution": "per_term_read_only_ai_handoff", "no_write_operations": true, "canonical": { "url": "https://core.yogoq.com/en-US/core/vendor-concentration-risk", "slug": "vendor-concentration-risk", "locale": "en-US" }, "summary": { "schema_version": "core-reviewed-term-summary-v1", "term_id": "05ce6f3b-d301-5b02-a2c0-3a6e9c4f0f26", "canonical_slug": "vendor-concentration-risk", "canonical_url": "https://core.yogoq.com/en-US/core/vendor-concentration-risk", "locale": "en-US", "display_name": "Vendor Concentration Risk", "english_name": null, "abbreviation": null, "short_definition": "Vendor Concentration Risk is the exposure created when too much critical capability, spend, data, or recovery dependency sits with one supplier or supplier cluster. It is used for when to diversify, add fallback capacit…", "quality": "reviewed", "publication_status": "published_reviewed", "version": "core-reviewed-term-summary-v1", "last_reviewed_at": "2026-05-14T00:00:00.000Z", "sources_count": 2, "limitations_key": "core-trust-policy-v1-2026-06-22" }, "content": { "definition": { "key": "definition", "title": "一言でいうと", "text": "Vendor Concentration Risk is the exposure created when too much critical capability, spend, data, or recovery dependency sits with one supplier or supplier cluster. It is used for when to diversify, add fallback capacity, renegotiate, insure, or accept the exposure by reading single-source dependency, spend share, switching time, data exit cost, and supplier failure impact and deciding when to diversify, add fallback capacity, renegotiate, insure, or accept the exposure.", "items": [] }, "formula": null, "boundary": { "key": "boundary", "title": "含めるもの / 含めないもの", "text": "Keep the inclusion and exclusion rules stable so decisions can be compared over time. Include | critical service dependency, spend share, data portability, switching path | These determine how severe supplier failure would be Exclude | low-impact commodity spend, replaceable subscriptions, one-time purchases | They may look concentrated but not threaten operations Define explicitly | single point of failure, exit plan, fallback vendor, contract leverage | The response depends on what kind of concentration exists", "items": [ "Include | critical service dependency, spend share, data portability, switching path | These determine how severe supplier failure would be", "Exclude | low-impact commodity spend, replaceable subscriptions, one-time purchases | They may look concentrated but not threaten operations", "Define explicitly | single point of failure, exit plan, fallback vendor, contract leverage | The response depends on what kind of concentration exists" ] }, "usage": [ { "key": "meaning", "title": "意味", "text": "Vendor Concentration Risk is a practical concept for improving operating, risk, and organization decisions. It makes single-source dependency, spend share, switching time, data exit cost, and supplier failure impact visible under shared assumptions so teams can decide when to diversify, add fallback capacity, renegotiate, insure, or accept the exposure. Without clear vendor concentration risk boundaries, owners, and review cadence, teams can improve one local view while moving vendor concentration risk pressure elsewhere.", "items": [] }, { "key": "usage", "title": "役立つ場面", "text": "Vendor Concentration Risk changes decisions by turning single-source dependency, spend share, switching time, data exit cost, and supplier failure impact into evidence for where scarce capacity and budget should go. It sets boundaries so improvement, control, resilience, and customer impact can be weighed in the same review. It makes when to diversify, add fallback capacity, renegotiate, insure, or accept the exposure operational by naming owners, triggers, and review cadence instead of leaving the concept as a discussion point.", "items": [ "Vendor Concentration Risk changes decisions by turning single-source dependency, spend share, switching time, data exit cost, and supplier failure impact into evidence for where scarce capacity and budget should go.", "It sets boundaries so improvement, control, resilience, and customer impact can be weighed in the same review.", "It makes when to diversify, add fallback capacity, renegotiate, insure, or accept the exposure operational by naming owners, triggers, and review cadence instead of leaving the concept as a discussion point." ] }, { "key": "usage", "title": "使い方のポイント", "text": null, "items": [ "Map critical vendors by service impact, not only annual spend.", "Estimate realistic switching time and data exit effort.", "Separate commercial concentration from operational recovery concentration.", "Review concentration before renewals, architecture decisions, and expansion plans.", "In every Vendor Concentration Risk review, record the customer impact, risk tradeoff, accountable owner, and next review date alongside the metric movement." ] }, { "key": "drivers", "title": "何が数字を動かすか", "text": "Breaking the topic into drivers shows which operating action is likely to move the result. Switching time | Longer switching time raises continuity exposure | Use tested migration effort, not vendor claims Data lock-in | Hard exits reduce negotiating and recovery options | Check export, format, and ownership rights Supplier health | Weak vendor finances or operations increase failure probability | Review signals before renewal", "items": [ "Switching time | Longer switching time raises continuity exposure | Use tested migration effort, not vendor claims", "Data lock-in | Hard exits reduce negotiating and recovery options | Check export, format, and ownership rights", "Supplier health | Weak vendor finances or operations increase failure probability | Review signals before renewal" ] } ], "misunderstandings": [ { "key": "misunderstandings", "title": "よくある誤解 / 落とし穴", "text": null, "items": [ "Low price can increase risk when the vendor becomes hard to replace.", "A second contract is not a fallback if it has never been tested.", "Concentration can hide in data, identity, logistics, or specialized knowledge, not just spend." ] } ], "examples": [ { "key": "examples", "title": "最小例", "text": "A company discovers that its customer identity, billing export, and incident notification all rely on one vendor. The vendor spend is moderate, but switching would take months. The team funds data export automation and a tested fallback for notifications before the renewal. In this example, Vendor Concentration Risk is treated as an operating decision that connects constraints, ownership, measurement, and review, so the team can reassess the change using the same evidence later.", "items": [] } ], "comparisons": [ { "key": "comparisons", "title": "似ている言葉との違い", "text": "Procurement strategy | Chooses sourcing and commercial approach | Vendor concentration risk tests whether the approach leaves critical exposure Supplier relationship health | Assesses ongoing supplier partnership | Concentration risk focuses on dependency severity and exit options Enterprise risk management | Prioritizes material risks | Vendor concentration is one operational and strategic exposure inside ERM", "items": [ "Procurement strategy | Chooses sourcing and commercial approach | Vendor concentration risk tests whether the approach leaves critical exposure", "Supplier relationship health | Assesses ongoing supplier partnership | Concentration risk focuses on dependency severity and exit options", "Enterprise risk management | Prioritizes material risks | Vendor concentration is one operational and strategic exposure inside ERM" ] } ], "faq": [ { "question": "Is concentration always bad?", "answer": "No. It can be acceptable when impact is low, controls are strong, and the exit plan is realistic." }, { "question": "What is the best first metric?", "answer": "Start with critical service dependency and switching time; spend share alone is not enough." }, { "question": "How do we reduce concentration?", "answer": "Use dual sourcing, tested fallback paths, data portability, contract rights, or explicit risk acceptance." } ] }, "sources": { "source_refs": [ "concept:business-concept-0060:en-US", "concept:business-concept-0060:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch1-2026-04-28" ], "visible_sources": [ { "label": "Introduction to Business (OpenStax)", "url": "https://openstax.org/details/books/introduction-business", "kind": "tier_s" }, { "label": "Wikipedia reference: Supply Chain Management", "url": "https://en.wikipedia.org/wiki/Supply_chain_management", "kind": "supplemental" } ] }, "related_terms": [ { "topic_id": "23da7a9a-48d5-5eaf-aacc-281059c4e742", "canonical_slug": "supplier-relationship-health", "canonical_url": "https://core.yogoq.com/en-US/core/supplier-relationship-health", "title": "Supplier Relationship Health", "relation_type": "used_together" }, { "topic_id": "14819475-3f6b-5bb7-a400-b81abc5e1885", "canonical_slug": "enterprise-risk-management", "canonical_url": "https://core.yogoq.com/en-US/core/enterprise-risk-management", "title": "Enterprise Risk Management (ERM)", "relation_type": "used_together" }, { "topic_id": "0f3f5f7e-5c9e-50dd-ad9d-655abd6b188c", "canonical_slug": "procurement-strategy", "canonical_url": "https://core.yogoq.com/en-US/core/procurement-strategy", "title": "Procurement Strategy", "relation_type": "related" } ], "quality": { "quality": "reviewed", "publication_status": "published_reviewed", "source_count": 2, "last_reviewed_at": "2026-05-14T00:00:00.000Z", "trust_policy_version": "core-trust-policy-v1-2026-06-22" }, "limitations": { "policy_version": "core-trust-policy-v1-2026-06-22", "professional_advice_boundary": "reference_only_not_professional_advice", "text": "This page is reference information for research and learning. For accounting, legal, finance, health, security, or other individual decisions, confirm against primary sources or qualified professionals.", "items": [ "Public pages support general understanding and practical context; they are not professional advice for individual cases.", "Fast-changing information such as regulations, accounting standards, prices, product specs, and legal requirements should be checked against primary sources before final decisions.", "Even when AI-assisted drafting or audit is used, publication relies on quality gates and human-readable evidence." ] } }