Supply Chain Management
BC-520
Level 1
Cross-Industry
40 providers
187 API surfaces
12 rated strong or better
End-to-end supply chain planning, orchestration, and execution.
Supply Chain Management (BC-520) is a level-1 business capability in the Cross-Industry model. The catalog holds 187 API surface(s) from 40 provider(s) that can perform some part of it, 12 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
Demand Planning Management BC-520.10
Demand forecasting, statistical and consensus planning.
1 provider,
1 API surface
Supply Planning Management BC-520.20
Supply network planning, sourcing balancing.
no catalog coverage
Sales & Operations Planning Management BC-520.30
S&OP / IBP, cross-functional alignment.
no catalog coverage
Order Fulfilment Management BC-520.40
Order promising, allocation, fulfilment orchestration.
30 providers,
78 API surfaces
Logistics Operations Management BC-520.50
Transport, warehousing operations within the supply chain.
27 providers,
108 API surfaces
Supply Chain Risk Management BC-520.60
Supply chain disruption, visibility, resilience.
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.
-
Shopify
CancelCompleteFulfillmentFulfillment OrdersFulfillmentsLineManagedManyMarkMerchantMoveMoves
exemplar
86.6
-
Lightspeed Commerce
Fulfillments
exemplar
83.8
-
AfterShip
Cancel LabelsCancel PickupsFulfillmentsManifestsPickupsTracking
exemplar
76.0
-
Commerce Layer
carrier_accountseasypost_pickupsordersparcelsshipments
exemplar
72.5
-
Toast
Orders
exemplar
67.7
-
ClickFunnels
FulfillmentOrderShipping::PackageShipping::Profile
strong
63.8
-
OK Capsule
FulfillmentsIntegrations OrdersOrders
strong
63.7
-
Medusa
FulfillmentsOrders
strong
63.1
-
Infusionsoft (Keap)
Orders
strong
62.5
-
Oracle E-Business Suite
Shipping
strong
61.4
-
LeafLink
Logistics Transportdeliveriesdistribution-zonesline-itemsorders-receivedtransportation
strong
59.3
-
MyCarrier
DispatchRatingShipmentDetails
strong
55.8
-
Flipdish
Orders
developing
54.0
-
Phasio
Manufacturer Shipment ControllerManufacturer Shipping Method ControllerManufacturer Tracking Controller
developing
53.9
-
Katana
DemandForecastControllerSalesOrderControllerSalesOrderFulfillmentController
developing
52.9
-
Cart.com
Order ShipmentsOrders
developing
50.3
-
Avito
Order ManagementParcelProcessingXDelivery
developing
49.8
-
Lokki
Delivery
developing
49.2
-
Xentral
DeliveryDelivery NoteDeliveryNoteShipments
developing
48.8
-
Zoho Inventory
delivery-challanspackagesputawaysshipmentorders
developing
48.4
-
SAP Sales and Distribution (SD)
Inbound Delivery HeaderOutbound Delivery Header
developing
48.0
-
tread.io
GeofenceTriggersJobAssignmentsJobsLoadsLocationHistoriesOrders
developing
48.0
-
OneRail
CarrierControlTowerDeliveryDelivery AttemptDelivery ExceptionOrderRouteRouteStopNoteRoutesShipping Label
developing
45.4
-
Newstore
fulfillment-requestsorder-injectionorderspackage-typesprovider-ratesroutingrouting-configrouting-rulesetshipping-labels
developing
43.9
-
Automile
ResourceOwnerRoutePlanner
developing
42.8
-
VTEX
CarriersChange Order (Beta)Delivery ServicesDocksExternal SellerOrdersPickup PointsScheduled DeliveryShipping PoliciesShipping Updates
developing
42.8
-
AMCS Group
OrderRouteRouteAssignmentRouteTemplateRouteVisitRouteVisitJobSchedule
developing
42.2
-
Spree Commerce
FulfillmentsOrder StatusOrdersShipments
developing
42.0
-
eBay
Fulfillment_policyOrderShipmentShipping_fulfillmentShipping_quote
developing
41.9
-
Loadsmart
AppointmentsAsset VisitDocksLoad OffersShipment StopsShipmentsWarehousesYMS - SpotYMS - Spot AssignmentYMS - Yard View
developing
41.4
-
Omniful, Inc.
OrdersOrders (V2)ReturnsShipmentShipment OrdersShipments
developing
40.2
-
Elastic Path
Order Shipping GroupsOrders
developing
40.1
-
Spree Commerce
OrdersShipments
thin
39.1
-
DSV
BPO InboundBookingBookingWebServiceBookingsDraftShipmentShipment detailsShipment listShipmentsTrackingTrackingWebServiceV3
thin
38.7
-
fabric
FulfillmentsOrdersShipments
thin
36.6
-
Samsara
Routes
thin
32.6
-
Picker
drivertracking
thin
31.8
-
Kuehne+Nagel
Assigned ConsignmentsBooking RequestsEventsExternalShipmentGPS TrackingJob DocumentsJob StatusPost eventProof of Deliverybookingcontainershipment
emerging
24.3
-
AEB
BSM CarrierCarrierEventServiceBFBeanLISBF20BeanRoutingShipping
emerging
23.6
-
Geniemode
courier-controllerlogistics-dashboard-controllerorder-v-2-controllershipment-controllershipment-tracking-controller
emerging
21.2
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 Supply Chain 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 →