A recurring inventory verification method where selected items are counted on a schedule instead of doing a full physical count.
Cycle counting is an inventory verification method in which a subset of items is physically counted on a recurring schedule, rather than stopping operations to perform a single, full physical inventory. The objective is to detect and correct inventory record discrepancies continuously, while keeping production and warehouse operations running.
In industrial and manufacturing environments, cycle counting is commonly managed through an ERP, warehouse management system (WMS), or inventory module integrated with MES or shop-floor systems.
In typical regulated or complex manufacturing environments, cycle counting:
– **Selects items or locations** based on rules such as ABC classification, transaction volume, value, criticality, or past error history.
– **Issues count tasks** to operators (often handheld or terminal-based) indicating what to count, where, and when.
– **Captures actual quantities** observed on the shop floor, in stockrooms, tool cribs, or warehouses.
– **Compares physical counts to system records** in ERP/WMS and records variances.
– **Triggers investigation and adjustment** when discrepancies exceed defined tolerances, including root cause analysis of process or data issues.
Cycle counting can be location-based (count everything in a selected area), item-based (count specific part numbers wherever they are), or process-based (e.g., count after specific process steps or events).
Cycle counting:
– **Is a control activity**, focused on verifying and correcting inventory records.
– **Does not replace** the need for sound material control processes (e.g., accurate issue, return, and scrap transactions) or formal change control.
– **Is not the same as** a full physical inventory, where all items are counted within a short time window, often requiring shutdown or freeze of inventory movements.
– **Does not inherently prove compliance** with any regulatory or financial standard; it is one technique that may support internal control frameworks.
In regulated or high-complexity manufacturing (such as aerospace, pharmaceuticals, or medical devices), cycle counting is often structured to support:
– **Traceability requirements**, by ensuring serialized or lot-controlled materials in ERP/MES match actual physical stock.
– **Reconciliation between systems**, for example where ERP inventory balances must stay aligned with MES or shop-floor tracking.
– **Controlled production areas**, where counts may be constrained by cleanroom, secure-storage, or export-control rules.
Cycle counting tasks may be scheduled to avoid disrupting critical operations, while still providing enough coverage to detect systemic issues.
– **Cycle counting vs. physical inventory**: Physical inventory counts all items over a short period, often with a freeze on transactions. Cycle counting spreads counts over time and usually occurs while operations continue.
– **Cycle counting vs. perpetual inventory**: Perpetual inventory refers to continuously updated system records based on transactions. Cycle counting is a way to validate and correct those records, not a transaction method itself.
– **Cycle counting vs. spot checks**: Spot checks are ad hoc counts, usually triggered by suspicion or a specific event. Cycle counting is systematic and scheduled.
In the context of inventory inaccuracies in manufacturing (including aerospace), cycle counting is often used to:
– Detect issues such as unrecorded material moves, mis-kitted parts, or incorrect scrap transactions.
– Reveal misalignment between ERP, MES, and actual shop-floor practices.
– Provide data for root cause analysis when recurring variances are found for particular items, locations, or processes.
The effectiveness of cycle counting depends on disciplined execution and on addressing underlying process and integration issues uncovered by the counts, not solely on performing more frequent counts.