Adjustment reasons
Every manual stock adjustment records why. The reason is chosen from your organisation's list.
The five you start with
Every new organisation is given these:
| Reason | Typically used for |
|---|---|
| Correction | The record was wrong and is being put right |
| Cycle count | A count found a discrepancy outside the formal count process |
| Damage | Stock damaged and no longer sellable |
| Found | Stock discovered that was not on the books |
| Return | Stock coming back |
You can add your own, and change which are in use.
Where they are managed
Under organisation settings, not in Inventory. Needs organisation-admin access.
Worth knowing, because the picker on the adjust screen gives no clue where its contents come from — see add an adjustment reason.
Direction
A reason carries a direction, controlling whether it applies to increases, decreases, or both.
It keeps the picker honest: Damage should not be offered when someone is adding stock, and Found should not be offered when they are removing it. A reason set to both appears either way.
Deactivating rather than deleting
A reason no longer in use can be deactivated. It stops appearing in the picker, and past adjustments keep it.
That is the right behaviour: deleting a reason would strip the explanation from every adjustment that used it, which is exactly the information you would want when reviewing a year later.
Why the reason matters
An adjustment without a reason is unreviewable. "Someone changed this by minus twelve" tells you nothing; "minus twelve, damage" tells you what happened and whether it should have.
The movement history filters by reason, so a pattern — repeated damage at one location, frequent corrections on one variant — becomes visible. See review stock movements.
Not the same as a count
A stocktake discrepancy is recorded as a count gain or count loss, not as an adjustment, and carries no adjustment reason. The two are deliberately distinguishable — see stock movement types.
The Cycle count reason is for a discrepancy handled outside the formal count process, which is a different thing from a count task's own result.