Writing on warehouse operations
These are not product brochures. Each article takes a problem that actually happens in a warehouse: why it appears, what it costs, and what has to change to close it.
AI in the warehouse: entering transactions by voice and barcode with your hands full
Where AI helps in a warehouse is not chat but the moment of recording. Scanning the item and saying "3 cases to A-12" should be enough, while the final word always stays with a person.
Read the articleA warehouse manager's morning: an exception list, not a report
A manager should start the day not with "what happened?" but with "what is broken and what do I do?". Management by exception makes that possible: only the deviation shows, with its fix next to it.
Read the articleWriting safely from the warehouse to Logo: preview, approval, read-back
Writing from a warehouse app to the ERP is easy; the hard part is never writing the same document twice when the connection drops, and knowing that what was written really was written.
Read the articleDirected work and task interleaving: cutting empty walks in the warehouse
An operator should not have to ask "what now?"; the system should say. Directed work takes jobs off the paper list into an ordered queue, and task interleaving keeps the walk back from being empty.
Read the articleWave, batch and cluster picking: when does each one help?
As order volume grows, picking one order at a time means walking the same aisle again and again. Wave planning groups orders; batch and cluster picking collect the group in one tour.
Read the articleReplenishing the pick face before it runs dry: minimum, maximum and FEFO
When a picker reaches an empty pick face the loss is not just that order; the trip to reserve stock, the wait and the broken tour all cost. Replenishment should trigger before the face is empty.
Read the articleLot recall: being ready for "who received this batch?"
The hard part of a recall is not the decision but producing the list. When where a lot came from, where it is and who received it are recorded inside the operation, the list is queried, not searched for.
Read the articleInternal requests: from a verbal ask to an approved, fulfilled record
If "we need two cases of this on the line" never becomes a record, nobody knows who asked, who approved or how much was sent. Request, approval and fulfilment are links in one chain.
Read the articleWarehouse memory: floor knowledge should not live in one person's head
"This supplier's carton holds 10, not 12" is useful to everyone in the warehouse, yet usually only one person knows it. When that person is on leave, so is the knowledge.
Read the articleBefore moving to a WMS: is your Logo stock data ready?
A warehouse management system does not fix bad data; it speeds it up. Negative stock, stock without a shelf and items without barcodes come back as floor errors from day one. Look at the data first.
Read the articleWhy doesn't the stock in your ERP match the shelf?
A stock discrepancy is rarely the ERP's fault. The problem is the gap between the moment goods move and the moment that movement is recorded. We explain where that gap comes from and why counting does not close it.
Read the articleWhat changes in your warehouse when goods are nationalised?
Bonded goods and goods in free circulation can sit on the same shelf without being the same thing. If the moment of nationalisation is not recorded on the warehouse side, your stock can look numerically correct while being legally wrong.
Read the articleChest, wardrobe, headboard: three products or one bedroom set?
Products sold as sets sit in stock as components but ship as a set. If that conversion is not recorded, your sellable stock looks different from what it actually is.
Read the articleThere's a count variance: is it an error or is it waste?
If waste and consumption are not recorded as they happen, a count variance can never be explained. And a variance nobody can explain is a variance nobody can fix.
Read the article