Warehouse and shelf management: WMS basics
Knowing how much stock you hold is one thing; knowing which bin it sits in is another. Here is the addressing, receiving, put-away and picking logic behind WMS.
On a Thursday afternoon you told a customer "we have it," because the system showed forty units. Two people searched the warehouse for forty minutes and came back empty-handed. The next morning, while doing something else, someone found the cartons behind the top shelf. The record was not wrong; the product really was there. The missing piece was knowing where.
This article is about the gap between knowing how much you have and knowing where it sits, and the system that closes it: addressing logic, receiving, put-away and picking strategies, counting discipline. It also covers the minimum setup you can run without software, and the point where a real WMS earns its keep.
What "we have it but we can't find it" really means
In most companies inventory management answers one question: how many units do I have? The person on the warehouse floor asks something else: which zone, which rack, which bin holds this item right now? Quantity is a number; location is an address, and a number without an address is useless.
Without addresses a warehouse runs on human memory. The supervisor with five years on the floor knows everything, and the operation crawls the week he takes leave. Pick time depends on who is looking rather than on what is being picked.
The second cost is quieter: what cannot be found gets bought again. A second batch arrives, the first ages in a corner and leaves as a markdown or as scrap. So "we can't find it" is a cash problem, not a time problem. We covered the quantity side in our piece on inventory management; this one is about location.
What a WMS is, and how it differs from a stock module
A WMS (warehouse management system) brings the physical reality of your building into software. A stock module says "you have 40 units of SKU-4471." A WMS says "24 units in bin A-03-02-1, 16 in bin B-01-05-3." The difference looks small on paper and changes everything on the floor: you stop searching and start walking.
The stock module inside your ERP or CRM holds the commercial truth: receipts, issues, cost, invoices, balances. A WMS holds the physical truth: which pallet sits in which bin and which bins are free. In a healthy setup the two talk to each other, and we walk through that conversation in our guide to ERP-CRM integration.
Most small and mid-sized businesses do not need a separate WMS at first. They need an address field on top of the stock module they already own, and the discipline to fill it every time. WMS is a way of working before it is a software category.
Addressing logic: zone, aisle, rack, bin
Addressing a warehouse works like addressing a city: district, street, building, door number. On the floor that becomes four layers: zone, aisle, rack level and bin. The bin is the smallest physical unit the system recognizes; stock lives in a bin, never merely "in the warehouse."
A zone is a functional slice of the building: receiving, a forward pick area for fast movers, reserve storage, a returns and quarantine corner, shipping. Numbering racks before defining zones is the most common mistake here, because adding a zone later forces a renumbering of everything.
How to code an address
A good address code is fixed length, human-readable and aligned with walking order. A-03-02-1 reads as "zone A, aisle 3, rack level 2, bin 1," and anyone who hears it knows where to go.
Labels belong on the bin itself, at eye level, with a barcode. A bin without a label does not exist as far as the system is concerned, and putting stock there is the same as losing it.
Nothing is ever lost in a warehouse. There are only items whose address was never written down.
Receiving: where the errors get in
Most warehouse errors are born at the dock door. Receiving does three things at once: match the delivery against the purchase order, count and inspect the goods physically, then accept them into the system at a temporary receiving address. When those collapse into "we'll count it later," every shipment turns into the next inventory variance.
Receiving is also the moment for labeling. If the supplier barcode does not scan or does not map to your code, the item gets labeled in receiving, not on the shelf. In food, cosmetics, pharma or spare parts, expiry and batch data go in here too; the setup is in our article on serial number and lot tracking.
The receiving area is a buffer, not storage, and pallets parked there show as available while being impossible to pick. A solid rule: every pallet that enters receiving gets a permanent address before the shift ends.
Put-away: fixed locations or dynamic ones?
Put-away means moving goods from receiving to their permanent address and recording that address. The choice between the two approaches depends on how wide your range is and how full the building runs.
| Criterion | Fixed location | Dynamic location |
|---|---|---|
| Logic | Every SKU owns a specific bin | Goods go to whatever bin is free |
| Strength | Memorable, survives without software | Uses cubic space far more efficiently |
| Weakness | Bins sit empty when the SKU is out | Without a system record, nothing is findable |
| Best fit | Narrow, stable product range | Wide range, seasonal swings, tight space |
Most operations land on a hybrid: fixed forward pick bins for a short list of fast movers, dynamic reserve locations for everything else. Refilling a pick bin from reserve is called replenishment, and it deserves to be scheduled as its own task.
Putting fast movers near the door
Walking distance is the biggest lever in warehouse productivity. A large share of order lines comes from a small share of your SKUs. Placing that short list closest to shipping at an ergonomic height cuts pick time noticeably with no software purchase. To work out which items belong there, use the method in our piece on ABC analysis for inventory prioritization.
That layout is not permanent. Reviewing the slotting plan every quarter keeps the warehouse moving at the same rhythm as sales.
Picking: single, batch and wave
Picking is the largest labor cost in a warehouse, which makes method selection a margin decision. With single order picking one person walks one order from start to finish. With batch picking several orders sharing items are picked in one trip and sorted at the pack bench. With wave picking orders are grouped by carrier cutoff, channel or priority and released in waves.
A rule of thumb: few orders with large baskets favor single picking, many orders with small baskets favor batch, and carrier cutoffs driving the day favor waves. Whatever you choose, sort the pick list by address rather than by product name.
How picking connects to the order side, and which status should change when, is covered in our guide to order management. When sales and the warehouse speak different status languages, the promise made to the customer drifts from what is on the shelf.
Barcodes and handheld scanners
Addressing can run on paper, but it will not last. Every handwritten address is a typo waiting to happen; every scanned barcode is verified data. A handheld tells the picker what to do in order: go to this address, scan this barcode, confirm this quantity.
Barcodes belong on both sides. The product barcode says what it is, the location barcode says where it is, and scanning both makes the movement final. For label design, scanner choice and code standards, our article on barcode inventory management is the right starting point.
Counting discipline and cycle counting
The once-a-year wall-to-wall count satisfies accounting but arrives too late for operations. Errors pile up for twelve months and detonate in a day. Cycle counting inverts that: you count a small slice daily, catching discrepancies while they are small and still explainable.
Build the schedule around movement speed, counting fast movers often and slow movers rarely. Location-based counting works too: walk an aisle end to end and verify bins rather than SKUs. Frequency and method are covered in our guide on how often to run a cycle count.
Never close a variance by adjusting the number. Every gap has a cause: a sloppy receipt, an unrecorded put-away, a return nobody entered. Until the cause is written down, the same variance returns on the next pass.
Starting without a WMS: the minimum setup
What a small warehouse can do on day one is refreshingly simple. Sketch the floor plan, define zones, label racks and bins with fixed-length codes. Add an address field to every product record in the software you already use. Then set one rule: nothing goes on a shelf until its address is recorded.
Add barcodes next, then start cycle counting. Automated alerts when stock drops below a threshold pay off here as well; the setup in our piece on inventory threshold alerts, combined with addressing, starts generating replenishment tasks on its own. Rocketly keeps products, variants, barcodes and stock movements next to customers and orders; the address discipline is yours to build.
When do you actually need a WMS?
The signals are clear enough. One SKU regularly living in several locations. Replenishment and picking constantly waiting on each other. Daily volume beyond what one person can plan by hand. Pick routes that need calculating rather than guessing. Bought before those signals appear, a WMS ends up as a module nobody opens.
Metrics worth tracking, and the usual mistakes
Warehouse order can only be managed once it is measured, and a short list of the right numbers beats a long dashboard:
- Order pick time: The time between releasing a pick order and handing it to packing, the fastest sign a slotting change worked.
- Order accuracy: The share of orders reaching the customer error-free, which alongside return records reveals the items people keep confusing.
- Inventory accuracy: How many counted bins match the system exactly, the cleanest summary of how far your records can be trusted.
- Throughput per square meter: Order lines handled against the space they occupy, the first number to check before leasing a bigger building.
- Unaddressed stock: Items that carry a quantity but no location, a count that pulls every other metric up as it nears zero.
The mistakes repeat too. Numbering racks before defining zones. Treating receiving as storage. Sorting pick lists by product name. Adjusting variances without investigating the cause. Drawing a slotting plan once and never touching it again. None of these are software problems; all of them are rule problems.
A faster warehouse leaves a mark on purchasing and sales as well, and tracking it through inventory turnover and aging analysis is the most honest way to see what your addressing work returned.
If you want products, variants, barcodes and stock movements on the same screen as customers, quotes and orders, you can open a Rocketly account and start on the books and inventory side. Layer address discipline on top, and the warehouse stops being a place you search and becomes a place you walk to.