How to choose a WMS for a UK wholesale operation
Start with the transactions your team struggles to finish, not a list of software acronyms. A stock total can look correct while the wrong pallet is picked, a customer receives the wrong price or an invoice needs re-keying. Evaluate a warehouse management system by following one ordinary order and one exception all the way through your business.
A connected operational flow
Workflow illustration—not a customer screenshot or live performance data.
- 01
Map
List the work, handovers and exceptions.
- 02
Demonstrate
Use a representative product and customer order.
- 03
Prove
Check evidence, permissions and documents.
- 04
Plan
Agree migration, training and acceptance checks.
Ask where the stock figure comes from
Ask the demonstrator to receive a purchase order into a named location, label a pallet and allocate part of it to an order. Then move the balance and inspect the history. You should be able to distinguish physical stock, stock available to promise and stock already allocated. For dated products, repeat the exercise with a short-dated batch and a held batch.
- Warehouse, bin and pallet identifiers
- Pack sizes and unit conversions
- Batch, expiry and held-stock rules
Test a sale that does not go perfectly
Use a customer-specific price, a shortage and a later delivery. Follow the warehouse pick into a vehicle load and delivery note, then record a return and credit. This exposes handovers that a polished dashboard alone will not show. Cash-and-carry, customer portals, rebates and multi-site stock should be demonstrated if they are part of your operation, not assumed from a generic feature list.
- Who can change prices or approve an exception?
- How are outstanding quantities handled?
- Can customer service trace the delivered goods?
Agree the complete implementation boundary
A WMS project includes data quality, label printers, scanner connectivity, accounts mapping and staff practice. Ask for a written scope separating standard configuration, optional modules and tailored development. Agree who owns each data source and what constitutes acceptance. Compare the whole scope and ongoing support arrangements rather than a licence price in isolation.
- Named accounting product and supported version
- Migration rehearsal and opening stock reconciliation
- Hardware tests, training and cutover responsibilities
Your practical checklist
- Bring an example purchase order, customer order and return.
- Use your own label formats and unit-of-measure rules.
- Ask for a demonstration of a failure or exception, not only the happy path.
- Agree deliverables, commercial terms and support arrangements in writing.