What makes a good WMS?

In a nutshell: This article is about how to identify a good Warehouse Management System and why "good" always depends on your own warehouse, your processes and your objectives. You'll get four perspectives to help you evaluate WMS systems effectively: functional scope, technical features and interfaces, flexibility for future requirements, and day-to-day usability. At the end, a short info box summarizes why almost every company today "must", "should" or "wants" to engage with IT in logistics.

This article is an excerpt from our report "State of WxS 2025: Cloud, AI, ROI". You can download the full report here for free. The author of this article is Christina Schühle, Head of Service for Logistics Management Services (LMS) at Miebach.

When our marketing department presented me with a few possible topics and ideas for white papers, this particular topic — this question — caught my eye immediately. And the first thoughts came rushing in: "What does 'good' even mean these days?" Does it mean "upper mid-range"? Or more like "really good = outstanding = excellent"? And how subjective that question really is! What I personally consider good, someone else might well find merely mediocre — or, conversely, outstanding. It's always a matter of perspective, or of one's (logistical) status quo. In short: a fascinating question!

But how do we go about answering this question seriously? In our digital world, the temptation is to consult AI first — and I had that initial impulse too. But then I was struck by moral doubts on one hand, and on the other, my personal ambition awoke: as a long-standing consultant, could I — or shouldn't I — still be a step ahead of AI? After all, I've spent many hours in warehouses conducting process assessments and process design workshops, defined numerous system requirements, and witnessed the implementation of a wide variety of systems up close. Surely that gives me something more to offer than AI. So: let's get started answering this exciting question!

Functional Scope

Warehouse Management Systems (WMS) are not new products. They have existed for decades and have grown accordingly in their functional scope and maturity into highly sophisticated systems. In order to remain competitive and grow revenues, more than a few WMS Vendors have also expanded their breadth, offering additional software products adjacent to WMS. A good WMS is certainly distinguished in part by the wide range of functionalities it makes available.

Nevertheless, it is worth asking yourself: Do I actually need the broadest possible range of functionalities — and am I willing to pay for it accordingly? Or is a more limited functional scope perfectly sufficient for my warehouse operations? On the other hand, you shouldn't cut corners in the wrong places. Instead, ask yourself: Where do I want my warehouse to grow? How might my business environment, my product range, my distribution strategy — and therefore my WMS requirements — change over time? If you plan to ship e-commerce orders from your warehouse in the medium term, or to serve new industries as a logistics service provider, entirely different functional requirements come into play — ones that would be absolutely necessary, not merely "nice to have".

However, comparing WMS systems solely on the basis of a list of available functionalities would be too superficial. Rather than looking at functionality within the system, you should approach it from the process side. And here we enter the perennial conflict: "Do processes follow the system, or does the system adapt to the processes?" If I follow the system standard, I have fewer (or no) customizations — and consequently lower implementation effort — and I don't need to worry about upgrade and release compatibility. On the other hand, adhering to such a standard may require me to bend my processes and prevent me from fully optimizing operations. Over time, productivity losses accumulate.

To bring the thought to a close: a good WMS is distinguished by the fact that its standard configuration already covers the process and IT requirements of warehouse operations very well. And as you'll notice: those requirements are always customer-specific. Which brings us back to the point made earlier — what is "good" for me won't necessarily be equally good for other logistics operations.

"A good WMS is distinguished by the fact that its standard configuration already covers the process and IT requirements of warehouse operations very well."

Technical Features

A good WMS should be built on the latest technical standards. Interface compatibility in particular is becoming a decisive factor. Whereas in the past the focus was primarily on the interface to the upstream ERP system, the system landscape of many companies today is far more complex. Diverse systems are interconnected, data is exchanged, converged, analyzed and, where appropriate, fed back.

Any organization running an older WMS with outdated interface formats will quickly fall behind — or make it harder to implement innovative digital Solutions available on the market. Consider all the automation technologies that exist in warehouse logistics today: every conceivable type of shuttle, container storage system, robot, AMR, AGV, and everything else in between. All excellent Solutions. But they don't just need to drive, store and transport — they also need to be connected and controlled at the software level. It's a problem if outdated compatibility forces you to add complexity to an already complex set of configurations and processes.

Here again, it's worth revisiting the earlier point on functional scope: Have you already factored in all these technologies — and the associated processes and WMS requirements — when assessing the functional scope you need?

When discussing technical characteristics, it's also worth touching on the comparison between on-premise and cloud Solutions. The cloud variant — Software-as-a-Service (SaaS) — can provide additional and/or improved functionalities through new releases. Maintenance and upgrades no longer require dedicated internal IT resources, and scalability