Cycle Counting Inventory: Stop Shutting the Plant for a Year-End Count

The plant is shut for the day. Twelve people are walking the racks with printed sheets, calling numbers down the aisle. It takes two days. On Wednesday the first pick of the week pulls a box the sheet said held forty pieces and finds twenty-two.

Two days of production, spent buying a number that was wrong by the middle of the following week.

Cycle counting inventory is the alternative every plant manager has heard of and few ever get running. You count one location at a time, on a rhythm, while the plant keeps working. Most programs stall because nobody owns the next count.

What cycle counting inventory actually means

Instead of counting everything once, you count a small slice often.

Zone A gets counted every week. The fastener bin rack gets counted every quarter. The WIP area on the production floor gets counted every day, because that is where stock moves fastest and drifts hardest.

Nobody stops, and nobody works a weekend. The gaps you find are small enough to explain, because the person who moved the pallet is still on shift.

You give up one big number in December and get a number that holds on a Tuesday morning when a customer asks whether you can ship this week.

Where a counting program usually dies

Most cycle counting programs start in a spreadsheet, in January, with real enthusiasm. They die the same four ways.

• Nobody owns a specific count. The warehouse is responsible, which means no one is.
• Counting loses to shipping. There is a truck every week, and the count is always the thing that moves.
• The tab goes stale. Last-counted dates stop being updated around week five, and after that nobody can say which zones are behind.
• Variances get fixed with no reason attached. The quantity gets corrected, the cause never does, and the same shelf is wrong again next month.

Those are scheduling and ownership problems, which is the part software is good at.

Setting up a count schedule in Qualis

A cycle count in Qualis is the standing plan to recount one location on a repeating rhythm.

The form asks four things, split across four tabs so you fill it in one part at a time.

1. Name and location. Give it a name a counter will understand, such as "Weekly - Zone A High Value Parts", and point it at the storage location it covers.
2. Priority. Low, Medium, High or Critical. This is how you tell your team which counts matter when the day gets short.
3. Frequency. Weekly, Monthly, Quarterly and Annually are built in. For any other rhythm, type the number of days. A daily WIP count is 1.
4. Product scope. Count everything at the location, or name a short list of products.

You can also assign the person responsible and leave counting instructions in the Notes tab.

Qualis works out the next count date for you, from the last count plus the frequency. You cannot type it in. A date you can type is a date somebody quietly pushes.

The reference code (CC-00001 and up) is generated when you save.

The board that tells you where you stand

Four numbers sit above the list: how many schedules are running, how many are late, how many fall due in the next seven days, and the share of active schedules that are not overdue.

Filter the list to Active, sort by next count date, and you are looking at this week's work with the late ones at the top in red. The filter shows as a chip you can remove, and the address bar carries it, so you can send that exact view to whoever does the counting.

Every column filters: location, status, priority, assigned person, product scope, and date ranges on the next count, the last count and the created date.

The overdue count comes looking for you

At 02:00 every day, Qualis looks for active schedules whose next count date has passed. For each one it sends a high-priority reminder to the person that schedule is assigned to, or to whoever created it if nobody is assigned. The message names the schedule and the date it was supposed to happen.

Open the schedule and it says the same thing louder, with a red banner across the top of the page and the next count date in red.

The same page carries the history without anyone maintaining it. Frequency, last count date, next count date, how many counts have been completed, the last adjustment the schedule produced, and the person it belongs to. Those fill in from the counts themselves, so the tally is not a figure somebody remembered to type.

When a zone should genuinely stop being counted for a while, during a reorganization for example, set the schedule to Paused. A paused schedule is never flagged as overdue and drops out of the due and overdue numbers until you resume it.

Not every shelf earns the same attention

Frequency and priority are separate fields on purpose. Frequency is how often a location comes round. Priority is how much it matters when it slips.

A hazmat zone on a weekly rhythm at Critical priority and a fastener rack on a quarterly rhythm at Low priority are both on the program, and nobody has to argue about which one gets counted first on a short-staffed Thursday.

Product scope narrows it one more step. A schedule can cover every product at the location, or a named list, which is how you put twelve expensive items on a weekly rhythm without counting the whole shelf every time.

What this prevents

Three things, each of which costs more than the counting does.

A shortage found at pick time. The order is picked, the rack is short, and somebody is calling a customer on a Friday afternoon. Accurate stock is the number available to promise checks before it lets sales confirm an order.

A write-off nobody can explain. When a year passes between counts, the variance you find is twelve months of small causes rolled into one number, and the trail is cold. A weekly count turns that same variance into an incident somebody can still remember.

Planning built on a wrong number. A reorder point is arithmetic on your on-hand figure. If that figure is out by 15%, automatic replenishment will buy the wrong quantity with perfect discipline.

The whole loop, end to end

The schedule sets the rhythm. The next count date falls due and the assigned person is told. The count happens. The result is recorded against stock as an inventory adjustment, which updates the schedule's last count date, its completed tally and the adjustment it links to. The next count date rolls forward by the frequency, and the location goes back in the queue.

Every change to a schedule is versioned, so if somebody stretches a weekly count to monthly you can see who did it, when, and what the value was before. With update permission, you can restore the earlier version.

Frequently Asked Questions

How is cycle counting different from a full physical inventory count?

A physical inventory counts everything at once and normally needs operations to stop. Cycle counting counts a small part of the warehouse at a time, on a repeating schedule, while the plant keeps running. Over a year the same stock gets covered, but in slices you can absorb into a normal shift.

How often should each location be counted?

Count by value and by movement, not evenly. A common starting point is weekly for fast-moving and high-value areas, monthly for the middle, quarterly for slow stock. In Qualis those three are preset, and any other rhythm is a number of days you type in.

Do we still need an annual physical count?

Often yes, usually because an auditor or an insurer asks for it. A cycle counting program does not remove that requirement by itself, but it changes what the annual count finds. When the warehouse has been counted in slices all year, the year-end exercise confirms a number rather than discovering one.

Who should actually do the counting?

Someone who works the area often enough to spot what looks wrong, and who is named. Each Qualis schedule carries an assigned user, and that is the person the overdue reminder goes to. Programs that survive tend to have one named person per location rather than a shared responsibility.

What happens when the count does not match the system?

The difference is recorded as an inventory adjustment, which corrects the stock figure and leaves a record of the correction behind it. The schedule then shows that adjustment on its detail page, next to the date it was counted, so the correction stays attached to the count that found it.

How long does it take to get a cycle counting program running?

Setting up the schedules is an afternoon. Pick your locations, decide the rhythm for each, name an owner, save. The slower part is the first month of counting, because that is when you find out which shelves have been drifting and how long the counts really take. After that the schedule runs itself and the daily reminder does the chasing.

The bottom line

A year-end count buys you one accurate number and two days of lost production. A count schedule buys you a number that stays roughly right all year, at the cost of an hour a week from somebody who is already in the building.

Three things keep the program alive: a named owner for each location, a next count date nobody can quietly edit, and something that notices when the date passes.

If your stock figures only get checked once a year, see how cycle counts work in Qualis and start a trial. If reserved stock is your next question, our post on available to promise shows what an accurate on-hand figure is actually worth.