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-0270
Extensiv 3PL Warehouse Manager
SURFACEproposed target — not qualified← CS-CON-0269CS-CON-0271 →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
Formerly 3PL Central warehouse manager
Segment
3PL WMS
Engine
rest
Read scope
Product-specific 3PL Warehouse Manager APIs with facility/customer scopes and vendor-provisioned application access
Interface detail
Configuration surface includes TPLGUID, facility and customer identifiers. Import actual account API resource schemas and grant configuration
Incremental and recovery
Partition checkpoints, records and access by warehouse customer and facility; qualify paging, deleted records and retry semantics
Limitations
Extensiv Order Manager, Integration Manager and other products are separate. Source 3PL customer partition is not the same as Optimon tenant identity
Implementation
Not built / not qualified
Configuration schema reference
catalogue/config-schemas/CS-CON-0270.schema.json
Reviewed primary source
Evidence
SURFACE — Interface draft — verify operations
Document
Setting up Extensiv 3PL Warehouse Manager
URL
Review date
2026-09-22
Evidence scope
Product-specific 3PL Warehouse Manager APIs with facility/customer scopes and vendor-provisioned application access.
Remaining verification
Extensiv Order Manager, Integration Manager and other products are separate. Source 3PL customer partition is not the same as Optimon tenant identity.
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
tpl_guidfacility_idscustomer_idsapplication_binding_refsource_timezoneapproved_endpoint_bindingfacility_mapping_set_refowner_mapping_set_refobject_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 |