OptimonCoreSync Studio
IE
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-0273

Unicommerce Uniware WMS

DETAILproposed target — not qualified← CS-CON-0272CS-CON-0274 →
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
Uniware warehouse management
Segment
India and omnichannel WMS
Engine
rest
Read scope
Warehouse REST documentation covers receiving/GRN, put-away, inventory snapshots and execution resources; operation contracts will be imported individually
Interface detail
Warehouse resource documentation reviewed; select read operations and approved exports, not GRN/put-away creation APIs under read permission
Incremental and recovery
Pin facility-scoped object keys and snapshot pagination; recover inbound and execution records without reissuing warehouse write operations
Limitations
Every operation requires an effect classification. The WMS overview includes both reads and commands; not all endpoints are ingestion
Implementation
Not built / not qualified
Configuration schema reference
catalogue/config-schemas/CS-CON-0273.schema.json

Reviewed primary source

Evidence
DETAIL — Technical reference reviewed
Document
Unicommerce API documentation — Warehouse Management
URL
https://documentation.unicommerce.com/docs/wms-overview.html
Review date
2026-09-22
Evidence scope
Warehouse REST documentation covers receiving/GRN, put-away, inventory snapshots and execution resources; operation contracts will be imported individually.
Remaining verification
Every operation requires an effect classification. The WMS overview includes both reads and commands; not all endpoints are ingestion.

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

uniware_tenantfacility_codesapi_generationwarehouse_resource_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.

Configure a simulated connection →

Per-object capability matrix — 17 objects

Warehouse objectNative supportSource-version qualification
Bin / location masterunverifiednot_run
Item / owner masterunverifiednot_run
Handling unitsunverifiednot_run
Inventory balancesunverifiednot_run
Inventory movementsunverifiednot_run
Reservationsunverifiednot_run
Inbound adviceunverifiednot_run
Goods receiptsunverifiednot_run
Warehouse tasksunverifiednot_run
Wavesunverifiednot_run
Outbound ordersunverifiednot_run
Shipmentsunverifiednot_run
Cycle countsunverifiednot_run
Adjustmentsunverifiednot_run
Returnsunverifiednot_run
Stock holdsunverifiednot_run
Location observationsunverifiednot_run
Capability discoveryRun the 12 scenariosRecovery & qualificationBack to WMS catalogue