Overview
The NexLog OS WMS controls the warehouse end to end: receiving (GR), put-away, wave picking, packing intelligence, shipping, cross-docking, slotting, quality gate and labor management.
Every movement generates a canonical event in the ledger and feeds Control Tower, ESG and finance in real time.
Core entities
The canonical WMS model gives each entity a display name and an English code name (the MongoDB collection), used across the whole platform: WMS, TMS, OMS, Control Tower, ESG and Finance.
| Entity | Code | Description |
|---|---|---|
| Warehouse | warehouses | DC, branch or hub. Contains zones, locations, equipment and staff. Each operating unit has its own space for movements, docks and counts. |
| Storage location | storageLocations | Physical position inside a warehouse, organized by aisle, column, level and bay. Supports zones (DRY, REFRIGERATED, FROZEN, FLAMMABLE, HIGH_TURNOVER, QUARANTINE). |
| Movement | movements | Transactional inventory event: INBOUND, OUTBOUND, TRANSFER, ADJUSTMENT or RETURN. Immutable, emitted to the event ledger with correlationId and causationId. |
| Inventory count | inventoryCounts | Cycle or full count. Produces auditable discrepancies, generates ADJUSTMENT movements and feeds the accuracy score by zone. |
Operational flows
The eight flows that take goods from the gate to shipping.
Receiving (GR)
Scheduling, unloading, blind check, SSCC labeling and auditable discrepancies.
Smart put-away
Slotting rules by turnover (HIGH_TURNOVER), weight, temperature and chemical compatibility.
Pick path and wave picking
Waves optimized by route, cluster or batch; optional voice picking and pick-by-light.
Cross-docking
Redirects received SKUs to the outbound dock without putting stock away.
Packing intelligence
Cubing, load balancing and packaging selection (AI-Pack), with a direct impact on CO2e.
Quality gate
Lot inspection, automatic quarantine in the QUARANTINE zone and a shipping block.
Labor management
Operators with targets, productivity per task and cumulative OEE by zone and shift.
Dynamic slotting
Continuous repositioning of the fastest-moving SKUs to the most accessible positions.
Movement types
Values of the movements enum.
| Code | Name | Description | Typical source |
|---|---|---|---|
INBOUND | Inbound | Receipt from a supplier or transfer between DCs. | NF-e + GR |
OUTBOUND | Outbound | Shipment to a customer or branch, or return to the supplier. | OMS order |
TRANSFER | Transfer | Movement between locations within the same warehouse. | Slotting or put-away |
ADJUSTMENT | Adjustment | Accounting correction after a count or an acknowledged loss. | inventoryCounts |
RETURN | Return | Customer return (B2C or B2B) with audited re-entry. | OMS returns |
Storage zones
Values of the storageLocations.zone enum.
| Code | Zone | Description |
|---|---|---|
DRY | Dry | Ambient temperature, general use. |
REFRIGERATED | Refrigerated | Usually 2–8 °C; light cold chain. |
FROZEN | Frozen | Below −18 °C; deep cold chain. |
FLAMMABLE | Flammable | Hazardous goods; segregation required. |
HIGH_TURNOVER | High turnover | Premium area near shipping. |
QUARANTINE | Quarantine | Blocked from use until quality release. |
REST endpoints
Endpoints versioned under /api/v1/.
| Endpoint | Methods |
|---|---|
/api/v1/warehouses | GET, POST |
/api/v1/locations | GET, POST |
/api/v1/movements | GET, POST |
/api/v1/inventory-counts | GET, POST |
Convention: endpoints in kebab-case, versioned under /api/v1/, and collections in camelCase.
KPIs the WMS delivers
Inventory accuracy
Percentage of positions checked with no discrepancy.
OTIF (On Time In Full)
Percentage of orders shipped complete and within the agreed time.
Productivity per operator
Units per hour, tasks per shift and cumulative OEE, broken down by zone and movement type.
The WMS as the backbone of the supply chain OS
A WMS is more than an inventory
For a long time, the WMS was seen as a system of record: how much there is, where it is, when it left. That view explains little of what a modern warehouse needs.
The NexLog OS WMS treats every point in the flow (receiving, put-away, picking, packing, shipping, cross-docking, slotting, counting, quality gate and labor) as a canonical event emitted to the event ledger (businessEvents). Every physical movement in a Warehouse (warehouses) and Storage location (storageLocations) generates a Movement (movements) with correlationId and causationId, enabling auditing, replay and analytics without ETL.
Zones, rules and compliance
Zones (DRY, REFRIGERATED, FROZEN, FLAMMABLE, HIGH_TURNOVER, QUARANTINE) stop being labels and become business invariants. The put-away engine respects chemical compatibility, temperature and turnover: flammable products are never put away in FROZEN, items in QUARANTINE are blocked from shipping and the HIGH_TURNOVER strategy reorganizes continuously based on picking frequency.
This rules layer reduces rework and operational risk while documenting compliance decisions for external audits.
From WMS to supply chain OS
Because the WMS shares the same MDM with the TMS (shipments), OMS (orders), YMS (dockSchedules) and Customs (tradeDeclarations), the picture changes. An omnichannel order received by the OMS triggers allocation in the WMS, which generates a picking and packing wave and releases loading at a dock scheduled by the YMS. The shipment leaves with a CT-e issued by the TMS and, for exports, with the customs declaration plugged in through Customs.
Each step emits a canonical event, and Control Tower sees all of it in real time. That is what sets a WMS inside a supply chain operating system apart from a standalone WMS.