Cycle counting template and workflow

Cycle counting splits inventory checking into smaller recurring counts, so teams can verify selected locations, bins, and SKUs without one large shutdown.

Use this page when selected items, locations, or ABC groups need repeatable phone or worksheet counts, reason-code review, and pending-review closeout instead of a full shutdown.

Cycle count planner

Plan cycle count scope and cadence

Choose whether each scope covers a full location or named products only. The planner scores risk and capacity, then builds session exports with the correct completion, exception, review, and release proof.

Scope and risk

Scope name Count coverage SKUs or locations in scope Inventory value in scope Recent variance rate % Barcode coverage %

Delivery capacity

Available count sessions per week SKUs or locations per session

Schedule, queue, and counters Show due dates, eligibility, queue CSV, and counter rotation

Late-date policy

Count generated Maximum days before late Working days Serialized stock

Maximum days before late counts selected working days. Days between completed counts use calendar days, then roll to the next working day. Company holidays are not modeled.

Multiple scopes CSV (optional) Paste capacity columns. Add ABC class, intended cadence weeks, and planned sessions to check portfolio coverage; add scope type for mixed full-location and named-product rows. Counter names for session export (optional) Enter names separated by commas or new lines. Sessions rotate counters and add review capacity, device readiness, movement cutoff, release gates, reason-code capture, pending review, and sign-off fields.

Cycle plan summary

Priority class: -
Cadence: -
Sessions per cycle: -
Capacity fit: -

Next action:

Next assignment batches

Plan a count to generate session batches.

Plan a count to generate handoff notes.

Evidence captured in sessions CSV Show export and closeout fields

Assignment release: Review capacity, device fit and readiness, mobile menu and work sequence, queue test, movement cutoff, and counter assignment.
Floor count proof: Location confirmation, count origin and source work, blind-count release, serialized-stock confirmation, first-count sign-off, and offline fallback.
Scan and stock exceptions: Unexpected-stock rows, no-read and manual routes, tracking IDs, reason codes, condition or expiry review, and location exception evidence.
Recount and approval: Attempt limit and number, independent counter, completion time, pending-review decision, owner, and posting or recount reference.
Bin and movement release: Open exception rows, variance clearance, freeze and bin gates, supervisor review, and stock-move release timestamps.
KPI and cadence closeout: Counted and within-tolerance rows, accuracy, repeated reasons, root-cause owner, quotas, catch-up, and next-cadence approval.

Warehouse supervisors, retail operators, and stock count leads can download the sessions CSV for the complete field-level proof trail and write-in columns.

Suggested count plan (0 rows)

CSV generated in your browser

Cycle count preview scopes, priority classes, count schedule, and next supervisor action.

Choose the count scope

Start with a simple rule for what gets counted this cycle. High-value, fast-moving, and error-prone items should appear more often than slow movers.

A items weekly or monthly
B items monthly or quarterly
C items quarterly or annually
Problem locations after repeated variances

Choose cycle count when

Use cycle counting when inventory risk is targeted enough to fix while the operation keeps running. Move to a full physical count when accuracy is unknown across most stock or an audit needs complete coverage.

High-value, fast-moving, or shortage-prone SKUs need regular checks
Problem bins or repeated reason codes need root-cause follow-up
Transaction volume makes one annual count stale before the next review
The operation cannot shut down long enough for wall-to-wall inventory
Each scope can be counted, reviewed, and released inside the planned cadence

Run a mobile location check

For phone-based counts, make the counter confirm the place before the item. Scan or select the location, scan the item barcode, enter the counted quantity, then file cycle handoff proof before stock moves are released.

Verify aisle, shelf, or bin before counting
Scan the product barcode instead of typing the SKU
Use blind counts when counters should not see expected quantity
Hold damaged, expired, unknown, or open exception rows out of bin and freeze release until reviewed
Record mobile menu release, count origin, source work ID, pending-review owner, and release status with the cycle handoff

Keep the count list short

A cycle count list should be smaller and more focused than a full stocktake sheet, with only the fields needed to count and review the selected scope.

SKU
Barcode
Location or bin
Expected quantity when allowed
Counted quantity
Variance
Reason code

Set approval thresholds before counting

Decide before counting which reason codes are mandatory, which variances close inside tolerance, which rows need independent recount, and which pending-review rows need manager approval before posting. Keep the reason, approver, accept/reject decision, and posting or recount reference with the count pack.

Quantity and percentage tolerances
Dollar threshold for manager review
Detail-level approve or reject decision
Controlled recount attempt limits
Reason code captured before pending-review release

Printable cycle count SOP checklist

Print this one-page checklist before assigning a cycle count batch. It keeps the planner export, mobile menu release, count-origin and source-work proof, cycle handoff proof, bin-release proof, freeze-release proof, approval-threshold policy, accept/reject disposition, discrepancy closeout packet, and sign-off evidence in the same workflow.

Before counters start

Freeze or control stock moves for the selected scope and count window.
Confirm the exported session batch has scope, mobile menu release, directed-or-spot origin, source work ID, creator evidence, location verification, freeze-release gate, bin-release gate, blind-count rule, approval owner, recount limit, and root-cause cadence columns.
Open the assigned mobile menu, confirm the released work matches the scope or source work ID, test one location and item scan, and agree on the offline fallback before counters leave for the floor.
Assign counters and separate recount ownership from the first count when possible.
Prepare exception rows for missing barcodes, unknown locations, damaged stock, and moved stock.

At each location

Verify the aisle, shelf, bin, or locator before scanning the first item.
Scan the item barcode or mark the row as manual-count when the barcode is missing.
Enter counted quantity without viewing expected quantity when blind count is required.
Record a reason code immediately for found, missing, damaged, expired, moved, no-barcode, or scanner-blocked stock so pending review can accept, reject, or open recount work.
Release the bin only after open exception rows, movement cutoff, counter sign-off, and supervisor review are recorded.

Review and close discrepancies

Recount rows that cross the quantity, percent, or value threshold, then confirm the reason code, attempt number, and approval owner before pending-review release.
Create a discrepancy packet for each open variance with first count, independent recount, reason code, root-cause owner, correction amount, and approval status.
Approve valid detail rows, reject only the rows that need recount, and record accepted posting references or rejected recount work IDs before posting inventory changes.
Post corrections only after the ERP adjustment reference, approval owner, and posting date are recorded.
Review repeated reason codes at the exported root-cause cadence and assign prevention work before stock moves are released.
Store the exported session CSV, discrepancy packets, freeze-release proof, bin-release proof, variance review, and signed checklist with the count pack.

Count pack sign-off

Counter Supervisor Cycle scope/source work Count date Count origin/threshold checked Root-cause owner assigned Discrepancy packet complete Stock moves released Adjustment reference recorded

Use this checklist with the cycle planner's session CSV so paper supervision, phone scanning, count origin, source work, freeze release, bin release, reason-code approval, recount attempts, discrepancy packets, and root-cause reviews follow the same evidence trail.

Continue mobile counts with Mobile Inventory.

Workflow

Workflow steps for Cycle counting template and workflow
Step	Action	Details
Step1	ActionSelect scope	DetailsPick SKUs, bins, categories, or ABC classes for this cycle.
Step2	ActionPrepare list	DetailsGenerate a focused template or CSV with stable SKU, barcode, and location columns.
Step3	ActionVerify location	DetailsScan or select the aisle, shelf, or bin before counting items in it.
Step4	ActionCount items	DetailsScan the item barcode, enter quantity, and add a reason or note when the row is unusual.
Step5	ActionReview variances	DetailsClose rows inside tolerance, recount rejected detail rows, and approve only rows that cross your quantity, percent, value, reason-code cluster, or recount-attempt thresholds.
Step6	ActionRelease and schedule	DetailsUnfreeze stock moves after exceptions and root-cause actions are cleared, then set the next cycle.

Stock count glossary

SKU

A stock keeping unit: the internal item code used to identify one product or variant.

Barcode

A scannable code such as UPC, EAN, or GTIN that should point to one item or package.

Variance

The difference between expected quantity and counted quantity after a stock count.

Cycle count

A recurring count of selected items, locations, or categories instead of the whole inventory.

Blind count

A count where counters do not see the expected quantity while entering the physical quantity.

Cutoff time

The point when stock movements are paused or controlled so the count matches system data.

Download tools

Stock count template Editable worksheet for counts and variances. Barcode readiness checker Check whether your item list is ready to scan. Variance reviewer Classify recount and approval rows after counting.

FAQ

Is cycle counting the same as a physical inventory count?

No. A physical inventory count usually covers all stock at one point in time. Cycle counting checks smaller groups on a recurring schedule so the team can fix targeted risk without a full shutdown.

When should I choose a full physical count instead?

Choose a full physical count when auditors, year-end close, a system migration, or a major location reset requires complete point-in-time coverage. Use cycle counts when targeted scopes can be counted, reviewed, and released repeatedly.

What should I count first?

Start with high-value, fast-moving, or error-prone items because those differences usually matter most.

Can cycle counts use barcodes?

Yes. Barcode scanning is useful because cycle counts are repeated often, location accuracy matters, and speed affects how often the team can count.

How should I use reason codes after a cycle count?

Capture the reason while the row is still pending review. Group reasons by item, location, session, and no-barcode route; then accept, reject, or open recount work before posting and assign root-cause action when the same reason repeats.

Should counters see the expected quantity?

Use blind counts when you want the physical count to be independent. Show expected quantity only when the workflow needs faster confirmation and a manager accepts the bias risk.