Inventory
The real reason your stock count never comes out right (hint: it isn’t your warehouse staff) — and the one thing to look at on your last count that tells you which problem you’ve actually got
The customer rang about the order that shipped short.
You didn’t send anybody out to check it. You went yourself, which should have told you something — the screen said eleven, and you have been doing this long enough to know what eleven of them looks like sitting on a shelf.
There were four.
And you stood there slightly longer than you needed to, because the arithmetic was not the problem. The problem was the sentence that arrived while you were looking at the gap.
Your name is on the front of this building, and you cannot tell anybody what is inside it.
Then you did what almost everybody does next. You went and found your warehouse manager.
It is never just the one order
That one you could live with. The customer was decent about it, which was somehow worse, and you sent the balance on Thursday and knocked the freight off.
But it is not one order, and you know it is not, because you have been keeping a private tally for a while now.
There is the pallet you bought in March that you already owned — two rows over, under a dust sheet, behind the thing nobody has moved since the extension went in. There is the item you are apparently out of on the screen, which your foreman can walk to blindfolded. There is the run you couldn’t quote on because you weren’t confident enough in your own numbers to promise a date, so you let it go and told yourself it was a thin margin anyway.
And there is the money. Not a figure you’ve ever written down, because writing it down would make it real — but you know roughly what is standing in that building doing nothing, and you know that a good chunk of it was bought twice.
Then there is the count itself. A Saturday. Four people, one of them you. Somebody brings pizza at two. And at the end of it the sheet and the system disagree by an amount that is too big to write off and too small for anybody to find, and the fix goes in as an adjustment with a note that says count.
Which brings us to the part that actually bothers you, and the reason you are still reading an article about stock counts.
You have now had the same conversation with your warehouse manager four times. He is not lying to you. You have known him for years, you have watched him work, and you would trust him with the keys and the float. He is not lying, and the numbers are still wrong, and those two things are not supposed to both be true.
If you want to skip the article and go straight to the nine checks that separate the two problems, they’re here and they’re free.
Open the nine checks →No card. Nothing to book. They open on the next screen.
You have already tried the sensible things, and that is the confusing part
Run through what you’ve done, because I suspect it’s most of this list.
- You started counting more often. Cycle counts instead of the annual bloodbath. The variance got smaller for about six weeks, which felt like proof, and then it drifted back.
- You tightened receiving. Genuinely a good move. Goods get booked in the same day now, mostly. It helped. It did not close the gap.
- You had the conversation. Then you had it again. Then a third time, more directly than you wanted to, and each time things were better for a fortnight.
- You hired somebody to own inventory. And now you employ a person whose actual job, when you describe it honestly, is reconciling two numbers that will not agree. You did not fix the disagreement. You staffed it.
- You bought the scanners. Or the app, or the add-on. The wrong number now arrives considerably faster.
Every single item on that list is the correct response to a discipline problem. Not one of them is stupid. If a business has sloppy handling, that is exactly the sequence a competent owner runs, and it works.
Which ought to tell you something, if you’re in the mood to hear it. If the correct treatment for a discipline problem doesn’t work, the odds are you haven’t got a discipline problem.
Two completely different problems that look identical from where you stand
Every inventory discrepancy in the world is one of two things, and they present exactly the same way — a number on a screen that does not match a number on a shelf.
Problem one — process
The system could have recorded what happened. Somebody didn’t, or did it late, or did it in the wrong place. There was a field for the truth and the truth didn’t get typed into it. This is a real problem, it is common, and discipline genuinely fixes it. More counting works. Tighter receiving works.
Problem two — structural
The system could not have recorded what happened. There is no field for it. No movement type, no second location, no way to express the thing that actually occurred on the floor. Nobody was careless. The information turned up and had nowhere to go, so it went into somebody’s head, or a spreadsheet, or nowhere at all.
Discipline fixes the first one. Discipline cannot touch the second one, because there is nothing there for anybody to be disciplined about. You can hold a meeting about it every Monday for a year and the number will keep coming out wrong, and the only thing you will actually achieve is making a good employee feel accused.
Here is how invisible the second kind can be.
Your system tells you what is on the shelf. It is right. It has been right all week. What it does not tell you — because there is nowhere in it to hold the thought — is how much of that shelf is already promised to orders you have taken and not yet picked. So your salesperson opens the screen, sees eleven, and sells eleven.
Nobody miscounted. The eleven were genuinely there. Four of them had already been sold to somebody else that morning, and your system had no way to mention it.
The part almost nobody runs
The thing to look at on a stock count is not how big the variance is
When a count comes back, everybody in the room asks the same question, and they ask it first. How bad is it?
That is the question your accountant needs answered, and it is the number that goes in the file, so it is entirely reasonable that it is the one everybody reaches for.
It is also close to useless. The size of a variance tells you how much. It does not tell you why — and why is the only thing that decides what you do about it on Monday morning.
The question worth asking is where did it land.
Spread the line detail out, not the summary, and look at whether the error is thin and everywhere or concentrated in particular places.
Thin and everywhere — a unit here, two there, scattered across hundreds of lines with no pattern to it — is handling. That is picking and put-away and counting technique. That is a process problem, it is real, and cycle counts will genuinely fix it. If that is your shape, close this article, go and sort your pick process out, and do not spend a penny on software.
Concentrated is a different animal. If the same handful of items are wrong every single time. If it is all sitting in one location. If it clusters on kits, on returns, on transfers between places. That is not carelessness, and here is the reason it cannot be:
Errors made by people scatter. Errors made by a system repeat.
A distracted picker on a Tuesday does not produce a tidy pattern. He produces noise. When the same thing is wrong in the same way every quarter, something is repeating it faithfully, and the only thing in your building capable of that kind of consistency is the software.
There are four shapes a variance can take and each one points somewhere different. I have written all four out, along with eight other checks you can run against your own operation, and I will tell you where to find them in a minute.
The four shapes, and eight other checks. Each one scored as process or structural, so you finish with an answer rather than a feeling.
Open the nine checks →No card. Nothing to book. They open on the next screen.
Don’t believe me. The evidence is already in your building
This is the point in an article like this where you would normally get a customer story. A distributor in Ohio, a percentage, a photograph of somebody in a hi-vis vest looking pleased.
I’m not going to give you one, for two reasons. The first is that you have read enough of them to discount them automatically, and so have I. The second is better: you can test the whole of this yourself, today, without me.
Get your last count. Not the summary sheet — the line detail. Then:
- Sort it by absolute variance and look at the top thirty lines.
- Ask whether those thirty are a random cross-section of what you stock, or whether the same names keep appearing.
- Then sort the same thirty by location, and ask the same question again.
- Then mark which of them are kits, assemblies, returns, or things that moved between sites.
If it is genuinely scattered — different items, different places, no repeats — you have a handling problem and you now know it for free.
If the same twenty names have been at the top of that list for three counts running, you have just watched a system fail the same way three times, and no amount of talking to your staff is going to change what happens on the fourth.
That will take you about ten minutes and it does not require my permission, my software, or my opinion. It is the only kind of proof worth anything at this stage, because it is yours.
What you are probably thinking right now
-
“We’re not big enough for this to be a system problem.”
Size is the wrong test. The test is whether what you do is more complicated than what your system can describe. A twenty-person distributor holding stock in two places, selling in different units to how they buy, and assembling anything at all, has already outrun most small-business accounting software. A ninety-person firm with one location and one unit of measure may be perfectly well served. It is about shape, not headcount.
-
“Our records are a mess. Wouldn’t any system struggle?”
Mess is the normal starting condition and it is not disqualifying. But it does matter for the diagnosis, which is why the checks ask you to look at the pattern rather than the accuracy. A mess scatters. If your mess is neat — and some of them are unnervingly neat — that is the signal.
-
“This is a long way of telling me to buy software.”
It would be, except that the checks have an outcome that says don’t. The first of the three scoring bands tells you in as many words that your problem is process, that you should fix it with process, and that buying a system would mostly make your existing habits more expensive to keep. I’d rather you got that answer from me than paid somebody to discover it eight weeks into an implementation.
-
“We already have a system.”
Almost everybody does. The question is not whether you have one, it is whether the one you have can hold the things that are actually happening on your floor. Several of the checks are simply asking your existing system a question and watching whether it can answer.
-
“I haven’t got an afternoon spare.”
Four of the nine you can do sitting at your desk in the next ten minutes, and the one described in this article you can run off a count you have already paid for. Start there. If nothing looks off, you have your answer and you have lost ten minutes.
What this costs, and what I am actually asking you for
This is where an article like this usually reveals a price, generally with a line through a bigger one next to it.
You are not getting a price, because I am not selling you anything today. What I am asking for is an email address, and what you get for it is the nine checks — each one with the instruction, the answer you want, and what a wrong one is actually telling you — plus a scoring page that turns your nine results into one of three conclusions.
It opens on the next screen. Nothing arrives in your inbox that you have to go and dig out, because I would rather you read it while you are still annoyed about the shelf.
And to be straight with you about the far end of this: if your answers come back structural, then eventually somebody quotes you for a system that can hold your business properly, and it might be us. Our prices for that are published on our own website and you can go and read every line of them without speaking to a human being. But that is a conversation for after you know which of the two problems you have got. You do not need me for this part, and you shouldn’t pay anybody until you do.
Before you decide
The version of this where you spend nothing
I want to be clear that it is a real outcome and not a rhetorical device. The lowest of the three scoring bands says your system can represent your business perfectly well and your habits have drifted; it then names the three process fixes worth doing and tells you an ERP would largely make those habits more expensive to keep doing badly.
I have put that band in for an honest reason and a selfish one. The honest reason is that it is frequently the true answer. The selfish one is that the worst customer I can have is one who bought a system to solve a problem the system was never going to solve, and I would genuinely rather lose you now than acquire you that way.
So picture the two Mondays that are actually available to you.
In the first, the checks come back scattered. You spend six weeks fixing receiving and moving to rolling counts on your fastest-moving lines, the variance thins out, and you never send me another email. That is a good outcome and it cost you an afternoon.
In the second, they come back concentrated, in the same places, for reasons you can now name out loud. And the first thing that changes isn’t the software. It is that you stop having that conversation with your warehouse manager — because you finally have the evidence that it was never his to answer for.
Either way you end the afternoon knowing which problem you own. Right now you are guessing, and you have been guessing for months.
Nine checks. One afternoon. Three possible answers, and one of them is “don’t buy anything.”
Open the nine checks →Free · no card · opens on the next screen
Advertisement — disclosure
This article is a paid advertisement. It was written and published by Clear Horizon Solutions Corp. to promote Footing, its own productised onboarding service for Microsoft Dynamics 365 Business Central. It is not independent editorial and it has not been reviewed by anybody impartial.
The author sells the category of product this article discusses. "Jay at Footing Tech" is the CEO who runs Clear Horizon Solutions Corp., a Microsoft partner that implements Business Central for small and mid-sized businesses. If the diagnostic described here returns a structural result, Clear Horizon is one of the firms that would be commercially interested in the outcome. That is exactly why the diagnostic has a result that says spend nothing, and why the article says so before asking for your details rather than afterwards.
The Shelf Test is a general operational diagnostic intended to help an owner tell a process problem from a structural one. It is not an audit, not a stocktake, and not a substitute for advice from your accountant. No third-party research is cited anywhere in this article, because none of the figures available on this subject come from a source we were willing to put our name to.
Microsoft, Dynamics 365 and Business Central are trademarks of Microsoft Corporation.
© Clear Horizon Solutions Corp.