Choose a WMS by proving that it can execute your real workflows and reconcile with the rest of the business. Define the process, then test the software against it.
Define what the warehouse needs to know about inventory
Item and quantity are a starting point. Your operation may also need location, owner, lot, expiry date, inventory status, pallet, or carton detail. Specify what makes inventory available to promise, what keeps it on hold, and who can release it.
Units deserve their own conversation. Selling a SKU by the case is different from knowing that the floor holds cartons packed in tens and twenties. Ask the vendor to demonstrate receiving, opening, moving, and picking those configurations while keeping the total correct. Do not assume a sales unit-of-measure field answers the warehouse question.
Walk the floor before writing the requirements
Follow a receipt from the dock to storage, then follow an order from release through shipping. Note the decisions people make outside the system: where to put an unexpected pallet, how to replenish a pick face, and who decides what happens when stock is missing.
Location naming, slotting, work assignments, and exception handling are implementation decisions. Microsoft’s warehouse documentation, for example, connects location configuration and work rules to receiving, storage, and outbound execution. A platform's feature list is only useful once you know which process those features must support.
Include handheld devices, barcode quality, printers, scales, and Wi-Fi coverage in the evaluation. Test on the equipment and in the areas where people will work.
Use a short set of demanding test scenarios
Accept a short delivery, record damage, and keep held stock unavailable.
Direct stock to a suitable location and refill a pick face before it runs empty.
Handle a short pick, a carton change, and an order that needs more than one package.
Receive a return and verify the inventory and ERP consequences.
For each test, write down the input, expected screen prompts, inventory movement, outbound message, and acceptance criteria. Ask someone who does the job to complete the task. A consultant clicking through a prepared demonstration is not the same as a trained warehouse employee executing it.
Make the ERP connection part of acceptance
Document which system owns item setup, orders, receipts, shipments, adjustments, and returns. Confirm when each event is sent, how it is identified, and what happens when the receiving system rejects it.
Include partial shipments, cancellations, and duplicate messages. A successful API response is not enough: confirm that the correct business transaction exists at the destination and that inventory agrees after the complete workflow.
For a 3PL, extend the tests to inventory ownership, client-specific instructions, access boundaries, and billable activities. Show how a warehouse action becomes a charge that the client can understand and the team can reconcile.
Treat go-live readiness as a separate decision
Agree on opening inventory, location labels, pending orders, and the timing of the last updates from the old system. Assign a person to approve each balance and each critical workflow. Define what work pauses during cutover and how the team will handle a failed test or an unavailable connection.
Your readiness list should include:
- Clean item, location, barcode, and unit data.
- Tested devices, labels, and integrations.
- Role-based training with real warehouse scenarios.
- An agreed inventory and open-order reconciliation.
- Named support coverage and a practical contingency plan.
RefureTech brings WMS selection and implementation together with warehouse process design, training, and integrations. Sometimes the right project is improving the WMS you already have.
Platform documentation referenced
Microsoft: warehouse management processes and configurationUse the linked documentation to check platform-specific behavior. Implementation scope depends on your requirements and configuration.