Cargo Documentation Management

BC-2500 Level 1 Transportation & Logistics 14 providers 18 API surfaces

Issuance, exchange, and lifecycle management of cargo documents including bills of lading, air waybills, road and rail consignment notes, manifests, and their electronic equivalents.

Cargo Documentation Management (BC-2500) is a level-1 business capability in the Transportation & Logistics model. The catalog holds 18 API surface(s) from 14 provider(s) that can perform some part of it. 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

Bill of Lading Management BC-2500.10

Issuance, surrender, and management of ocean and inland-water bills of lading in negotiable and non-negotiable forms.

3 providers, 4 API surfaces

Air Waybill Management BC-2500.20

Issuance and management of master and house air waybills including e-AWB.

no catalog coverage

Road and Rail Consignment Note Management BC-2500.30

Issuance and management of road and rail consignment notes under CMR and CIM/SMGS regimes.

no catalog coverage

Manifest and Cargo Declaration Management BC-2500.40

Filing of cargo manifests and pre-arrival cargo declarations to customs, terminals, and partner carriers.

6 providers, 6 API surfaces

Electronic Documentation Management BC-2500.50

Operation of electronic transport-document platforms including eBL and ONE Record exchanges.

1 provider, 1 API surface

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.

Developing 5 Usable, with meaningful gaps to close

KarrioManifests1 API53.9 OTO GlobalShipping Label(AWB)1 API53.5 MaerskBillOfLadingVGM2 APIs48.7 SendleManifests1 API44.6 LoadsmartBOL1 API41.0

Thin 5 Limited public surface area

Royal MailManifests1 API39.0 Port Community SystemsCargoManifests1 API36.1 CargoSmartDocuments1 API33.9 BoxcManifests1 API32.9 CargoDocsDocumentsIssuanceSurrender3 APIs31.4

Emerging 4 Early or largely undocumented

Old Dominion Freight LineBill of LadingDocuments2 APIs25.9 Pitney BowesManifests1 API25.0 Kuehne+NagelList1 API20.7 NMFTACarrier API Standards1 API18.4

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 Cargo Documentation 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 →