It is the second week of December. The CFO wants the year-end stock value locked by the end of the month. The plant manager wants to keep the line running through the holiday rush. The auditor wants documentation that supports whatever number lands on the balance sheet. And the warehouse supervisor wants to know who is going to count the back row of pallets that nobody has moved since June. Every December, the same conversation, and every December, the same outcome: a rushed weekend count that produces a number nobody fully trusts, followed by a January reconciliation that drags into February.
The standard answer to this is a full production freeze. Stop everything for a weekend, count it all at once, restart on Monday. This works in theory and fails in practice for any operation with more than one site, more than a thousand SKUs, or any meaningful in-flight inventory between locations. The freeze costs more than the count is worth, and the count itself is rarely as accurate as the freeze implies.
There is a better way. A year end inventory count plan that runs over five working days, does not require a production freeze, produces audit-ready records, and treats counting as an extension of normal operations rather than an interruption of them. This guide walks through how to structure that plan, what to count first, and how to record adjustments so the auditor and the controller both come away satisfied.
Why the Freeze Approach Quietly Fails
The production freeze model assumes that stopping all activity creates a clean snapshot. In practice, it creates a different kind of mess. Materials in transit between locations are neither at the source nor at the destination at the moment of the freeze. Production runs in mid-batch have consumed inputs but not yet produced outputs. Quality control holds contain materials that nominally exist but cannot legally be issued. The freeze does not eliminate these in-flight states. It just hides them inside a single point in time and forces the count team to make assumptions about how to record them.
Multi-site manufacturers face a compounding version of this problem. A freeze at plant one is meaningless if plant two is still running and consuming materials that were nominally transferred from plant one but have not yet been received. To get a true freeze, you need to stop everything everywhere simultaneously, which is operationally and politically expensive.
The cycle count vs freeze debate often misses the more useful framing: a continuous cycle count program throughout the year reduces the year-end count to a verification exercise rather than a discovery exercise. If your cycle counts have been running monthly and your discrepancies have been resolved with proper adjustment movements, the year-end count is a sample audit, not a full census. We covered the importance of treating cycle counts as a continuous practice in our earlier piece on why spreadsheet inventory fails at scale, where the absence of an audit trail makes every count an act of faith.
Day One: Plan the Sequence and Lock the Cutoff
The count plan begins before any pallet is touched. On day one, the operations team defines the sequence in which locations will be counted, sets the cutoff time for transactions to be reflected in the opening snapshot, and freezes the reference data that the count will be measured against. Every site needs a printed or digital count sheet that lists the SKUs expected to be present in each location at the cutoff time, along with the system quantity at that moment.
The sequence matters. Count finished goods stores first, because they are the most static. Count raw material stores second, because consumption can be paused briefly without disrupting active production. Count factory floor locations last, because they are the most dynamic and need the smallest window between system snapshot and physical count. Count quality control hold areas in parallel with whichever production area they serve.
The cutoff is the single most important administrative element of the count plan. Every transaction up to the cutoff is included in the system quantity that the physical count will be compared against. Every transaction after the cutoff is excluded from the count comparison and instead becomes part of the post-count adjustment reconciliation. A platform with location-level stock records and immutable movement timestamps makes this trivial. The system can produce, at any moment, an accurate snapshot of what was in each location at the cutoff time, and a clear list of what has moved since.
Day Two: Count Finished Goods and Reconcile the Easy Cases
Day two is for finished goods stores. These are the simplest locations to count. The SKUs are large, the quantities are modest, the storage is structured, and the consumption rate is low compared to raw materials. A two-person count team should be able to process a full finished goods store in half a day, with the other half reserved for entering the counted quantities into the system and reviewing variances.
Most variances at this stage will fall into one of three categories. There will be small clerical variances of one or two units that reflect normal rounding and packaging differences. There will be larger variances tied to specific events that the count team can usually identify in real time, such as a recently dispatched order that was not yet recorded. And there will be a small number of true unexplained variances that need to be flagged for further investigation.
The key administrative discipline here is that every variance is recorded as an adjustment movement in the system, with a category, a reason, and the user who made the entry. The stock quantity is never edited directly. This is the audit-ready stocktake principle in action. The auditor in February will not ask you what your finished goods count was. The auditor will ask you to explain the adjustment movements that were created in December, and your answer is the reason field on each one.
Day Three: Raw Materials Without Stopping Production
Day three handles raw material stores. The challenge is that raw materials are actively being consumed by production, so you cannot count them with the same static-snapshot logic that worked for finished goods. The solution is location-by-location sequencing within the day, where each raw material location is briefly paused for issue while the count happens, then released back to normal operation.
A platform with role-based adjustment authority is essential here. The raw material count team needs to be able to enter counted quantities for the locations they are counting, but they should not be able to enter counts for locations they are not at. Permissions need to be tight enough that an operator at plant two cannot accidentally enter a count for plant one, but flexible enough that the count team at each plant can move efficiently without bottlenecking on a single approver.
For high-velocity raw materials that cannot be paused even briefly, the count happens in motion: the system records the quantity at the start of the count window, every consumption movement during the window is logged normally, the physical count is taken, and the variance is calculated against the system quantity adjusted for the movements that occurred during the count. This sounds complex but it falls out naturally from any system that maintains an immutable movement record with accurate timestamps.
Day Four: Factory Floor and Work in Progress
Day four is the hardest day. The factory floor contains active work in progress, materials staged for upcoming runs, finished goods waiting to be moved to the warehouse, and quality control holds. Each of these states needs to be counted and reconciled differently. Work in progress, in particular, needs to be valued based on the BOM consumption that has already happened against active production runs, which is a calculation rather than a count.
The count plan multi-site approach handles this by treating each factory floor location as its own count exercise, with its own count team, and its own reconciliation workflow. The plant manager owns the factory floor count for their plant. The operations director sees the consolidated view across all plants in real time, with cascading health indicators that show which plants are converging and which are still in active reconciliation.
Adjustments on the factory floor need especially careful handling. A variance of fifty kilograms of raw material on the factory floor could be a genuine inventory loss, an unrecorded consumption, a BOM accuracy issue, or simply material staged for a run that has not started yet. The adjustment movement category needs to capture which of these is suspected, and the QA or production team needs to follow up on each one in the days after the count.
Day Five: Reconciliation, Adjustments, and the Audit Package
Day five is reconciliation. The count team works through the variance list, classifies each one, creates the appropriate adjustment movements, and produces the documentation that the auditor will rely on in the new year. The output of day five should be a complete adjustment ledger that lists every change made as a result of the count, with the reason, the user, the location, and the dollar impact.
This is where an immutable adjustment event model pays off most. The auditor does not need access to the full transaction history of the entire year. The auditor needs the count documentation, the variance analysis, and the adjustment ledger that ties them together. A platform that produces these as a normal export, without requiring custom report development, turns the audit package from a project into a download.
The same principles that we described in the move from reactive to predictive procurement apply to year-end stocktake. The reactive version is a December scramble. The predictive version is a continuous cycle count program with monthly reconciliation, where the year-end stocktake is a sample verification rather than a full physical count. The five-day plan in this guide bridges the two, giving operations teams a path to a clean year-end without a production freeze and with audit-ready records at the finish.
What a Good Year-End Count Actually Proves
A year-end count is not really about getting the inventory number right. It is about proving that the inventory number is right. The number itself was either right or wrong before the count started. The count is the evidence. What you want, when the auditor sits down in February, is to be able to point to a clean count plan, an immutable adjustment record, and a small number of explainable variances. That combination produces a clean audit opinion regardless of the absolute size of the variances.
The operations directors who run year-end well treat the count as the verification step in a year-long discipline rather than the discipline itself. The plan in this guide assumes that discipline exists. If it does not, the count will surface that fact, and the work of the new year is to build it. Visit falorb.com for a longer look at how location-level stock records, immutable movement events, and role-based adjustment workflows support this kind of count plan in practice.
FalOrb supports five-day year end inventory count plans across multi-site manufacturers with location-level stock, immutable adjustments, and role-based authority. Book a 30-minute walkthrough or email us at [email protected] to see how it applies to your operation.