Telecom Product Catalogue Management

BC-2650 Level 1 Telecommunications 10 providers 18 API surfaces 1 rated strong or better

Design, configuration, lifecycle, and channel publication of telecom products, tariffs, plans, bundles, and promotions across consumer, enterprise, and wholesale.

Telecom Product Catalogue Management (BC-2650) is a level-1 business capability in the Telecommunications model. The catalog holds 18 API surface(s) from 10 provider(s) that can perform some part of it, 1 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

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Product Offer Design BC-2650.10

Design of new commercial offers including features, eligibility, and pricing structures.

1 provider, 1 API surface

Tariff & Plan Management BC-2650.20

Definition and lifecycle of tariffs, recurring charges, and fair-use policies underpinning offers.

5 providers, 5 API surfaces

Bundle & Promotion Management BC-2650.30

Composition and rules of multi-product bundles and time-bound promotions.

no catalog coverage

Product Catalogue Publication BC-2650.40

Publication of catalogue versions to channels and partners with version control and regional variants.

2 providers, 2 API surfaces

Telecom Product Lifecycle Management BC-2650.50

Lifecycle management of offers from launch through modification, sunset, and grandfathering.

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
TwilioRatePlans1 API73.8
Developing 4 Usable, with meaningful gaps to close
MTN GroupcatalogcategoryproductOfferingproducts4 APIs51.6MEFcategory1 API51.4KORE WirelessRatePlans Resourceeligibility2 APIs46.6ZayoProduct Catalog1 API43.9
Thin 5 Limited public surface area
AlianzaCalling Plan Product1 API33.7Truphone (1GLOBAL)Plans1 API32.1eSIM GoCatalogue1 API31.9TM ForumcategoryproductCatalogproductOfferingproductOfferingPrice5 APIs30.2Maya MobilePlans1 API28.0
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 Telecom Product Catalogue 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 →