Home / Insights

Warehouse operations series · Part 4 of 8

Phantom Stock: Why Your System Says 40 and the Shelf Says 12

Contents
  1. What accuracy means
  2. Where records go wrong
  3. Annual count or cycle counting
  4. The result
  5. How to run a cycle count
  6. Measures to track
  7. Common mistakes
  8. Key points
  9. Sources

A customer calls for 40 cases. The system shows 40 in location R3-B12, so sales confirm the order. The picker finds 12. Somewhere there are 28 more cases, or there are not, and nobody can say which until someone searches. The order ships short, the buyer places a rush order for stock that may already be in the building, and the next week the same thing happens with another item.

This is phantom stock: the system says it is there and the shelf says it is not. It undermines everything that relies on the records: sales promises, purchasing, safety stock, and the slotting and put-away of Parts 1 to 3. This part measures how fast records go wrong in the example warehouse and compares the classic once-a-year count with cycle counting.

What accuracy means

Most systems report how close the total quantity is to the count. That number hides errors, because an over-count in one location cancels a short count in another:

SKU 4471SystemShelfRecord right?
Location R3-B124012No
Location R7-B04028No
Total4040Total quantity: 100% accurate

The total is perfect, yet both location records are wrong, and the picker sent to R3-B12 comes back short. The measure that matters on the floor is location accuracy: the share of locations whose SKU and quantity are both right, within a small tolerance for loose items. The WERC benchmark puts best-in-class inventory count accuracy by location at 99.5% or better.

\[\text{Location accuracy} = \dfrac{\text{locations counted with the right SKU and quantity}}{\text{locations counted}}\]

Where records go wrong

CauseHow it happensFix at the source
Receiving miscountThe packing slip is keyed in, not the count. Short or over shipments go unnoticedCount or scan at the door, against the ASN (Part 3)
Wrong put-away locationThe driver puts the pallet in the nearest hole and means to record it laterScan the pallet and the location at put-away (Part 3)
Mis-pickWrong item or wrong quantity taken, so two records are now wrongScan at pick (Part 5)
Unrecorded movesStock moved to make room or to top up a pick face, with no transactionA move is always a scan, or it does not happen
Damage and shrinkBroken cases thrown away without an adjustmentA damage bin and a weekly adjustment routine

Busy locations go wrong most often because they have the most transactions. In the example the chance that a location's record goes wrong in a given week is taken as 2.2% for A items, 0.9% for B and 0.4% for C. About 35% of errors are phantom stock. A phantom on a busy location is usually found by a picker within a week or two, the hard way.

Annual count or cycle counting

The traditional fix is the wall-to-wall count: close the warehouse for a couple of days at year-end, count everything and correct the records. It gives a good number on one day. Records then decay all year, and the count does nothing about why they went wrong.

Cycle counting counts a few locations every day instead, so every location is counted several times a year and the busiest most often. The usual rule follows the ABC classes. In the example:

\[\text{Counts a year} = \sum_{c} N_c \, f_c = 425 \times 13 + 502 \times 4 + 269 \times 2 = 8{,}071\]

That is A locations every 4 weeks (13 times a year), B every 13 weeks and C every 26. Over 250 working days:

\[\dfrac{8{,}071}{250} \approx 32 \text{ counts a day} \times 3 \text{ min} \approx 1.6 \text{ hours a day}\]

One person for a quiet part of the morning, before the first wave of picking, with no shutdown.

Figure 2 runs a year of stock records in the example's pallet racks, one week at a time. Each pallet is coloured by what its record says: grey when the record is right, amber when the quantity is wrong, and red for phantom stock, drawn as a see-through ghost because the system shows a pallet that is not really there. Rings mark the locations counted that week. Choose a counting plan, or Compare all to see the three side by side, with the panel showing each plan's numbers in the same order.

Week 0
Records right this week
Average over the year
Short picks a year
Counting hours a year
Counting and searching hours
Days closed to count

  • Record right
  • Wrong quantity
  • Phantom stock
  • Counted this week
Figure 2. A simulated year of location records in the example's racks, 1,196 occupied locations. The replay shows one year. The numbers in the panel are averages over 20 simulated years. A short pick is a picker finding less stock than the system shows.

The result

Counting planAverage accuracyLowestShort picks a yearCounting hoursCounting and searchingDays closed
Annual count only79.1%67%23780 h139 h2
ABC cycle counting95.8%94%150404 h441 h0
Cycle counting + causes fixed97.4%95%62340 h356 h0
60%70%80%90%100%Week 0Week 13Week 26Week 39Week 52Best in class: 99.5%Annual count onlyABC cycle countingCycle counting + causes fixedLocation records right
Figure 3. Location records right, week by week. The annual count gives one good day. Cycle counting keeps the records right all year.

With the annual count alone, accuracy drifts down from 95% to about 67% just before the year-end count, and averages 79.1% over the year. For most of the year one location record in five is wrong. ABC cycle counting holds it near 95.8% and cuts short picks from about 237 to 150 a year.

Be clear about the cost. Cycle counting takes more counting hours than one annual count: about 404 against 80 in the example's racks, or 441 against 139 hours including the time spent searching after short picks. What it buys is records that can be trusted on every day of the year, no two-day shutdown, and the information to fix the causes. In a real warehouse the annual count also covers all the shelving and usually needs every person in the building, which narrows the gap.

The biggest gain comes from fixing the causes. With scanning at receiving, put-away and picking, fewer records go wrong in the first place. Accuracy averages 97.4%, short picks fall to about 62 a year, and the B and C locations can be counted half as often, bringing the hours down to 340.

How to run a cycle count

  • Count blind. The counter sees the location and the SKU, not the system quantity, so they count instead of confirming.
  • Recount before adjusting. A variance above the tolerance gets a second count by another person, then a check of open transactions such as stock received or picked that day.
  • Log a cause for every adjustment. Receiving, put-away, pick, move or damage. The log is what tells you which fix to make.
  • Count when it is quiet. First thing in the morning or between waves, and never a location with a pick in progress.
  • Count when it is cheap. A location that has just been picked empty, or is down to its last cases, is quick to count, so count it then.
  • Approve large adjustments. A manager signs off adjustments above a value limit, which also satisfies the auditors.

Measures to track

MeasureWhat it shows
Location accuracy from cycle countsHow far the records can be trusted. Track it by class and by zone
Short picks per 1,000 linesPhantom stock found the hard way, by customers' orders
Adjustments by causeWhere the errors come from, and which fix to make next
Adjustment value, gross and netGross shows the size of the problem. Net hides it
Counts completed against planWhether the counting habit is holding

Common mistakes

  • Measuring total quantity accuracy. Errors cancel out. Measure by location.
  • Adjusting without a cause. The record is fixed and the process that broke it is not.
  • Counting what is easy. The slow C items are quick to count and rarely wrong. The A items are where the errors are.
  • Letting counting slip in busy weeks. Those are the weeks when records go wrong fastest.
  • Raising safety stock to cover bad records. It hides the problem at the cost of cash tied up in stock. Fix the records, then set safety stock properly.

Key points

  • Phantom stock is the system showing stock that is not on the shelf. It is found by customers' orders, as short picks.
  • Measure location accuracy, not total quantity accuracy. Best in class is 99.5% or better.
  • An annual count gives one good day. In the example, records then fall to about 67% right before the next count.
  • ABC cycle counting takes about 1.6 hours a day here and keeps accuracy near 96% all year.
  • Fixing the causes with scanning lifts accuracy further and cuts the counting needed.

Earlier in this series: Part 1 won back space, Part 2 cut the pickers' walking, and Part 3 cleared the dock. Next: Part 5 looks at mis-picks and mis-ships, and what each error really costs.

Sources

The distributor, its error rates and its times are an illustrative example built from stated assumptions. Measure your own record accuracy with a sample count before choosing a counting plan.

Keep reading

Related articles

All 168 articles

Ready to find your next improvement?

Book a strategy call. We will talk through your goals, pain points and where AI, systems or process work can make the biggest difference.