Inventory Management

BC-530 Level 1 Cross-Industry 7 providers 10 API surfaces 3 rated strong or better

Stock levels, replenishment, allocation across the supply network.

Inventory Management (BC-530) is a level-1 business capability in the Cross-Industry model. The catalog holds 10 API surface(s) from 7 provider(s) that can perform some part of it, 3 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Stock Level Management BC-530.10

Target stock levels, safety stock, reorder points.

no catalog coverage

Replenishment Management BC-530.20

Replenishment policies, automated replenishment.

no catalog coverage

Inventory Allocation Management BC-530.30

Allocation across the network, reservations.

2 providers, 2 API surfaces

Inventory Accuracy Management BC-530.40

Cycle counts, physical inventory, discrepancy resolution.

no catalog coverage

Slow-Moving & Obsolete Stock Management BC-530.50

SLOB identification, write-off, disposition.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 1 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Thin 1 Limited public surface area

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Inventory Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →