How to Prepare for a Flawless Year-End Physical Inventory
It’s late October. Your finance team has circled a date in December for the year-end physical inventory count. Your operations team looks at the calendar and starts calculating how many temporary counters they’ll need, how many shifts they’ll suspend, and how many days of normal operations they’ll lose.
If this is how your year-end inventory prep starts, it started two months too late.
A flawless year-end physical inventory — one where the count matches the system, the variances are explainable, and finance can close the year without a three-week reconciliation nightmare — is built in September and October, not December. By the time the counters arrive, the outcome is already determined by the preparation that happened (or didn’t) in the weeks before.
Here’s how to prepare for a year-end warehouse audit that actually produces a clean number, and why the preparation starts long before the count team shows up.
Why Year-End Physical Inventory Counts Fail
Most year-end inventory counts don’t fail because the counting is wrong. They fail because the preparation was wrong. Here are the four most common failure modes.
The System Was Already Wrong Before the Count Started
If your WMS inventory accuracy is 90% going into the count, the count will reveal a 10% variance. That variance then has to be investigated, categorized, explained to finance, and reconciled. The count team gets blamed for counting errors that were actually system errors that existed before anyone started counting.
This is the most common year-end inventory failure: using the count to discover problems that should have been found and fixed weeks earlier. The real cost of delaying a WMS upgrade shows up most painfully at year-end, when a legacy system’s accumulated inaccuracy turns the count into a forensic exercise.
The Count Was Rushed
Year-end counts are often scheduled between Christmas and New Year’s, when operations are skeleton-staffed and everyone wants to be done quickly. A rushed count produces miscounts, missed locations, and incomplete lot-level verification. The result is a count that’s no more accurate than the system it was supposed to validate.
Lot-Level and FEFO Data Wasn’t Verified
For food and beverage brands, lot-level accuracy is as important as quantity accuracy. If the count team verifies that 1,200 cases of a SKU are physically present but doesn’t verify the lot numbers and expiration dates, the FEFO (first-expired-first-out) data in your WMS is unverified. Come January, your picks may be shipping product based on lot assumptions that were never validated.
Shrinkage Wasn’t Addressed Before the Count
Shrinkage — the gap between what the system says and what’s physically there, caused by damage, theft, mispicks, unrecorded movement, or process errors — accumulates throughout the year. If you don’t address shrinkage before the year-end count, the count absorbs the full year’s accumulated variance in a single event. That makes the variance look enormous, triggers finance investigations, and creates a reconciliation burden that could have been distributed across the year through cycle counting.
The Preparation Timeline: What to Do in September, October, and November
A flawless year-end count is built on a structured 12-week preparation timeline. Here’s what to do at each stage.
September: Clean the Foundation
September is when you fix the system before the count tests it.
Run a full cycle count on your top 50 SKUs. These are the SKUs that represent 70 to 80% of your inventory value. If the cycle count reveals variances, investigate and fix the root causes now, not during the year-end count. Improving inventory accuracy is a process, not an event.
Reconcile ERP to WMS. If your ERP and WMS show different on-hand quantities for the same SKUs, that drift will show up as a variance during the year-end count. Reconcile the two systems now and fix the integration gaps that caused the drift. When your ERP and warehouse systems aren’t talking, year-end inventory is where the communication gap becomes visible.
Audit your lot and expiration data. Pull a sample of SKUs and verify that the lot numbers and expiration dates in the WMS match the physical product on the floor. If they don’t, your FEFO picks have been wrong, and the year-end count will expose the full extent of the discrepancy.
October: Tighten the Processes
October is when you stop the bleeding and prevent new variances from accumulating before the count.
Freeze new SKU onboarding if possible. Every new SKU added between October and the count introduces a new variable. If you can delay new product introductions until after the count, you reduce the risk of receiving errors and putaway errors that create variances.
Enforce receiving accuracy. Most inventory variance starts at receiving. If product is received short, over, or misidentified and the discrepancy isn’t caught at the dock, it propagates through the system until the year-end count reveals it. Tighten receiving procedures in October: require blind counts at the dock, verify ASN accuracy, and escalate any discrepancy immediately.
Address known shrinkage. If you know a site has a shrinkage problem like damage in a specific zone, mispicks on a specific SKU line, or unrecorded transfers between sites, fix it now. The hidden costs of poor inventory visibility are most expensive when they surface all at once during a year-end count.
November: Plan the Count
November is when you build the count plan.
Define the count scope and methodology. Will you do a full wall-to-wall count, or a stratified sample count with statistical extrapolation? Full counts are more accurate but more disruptive. Sample counts are faster but require statistical rigor to be defensible for financial reporting. For most growth-stage CPG brands, a full count at the primary DC and a sample count at satellite sites is the right balance.
Prepare count documentation. Every location in the warehouse should have a count sheet with the expected SKU, the expected quantity, and a blank for the actual count. Use blind count sheets — the counter doesn’t see the system number. There are 5 signs your WMS is costing you more than it saves, and one of those signs is a WMS that can’t generate count sheets efficiently.
Schedule the count team and freeze operations. Plan a complete operational freeze during the count. No receiving, no shipping, no transfers, no movement. Every transaction during the count creates a variance. The freeze should be communicated to customers, carriers, and retailers well in advance.
The Count Day Playbook
When count day arrives, the preparation pays off. Here’s how to run the count itself.
1. Freeze All Movement
Before the first count sheet is distributed, confirm that all inbound and outbound operations are stopped. No trailers being unloaded. No picks being made. No transfers being processed. The system snapshot must match the physical reality at a single moment in time.
2. Distribute Blind Count Sheets
Every counter gets a count sheet with location identifiers only — no system quantities. The counter physically counts the product at each location and records the actual quantity, lot number, and any observed damage.
3. Reconcile Against the System
After the count is complete, reconcile each location’s counted quantity against the WMS on-hand. Every variance is flagged for investigation. Variances should be categorized: system error (the WMS was wrong), process error (the floor was wrong — mispick, misputaway, unrecorded movement), or shrink (damage, theft, unexplained loss).
4. Investigate Significant Variances
Any variance above a defined threshold, typically $500 or 5% of location value, gets a recount by a different counter. If the recount confirms the variance, investigate the root cause. Was there a receiving error? A shipping error? A transfer that was never closed? A damage event that wasn’t recorded?
5. Adjust and Document
Adjust the WMS to match the verified count. Document every adjustment with the variance reason, the root cause, and the corrective action. This documentation is what finance and auditors need to close the year without extended reconciliation cycles.
Frequently Asked Questions
How should a CPG brand prepare for a year-end physical inventory audit?
A CPG brand should prepare for a year-end physical inventory by starting 12 weeks before the count date. In September, run cycle counts on top SKUs, reconcile ERP to WMS discrepancies, and audit lot-level data. In October, tighten receiving processes, address known shrinkage, and freeze new SKU onboarding. In November, define the count methodology, prepare blind count sheets, and schedule the operational freeze. The count itself should use blind counting, immediate variance categorization, and root cause investigation for significant discrepancies.
What are the best practices for year-end warehouse audits in food and beverage?
The best practices are: start preparation in September (not December), run cycle counts before the year-end count to find and fix systemic issues, reconcile ERP and WMS data before the count, verify lot numbers and expiration dates (not just quantities), enforce a complete operational freeze during the count, use blind count sheets so counters aren’t biased by system numbers, and document every variance with root cause and corrective action. Food and beverage brands should pay special attention to lot-level accuracy because FEFO compliance depends on it.
How can I reduce inventory shrinkage before year-end close?
Reduce inventory shrinkage by running cycle counts in September and October to identify and fix the root causes of variance before the year-end count. Common shrinkage sources include receiving errors, unrecorded damage, mispicks, unrecorded transfers between sites, and theft. Fix the processes that allow shrinkage to accumulate: enforce blind receiving counts, require damage reporting, verify transfer completions, and tighten physical security in high-value zones.
Distributing shrinkage discovery across the year through cycle counting prevents a single massive variance at year-end.
What steps ensure a flawless year-end physical inventory count?
The steps are: (1) start preparation 12 weeks early with cycle counts and system reconciliation, (2) tighten receiving and process accuracy in October, (3) prepare blind count sheets and plan a complete operational freeze in November, (4) freeze all movement before counting begins, (5) use blind counting with no system quantities visible to counters, (6) reconcile and categorize every variance, (7) recount significant variances with a different counter, (8) investigate root causes, and (9) document every adjustment for finance and auditors. Learn more about why 98% accuracy isn’t enough for CPG financial reporting, because the year-end count is where that gap becomes visible.
A Clean Close Starts in September
The brands that close their year with a clean inventory number and no extended reconciliation aren’t lucky. They’re prepared. The preparation starts 12 weeks before the count, not 12 hours. And it depends on a WMS that can produce accurate data, generate count sheets, track lot-level detail, and integrate with ERP systems without drift.
If your current WMS is the reason your year-end count is a nightmare because the system data is already wrong, the lot tracking is unreliable, or the ERP integration has been drifting all year, the fix isn’t a better count process. It’s a better system.
The Hive was built on Schreiber Foods’ own warehouse operations to deliver the real-time, lot-level, multi-site inventory accuracy that makes year-end counts routine instead of painful. Request a consultation to see whether your WMS is ready for the count that defines your year.
