Skip to content
←Back to Insights
Updated•9 min read

How to select a WMS: criteria, demo and pilot scenario

WMS selection should not start with a long feature checklist. Define the most important operational scenarios and exceptions, then test them end to end in the supplier demo.

Start with processes

Split requirements into day-one essentials, next-year needs and later options. Link each requirement to a business reason such as error prevention, traceability, SLA, productivity or integration.

Do not test only the happy path. Ask to see short receipt, damaged stock, partial pick, cancellation after picking begins and an adjustment audit. Exceptions reveal whether the system will work in a real warehouse.

Criteria worth scoring separately

Use a scoring matrix, but apply pass/fail gates to critical needs. A polished interface cannot compensate for missing traceability or unmanaged integration failure.

  • Process configuration, roles, audit trail and mobile usability.
  • APIs, events, error queues, retries and monitoring.
  • Implementation, migration, training, support and release practices.
  • Total cost: licences, devices, integration, implementation and internal effort.

A practical demo script

Prepare one realistic order: a lot-controlled item in two bins, one damaged unit and an SSCC-labelled pallet requirement. Ask the supplier to show receipt, putaway, allocation, picking, discrepancy, packing, shipping and the final audit record.

Common selection mistakes

Do not rely on “yes, supported”. Record whether a capability is standard, configurable, custom or merely planned. Also size for future channels, clients, sites and exceptions—not only today’s order count.

WMS demo evaluation matrix

Use the same scenario with every supplier. Mark each result as demonstrated, requiring configuration, requiring development or unconfirmed, and record its owner.

WMS demo evaluation matrix
CriterionWhat to testAcceptance evidence
Receiving discrepancyFewer units arrive than expected.Actual quantity, discrepancy and resolution are recorded.
Partial fulfilmentOne order line is unavailable.Only approved quantities ship; the remainder is retained.
Integration failureThe connection fails and a message is retried.No duplicate order; the error and retry are visible.
Implementation scopeSeparate standard functionality from extra work.Written scope, responsibilities and test criteria.

Key terms

TCO
Total cost of ownership over the selected period, not only licence price.
SLA
An agreed service level, such as an order dispatch deadline.
Pilotinis scenarijus
A limited real-process test before full rollout.

Sources and further reading