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-0256
Manhattan Active Warehouse Management
SURFACEproposed target — not qualified← CS-CON-0255CS-CON-0257 →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
Manhattan Active WM
Segment
Enterprise WMS
Engine
rest
Read scope
Authorized Manhattan Active application APIs/events for warehouse resources, subject to licensed modules and tenant entitlements
Interface detail
Developer and API-limit surfaces identified. Import tenant-specific WM resources and schemas; paths and payloads remain unpinned
Incremental and recovery
Honor tenant API budgets and native continuation/change identifiers; use reconciled snapshots when a selected object has no lossless change feed
Limitations
Do not apply Active APIs to SCALE. WES/robot orchestration features do not confer equipment-control permission
Implementation
Not built / not qualified
Configuration schema reference
catalogue/config-schemas/CS-CON-0256.schema.json
Reviewed primary source
Evidence
SURFACE — Interface draft — verify operations
Document
Manhattan Active developer documentation
Review date
2026-09-22
Evidence scope
Authorized Manhattan Active application APIs/events for warehouse resources, subject to licensed modules and tenant entitlements.
Remaining verification
Do not apply Active APIs to SCALE. WES/robot orchestration features do not confer equipment-control permission.
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 — 9 settings
organization_idfacility_idsactive_releaseapi_catalog_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 |
