WMS requirements built from warehouse risk
Choose WMS features from the work you run
Select features from the operation you need to control. Separate baseline execution, conditional capabilities and specialist optimization so the shortlist reflects your warehouses instead of a generic feature grid.
The App contains fictional warehouse, client, item, receipt, stock, task and dispatch records. Sign in to inspect a view or install a copy with the sample data.
Start with the capabilities most warehouses must prove
| Capability | Question it must answer | Pilot evidence |
|---|---|---|
| Location control | Where is the stock and which states affect availability? | A location record with on-hand, allocated, held and available quantities |
| Inbound execution | What arrived and what still needs a receiving or disposition decision? | Normal, short and damaged receipts with evidence |
| Putaway | Which accepted stock must move to which destination? | Assigned, overdue, blocked and completed tasks |
| Replenishment | Which pick face cannot cover released demand or its control point? | Source, destination, quantity, due time and verified completion |
| Outbound execution | What was requested, picked, packed, staged and handed off? | Short pick and package verification without changing demand silently |
| History and exceptions | Who changed the record and which unresolved work needs intervention? | Traceable status, owner, due date, reason and outcome |
Reviewed September 2026. Treat this as a requirements framework, then adjust it for your warehouse volume, traceability, devices, automation and connected systems.
Add conditional features only when the operation needs them
Lot, serial and expiry
Required when traceability, recall, warranty or shelf life changes stock selection.
Wave or waveless release
Required when cutoff, order mix, congestion and equipment need active orchestration.
Labor management
Required when engineered standards, indirect time and workforce planning are buying drivers.
Yard and dock scheduling
Required when trailer, appointment and door constraints materially affect flow.
Robotics and material handling
Required when the WMS must coordinate automation, not merely exchange completed events.
3PL ownership and billing inputs
Required when client stock, service levels, access and chargeable events differ.
Write the integration contract before naming a connector
Decide where each record is maintained
Name the system that controls items, locations, receipts, demand, warehouse balance and shipment status.
Event contract
Define the business key, payload, timing, ordering, retry and duplicate rule for every exchanged event.
Recovery and reconciliation
Give operators an error queue, safe replay path and comparison that exposes missing or conflicting records.
Configurability test: ask a trained business administrator to add a field, change an exception path, create a role-specific view and update a dashboard. Then confirm permissions, history and integrations still behave correctly.
Questions about WMS features and requirements
Which WMS features are essential?
Essential features depend on the operation, but most warehouses need controlled locations, receiving, putaway, stock status, replenishment, picking, packing, exceptions, mobile execution and history. Lots, serials, waves, labor, automation and yard control are conditional.
Should every warehouse buy advanced wave optimization?
No. Wave and waveless orchestration matter when volume, cutoff, order mix and equipment justify them. A smaller operation may gain more from accurate locations, simple release rules and fast exception recovery.
How do we compare configurability?
Ask a trained business administrator—not a vendor engineer—to add a field, change an exception path, create a role view and update a dashboard in a sandbox. Then test whether the change preserves permissions, history and integrations.
What integration questions belong in WMS requirements?
Define source and target ownership, business keys, event timing, retry behavior, duplicate prevention, error queues and reconciliation. A connector name alone does not prove a reliable operating integration.