Serialized items – a series of 6 articles. Read them in this order:
What you’ll learn
What a serialized item is, how each serial number moves from New through picks, returns and service, and the seven statuses it can hold. Start here before the other parts of the series.
When an item is set as serialized, the Serialized item tab appears on the item and lists every serial number that exists, with its current location and status.
What a serialized item is
A serialized item is a durable item where every unit has its own serial number. CRIBWISE then tracks each unit separately: who picked it, the condition it came back in, when it is due for service, and its own documents and history.
Use it for tools where you need to know which unit is where, such as gauges that are calibrated or holders that are serviced after a number of uses. For items you only need to count, a normal item is enough.
- Durable items only. A consumable item cannot be serialized.
- Set it while the item is Defined. Serialized locks as soon as the status changes to Phase in or Released, see Serialized items: Setup.
- Condition and status are the same thing. The Shop Floor Interface calls it the condition, the Admin Portal the status.
The life of a serial number
Every serial number goes through the same cycle. The Shop Floor Interface sets each status as you work, so nobody has to maintain them by hand.
The six stages of a serial number. The Setup, Picking, Returning and Service articles of this series walk through them on the Shop Floor Interface.
Serialized item statuses
| Status | Set when |
| New | The default. The item was restocked from a purchase order, or the instance was created during assignment. It has not been used in production yet. |
| Used | The item has been picked and returned as used. |
| Refurbished | Service has been performed. Set when the item is restocked from service. |
| Scrapped | The item cannot be used any more – returned as scrap, scrapped from a service order or list, or the loan time was exceeded with an auto scrap period. |
| For service | The item was returned for service, or automatic service rules triggered it. It is not offered for pick, and it can be added to a service list or service order. |
| In assembly | The item was picked to create a new assembly. It is a permanent part of that assembly and cannot be picked or serviced separately. |
| In service | The item is currently picked for service against a service list or service order. |
Each serial number also has its own detail page in the Admin Portal, with its service dates, documents, transaction history and comments. It is described in Serialized items: Tracking.
Common confusion
| People often think… | But actually… |
| Instance statuses are maintained by an administrator. | They follow automatically from operations on the SFI. Manual changes are for exceptions only. |
| An item in assembly can still be serviced on its own. | It became a permanent part of the assembly and can no longer be picked or serviced separately. |
| Only one service rule can apply. | Several can. The instance goes to service as soon as the first of them is fulfilled. |
Take action
Ready to set one up? Continue with Serialized items: Setup. To trigger service automatically from usage, see How to set up tool life tracking and automatic service triggers.
Related articles
- How to set up tool life tracking and automatic service triggers – automatic service based on consumed tool life.
- Understanding service order scripts: automated service and calibration rules – how items set For service reach a service order.
- Understanding the service flow: from pick to restock – the service route for every service item, serialized or not.
- Understanding item statuses – the item’s own status (Defined, Released…), not that of a serial number.