Warehouse Operations: Receiving, Putaway and Picking Done Right
Most picking errors are created at the receiving dock, days earlier. A practical look at the three core warehouse processes and the simple rules that keep stock where the system says it is.

When a customer receives the wrong item, the blame usually lands on the picker. In most warehouses the error started days earlier, at the receiving dock, when a pallet was accepted without a proper count or put on whichever shelf had space. Picking is where the problem shows up. Receiving and putaway are where it is made.
Below are the three core processes of warehouse operations, in the order stock moves through them, with the rules that matter in each and the failures most common in mid-sized distribution and manufacturing sites.
Receiving: the only moment you can catch a supplier’s mistake cheaply
Once goods are on the shelf and the supplier invoice is posted, a shortage costs a phone call, a credit note request and often an argument. At the dock it costs a signature. Receiving deserves your most careful staff, not your newest.
A sound receiving process has a few non-negotiable steps:
- Receive against a purchase order (PO). If there is no PO in the system, the goods wait in a marked quarantine area until purchasing confirms. Accepting “we will create the PO later” is how phantom stock is born.
- Count blind where you can. The receiver records what arrived without seeing the expected quantity. It takes slightly longer and catches far more discrepancies than ticking off a printed list.
- Check what matters for the product. Batch and expiry for food and pharmaceuticals, serial numbers for electronics, visible damage for everything. Record it at the dock, not later from memory.
- Post the receipt the same day. Goods that are physically present but not in the system will be sold twice or not at all.
Discrepancies should go into a short log with the PO number, the item, expected and received quantities and a photo when relevant. Purchasing owns the follow-up with the supplier. The warehouse owns recording it accurately.
Putaway: deciding where stock lives
Putaway is where many warehouses lose control quietly. Staff under pressure put pallets wherever there is room and plan to “sort it out on Friday.” By Friday there is a new delivery.
The fix starts with location discipline. Every storage position needs a label and a code, and the system needs to know which item is in which location. Some warehouses use fixed locations, where each item always lives in the same slot. Others use random or dynamic locations, where any free slot can be used as long as the system records it. Fixed locations are easier to run manually. Dynamic locations use space better but only work if every move is scanned or entered.
Slotting, deciding which item sits in which location, is the second lever. Fast-moving items belong close to the packing area at waist height. Slow movers and bulk reserve stock can sit higher or further away. Review the slotting every few months using picking frequency, not sales value, since a cheap item picked 200 times a week deserves the best slot more than an expensive one picked twice.
Picking: speed comes from layout and sequence
In most warehouses picking takes more labour time than any other activity, and much of that time is spent walking. The gains come from reducing travel and removing decisions, not from asking people to move faster.
Three methods cover most situations. Order picking, one order at a time, is simple and suits small volumes or large orders. Batch picking, collecting the same item for several orders in one trip and then sorting, suits many small orders with overlapping items. Zone picking, where each picker covers one area and orders pass between zones, suits larger warehouses with distinct product areas.
Whatever the method, the pick list should be sorted in walking sequence by location, not by item code or the order the customer typed it. That single change often makes a visible difference within a week. Add a check step before dispatch, either a scan against the order or a second person on high-value orders, and record who picked and who checked.
An illustrative scenario: a consumer goods distributor in Zarqa
Take a distributor with a 3,000 square metre warehouse, around 1,800 active items and a small team running two shifts. Customers complain about short and wrong deliveries every week, and the monthly stock count never matches the ERP (enterprise resource planning system). Management is looking at warehouse management software.
A week spent watching the floor shows that receiving is done by whoever is free, often a driver, against the supplier’s delivery note rather than the PO. About a third of locations have no label. Pick lists print in item code order, so pickers cross the warehouse several times per order and skip items they cannot find, intending to come back.
The improvement plan is mostly process. Two trained receivers per shift, blind counts against POs, and same-day posting. A weekend to label every location and record each item’s location in the ERP. Pick lists sorted by location. A daily cycle count of 40 locations, chosen by the system, with differences investigated the same day.
After a couple of months the team can see whether errors and count differences are falling. Only then does the software question make sense, and the requirements are now clear: barcode scanning, dynamic locations and batch picking, because the basics are already in place.
Measuring a warehouse without drowning in metrics
A handful of measures tells you whether the three processes are healthy:
| Process | Measure | What it tells you |
|---|---|---|
| Receiving | Dock-to-stock time | How long goods sit before they can be sold |
| Receiving | Supplier discrepancies logged | Whether counting is happening at all |
| Putaway | Location accuracy from cycle counts | Whether the system knows where stock is |
| Picking | Order lines picked correctly | Customer-facing quality |
| Picking | Orders dispatched on the promised day | Whether the warehouse keeps pace with sales |
Review these weekly with the warehouse supervisor. A sudden drop in supplier discrepancies is not always good news. It can mean receivers have stopped counting.
Getting the warehouse right before the software
Warehouse software amplifies whatever process it is given. Before you look at software, run one test: pick 20 locations at random tomorrow morning and check whether the shelf matches the system. The mismatches tell you which of the three processes to fix first, and later what the software must do. Our Operations Transformation work starts there: observing the floor, redesigning the flow and setting clear ownership, so that the technology that follows has something solid to build on.



