# Item States

An item state is a classification applied to count events. In Kanoa Ops, the most common use is waste reason coding: a waste count tells you *how much* waste occurred, and an item state tells you *why*.
For example, a packaging line might record waste for reasons such as Bad Coating, Insufficient Coating, Damaged Parts, Cosmetic Defect, or Incorrect Item. This gives the quality component of OEE much more detail than a simple waste count.
This can be used by operators to code scrap reasons or when connected directly to a plc, to automatically set bottles kicked off a bottling line for say 'Low fill level' or 'Missing bottle cap'. 
It can also be used to differentiate between say 'First Pass' and 'Rework' on infeed counts.

## Categories, counter types, and links

- **Categories** organize item states into a hierarchy, just as state categories do for downtime.
- **Counter type association**: item states can be associated with counter types. For waste coding, associate them with waste count events, which tells Kanoa these reasons are appropriate when recording waste.
- **Linking**: like states, item states can be linked to the assets or items where they apply, so operators don't see irrelevant waste reasons on unrelated assets.

![scrapReasons](https://kanoa-software.netlify.app/img/asset-operation/scrapReasons.png)

Items States are configurable via the **Configuration > Ops > Item States**

![itemStateConfig](https://kanoa-software.netlify.app/img/asset-operation/itemStatesConfig.png)