Cycle count investigation and reconciliation

A useful count starts with a warehouse, a count type, and lines that reflect a real operational question. The runtime expects Count Number, Warehouse, Count Date, Count Type, and then line-level detail such as Product, Bin, Lot, Serial Number, System Qty, and Counted Qty. That is not paperwork. It is the evidence set the reviewer will use later.

Teach the team to choose the count type deliberately. A cycle or spot count should target risk areas and movement-heavy locations. A blind count should be used when independence matters more than convenience. A full count should be reserved for broad verification, not casual routine.

Evidence should come from cockpit signals, balances, lots, serials, transactions, cost layers, reservations, transfers, adjustments, counts, receiving, putaway, scans, or audit history. For Start the count with a real scope, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

The runtime enforces a controlled sequence: draft counts can be submitted, submitted counts can be approved, and only approved counts can be posted. That matters because the business should not treat observation, review, and final stock correction as the same click.

Teach learners to use those gates intentionally. Submit when the scope and lines are ready for review. Approve when the recorded quantity is defensible. Post only when the team can justify why the ledger now needs correction.

For Submit, approve, and post are different decisions, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

The Audit tab is where the count becomes explanation instead of a discrepancy. Warehouse Reconciliation View lets the team load a Product and Warehouse scope, then inspect On Hand, Reserved, Available, Layer Stock Value, and Open Cost Layers before anyone posts a variance.

That is the correct place to ask whether the problem is only a physical quantity gap or whether the warehouse also has a valuation or reconciliation inconsistency. A count should make the stock story clearer, not just force the total to match what someone wants to see.

Use this section to confirm the learner understands more than the page label. They should connect Audit explains the gap before the ledger changes to the business state, owner, and consequence behind it.

Receiving Sessions and Putaway Tasks are part of count diagnosis because inbound stock may still be under QC review or waiting for final bin confirmation. If the item never cleared those stages, the count may be detecting a process delay instead of unexplained shrinkage.

Mobile Scanning and Control Tower then explain whether scan-confirmed picks, putaways, or exception spikes caused the drift. If the issue is recurring, Rollout Controls also matters because the tenant may not have had the same WMS behavior enabled when the stock movement occurred.

Use this section to confirm the learner understands more than the page label. They should connect Check inbound and execution evidence before posting to the business state, owner, and consequence behind it.

A good count does more than post a gain or loss. It leaves a traceable record of the scoped lines, the approved variance, the reconciliation evidence, and the operational reason the difference existed in the first place.

That is when cycle counting becomes useful management signal. The team can see whether the underlying failure was inbound staging, delayed putaway, poor scan compliance, exception buildup, or another repeatable process weakness.

For What good looks like after reconciliation, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Run the lesson as a stock-evidence investigation. Start with the practical task: prepare a count with the right warehouse scope, count type, and line-level evidence before status changes begin. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from cockpit signals, balances, lots, serials, transactions, cost layers, reservations, transfers, adjustments, counts, receiving, putaway, scans, or audit history. The practice should end with the learner connecting the action back to the lesson summary: teach inventory teams to run a count as a controlled workflow: start the count, record the scoped lines, move it through submit and approve, and only post variance after audit, receiving, putaway, and scan evidence explains the gap.

Close the exercise by asking the learner to restate the objective in operational terms: prepare a count with the right warehouse scope, count type, and line-level evidence before status changes begin. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not let learners correct stock before they can explain the stock state. Quantity, location, value, movement source, and audit evidence should be checked before action. In this lesson, watch for that risk while learners work on this objective: prepare a count with the right warehouse scope, count type, and line-level evidence before status changes begin.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain which fields and lines must exist before a count should move beyond draft and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot explain which fields and lines must exist before a count should move beyond draft, keep the lesson in practice mode before marking it complete.