Stock Counts & Adjustments

Keep recorded stock matching reality — count it, explain the variance with a reason, and adjust under control.

4 lessons 35 min 5-question assessment 70% to pass

What you’ll learn

Explain why physical counts keep inventory trustworthy

Run cycle counts without halting the business

Record variances with reason codes

Make controlled adjustments and write-offs

Lesson 1 of 4 Reading 8 min

Why count at all

Recorded stock drifts from reality over time — breakage, miscounts, theft, and unrecorded movements all create gaps. A stock count compares what the system says against what is physically on the shelf, so the record can be corrected to the truth.

Counting is not an admission of failure; it is routine hygiene. Every accurate count rebuilds trust in the numbers that drive purchasing, selling, and finance.

Count blind to keep it honest: have the counter record the physical quantity without seeing the system figure first, then enter it for AWRA to compute the variance. If counters can see “system says 40,” the lazy ones simply confirm 40 and the whole exercise proves nothing. The point is to discover the gap, not to rubber-stamp the record.

Key takeaways

Recorded stock drifts from reality over time.
A count compares system figures against physical stock.
Regular counting rebuilds trust in the numbers.
Count blind — record physical quantities before seeing the system figure, or counters just confirm the number.

Lesson 2 of 4 Reading 9 min

Cycle counts vs full counts

A full count checks everything at once — thorough, but it usually means stopping operations. A cycle count checks a slice of stock on a rolling schedule, with high-value items counted more often, so accuracy is maintained continuously without shutting the business down.

Cycle counting spreads the effort and catches problems sooner. Instead of one big annual shock, you get small, frequent corrections that are easier to investigate.

A practical cadence is ABC-based: count your high-value or fast-moving “A” items monthly, “B” items quarterly, and the long tail of “C” items once or twice a year. That way the stock that carries the most cash and the most theft risk is checked often, while you don’t burn the team counting cheap, slow-moving items every week. AWRA’s reason and variance history per item tells you which class each SKU belongs in.

Key takeaways

A full count checks everything but usually halts operations.
A cycle count checks a rolling slice on a schedule.
Cycle counts catch issues sooner with less disruption.
Count by ABC cadence — high-value items monthly, the cheap long tail rarely — to focus effort where the cash and risk sit.

Lesson 3 of 4 Practice 9 min

Variance and reason codes

When the count differs from the record, that gap is the variance. AWRA lets you attach a reason code — damage, theft, miscount, expiry — so an adjustment is never just a silent number change. The "why" is captured alongside the "what".

Reason codes turn variances into information. Patterns become visible: if "damage" keeps appearing in one location, that is a process problem worth fixing, not just a number to correct.

Resist the default to “miscount” for everything — it is the reason code that explains nothing and lets real problems hide. If the same SKU shows a steady monthly shortage all coded “miscount,” that is far more likely theft or an unrecorded sale than a counter who can’t add. Reserve “miscount” for genuine counting errors and you keep the report meaningful.

Key takeaways

Variance is the gap between counted and recorded stock.
Reason codes record why an adjustment happened.
Reason patterns reveal process problems to fix.
Don’t default everything to “miscount” — a recurring shortage so coded usually hides theft or unrecorded sales.

Lesson 4 of 4 Reading 9 min

Controlled adjustments and write-offs

An adjustment corrects on-hand to match reality; a write-off removes stock that is gone or unsellable. Because both change inventory and can touch finance, they are controlled — recorded, attributed, and, for larger changes, subject to approval.

Control is what separates a legitimate correction from a cover-up. Every adjustment leaves a trail showing who changed what, by how much, and why — so honesty is the easy path.

Set the approval threshold by value, not just quantity, and never let the same person both count and approve their own large write-off — that combination is exactly how shrinkage gets quietly “corrected” away. A reasonable rule: the counter records the variance, a supervisor approves anything above a set value, and the adjustment posts only once approved. Separation of these two roles is the control; the trail is just the evidence.

Key takeaways

An adjustment corrects on-hand; a write-off removes lost or unsellable stock.
Both are recorded, attributed, and can require approval.
The trail makes legitimate corrections easy and cover-ups hard.
Separate counting from approval — never let one person both record and sign off their own large write-off.

| AWRA OpsHub

Stock Counts & Adjustments

What you’ll learn

Course content

Why count at all

Cycle counts vs full counts

Variance and reason codes

Controlled adjustments and write-offs

Finished the material?

More in this path

Inventory Foundations

Warehouse & Locations

Operations Data Model

Need a quick answer while you read?

AwraIQ