Part 4 of our series on making stock takes quicker and more accurate
Your system says you have zero units of part number 5447.
You need five for tomorrow's production run.
So you order more. Expedite them. Pay extra for overnight freight.
Then three weeks later, someone finds twelve units of 5447 sitting on a pallet in the returns area.
The inventory wasn't missing. It was just somewhere else.
This is the secret that every warehouse manager knows but rarely admits: most inventory variances aren't about theft or miscounts or data entry errors.
They're about geography.
The goods are exactly where someone put them. Just not where the system thinks they are.
Your warehouse management system has a beautiful map of where everything lives.
Aisle three, bay four, level two. Every item has an address.
But your warehouse has a second, invisible map. The map of where things actually end up.
The staging area where someone set down a box during a phone call.
The returns corner where customer rejections wait for credit approval.
The quarantine zone where suspect material sits pending quality review.
The floor next to the dock door where inbound freight gets unloaded but not yet received.
The problem isn't that these places exist. The problem is that your counting process pretends they don't.
You count the bins. You check the racks. You verify the assigned locations.
And you completely miss the twenty percent of your inventory that's wandering around homeless.
Before you can sweep for misplaced stock, you need to know where to sweep.
Walk your facility with fresh eyes. Not the eyes of someone who works there every day and has learned not to see the clutter.
Where do things accumulate?
Every warehouse has hot spots. Places where inventory naturally drifts. Your job is to make them visible and official.
Workflow: A metal fabrication shop creates a formal map of their "non-standard zones." They identify seven areas: customer returns holding, quality hold, scrap pending disposal, finished goods awaiting shipment, receiving staging, maintenance parts temporary storage, and the area near the saw where offcuts pile up. They give each zone a formal name and location code in their system. Now when they do cycle counts, these zones are on the checklist.
Example: A plumbing supply distributor notices that returned goods from customers often sit in receiving for days before getting processed back into stock. They create a designated "returns pending" area with tape marking the boundaries on the floor. They assign it location code RTN-01 in their WMS. Now when someone counts pipe fittings and finds a variance, the first place they check is RTN-01. They find the missing inventory seventy percent of the time.
You can't manage what you don't acknowledge exists.
Most cycle counting programs work like this: check the location, compare to the system, record the variance, move on.
That's half a process.
A complete process includes the sweep. When you find a variance, you don't just record it. You go looking.
Check the adjacent bins first. Then the floor below the rack. Then the designated sweep zones.
This isn't extra work. This is the actual work.
Workflow: An electronics distributor revises their cycle count procedure to include a mandatory sweep step for any variance over five units. The counter checks the assigned location first. If there's a discrepancy, they immediately check: both adjacent bins, the aisle floor, the returns area, quality hold, and receiving. Only after checking all six places do they record the variance as confirmed. Their "found during sweep" rate is forty-three percent.
Example: A pharmaceutical wholesaler programs their RF scanners to prompt sweep locations automatically. When a counter enters a quantity that differs from the system, the scanner displays: "Check adjacent bins? Check floor? Check QC hold? Check returns?" The counter has to answer yes or no to each prompt before they can move to the next item. This forces the discipline of looking before assuming the stock is truly missing.
Finding beats assuming every single time.
Your business is unique — your software should be too. Let's talk about a system built around how you actually work.
Get a free quoteSomeone picks from bin A-03-12.
They grab the last box. But they're in a hurry, and there's another box that looks similar in bin A-03-13.
So they grab it.
Now the system thinks A-03-13 has four boxes when it actually has three. And it thinks A-03-12 is empty when there's nothing wrong with that count.
The inventory is fine. The locations are confused.
This happens constantly. Which is why checking adjacent locations isn't optional.
Workflow: A fastener distributor teaches their counters the "three bin rule." When counting any location, always verify the bin immediately to the left and immediately to the right. If you find unexpected inventory in either adjacent bin, check if it belongs in the bin you're counting. If the SKUs match, investigate why it migrated. This simple rule catches about thirty percent of their location variances before they become permanent.
Example: An industrial supply warehouse uses vertical racks with five levels. They discover that items fall from upper levels to lower levels more often than anyone realized. They add a specific step to their count process: when counting any level two through five, check the level directly below for orphaned units. They mark found items with a red tag and have a supervisor relocate them properly at the end of each shift.
Gravity and hurry are more powerful than your WMS.
Inventory in motion is inventory that's invisible.
It's not in the source location anymore. It's not in the destination location yet.
It's on a cart. Or a pallet jack. Or sitting on the staging table.
Your system thinks it's in one place. Reality disagrees.
The answer isn't to eliminate transit. The answer is to make transit visible and bounded.
Workflow: A food ingredients distributor establishes three official transit zones: pick staging (where picked orders wait for packing), inbound staging (where received goods wait for putaway), and transfer staging (where inventory moving between buildings waits for transport). Each zone has painted floor markings and a maximum dwell time. Nothing can sit in pick staging for more than two hours. Nothing in inbound staging for more than four hours. These zones are checked every cycle count, and anything found there gets traced back to why it's stuck.
Example: A machinery parts warehouse has a chronic problem with items "lost" during picking. They create a designated staging area between the pick racks and the packing stations. They paint the floor yellow and label it "PICK STAGING." They add a rule: if you pick something but get interrupted before packing it, it goes in pick staging with a note showing the order number. Now when a part shows a variance, the first place they check is pick staging. They find items there daily, usually because someone got called away to help with a forklift issue or answer a customer call.
In-transit isn't an excuse. It's a category that needs management.
Customer returns are where inventory goes to become invisible.
Same with quality holds. And warranty returns. And damaged goods awaiting disposal decisions.
These items exist physically. But the system is confused about their status. Are they available? Are they quarantined? Are they waiting for credit?
So they sit in limbo. And your counts miss them.
Workflow: A beverage distributor creates a formal returns processing procedure with hard time limits. When a customer returns product, it gets scanned into location RTN-PROC immediately, which flags it in the system as "return pending inspection." Quality has forty-eight hours to evaluate it. If it's good, it gets scanned back into regular stock. If it's bad, it gets scanned to location DMG-HOLD for disposal. Nothing sits in an undefined state for more than two days. When they do cycle counts, both RTN-PROC and DMG-HOLD are checked for each item being counted.
Example: A hydraulics manufacturer has a quality hold area for parts that failed inspection. The problem was that items would sit there for weeks while engineering decided whether they could be reworked or needed to be scrapped. Meanwhile, the system showed them as available inventory. They solved it by creating a "QC-HOLD" location in their ERP. When a part goes to quality hold, it gets transacted to QC-HOLD, which removes it from available inventory but keeps it in total inventory. Now cycle counts include QC-HOLD as a standard check location. The parts are still there, but the system knows where.
Limbo is a location. Treat it like one.
Your warehouse team walks past misplaced inventory every day.
The box sitting on top of a rack that's too tall for the space.
The pallet in the aisle that everyone walks around.
The bin with two different SKUs mixed together.
They see it. But they don't see it as their problem.
Because nobody told them to look.
Workflow: A chemical distributor creates an "orphan alert" system. Any warehouse employee who spots inventory in a location that seems wrong can scan it and press a button labeled "orphan." This creates a work order for a supervisor to investigate and relocate the item properly. They track orphan alerts as a metric and recognize the employee who finds the most each month. What was invisible becomes a game worth playing.
Example: A building materials supplier trains their forklift operators to do a daily visual sweep of the aisles during their first route of the day. If they see anything on the floor, leaning against a rack, or otherwise not in a proper location, they radio it in. A dedicated "orphan wrangler" (they actually call the person this) spends the first hour of every shift relocating misplaced items based on the morning reports. It takes one hour of labor per day and eliminates about fifteen percent of their cycle count variances.
Everyone on your team has eyes. Teach them what to look for.
If you find the same items in the same wrong places month after month, you don't have a location problem.
You have a process problem.
The sweep finds the symptoms. Your job is to cure the disease.
Workflow: An automotive parts distributor keeps a log of every item found during location sweeps. They track: what was found, where it was found, where it should have been, and when it was last transacted. Once a quarter, they analyze the log for patterns. They discover that seventy percent of misplaced items in the returns area are from orders picked in the last two hours of the shift. Investigation reveals that night shift is rushing and not processing returns before they leave. They adjust staffing and add a handoff checklist. Misplaced returns drop by sixty percent.
Example: A electrical supply warehouse notices that certain high velocity items keep showing up in adjacent bins. They realize it's because pickers work fast and sometimes grab from the wrong bin when theirs is empty. The WMS doesn't flag the error because the adjacent bin shows inventory. They solve it by physically separating high velocity items with empty bins or different product families. If bearing SKU 4471 is in bin A-12-04, they leave A-12-05 empty or put a completely different product there. Wrong bin picks drop by eighty-five percent.
The sweep shows you where things are. The analysis shows you why they got there.
Counting is easy.
Looking is hard.
Counting means going to the location on the list and verifying what's there.
Looking means checking the locations that aren't on the list.
Looking means getting on your hands and knees to check if something fell off the rack.
Looking means walking to the returns area even though your count sheet doesn't say to.
Looking means checking the staging area even though it's "not your job."
Most inventory variance isn't variance at all.
It's just stuff in places you didn't think to look.
The metal plate isn't missing from your system because someone stole it or because the data entry was wrong.
It's sitting three bins over where someone set it down in a hurry.
Or it's in the quality hold area waiting for engineering approval.
Or it's on a cart in the staging zone that got pushed into a corner.
Your inventory is there.
You're just not looking there.
Start looking.
Your business is unique, but your software is off the shelf? Ditch the workarounds and let's build your ERP systems to fit your teams.