A warehouse management system may show 240 units available, while the warehouse team can only locate 231.
The missing nine units are the immediate problem. The larger issue is determining where the discrepancy began.
The shipment may have been received incorrectly. A pallet, case or unit conversion may be wrong. Some products may be stored in another location, recorded as sellable after being damaged or still tied to an incomplete return.
This is why reliable inventory control cannot depend only on the quantity displayed in a system.
Cycle counting helps warehouses identify inventory discrepancies throughout the year before they affect order fulfillment. In a 3PL environment, however, an accurate count means more than confirming the total number of units.
The warehouse must also verify:
- Which client owns the inventory
- Which SKU and unit of measure are being counted
- Where the products are stored
- What condition they are in
- Whether they are actually available for fulfillment
A reliable cycle count preserves all of that context.
What Is Cycle Counting?
Cycle counting is the practice of regularly counting selected inventory instead of waiting for one complete annual physical inventory count.
During a cycle count, the warehouse selects specific SKUs, storage locations or inventory categories. The physical quantity is then compared with the amount recorded in the warehouse management system.
If the quantities do not match, the warehouse should confirm the count, investigate the discrepancy and document any approved adjustment.
Oracle’s guidance on cycle counting describes it as a recurring inventory control process used to identify differences between physical and recorded quantities. Patterns in those differences may also reveal problems in warehouse processes, tools or staff training.
The objective is not simply to correct a number.
A cycle count should help determine:
- Whether the inventory record is accurate
- Why the discrepancy occurred
- What needs to change to reduce the chance of the same problem recurring
Where Inventory Discrepancies Usually Begin
Inventory discrepancies often develop through small errors across several warehouse activities rather than one major failure.
Receiving errors
A shipment may arrive short, damaged or labelled incorrectly. If the expected quantity is entered before the actual shipment is verified, the inventory record begins with the wrong number.
The receiving process should confirm quantities, SKUs, packaging condition and visible exceptions before inventory becomes available for fulfillment.
Pallet, case and unit conversions
3PL warehouses often receive, store and ship the same product in different units of measure.
A shipment might contain:
- 40 cases per pallet
- 12 units per case
- Individual units sold through eCommerce orders
If the system incorrectly records one case as one unit, the resulting discrepancy can be much larger than a simple counting mistake.
Unrecorded inventory movements
Products may be moved between storage locations, staging areas or picking zones without the location update being completed.
The inventory is still physically in the warehouse, but the system no longer identifies where it can be found.
Picking and transaction timing
Inventory can appear inaccurate when a physical movement and its system transaction are completed at different times.
For example, products may already have been removed for an order while the WMS still shows them in the original location.
Damaged and returned inventory
Returned products should not automatically re-enter sellable inventory.
They may require inspection, repackaging, relabelling or segregation before their status is confirmed. A structured returns management process helps keep sellable, damaged, returned and quarantined inventory separate.
The total physical quantity may be correct while the quantity available for customer orders is still wrong.
How a Reliable Cycle Count Should Work
The exact procedure depends on the warehouse and inventory profile, but a controlled cycle count generally follows five stages.
1. Select inventory based on risk
Warehouses may select SKUs or locations based on:
- Product value
- Order frequency
- Previous discrepancies
- Damage or shrinkage risk
- Return volume
- Customer requirements
- Time since the previous count
Not every product requires the same counting frequency.
2. Control inventory movements
Receiving, picking, replenishment and location transfers can change inventory while it is being counted.
The warehouse should establish a clear transaction cut-off or temporarily restrict movements involving the selected inventory. Physical stock and system records must represent the same point in time.
This is particularly important in a 3PL facility where inbound receiving and outbound fulfillment may continue throughout the day.
3. Perform the physical count
The selected inventory is counted using the correct unit of measure, whether that is pallets, cases or individual units.
Some warehouses use blind counts, meaning the employee does not see the quantity expected by the system before completing the count. This reduces the risk of unconsciously adjusting the physical result to match the expected number.
4. Recount and investigate discrepancies
A mismatch should not immediately trigger a system adjustment.
The warehouse should first confirm the result and review relevant records, including:
- Receiving documents
- Pick and pack transactions
- Location transfers
- Damage reports
- Returns
- Open orders
- Previous inventory adjustments
- Unit-of-measure settings
IBM’s cycle counting guidance separates the physical count from reconciliation. The recorded balance should be reviewed before an adjustment is approved.
5. Approve adjustments and record the cause
Once the discrepancy has been confirmed, an authorized inventory adjustment can align the system record with the physical count.
The reason should also be documented. Otherwise, the warehouse may repeatedly correct the same SKU without addressing the receiving, storage, picking or returns issue causing the discrepancy.
What Cycle Counting Looks Like in a 3PL Warehouse
Cycle counting becomes more complex when a warehouse manages inventory for multiple clients.
A reliable 3PL cycle count should verify more than the total number of units.
Client ownership
Similar products or packaging may belong to different clients.
The count must confirm the correct customer account, SKU and inventory record. Products should not be treated as interchangeable simply because they look alike.
Inventory status
Suppose a warehouse physically holds 100 units:
- 82 are sellable
- 8 are damaged
- 6 are returned and awaiting inspection
- 4 are quarantined
A count of 100 is technically correct, but the warehouse does not have 100 units available for fulfillment.
Physical quantity, condition and system status must all agree. Otherwise, the WMS may overstate the quantity that can actually be allocated to customer orders.
Unit of measure
The count must clearly identify whether the warehouse is counting pallets, cases or individual units.
This matters when B2B orders ship by pallet, wholesale orders ship by case and eCommerce orders ship by individual item.
Open transactions
Inventory may be:
- Received but not yet put away
- Picked but not yet shipped
- Moved to a staging area
- Reserved for an order
- Awaiting returns inspection
These open transactions need to be reviewed before a discrepancy is confirmed.
Discrepancy reporting
A reliable 3PL should not simply treat an inventory adjustment as the end of the process.
Depending on the warehouse system, reporting workflow and service agreement, the supporting record may include:
- The SKU and location counted
- The system quantity
- The physical quantity
- Any recount result
- The inventory status involved
- The approved adjustment
- The identified or suspected cause
This context can help determine whether the discrepancy was an isolated event or part of a recurring operational problem.
Which Inventory Should Be Counted More Often?
Many warehouses use ABC cycle counting to assign different counting frequencies to different groups of inventory.
Under this method:
- A items are counted most frequently
- B items are counted at a moderate frequency
- C items are counted less often
The classification does not need to depend only on product value.
A lower-cost item may still require frequent cycle counts if it moves quickly, has a history of discrepancies or is operationally important to customer orders.
Oracle’s cycle count criteria guidance allows count schedules to be organized by ABC classification or product category, with higher-priority inventory counted more frequently.
The correct frequency depends on how the inventory moves and what happens when the record is wrong.
Cycle Counting, Stocktaking and Inventory Audits
These terms are related, but they do not describe the same process.
| Method | Primary purpose | Typical scope |
| Cycle counting | Ongoing inventory accuracy and discrepancy detection | Selected SKUs or locations |
| Stocktaking or stocktake | Physical inventory snapshot at a specific time | All or most inventory |
| Inventory audit | Review of inventory records, controls and financial reporting | Quantities, procedures, documentation and valuation |
Cycle counting is integrated into ongoing warehouse operations.
Stocktaking usually involves a broader physical inventory count and may require warehouse activity to be reduced or temporarily suspended.
An inventory audit can include physical counts, but it may also review inventory ownership, adjustment approvals, supporting documents, damaged goods and financial inventory values.
A business may use cycle counting throughout the year and still conduct a complete stocktake or inventory audit when required.
Why Inventory Accuracy Matters Beyond the Warehouse
An inventory discrepancy does not stay inside the warehouse.
It affects sales when a team commits inventory that cannot be located. It affects purchasing when replenishment decisions are based on incorrect quantities. It affects customer service when orders must be delayed, changed or cancelled.
For retail suppliers, inventory accuracy also affects how quickly they can answer buyer questions and confirm replenishment quantities.
As discussed in Transnova’s article on inventory replenishment pressure for Canadian suppliers, businesses need to distinguish between inventory that is available, reserved, damaged, inbound or ready to ship.
Cycle counting helps test whether those records can be trusted.
It also supports the wider fulfillment process. Receiving, storage, picking, packing, shipping and returns all depend on accurate information about what is physically present and available. Transnova’s overview of what happens inside a fulfillment centre explains how these warehouse activities connect.
What Businesses Should Ask Their 3PL
When inventory is managed by a third-party logistics provider, businesses should understand how counts and discrepancies are handled.
Five useful questions are:
- How are SKUs and locations selected for cycle counts?
- How are inventory movements controlled during a count?
- What happens when the first count does not match the WMS?
- Who can approve an inventory adjustment?
- What count, adjustment or discrepancy information is available to the client?
A response such as “the system tracks everything” is not enough.
A WMS records transactions, but it cannot guarantee that every physical movement, quantity, location, and inventory condition was entered correctly.
Reliable inventory control depends on both the system and warehouse procedures.
Build Inventory Accuracy Into the Fulfillment Process
Cycle counting is most effective when it forms part of a wider inventory control process.
Receiving needs to establish an accurate starting quantity. Pallet, case and unit conversions need to be configured correctly. Inventory movements need to be recorded. Returned and damaged products need clear statuses.
The cycle count then tests whether those processes are working as intended.
Transnova provides Canadian warehousing and fulfillment services for businesses managing eCommerce, retail and cross-border inventory.
When inventory records are becoming difficult to reconcile, the answer is not simply to count more often. The receiving, storage, returns and fulfillment processes behind the discrepancies also need to be reviewed.
Contact Transnova to discuss your inventory requirements and the warehouse processes supporting them.
FAQ
What is a cycle count?
A cycle count is a recurring physical count of selected inventory. The result is compared with the warehouse management system to identify and investigate discrepancies.
How often should cycle counting be performed?
Cycle counting frequency depends on product value, order volume, discrepancy history, return activity and operational risk. High-value, fast-moving or frequently inaccurate inventory is generally counted more often.
What is the difference between cycle counting and stocktaking?
Cycle counting checks selected inventory throughout the year. Stocktaking usually involves counting all or most inventory at one defined time.
What happens when a cycle count finds a discrepancy?
The warehouse should confirm the count, review the relevant transaction and inventory records, identify the likely cause and obtain authorization before adjusting the system balance.