WMS features that matter, grouped by the problem they solve

Read this before the feature list

Every WMS has a long feature page. Most of it is true and most of it will not matter to you. The way to read a feature is to ask what problem it removes from your floor, and whether you have that problem. This guide groups features by problem, and says which are universal, which depend on what you sell, and which are demo furniture.

Features every warehouse needs

A movement ledger. Every receive, putaway, allocation, pick, pack, ship, return, adjustment and count as its own row with type, location, quantity, user, time and reference document. Balances computed from the rows, never typed. This is the feature that makes every other number trustworthy.

Locations and buckets. Stock by bin, and by state: on hand, allocated, received on dock, damaged, quarantined, on order, in transit. A single quantity per SKU hides where the stock is and whether it can be sold.

Available to promise, computed once. Sellable stock minus what earlier orders already own, calculated on the server and read by every screen and every channel. With more than one channel, the ability to hold back a quantity or a percentage per product for wholesale.

Scan-first execution. The scan is the confirmation. Wrong product, wrong bin, wrong quantity are refused by name, on the handheld and on the desktop bench. A prefix never matches.

Directed receiving and putaway. Goods arrive against a purchase order, land in a dock bucket, and become sellable only when put away to a location.

Cycle counting with reasons. A few locations a day, variance lines that cannot be approved without a reason, and an adjustment row on approval.

Store and marketplace integration. Orders in, listings mapped to SKUs with a human approving the match, available to promise out, shipments and tracking back.

Roles and an audit trail. Who can do what, and who did what. This becomes non-negotiable the day a second person has a login.

Features that depend on what you sell

Lots and expiry, with first-expired-first-out. Food, cosmetics, supplements, pharma, anything recalled by batch. Costs discipline at receiving; pays for itself at the first recall.

Case and piece conversions. Products bought by the case and sold by the piece. Demand in pieces should reserve exact pieces; case fallback only when no conversion exists.

Kits and bundles. Selling a pack that is stocked as its parts. The kit is a catalog entity; the components are what the ledger tracks.

Alternate barcodes. Marketplace fulfilment stickers, vendor labels, legacy codes, all resolving to one SKU without renaming it.

Pallets and license plates. Moving a container and letting its contents follow. Matters for bulk storage and inbound containers; irrelevant for a small pick-face-only operation.

Waves and batch picking. Grouping orders for a picker. Matters at volume; adds steps below it.

Replenishment triggers. Minimum and maximum per pick face, with a task when it dips. Matters when bulk and pick face are separate.

Packaging as stock. Boxes and mailers tracked like any other inventory, consumed at pack. Matters when packaging cost is real money.

Carrier labels at the bench. Rate, buy and print without leaving the pack screen.

Returns and channel removals. A return is a document with a disposition; a marketplace removal is booked as its own movement type, not as a customer return.

Multi-client separation. For a 3PL: each client’s stock, orders and users strictly apart, on one platform.

Features that look good in a demo

Forecasting and “AI” replenishment. Useful with two years of clean history. Useless without a ledger, and most buyers do not have one yet.

3D warehouse maps. Pretty. The picker looks at the bin label, not the map.

Real-time dashboards. The ones that get used are the exceptions lists: what is short, what is stale, what is unmapped. The rest are screensavers.

Robotics and automation connectors. Real for a handful of operations. Ask whether a human at a bench with a scanner is the actual plan for the next three years.

Voice picking. Excellent at very high line counts with a stable catalog. Below that, the scanner wins.

How to use this list

Circle the universal features and refuse to compromise on them. Circle the dependent features that match what you sell. Ignore the demo furniture unless a vendor charges for it. Then take the checklist to the trial.

How DockingWare reads against it

DockingWare ships every universal feature above, and the dependent ones for lots and expiry, case conversions, kits, alternate barcodes, pallets, waves, replenishment, packaging as stock, carrier labels, returns and channel removals, and multi-client separation. It does not ship forecasting, 3D maps, robotics connectors or voice picking, and the changelog says when each feature it does ship arrived, by version.