WMS-UI-01 CatalogueUI-02 Connection & 3PL scopeUI-03 Capability matrixUI-04 Warehouse contractsUI-05 BindingsUI-06 Inventory reconciliationUI-07 InboundUI-08 OutboundUI-09 LocateLinkUI-10 Count / return / holdUI-11 Recovery & qualificationUI-12 Simulation labImport checks
CS-CON-0258
Blue Yonder Warehouse Management
GATEDproposed target — not qualified← CS-CON-0257CS-CON-0259 →Synthetic warehouse workspace. No native WMS source has been connected. Every profile is a proposed target, no adapter is live or qualified, and no row here was read from a WMS, a WES/WCS or an RTLS. The 18 warehouse payload specs are proposed additive specializations of the V9 canonical contracts, not approved replacements.
Source identity and scope
Aliases
Blue Yonder WMS · JDA lineage when release-compatible
Segment
Enterprise WMS
Engine
vendor
Read scope
WMS-version-approved integration via licensed APIs, events, Connect or customer-authorized export services
Interface detail
Exact WMS resource contract required. Blue Yonder platform/robotics APIs do not automatically expose WMS stock and task data
Incremental and recovery
Pin event retention, ordering, object revision, cancellation handling and snapshot method for the installed WMS
Limitations
Legacy JDA/RedPrairie variants and current cloud offerings cannot share a support claim without a compatibility matrix
Implementation
Not built / not qualified
Configuration schema reference
catalogue/config-schemas/CS-CON-0258.schema.json
Reviewed primary source
Evidence
GATED — Partner/device contract required
Document
Blue Yonder Connect integration overview
Review date
2026-09-22
Evidence scope
WMS-version-approved integration via licensed APIs, events, Connect or customer-authorized export services.
Remaining verification
Legacy JDA/RedPrairie variants and current cloud offerings cannot share a support claim without a compatibility matrix.
DETAIL means the stated technical reference was reviewed — it does not mean every warehouse function of this product was verified, and vendor wire formats are never inferred from the supplied normalized fixtures.
Required configuration — 10 settings
wms_editionwms_releasewarehouse_idsintegration_productinterface_package_refapproved_endpoint_bindingfacility_mapping_set_refowner_mapping_set_refsource_timezoneobject_contract_refs
Every one of these must be supplied before a connection draft is accepted. Secrets are held as opaque references; no credential value is ever entered or displayed here.
Per-object capability matrix — 17 objects
| Warehouse object | Native support | Source-version qualification |
|---|---|---|
| Bin / location master | unverified | not_run |
| Item / owner master | unverified | not_run |
| Handling units | unverified | not_run |
| Inventory balances | unverified | not_run |
| Inventory movements | unverified | not_run |
| Reservations | unverified | not_run |
| Inbound advice | unverified | not_run |
| Goods receipts | unverified | not_run |
| Warehouse tasks | unverified | not_run |
| Waves | unverified | not_run |
| Outbound orders | unverified | not_run |
| Shipments | unverified | not_run |
| Cycle counts | unverified | not_run |
| Adjustments | unverified | not_run |
| Returns | unverified | not_run |
| Stock holds | unverified | not_run |
| Location observations | unverified | not_run |