10 signs your warehouse is working around D365
Many warehouses go live on D365 and keep the setup from the first hectic weeks. Two years later the system runs, but the people run around it. These are the signs, and what is usually behind them.
1. There is paper next to the scanners
A printed pick list, a whiteboard with today's priorities, a list of "special" customers taped to the wall. Each one is information the mobile device does not give. Usually the work template or the mobile device menu does not show what the worker needs: the order, the customer, the remark, the next stop.
2. Extra scans that nobody can explain
"We scan the location twice, that's how it is." Extra confirmation steps were often added at go-live to be safe and never removed. Every unnecessary scan, times every pick, every day, is real time. Review the mobile device menu items and their confirmation settings against what the floor actually needs.
3. Stock is moved by hand every day
If the same kind of manual movement happens daily, D365 keeps putting stock in the wrong place. The put-away location directives no longer match the warehouse: new zones, new products, a changed layout, and directives from the original design.
4. Pickers override the proposed location
When workers routinely pick from somewhere else than the location on the scanner, they know something the system does not: the proposed location is hard to reach, empty in reality, or reserved for another flow. Look at the pick location directives and at whether on-hand matches the shelf.
5. Replenishment happens by shouting
"Can someone bring down a pallet of A-200?" means replenishment lives outside D365. Min/max replenishment for the pick faces, and wave demand replenishment for what min/max does not cover, can take this over, if the locations and stocking limits are set up for it.
6. One person releases the waves, and only they know how
A morning routine of manual steps that one key user knows by heart is a risk on their day off. Wave templates can create, process and release waves automatically, with thresholds and timing, so the routine becomes setup instead of knowledge.
7. The same corrections every week
Counting adjustments on the same items or locations, or negative stock that keeps coming back, point to a process gap, not to careless counting: a flow that is posted in the wrong order, a unit conversion, a location that is used without being registered.
8. The day is planned in Excel
A daily export of open orders, shipments or work, reworked in a spreadsheet to decide what to do first. The warehouse needs a view D365 is not giving them, and the workbenches, work lists or wave priorities could, once they are set up for it.
9. Work is cancelled and created again
Cancelling and recreating work to get a different location, a different split or a different worker is a workaround for a work template or directive that does not fit. Frequent cancelled work in the work history is easy to measure and a good starting point.
10. "We don't use that, it didn't work at go-live"
Cluster picking, containerization, cycle counting, mobile device flows for returns: features switched off in the go-live rush and never revisited. What did not work then, under time pressure and with test data, often works now, and D365 has had many updates since.
What to do with this list
Count how many of the ten you recognise. One or two are normal. Five or more means the warehouse is paying every day for setup that no longer fits. The fixes are rarely large: most are directives, templates and menu items, not development.
Two related guides: Why is no work created for my wave in D365? and Why won’t my sales order release to the warehouse?
Menu names and behaviour can differ between D365 versions and your own setup. Check in your environment before you act.