Run inventory cycle counts with a clearer review path.

01 / Prepare the count

Decide what the count will actually cover.

A useful cycle count has a defined boundary. Start with a manageable group of items or locations and describe the conditions under which the count will be taken. The goal is a traceable observation, not a number detached from its timing and context.

• Which items, variants, locations, and storage areas are in scope for this count?
• What count window will reduce movement, and how will sales, receiving, transfers, returns, or damage be noted during it?
• Which unit of measure should the counter use, and where are pack sizes or substitutions likely to cause confusion?
• Who will count, who can answer product questions, and who is responsible for reviewing and approving a discrepancy?
• What source context will be available, such as the last recorded quantity, recent movements, or an approved receiving record?

Write down the count scope and pause conditions before anyone begins. If movement, identification, or source context cannot be understood, mark the uncertainty and have the reviewer decide how to proceed.

02 / Count carefully

Make the observation reproducible.

Counting is more than entering a quantity. It includes identifying the right item and unit, following a repeatable path, and keeping exceptions visible. A second person or a second pass may be appropriate for higher-risk items, but the process should say who checks what and why.

Identify the item

Read the item name, SKU, variant, unit, and location before writing a quantity. Do not combine similar-looking items.

Count systematically

Use a consistent path through the shelf, back room, or other area and mark counted sections to avoid omissions or repeats.

Capture exceptions

Note damaged, opened, unlabelled, reserved, in-transit, or otherwise uncertain stock instead of silently forcing it into a total.

Record movement

Write down sales, receipts, transfers, returns, or other movement that occurs during the count window and who observed it.

03 / Record the evidence

Keep the count beside the context that explains it.

A quantity without an item, location, unit, timestamp, or source context is difficult to review. Keep the original count and notes available even if the team creates a more organized summary later.

Count identity

Item, variant, location, unit of measure, count date, and count window.

Observed quantity

The quantity actually counted, including a separate note for uncertainty or excluded stock.

Source context

The record or event used for comparison, its date, and whether it was confirmed or still pending.

People and review

Counter, reviewer, approval status, corrections, and any unresolved question.

04 / Reconcile discrepancies

Investigate an apparent difference before explaining it away.

A difference between a count and another record is a prompt for investigation, not proof of shrink, a counting mistake, or a required adjustment. Compare like with like, trace the timing, and keep the unresolved state visible until someone can explain it.

• Confirm that the item, variant, location, and unit match on both sides of the comparison.
• Check count timing against sales, receiving, transfers, returns, damage, and other movement during the window.
• Trace the source context to the record or person that can confirm it; do not treat a missing source as zero movement.
• Separate a counting error, timing difference, data-entry issue, location issue, and unexplained difference rather than collapsing them together.
• Record what was checked, what was corrected, what remains uncertain, and who owns the next review.

A flagged discrepancy is not a verified discrepancy. The reviewer needs the original count, the source context, the apparent difference, and the explanation or remaining uncertainty before approving a resolution.

05 / Human control

Verify before changing any inventory record.

Treat this as a control in the workflow, not a disclaimer added after the fact. Record who verified the evidence, what they approved or corrected, and what remains unresolved. If the count or source context cannot be verified, leave the record unchanged until the responsible person decides what happens next.

06 / Follow up

Close the loop and improve the next count.

Once a person has verified the evidence and approved a resolution, preserve the trail and look for process changes that could make the next count easier to understand. The follow-up may be a correction, a training note, a location-label change, a timing change, or a decision to leave the question open.

• Document the approved resolution and the evidence supporting it.
• Have the responsible person make any permitted inventory change only after verification and approval.
• Keep the original count, notes, source context, discrepancy explanation, and reviewer identity together where the team can find them.
• Look for repeat causes such as unclear locations, unit confusion, receiving delays, or movement during count windows.
• Choose the next cycle-count scope and timing from observed needs, not from an assumed accuracy or savings target.

07 / Keep the scope honest

Limits and practical checklist.

This is a planning guide, not an inventory policy, accounting standard, system specification, or promise of accuracy, savings, availability, fewer discrepancies, better margins, or any other outcome. Results and risks depend on the retailer’s records, process, products, people, and review decisions. It makes no claim about a third-party integration or a particular tool.

Want to discuss a cycle-count workflow? Share the context through an inquiry. Start with the process and its review boundaries, not a predetermined tool or outcome.