Launching soon: book a free 30-min call Launching soon: D365 WMS services are coming to APAC. The free 30-minute discovery call is bookable now, and you can generate an instant Accelerated WMS proposal.
Skip to content
Book a free 30-min call

Article

Five signs your D365 WMS isn't ready for go-live

The warning signs we see most often in the weeks before a Dynamics 365 warehouse go-live, and what to do about each one while there is still time.

Vidda3651 min read

Sample content. This is a placeholder post to preview the layout. It is not indexed by search engines.

Sample post: placeholder text to preview the layout. Replace it with your own article.

Most warehouse go-lives that struggle don't fail on the day. The warning signs show up weeks earlier, in test results, in data loads, and in how confident the floor team feels with a scanner in their hand.

An independent health check looks for exactly these problems: it traces each slowdown on the floor back to the configuration behind it.

Dock to ship4.5 h29% shorter
Illustrative example
Animation of a WMS health check on an illustrative example warehouse. Inbound (receive and put away, dock-to-stock 1.2 hours) and outbound (pick, pack and ship, order cycle 3.3 hours) run as two groups, with replenishment feeding pick from below; late replenishment adds 30 minutes of waiting to picking. An audit flags four configuration areas: location directives, replenishment templates, wave templates and container build. Fixing replenishment recovers the 30 minutes on pick, and once all four are fixed dock-to-stock falls to 1.0 hours, the order cycle to 2.2 hours, and dock-to-ship from 4.5 to 3.2 hours, 29% shorter.

1. Location data is still "nearly done"

Every pick, put-away and count in D365 Warehouse Management depends on locations, location profiles and fixed locations being right. If the location load is still changing in the last weeks, every test run before that point tested something slightly different.

What to do: freeze the location structure, load it into the test environment, and rerun the end-to-end scenarios against the frozen data.

2. Work templates were tested one at a time

Work templates and location directives interact. A template that works alone can be overridden by a more specific one, or never reached because a directive query is too broad.

  • Test full flows (receive → put away → pick → pack → ship), not single steps.
  • Include the awkward cases: partial pallets, short picks, mixed batches.

3. Nobody on the floor has used the mobile app with real labels

If the first time a picker scans a real licence plate label is go-live morning, go-live morning becomes the test.

4. Exceptions have no owner

Short picks, damaged stock and blocked locations happen on day one. Decide who resolves each one in D365, and how, before you go live.

5. Rollback isn't written down

A rollback plan you never use is still worth having. Write it down, agree the decision point, and name who makes the call.

More insights

All insights