Cycle Count Template: Free Excel Spreadsheet for Warehouses

A cycle count template gives your count process a fixed structure so every run produces data you can actually trace and act on. According to the Warehousing Education and Research Council (WERC), warehouses that run structured cycle counts maintain accuracy above 97%, compared to 85-90% for teams relying on annual physical counts. This spreadsheet covers count execution, variance capture, and weekly reconciliation in one file.

The Aberdeen Group found that top warehouses count 65% of SKUs monthly, while average performers count just 20%. The difference shows up directly in order accuracy and fulfillment speed.

Get Excel Template

Count run header: 5 fields

What information should a cycle count form include?

Each count run starts with a header block that captures the who, what, when, and scope. These 5 fields tie the count to a specific time and person, which matters when investigating a discrepancy weeks later.

Field	Purpose	Example
Count date	Date of count execution	2026-03-07
Location	Warehouse or area code	WH-01
Counter	Person performing the count	Maya
SKU class	ABC classification being counted	A
Freeze time	Time inventory movements were paused	09:00

Freezing inventory movements during the count window prevents discrepancies caused by picks or receives happening mid-count. Even a 30-minute freeze is enough to get a clean count. Operations that skip the freeze step see 3-5x more phantom variances that waste investigator time.

Count lines: 9 columns per SKU

The count line section captures every data point needed to identify, verify, and resolve discrepancies at the SKU level.

Column	Type	Purpose
SKU	Manual	Product variant being counted
Bin	Manual	Physical storage location
System qty	Pre-filled	Quantity the system shows before count
Physical qty	Manual	Actual quantity counted on shelf
Variance	Formula	Physical qty minus system qty
Recount?	Decision	Yes if variance exceeds threshold (typically plus or minus 2 units or 5%)
Final qty	Manual	Confirmed quantity after optional recount
Reason code	Dropdown	Root cause classification (see codes below)
Owner	Manual	Person responsible for resolving the variance

The variance column auto-calculates. Any non-zero variance should get a reason code and an owner. Teams that assign variance ownership resolve discrepancies 60% faster than those that leave investigation to whoever gets around to it.

5 reason codes for variance classification

Every variance needs a root cause. These 5 codes cover approximately 95% of warehouse discrepancies according to supply chain benchmarking data:

• RCV: receiving error (wrong qty booked in, missed item on PO)
• PICK: pick error (wrong item picked, quantity mispicked)
• BIN: bin transfer error (stock moved but not logged in system)
• DMG: damaged or lost (breakage, theft, spoilage)
• OTH: other (catchall for edge cases; investigate if this exceeds 10% of variances)

Track reason code frequency weekly. If one code dominates (e.g. 40% or more of variances are PICK), that process needs attention first. Warehouses that act on reason code trends within 2 weeks reduce repeat variances by 30-45% in the following quarter.

For deeper methodology on running counts at the right cadence, the inventory accuracy guide covers how to set targets and measure improvement over time.

Weekly summary dashboard: 4 metrics

Metric	Formula	Target
Count completion rate	SKUs counted / SKUs scheduled	100%
Variance rate	SKUs with non-zero variance / total SKUs counted	Under 2%
Recount compliance	Recounts completed / recounts triggered	100%
Open actions past due	Unresolved variances older than 48 hours	0

Use this summary to spot trends. A rising variance rate points to a breakdown upstream, usually in receiving or picking, not in the count itself. The ASCM (formerly APICS) inventory control framework treats cycle counting as the primary tool for maintaining ongoing record accuracy. Warehouses that review these 4 metrics weekly achieve 15-20% fewer variances per quarter than those that review monthly.

Count frequency by ABC class

How often should you do a cycle count?

Not every SKU needs the same count cadence. ABC analysis segments your catalog by revenue contribution so you can allocate counting effort where stockouts hurt most.

SKU class	% of revenue	Count frequency	Typical SKU count	Annual counts per SKU
A	70-80%	Weekly	Top 20% of SKUs	52
B	15-20%	Bi-weekly	Middle 30%	26
C	5-10%	Monthly	Bottom 50%	12

Class A SKUs drive the majority of revenue and should get the most count attention. Counting every SKU every week is not practical for most operations. ABC classification focuses effort where the financial impact of a stockout or miscount is greatest. A warehouse with 1,000 SKUs under this model runs roughly 340 count lines per week: 200 A-class, 115 B-class, and 25 C-class.

Handling recounts and escalations

25% of initial cycle count variances are transcription errors

When a variance exceeds the recount threshold, the template flags it automatically. The recount process adds 3-5 minutes per SKU but catches transcription errors that account for roughly 25% of all initial variances.

The recount workflow:

• A different counter performs the second count (blind to the first count result)
• If the recount confirms the variance, assign the reason code and owner
• If the recount resolves the variance, mark as “counting error” and record the corrected quantity
• Variances unresolved after 48 hours should escalate to the warehouse supervisor

For operations where variance investigation leads to broader inventory reconciliation, the reconciliation guide covers the full close-out process from count data to system adjustment.

Scaling beyond a spreadsheet

This template works well for warehouses counting up to 150-200 SKUs per week across 1-2 locations. Beyond that, manual overhead compounds:

• Transcribing counts from paper to spreadsheet introduces a second error layer
• Reason code trend analysis requires manual pivot tables after every count cycle
• Multiple counters on different zones means reconciling 3-5 separate sheets
• Historical count data grows unwieldy past 6 months of weekly counts

Dedicated inventory tracking software for growing businesses automates the count workflow: it assigns count lists, hides system quantities for blind counts, flags recount thresholds in real time, and posts adjustments with reason codes in one step. If your team is spending more time managing the spreadsheet than investigating variances, the template has become the bottleneck.

Quick Reference

• A cycle count run needs 5 header fields: date, location, counter, SKU class, and freeze time.
• Each count line has 9 columns: SKU, bin, system qty, physical qty, variance, recount flag, final qty, reason code, and owner.
• Use 5 reason codes: RCV (receiving), PICK (picking), BIN (bin transfer), DMG (damaged/lost), OTH (other).
• Track 4 weekly metrics: completion rate (100%), variance rate (under 2%), recount compliance (100%), open actions (0).
• Count Class A SKUs weekly (52 counts/year), Class B bi-weekly (26), Class C monthly (12).
• Warehouses with structured cycle counts maintain accuracy above 97% vs 85-90% without them.

Metric	Target	Red flag threshold
Count completion rate	100%	under 90%
Variance rate	under 2%	over 5%
Recount compliance	100%	under 80%
Open actions past due	0	3+ unresolved
Single reason code dominance	under 30%	over 40%
Time to resolve variance	under 48 hours	over 72 hours