What won't a WMS fix?

Everything it inherits. A warehouse management system directs work and records what happened. It does not repair the material it's handed — item dimensions nobody ever verified, unit-of-measure conversions that have been quietly wrong for years, an ERP nobody configured past go-live, the receiving exception one supervisor carries in their head. All of it crosses into the new system intact. What changes is that it becomes encoded, and the cost of correcting it goes up the day a system starts depending on it.

These are hard to see during a selection for a specific reason, and it isn't carelessness. A selection is a comparison. It's built to surface differences between options and it's good at that. But bad item data is bad under every system on the shortlist. An unconfigured ERP is unconfigured regardless of which vendor wins. Anything that holds constant across all the options isn't a difference, so a process designed to find differences never returns it. The problems that survive the decision are invisible to the process that makes the decision.

Nobody in the room raises them either. A vendor has no particular reason to: none of it differentiates the product, and introducing it adds friction to a sale. That's strategic omission rather than dishonesty — the information left out is the information nobody was going to ask for. And the buyer doesn't raise it because the buyer is, correctly, in comparison mode. Everyone is answering the question that was actually asked.

The categories are learnable in the abstract. Anyone can read that master data, process documentation, and system configuration matter, and that reading is accurate as far as it goes. What can't be done from a reading list is scoring a specific operation against them, because the gaps that matter most are the ones normalization has already absorbed. That's a proximity gap rather than a knowledge gap, and it's why a real readiness picture comes from someone walking the floor instead of from a self-assessment.

For plenty of operations that list turns out to be short, and the honest read is to go buy something. When it's long, it's worth treating as information rather than as discouragement. Nobody hands an operation a verdict on whether it's too early to buy. The length of the list is the verdict, and it only becomes legible once somebody writes it down — which is also the difference between deciding to wait and drifting into a purchase that was never going to land.

The shortlist decides which system you run. It doesn't decide what that system will be running on.