Count a defined item at a defined moment
A useful stock count specifies what is included, where it is located, which unit is counted and when movements are paused or separately logged. Otherwise, a perfectly careful counter can disagree with an equally correct screen because the two refer to different moments. Start with the cycle-count guide to define scope and ownership. Use the count worksheet to make arithmetic visible, then investigate the variance rather than treating the computed difference as permission to post it. A fictional record of forty units and a count of thirty-six creates a question about four units. It does not establish theft, loss, a receipt error or any other cause.
Trace exceptions through events and neighboring records
A negative balance, a failed integration or an unexplained adjustment is a symptom. Trace the specific item and event through the relevant order, receipt, transfer or return. Check timestamps and nearby records for duplicates before replaying an uncertain operation. The negative-stock and sync-troubleshooting guides focus on bounded investigation, while the count-variance guide separates an observed difference from a correction decision. Keep the original evidence, the proposed repair and the authorized outcome together. If the cause remains unknown, label it that way and control the affected workflow; an invented explanation makes the next investigation harder.
Treat replenishment inputs as assumptions to review
The reorder point and safety-stock guides explain how simple inputs change a purchasing trigger. Demand during lead time, stock already reserved and goods on order are different parts of the decision. The worksheet lets you inspect the arithmetic without presenting a result as a forecast or service guarantee. Use a fictional example first so everyone agrees on the definitions. Then decide which actual history is suitable, what unusual periods should be identified and who reviews changing supplier lead times. Slow-moving stock needs its own decision because buying more efficiently is not the same as deciding whether an item should be bought again.
Keep the evidence needed to recover and learn
A downloadable file is useful only if you know what it contains, what it omits and how you would use it after a problem. The export-and-recovery guide asks for a bounded recovery demonstration rather than assuming a full account restore exists. Retain appropriate non-sensitive records of material configuration changes and approved corrections, under your own retention and access rules. Review a small set of completed exceptions to see whether the same handoff keeps failing. If receiving units repeatedly cause differences, return to Prepare; if a feature cannot represent the required state, return to Choose. Control should improve the process that produced the number, not become a permanent queue of unexplained adjustments.