WMS features - what a warehouse management system really does

The most common misunderstanding in system selection: "our ERP already has inventory management". It does - but the ERP inventory module answers the question "how much of what do we own and at what value" (the accounting view), while a WMS answers "where exactly is it, who should go get it, by which route and in what order" (the operational view). The ERP sees a stock level of 340 units; the WMS knows 120 sit in location A-03-2, 200 wait in the receiving buffer, and 20 are reserved for an order being picked right now by an operator with a scanner. The two systems do not compete - they cooperate through integration, with the ERP owning documents and values and the WMS owning the physical goods.

Everything that goes wrong at receiving, the warehouse pays back with interest for months. That makes receiving features the foundation:

• Delivery notifications and ASN. The system knows in advance what is coming - from a purchase document in the ERP or an ASN message from the supplier. Receiving turns from "write down whatever arrived" into "tick off differences against the notice".
• Scanner-based receiving with verification. Scan the EAN or the SSCC pallet label, check quantities, get an instant signal on any discrepancy - documented immediately, not discovered at the annual count.
• Batches, expiry dates and serial numbers. Mandatory in food and pharma, useful everywhere - without them neither FEFO nor recall traceability works.
• Labelling at the dock. Goods without a barcode get an internal label right at the gate, because an unlabelled unit on a shelf is a future picking error.
• Quality control holds. A batch held for inspection gets its own status and zone - a held unit must not be reservable for orders.

The heart of a WMS is the warehouse map: zones, racks, levels, bins - every spot with an address and parameters (load capacity, dimensions, accessibility class). On that map run put-away strategies, the rules suggesting where received goods should go: fast movers close to the picking zone, heavy items on lower levels, chemicals away from food. More mature systems also run slotting based on ABC/XYZ analysis - a periodic re-arrangement of the warehouse to keep picking routes as short as possible. Add replenishment handling: an automatic transfer task from reserve to picking locations, triggered before the picking slot runs empty, not after.

The layer nobody sees on the shop floor, and the one everything rests on. Available-to-promise stock (physical minus reservations and holds) computed in real time, reservations placed the moment an order arrives, FIFO/FEFO rotation strategies applied at issue, quality and stock-take holds, batch traceability from supplier to customer. This layer decides whether multi-channel selling works without overselling - sales channels should see available stock from the WMS, not the raw quantity from the ERP.

Picking typically consumes 50-60% of warehouse labour cost, so picking features have the biggest impact on the bottom line. The baseline: pick tasks guided on a terminal with route optimisation (the system dictates the sequence of locations, the operator does not wander), every pick verified by scan, instant feedback on errors. Above that come order grouping strategies - multipicking, batch and zone picking - which with small e-commerce orders can double the orders picked per labour hour. In high-density operations supporting technologies enter the picture, from pick-to-light to voice picking; whether they make sense depends heavily on scale.

The last metres of the process: scan-verifying box contents before sealing (the final chance to catch a mistake), packaging selection, a bench scale, document printing. The key feature here is carrier integration: registering the shipment via API the moment the box closes, a ZPL label straight to the thermal printer, the tracking number returned to the shop automatically, and an end-of-day manifest for the driver. In B2B operations the courier label gives way to the GS1 logistics label with an SSCC code and a document set matching retail-chain requirements.

A WMS turns stock-taking from an annual weekend heroic into a continuous process: cycle counting of locations on a schedule (more often where rotation and value are higher), opportunistic counts when a location hits zero, an immediate recount task after any discrepancy. The result: stock accuracy held at 99%+ all year round instead of a once-a-year cleanup of differences. I compared both approaches in detail in the article on continuous versus annual inventory.

A feature group underrated at purchase and used daily after go-live. Task queuing and prioritisation (an urgent order jumps the queue automatically), work assignment to people and zones, a live view of what is happening on the floor, productivity per operator and per process. Reporting stands on that foundation: from simple daily summaries to the KPIs genuinely worth tracking - order-to-ship time, cost per pick line, stock accuracy. Without WMS data those numbers simply do not exist, and what does not exist cannot be managed.

A stand-alone WMS is half the value. The full value arrives when the system exchanges data with its surroundings: with the ERP (documents, items, business partners), with webshops and marketplaces (orders and stock), with carriers (labels and statuses), with warehouse automation (conveyors, sorters, AMR robots). When comparing systems, the list of ready, maintained integrations means more than many a brochure feature - because any integration "can be built", the only questions being for how much and by when.

For a 2-6 person warehouse moving off Excel or an ERP inventory module, the realistic minimum is: addressed locations, scanner-based receiving and dispatch, stock with reservations, simple pick verification by scan, and one integration - ERP or webshop. That alone cuts shipping errors by an order of magnitude. Put-away strategies, batch picking, labour management, quality control, batch tracking - that is the layer you add when volume grows or your industry demands it. From experience: it is better to go live with the minimum in 6 weeks and grow a working system than to spend a year designing a "complete implementation of everything" that overwhelms the team on day one.

WMS features line up along the process chain: notified receiving, addressed locations, real-time stock with reservations, scan-guided picking, packing with carrier integration, continuous stock-taking, and reporting that turns the shop floor into numbers. When comparing systems, do not ask "do you have feature X" - ask how exactly it works in the process that concerns you, and which integrations are ready versus "on the roadmap".

Weaver WMS covers the whole chain described above - from delivery notifications, through locations with put-away strategies and terminal-guided picking with scan verification, to built-in integrations with ERP systems, webshops and carriers - and implementations start precisely from the operational minimum, extended as needs grow. If you want to check which features make sense at your scale, book a free demo - we will show the system on processes close to yours, not on slides.