Executive Summary
Imagine you are a student. It is well known that all students have to pass a final set of examinations, to be able to get into a higher grade. Therefore, there are regular tests throughout the year to evaluate the performance of each student so that the students who are under-performing can be guided by the teachers for improvement.
The same is true for cycle counting. It is a regular, ongoing way to do an inventory count instead of waiting until the end of the year to do one.
Cycle counting is an inventory auditing method that counts a portion of the inventory in a given location on a given day, on a rotating schedule throughout the year, instead of shutting down operations for an annual physical inventory count.
Each location or SKU group is counted several times each year. Whatever discrepancies that arise, are looked into and corrected as and when they are found. This approach helps to maintain the accuracy of the inventory while creating the possibility for warehouses and production facilities to continue to operate normally.
What Cycle Counting Is and Why It Replaced Annual Physical Inventory
Cycle counting inventory is providing faster and more reliable visibility into inventory records. It is observed that the traditional annual stock count for most manufacturers and distributors is being replaced by cycle counting inventory.
Cycle counting runs alongside normal operations instead of shutting the warehouse down
No shutdown required
At an annual physical inventory, production, shipping and warehouse operations are shut down for one to three days.
But for organizations that operate on a daily basis, every hour of downtime impacts customer deliveries and revenues.
Errors stay traceable
A cycle count can also detect inventory errors and these errors can still be investigated. For example, if an inventory is wrong for 6 months, it is difficult to find out the root cause. Because it is no longer easy to re-establish transactions, operator activities and process modifications.
With inventory cycle counting, however, discrepancies are found in days or weeks, making it much easier to identify whether a problem is due to an incorrect receipt, picking error, production transaction, or inventory movement.
Fewer counting errors
Another advantage is consistency. Teams count thousands of SKUs in a short period of time, during the yearly physical inventories. This increases the risk of counting errors due to fatigue and time pressure.
Smaller, scheduled cycle counts are easier to manage because they require fewer resources. They can be done during normal warehouse operations without disturbing receiving, picking or shipping activities.
Where annual counts still apply
This is a common comparison between physical inventory vs cycle counting, but the answer is not always one or the other. In some regulatory environments, such as GAAP audits and some FDA or USDA compliance frameworks, the annual physical inventory is still a requirement.
It may also be appropriate for very small operations with limited inventory. But for many mid-market manufacturers running 500+ active SKUs, cycle counting is the more practical and effective way to manage inventory accuracy over the long haul.
| Factor | Annual physical count |
|---|---|
| Frequency | Once or twice per year |
| Operational disruption | Requires production and shipping shutdown |
| Error detection speed | Errors discovered months later |
| Root cause traceability | Difficult to determine after long periods |
| Resource requirement | Large teams over a short period |
| Accuracy over time | Records gradually become less reliable between counts |
Let’s
Talk
Book your manufacturing AI strategy session
ABC Classification: How to Structure a Cycle Count Program
It is important to know that not all inventory should be counted at the same frequency. ABC classification is the basis of any successful cycle counting inventory program, where SKUs are classified based on their value and velocity impact.
Manufacturers can use warehouse resources more effectively to improve inventory accuracy by focusing counting efforts on the most critical items.
A items should be counted with the greatest frequency, typically on a monthly or even weekly basis. These are high value, high velocity SKUs that typically account for only 10 to 20% of total inventory items but account for 70 to 80% of inventory value. Errors in this category can cause challenges such as production delays, missed customer shipments, stockouts, and inaccurate financial reporting.
B items are generally booked on a quarterly basis. These are moderate value, moderate velocity inventory items that make up approximately 30% of SKUs and 15 to 25% of inventory value. A-class items are more likely to cause an immediate interruption to operations, but B-item discrepancies should still be investigated.
C items are checked the least often and are usually counted once or twice a year. They typically represent approximately 5% of the total inventory value, but they often comprise 50 to 60% of all SKUs. These low value items are the best match with the traditional annual physical inventory. In this category it is often still possible to count infrequently and it is the only category where this holds.
ABC classification puts counting effort where an error costs the most
Cycle Count Best Practices Beyond ABC Classification
There are several best practices for inventory cycle counting that can help strengthen a cycle count program beyond ABC classification.
Control group counting
The control group cycle counting process involves the same small group of items being counted repeatedly to validate counting procedures prior to expansion of the program.
Blind cycle count
In the blind cycle count the ERP quantity is hidden from the counter. This avoids bias to the expected inventory balance.
Location-triggered counting
In the location-triggered counting method, a count is started when a receipt, pick, or transfer occurs, linking verification to a warehouse activity instead of a set calendar.
A items are counted 4-12 times per year, B items are counted 2-4 times per year, C items are counted 1-2 times per year. In the cycle count schedule, best practices can deliver better than 99% inventory record accuracy across the board in all inventory classes in 6-12 months, while consistent execution and world class cycle counting can help attain 99% inventory record accuracy.
Cycle Count Process: A Step by Step Guide
A cycle count is more than just walking the warehouse and counting shelves. This process has certain steps that can determine if the count is able to generate reliable data or if it is just a number written down by someone.
Create the count list
An ERP or WMS generates a list of locations and SKUs to be counted based on ABC classification and count frequency.
Inventory teams need to conduct a blind count. That is, system quantities are not visible to counters until the physical counting is done. This helps avoid bias and improves the accuracy of cycle counting inventory.
Perform the count
All units are physically checked by the counter in their location or SKU assigned during the count. This includes partial pallets, damaged units and items in staging areas.
Verification of lot numbers and serial numbers, where applicable, must also be done for regulated operations. A location count that does not verify lot identity may not meet traceability requirements for FSMA 204 or USDA operations.
Count vs system record comparison
Compare the physical count to the ERP inventory record. Deviations above thresholds are flagged for review.
Typical thresholds are 1-3% for A items and 2-5% for B items depending on the value of inventory and operating requirements.
Investigate the discrepancy
A second employee verifies any large discrepancy before any adjustment is posted.
If the discrepancy is confirmed, a root cause review is performed to determine why the inventory record was incorrect.
Adjustment after inventory
The ERP record is updated with the correct quantity once it is approved.
Adjustments are assigned reason codes like shrinkage, receiving error, picking error, damaged inventory or cycle count correction. The adjustment also makes the needed accounting entry.
Root cause analysis
The last step of an effective inventory cycle counting best practice is to identify why the errors occurred.
Common causes are receipts not being recorded, picks not being completed, inventory being moved without authority, and write-offs for damaged goods. The cycle count process is meant to achieve not just accurate records, but also the prevention of recurring errors.
Is Your Cycle Count Program Actually Running?
20 minutes. Tell us which ERP you run, how often counts are scheduled versus completed, and where your inventory accuracy sits today. We will show you where the program is leaking.
Inventory Accuracy: How to Measure, Formula, Benchmarks and KPIs
We measure inventory accuracy at the location level, not at the SKU level. An ERP that shows the right total quantity but has it split across the wrong locations is not accurate; a picker sent to the wrong bin will come up short.
Location-level accuracy, not SKU totals, is what a picker actually experiences
The most common formula for inventory accuracy is:
Inventory Record Accuracy (IRA) = (Number of locations with no discrepancy / Total locations counted) × 100
For example, if 95 out of 100 locations counted exactly match the ERP record, then the IRA would be 95%.
Some operations also have a formula based on units:
IRA = (Units counted matching ERP / Total units counted) × 100
Most manufacturers measure both location accuracy and unit accuracy. Location-based IRA will still consider a location inaccurate even if it only misses one unit, even if the variance is small, but has the right SKU.
What Counts as a Discrepancy
A discrepancy means any difference between what is physically present and what is recorded in the system, such as:
- Wrong quantity, even by 1 unit
- Incorrect lot number in lot tracked operations
- SKU physically available, but not in ERP record
- SKU in system, not in stock
Inventory accuracy KPIs vary based on operational maturity and industry standards. If the level drops below 85%, it will often lead to stockouts, phantom inventory and production delays.
Manufacturers without structured cycle-counting programs often achieve 85-95 percent accuracy. Good is 95-98% and 98-99.5% is expected for reliable forecasting, vendor managed inventory and automated replenishment. Scan based perpetual inventory systems or RFID typically achieve world class inventory accuracy of over 99.5%.
Inventory Accuracy Benchmarks
Where an operation sits, by cycle count maturity
In addition to IRA, important inventory accuracy KPIs are location accuracy rate, adjustment frequency, adjustment value and days to discrepancy detection. Monitoring these metrics can help determine if inventory problems are simply the result of counting errors or are symptomatic of larger process failures. A strong cycle counting program can reduce the time to detect discrepancies from an annual inventory event to days or weeks.
Let’s
Talk
Book your manufacturing AI strategy session
Inventory Adjustments and Reconciliation: How They Relate to the ERP
Inventory adjustment and inventory reconciliation are similar, but different processes.
- An adjustment balances a difference in quantity in the ERP.
- It updates the quantity on hand in the ERP for a specific SKU, location and lot.
- It is posted with a reason code and an automatic accounting entry is generated.
- Reconciliation verifies that the inventory subledger agrees with the general ledger.
- The dollar value of inventory in the ERP is consistent with the dollar value of inventory in the accounting system.
Reason Codes and the Journal Entry
Reason codes are important for root cause analysis and can be as follows: cycle count correction, receiving error, picking error, shrinkage damage, write off expired or obsolete inventory, and system error correction.
The journal entry for the inventory adjustment will depend on whether inventory is increased or decreased. If the quantity is lowered, inventory is credited, and a variance or shrinkage account is debited. If the quantity is increased, inventory is debited, and the offset is posted to a gain or correction account as per ERP configuration.
Each adjustment must have an audit trail with the person who made the adjustment, when it was made, the reason code and the supporting count record. Lot number should also be required for lot-tracked operations.
Cycle counting aids reconciliation with inventory records accurate before financial reporting. If the adjustments are coded properly and posted automatically, the inventory subledger and general ledger are in sync.
Without regular cycle counts and accurate reason codes, reconciliation becomes a manual investigation, not a simple verification step. The aim is to have a system where the right adjustments are made, the records stay in sync, and reconciliation is used to prove accuracy, not to find problems.
When Manual Cycle Counting Becomes the Bottleneck, and How Automation Changes It
Counts that are scheduled but never completed are the most common failure mode
Execution Consistency, Not Intent
- For mid-market manufacturers running ERP, the most common cycle counting failure is not bad intentions; it is execution consistency. Cycle counts get scheduled and not completed.
- Count sheets are filled in from memory rather than from physical counts. Adjustments are posted without root cause investigation. The program degrades.
Removing the Manual Steps Where Errors Occur
- Automation helps manufacturers improve inventory accuracy by removing the manual steps where errors usually occur. Automated cycle counting systems can generate count schedules based on ABC classification, time since the last count, or location activity instead of relying on spreadsheets and manual planning.
- Mobile scan-based counting allows employees to scan location and item barcodes using handheld devices, entering quantities directly into the ERP. This eliminates paper count sheets, manual re-entry, and transcription errors.
- Software can also enforce blind counts by controlling whether counters see system quantities before completing the count.
- Automated cycle counting also improves control by triggering recounts when discrepancies exceed configured thresholds. In addition, machine learning models can analyze ERP adjustment data to identify locations, operators, or product categories with recurring accuracy issues, helping teams focus root cause investigations where they matter most.
Scan-based counting posts the adjustment at the point of count confirmation
GrayCyan connects scan-based cycle counting directly to ERP inventory records, eliminating paper count sheets, batch uploads, and manual re-entry. Adjustment postings happen in real time at the point of count confirmation, with reason codes assigned from a mobile device.
The result is a cycle count program that runs without administrative overhead and produces adjustment data the ERP can use immediately for reconciliation.
A Fishbowl ERP distributor reduced manual inventory data entry by 85%, from 12 hours to under 2 hours daily, by connecting scan events directly to ERP transactions. Cycle count accuracy improved from 88% to 97% within the first quarter.
What a Fishbowl ERP distributor measured after connecting scan events to the ERP
Learn more about ERP inventory management and integration or explore custom WMS development to modernize warehouse operations.
Let’s
Talk
Book your manufacturing AI strategy session
FAQs: Cycle Counting and Inventory Accuracy
Not Getting the Inventory Accuracy Your ERP Should Provide?
If your cycle count program is inconsistent, your inventory accuracy is below 95%, or your month-end reconciliation requires manual journal entries, the issue is usually data entry, not the ERP itself. Tell us which ERP you run and where inventory accuracy is breaking down, and GrayCyan will show you what connecting scan-based cycle counting to your ERP looks like in practice.
