WMS implementation: a step-by-step plan to go live in 90 days

Phase 1 — Preparation and data quality (weeks 1 to 3)

If the building itself is still in play — a move, an extension, a first purpose-built site — do the demand work before the rollout plan, not alongside it.

And check the power before you check anything else about the site. A grid connection is a multi-year queue rather than a purchase, and a transformer standing on a plot is not proof that capacity comes with it.

This phase makes or breaks the project. Clean your article master data: unique article codes, correct barcodes, dimensions and weights, packaging units and shelf-life or batch requirements. A WMS exposes data errors you have been able to ignore on paper for years.

Fix the location structure at the same time: how do you name aisles, racks, levels and positions? Consistent location coding determines walking routes and therefore your productivity. Print and apply location labels before configuration starts, not after.

Phase 2 — Configuration and integrations (weeks 3 to 7)

Configure the processes from your process inventory: receiving, putaway, replenishment, picking strategies, packing, shipping and returns. Start with the standard flow and add exceptions afterwards — not the other way round.

Set up the connections to ERP, webshop, marketplaces and carriers in parallel. Test every connection on four scenarios: new order, change, cancellation and return. Connections tested only on the happy path break in week one after go-live.

Phase 3 — Testing and training (weeks 7 to 11)

Replay a full production day in the test environment, with real orders from last week and with the people who will be scanning. Measure the same figures as in your baseline, so you know before go-live whether you are improving.

Train per role, not per job title: receiving, picking, packing, returns and supervision. Budget two to four hours per role. Appoint a key user per shift to absorb the first questions, or the project lead spends three weeks on the floor.

Phase 4 — Go-live and aftercare (weeks 11 to 13)

Pick a quiet moment in the week and never just before a peak period. Freeze stock, count the locations you will use, load the count and start. Plan the first three days with extra staffing and the vendor reachable.

Measure your core figures again in week two and week four and compare with the baseline. That is the moment to tune the pick logic — and exactly why configurability without a consultant matters.

The five pitfalls

• Dirty master data. By far the biggest delay. Start here on day one.
• Going live just before peak. Never do it; you lose the learning curve exactly when you cannot afford to.
• No operational staff in the project team. The system gets worked around after go-live.
• Configuring every exception up front. Start standard, refine after two weeks of real data.
• No baseline. Without figures up front you cannot evidence the result and the project drowns in opinions.

What you have to supply

Budget a project lead for two days a week, a key user per shift, someone with ERP knowledge for the connections, and warehouse management availability on the test day. Vendors who say this is unnecessary are simply moving the work to the weeks after go-live.

Still deciding whether you need a system? Read what a WMS system does. Work through the selection checklist first, budget with the cost breakdown, and score vendors with the comparison framework.

Implementation effort differs sharply by vendor model — see BizBloqs vs Boltrics and BizBloqs vs Picqer.