WMS Implementation Checklist by Phase

A WMS implementation checklist runs in nine phases: set up the project, document how you work, prepare the data, sort hardware and network, configure and connect, test, train, go live, and watch the first weeks. Most WMS projects do not fail on software. They stumble on preparation: item data nobody cleaned, locations nobody labelled, and a go-live date picked before anyone had tested a real order.

This checklist follows the order you will meet things. Tick the boxes in your own copy. Timelines vary a lot by building and system, so we give no durations. Set yours with your vendor and add a margin.

Phase 1. Set up the project

[ ] Name one project owner on your side with authority to make calls
[ ] Name a floor lead who knows how work really gets done, not how the manual says it should
[ ] Agree what "done" means, in writing (for example, "all inbound and outbound running on the new system, old sheets closed")
[ ] Get the vendor's plan with milestones and what they need from you each week
[ ] Decide who is backup for each person, because someone will be away at the worst time
[ ] Pick a go-live window away from your busiest days

Phase 2. Document how you work today

[ ] Write the steps for receiving, putaway, picking, packing, shipping and returns, one page each
[ ] Mark every exception you handle (damaged goods, partial pallets, rush orders, client-specific rules)
[ ] List the reports people rely on and who reads them
[ ] Decide what you will change and what you will keep. Changing the process and the system on the same day doubles the risk

Phase 3. Clean and prepare the data

This is where the schedule slips, so start early.

[ ] Items: one row per item, unique code, description, unit of measure, case and pallet quantities, dimensions and weight where needed
[ ] Locations: a naming scheme (for example aisle, bay, level, position), every location labelled in the building
[ ] Opening stock: a physical count close to go-live, compared to the sheets, differences explained
[ ] Customers or clients, suppliers, carriers: names, addresses, service levels
[ ] Open orders and open purchase orders: decide whether they are finished in the old way or loaded in
[ ] Remove duplicates and retired items instead of carrying them over

Example (hypothetical): a distributor finds the same bolt under three codes. If all three move into the new system, the new system will show three stock levels for one thing. Merge them before loading.

Phase 4. Hardware and network

[ ] Handheld scanners or tablets ordered and confirmed compatible
[ ] Label printers installed, test labels read by the scanners
[ ] Wi-Fi coverage checked in every aisle, the corners and the dock, not only the office
[ ] Spare batteries, chargers and a few spare devices
[ ] Location, pallet and item labels printed and applied

Phase 5. Configure and connect

[ ] Settings match your documented process, with each deviation recorded
[ ] Users and roles set up so people see only what their job needs
[ ] Each integration (accounting, storefront, carrier, EDI) built and tested one by one
[ ] Reports rebuilt or replaced, checked against the old numbers

Phase 6. Test before anyone relies on it

[ ] Test with real scenarios from your own floor: a split receipt, a short pick, a wrong location scan, a return, a rush order
[ ] Run every integration with real examples, including an order that fails
[ ] Have floor staff try it, not only managers. Write down every place they hesitate
[ ] Do a dress rehearsal: a day of parallel orders in test while the old process runs for real
[ ] Agree a list of known issues you can live with on day one, and one you cannot

Phase 7. Train

[ ] Short sessions by role, held on the floor with the real devices
[ ] A one page quick card per task, stuck at the station
[ ] A named super user per shift who can answer questions
[ ] A written plan for what staff do when the system is slow or down, and who they call

Phase 8. Go-live

[ ] Final count and cut-off time for the old system
[ ] Opening stock loaded and checked against the count
[ ] Vendor support and your project owner reachable the whole first day
[ ] A short end-of-day meeting: what broke, what confused people, what to fix tonight
[ ] Decide the rollback trigger in advance, such as "if we cannot ship X by Y, we go back." Most teams never use it, but having it calms the room

Phase 9. The first weeks after

[ ] Count a sample of locations every day and compare to the system
[ ] Review the same issues list each morning until it is short
[ ] Check billing, if you are a 3PL, against your old numbers before sending any invoice
[ ] Ask the floor what slows them down and fix the top three
[ ] Close the old spreadsheets so nobody keeps updating both
[ ] Write the lessons down while they are fresh

Common mistakes

Going live with dirty data. The system is only as right as what you load.

Training managers and skipping the floor. The floor does the scanning.

Treating go-live as the finish line. Stock accuracy usually takes a few weeks of attention to settle.

Not deciding who owns changes. After go-live, everyone will ask for something. Name one person to triage requests and a simple way to submit them.

If you are comparing routes

Subscription software usually comes with a standard implementation path, and a custom build follows your process more closely but needs clear requirements early. Cargohold, which we make, is a one-time custom build, no per-seat, per-truck or per-client fees. Whatever you choose, this checklist applies.

If you are still at the buying stage, write your requirements first and ask each vendor to answer them in the same format.

Questions people ask

What is WMS implementation?

Setting up and starting to use a warehouse management system in your building, from project setup through go-live and the first weeks after.

What are the steps of a WMS implementation?

Project setup, documenting how you work today, data cleanup, hardware and network, configuration and integrations, testing, training, go-live, and the first weeks after.

Why do WMS implementations stumble?

Mostly on preparation rather than software. Item data nobody cleaned, locations nobody labelled and a go-live date picked before anyone tested a real order are the usual causes.

What should I test before WMS go-live?

Real scenarios from your floor, such as a split receipt, a short pick, a wrong location scan, a return and a rush order. Also run every integration with real examples, including an order that fails.

Who should be trained on a new WMS?

The floor staff who do the scanning, not only managers. Hold short sessions by role on the real devices and name a super user for each shift.

What mistakes should I avoid in a WMS rollout?

Going live with dirty data, training managers but skipping the floor, treating go-live as the finish line, and not deciding who owns change requests afterwards.