WMS & WES REQUIREMENTS AND SELECTION SUPPORT
Define the operating requirement before the vendor demonstration.
A system comparison is only useful when everyone agrees on the work the system must support. WMS and WES selection support turns operating needs into requirements, test scenarios, and a visible basis for evaluating tradeoffs.
Obsidian Axis Group helps warehouse leaders organize the operational side of the decision alongside their technology and procurement teams.
Start with the operation.
How does work enter the building? Who releases it? What makes it executable? How are exceptions handled? Which system owns the transaction or decision at each handoff?
Those questions help separate required capabilities from attractive features that may not address the actual constraint.
What you receive
- An operating requirements register with priorities and ownership.
- A high-level system/interface inventory for the scope.
- Representative workflows and exception scenarios for demonstrations or evaluation.
- A comparison framework with evidence and unresolved questions.
- An implementation-readiness and operating-risk summary where included.
Example evaluation question
Rather than asking whether a system supports exceptions, ask the vendor to demonstrate a defined exception: what the user sees, who can resolve it, what changes in inventory or order status, and how the next process knows the work is ready. Record what was demonstrated and what still needs verification.
What your team provides
Operating requirements, expected growth, the current systems landscape, known constraints, and the stakeholders who own operations, technology, procurement, and implementation decisions.
Scope boundaries
Selection support does not imply software resale, vendor certification, a guaranteed implementation outcome, or authority to sign agreements on your behalf. Technical architecture, licensing review, integration development, and implementation responsibilities are assigned explicitly.
How success is agreed
The team can explain why a capability matters, how each option was evaluated, and which assumptions or risks remain. The selection record is usable by the people responsible for implementation.
Practical questions
Can you help before we have a shortlist?
Yes. Requirements and operating scenarios can be defined before a vendor shortlist exists.
Can you support an evaluation already underway?
Yes. The scope can focus on gaps in the requirements, unclear ownership, or scenarios that have not been tested.
Do you choose the vendor for us?
The client retains the decision. The work provides an organized basis for comparing options and identifying what needs further validation.
Bring the operating questions the demonstrations have not answered.
Related: Choosing a WES field guide · WMS go-live and stabilization support
Service descriptions on this website explain the types of work available. Deliverables, responsibilities, fees, timing, and acceptance criteria are established in the written agreement for each engagement.