Warehouse management systems, explained for people who run one
A buyer's guide to WMS software written by the people who build one: what a WMS is, how it works on the floor, how it differs from an ERP, an OMS and an inventory app, what features matter, and a checklist to run before you sign anything.
Start here
Most guides to warehouse software are written by people who sell it or people who have never packed a box. This one is written by people who build a WMS and run it against a real warehouse every day, so it has opinions, and it says where those opinions come from.
Read in order if you are new to the category. Jump to the comparison pages if you already run an ERP or an order system and are trying to work out what a WMS would add. Finish with the checklist before you talk to any vendor, including us.
The guides
What a WMS is. The plain definition, the one-sentence test for whether you need one, and the three things every WMS must record or it is not one.
How a WMS works. One order, one carton, from the dock to the truck, step by step, and what gets written down at each step.
WMS vs ERP. The ERP owns the books; the WMS owns the floor. Where they meet, and why running a warehouse out of the ERP’s inventory module stops working at the second sales channel.
WMS vs inventory management system. Quantity tracking is not the same as directing work. When a spreadsheet or an inventory app is enough, and the day it stops being enough.
WMS vs OMS. The order system decides what to sell and where to fulfil it; the WMS decides how to get it out of the building. The two are often confused because vendors bundle them.
WMS vs ERP vs OMS. All three side by side, with the one job each one should own and the data each one should never be the source of truth for.
WMS features. The features that matter, grouped by the problem they solve, and the ones that sound impressive in a demo and rarely get used.
WMS checklist. Questions to ask a vendor, questions to ask yourself, and the tests to run on a trial before you decide.
One idea that runs through all of them
A warehouse is a place where physical things move. The only honest record of a warehouse is a record of those movements: what moved, how much, from where to where, who did it, when. Every balance on every screen should be computed from that record, never typed over it. If a system cannot show you the movement that made a number change, it is not telling you what happened in the building. It is telling you what someone entered.
That is the standard these guides hold every system to, including ours.
-
A warehouse management system directs the physical work of a warehouse and keeps the record of it. Here is the definition, the one-sentence test for whether you need one, and the three records a WMS must keep or it is something else.
-
Follow one purchase order and one customer order through a warehouse management system, step by step, and see what gets written down at each step and why the order of the steps is not negotiable.
-
Most businesses run their first warehouse out of the ERP's inventory module. It works until the second sales channel. Here is what each system should own, where they meet, and how to tell when the ERP has stopped being enough.
-
An inventory app tells you how many you have. A WMS tells a person which bin to walk to, refuses the wrong scan, and writes down what happened. Here is when the inventory app is enough, and the day it stops being enough.
-
An order management system decides what to sell, where to fulfil it and how to talk to the customer. A warehouse management system executes inside one building and records every physical step. Vendors bundle them, which is why they get confused.
-
Three systems, three jobs, one rule: each is the source of truth for exactly one thing. A side-by-side of what each should own, what each should never be trusted for, and the smallest stack that works at each stage.
-
A feature list is only useful next to the problem it solves. Here are the warehouse management features that earn their place, the ones that only matter for some operations, and the ones that look good in a demo and rarely get used.
-
Questions for yourself, questions for the vendor, and five tests to run on any trial, ours included. If a system fails the tests, the feature list does not matter.
Related terms
See how DockingWare handles this →
Ready to see it on your floor?
Early access. We onboard a small number of operations at a time.
Start Early Access