Know where counts drift
Most stock gaps come from ordinary movements that do not look important in the moment. A return gets placed on a shelf before it is checked. A damaged unit is set aside. A sample leaves the building. A transfer happens between locations and nobody records it.
- Sales and refunds update the count, but damaged or returned items may not.
- New stock is counted when ordered instead of when received.
- Bundles, samples, or replacements leave stock without a clear reason code.
- Multiple people edit the spreadsheet without the same rules.
Keep one working record
Pick one place where the team expects the current count to live. A spreadsheet can still be useful as an export or planning copy, but the operating count should not split across several files, notes, and messages.
Record non-sale movement with reasons
Stock changes need simple reasons: return received, damaged, sample, transfer, correction, or supplier issue. The reason does not need to be complicated. It needs to be quick enough that the team actually records it while the movement is fresh.
| Movement | Why it matters |
|---|---|
| Return received | Separates sellable stock from items that need review. |
| Damaged item | Prevents broken or worn stock from being counted as available. |
| Transfer | Keeps locations from drifting in opposite directions. |
| Correction | Creates a place to investigate repeated gaps. |
Use cycle counts instead of one big review
A cycle count means checking a small group of products on a regular schedule. Counting ten or twenty SKUs each week catches drift while it is still small enough to understand. Waiting for one large review makes every gap harder to trace.
What this guide is not saying
This is an operating habit, not a promise of perfect counts. It helps small teams keep product records, stock movements, and physical counts close enough for daily decisions.