A WMS Won’t Fix Broken Processes

I’ve seen plenty of Warehouse Management System (WMS) projects over the years, and I’ve

also seen far too many of them fail to deliver what was promised. In almost every case, the

problems start well before a system is selected.

The biggest issue I encounter is data accuracy, particularly item master data. If the foundation data is wrong, no WMS in the world is going to fix it. Closely behind that is a poor

understanding of functionality. Many organisations can’t clearly articulate what functions

they actually need to replace or improve their current processes. Without a proper functional breakdown, the system ends up automating bad habits rather than enabling better ones. That’s where failure usually creeps in.

This also explains why so many warehouses install a WMS but never achieve meaningful

labour or cost savings. They don’t manage their processes well to begin with. They lack

visibility over costs and performance indicators, so when the new system goes live, there’s no baseline to measure improvement against. Instead of rethinking how work should flow, the WMS simply becomes a digital wrapper around existing processes. The opportunity for step-change improvement is missed.

When it comes to ROI, the features that genuinely deliver value are usually the unglamorousones: speed and accuracy. A system that prints labels in five seconds instead of 40 might not sound exciting, but over a million labels, that time difference is enormous. System-directed put-away, picking and task allocation also drive real returns, yet many warehouses continue to rely on people-directed decisions, even after investing in advanced software. That’s a common and costly mistake.

From a CFO’s perspective, the warning signs are clear. If labour headcount hasn’t reduced as planned, if peak labour is still excessive, or if transport costs haven’t improved, value is

being eroded. Integration also matters. A WMS should seamlessly connect with your TMS and ERP, automating order processing and reducing manual handling. If manual tasks persist, the system isn’t being fully utilised.

Twelve months after go-live, success should look boring. The system should be stable,

downtime minimal, and people should never be waiting for labels, instructions or system

responses. Most importantly, you should be using what you paid for. If you’re leveraging 90

per cent or more of the available functionality, particularly system-directed tasks, your WMS

is supporting your commercial strategy rather than defining it for you.