Warehouse Software Stack

Overview

The warehouse technology stack is a layered hierarchy of systems, each responsible for a distinct scope of decisions and actions. Understanding which layer owns which function prevents integration gaps and avoids buying capabilities already present in an adjacent system.

┌─────────────────────────────────────────┐
│  ERP (SAP, Oracle, Microsoft D365)      │  Financial, master data, order of record
├─────────────────────────────────────────┤
│  OMS (Manhattan, IBM Sterling, Kibo)    │  Where to fulfill from; order routing; ATP
├─────────────────────────────────────────┤
│  YMS (Körber, 10-4, PINC)               │  Yard / dock scheduling; trailer tracking
├─────────────────────────────────────────┤
│  WMS (Manhattan, Blue Yonder, SAP EWM)  │  Inventory, pick/pack/ship, cycle count
├─────────────────────────────────────────┤
│  LMS (Manhattan, Infor, Epiphany)       │  Labor standards, productivity, incentives
├─────────────────────────────────────────┤
│  WES (Körber, Honeywell, Swisslog)      │  Real-time task orchestration; load balance
├─────────────────────────────────────────┤
│  WCS (Dematic iQ, Hytrol, Cisco-Eagle)  │  Equipment control; conveyor/sorter commands
├─────────────────────────────────────────┤
│  PLCs / Field Devices                   │  Physical execution at millisecond latency
└─────────────────────────────────────────┘

ISA-95 alignment: ERP = Level 4, WMS/LMS/OMS = Level 3, WES = Level 3/2 boundary, WCS/PLCs = Level 2/1.

---

Layer Responsibilities

Layer	Core Question	Decision Horizon	Latency Tolerance
ERP	What are we buying/selling?	Days–weeks	High
OMS	Which node fulfills this order?	Hours–days	High
YMS	What’s in the yard / which door?	Hours	Moderate
WMS	What’s in the building and where?	Minutes–hours	Moderate
LMS	How is labor performing vs standard?	Shift	Moderate
WES	What task runs next, on which resource?	Seconds–minutes	Low
WCS	Which motor activates at which speed?	Milliseconds	Very low

---

Integration Seams and Failure Points

ERP → WMS: The most common integration gap. ERP thinks in financial units; WMS thinks in physical locations and license plates. Mismatches in unit-of-measure definitions cause inventory reconciliation failures.

OMS → WMS: OMS sends orders for execution; WMS must have real-time inventory to confirm ATP before OMS commits to customer. Latency in this feed causes oversells.

WMS → WES: WMS releases work orders or pick tasks; WES decomposes into real-time task sequences. If WMS remains in wave mode, WES loses ability to dynamically rebalance.

WES → WCS: Task-level commands (move pallet from A to B) vs equipment-level signals (rotate motor 3 at 45 ft/min). Protocol mismatch or version changes in either system can sever this interface.

LMS → WMS: LMS accuracy depends entirely on WMS task time-stamping quality. Gaps in WMS scanning discipline corrupt the ELS baseline.

---

Common Misconceptions

• “We need a WES.” Most operations with one or two automation zones don’t. WMS + WCS integration is sufficient. WES adds value when 2+ automation types must be coordinated simultaneously.
• “Our ERP has a WMS module — we’re covered.” ERP WMS modules (SAP EWM, Oracle, D365) are adequate for simple to moderate complexity. High-velocity or complex omnichannel operations routinely outgrow them.
• “The vendor said their platform does everything.” Every major vendor claims to cover multiple layers. Probe the integration seams: what happens between their WES and a third-party WCS? What’s the native LMS depth?

---

Selection Sequence

When evaluating warehouse technology:

1. Map current-state flow against the stack — which layers are missing, underperforming, or unintegrated?
2. Define order profile requirements (orders/hr, lines/order, SKU count, channels)
3. Select WMS first (core system of record); then WES if automation complexity warrants it
4. LMS, YMS, OMS selected based on operational pain points
5. Avoid buying a layer you don’t need to eliminate an integration point you’ll create instead