# Serialized items

Serialized item fields, service threshold types, and lifecycle event log.

Source: https://support.toolingmetrics.com/en/inventory/reference/serialized-items/
Updated: 2026-10-29

A **Serialized Item** tracks an individual physical piece of a Serialized [Item](https://support.toolingmetrics.com/en/inventory/reference/items/) by its own identity — a serial number (a UUID by default), shown as text and as a data-matrix code. Unlike the bulk quantity on a non-serialized item, each Serialized Item has its own condition, cost, location history, and usage figures. A Serialized Item record is created only as a side effect of a move line (a Purchase Order receipt, Transfer, or Inventory Adjustment increase against a Serialized item) — there is no standalone creation screen.

## Fields

### Identity

| Field | Description |
|---|---|
| **Serial Number** | Unique identifier for this physical unit, 3–36 characters, unique across the entire application. System-generates a UUIDv7 by default; fully editable so a real manufacturer or upstream serial number can be entered instead. Displayed on the detail page as text and as a data-matrix code. |
| **Item** | The parent Item this piece belongs to. Determines the piece's product data, cost configuration, and (if Serviceable) service thresholds. |
| **Condition** | Brand new, Used, Under service, Refurbished, Scrapped, or Need service. |
| **Location** | Derived live from this piece's move history — not a stored field. Reflects a storage location, machine, or assembly station. |
| **Cost** | This piece's own current cost, set at creation from the move line's cost and decremented as usage cost posts against it. |

### Usage and service

Service thresholds are not stored on the Serialized Item — they live on the parent Item's **Service Thresholds** (Time Interval, Usage Cycles, Usage Time, Usage Cost, Remain Cost), and only exist when the parent Item is both a **Serialized Item** and **Can be Serviced**. Each Serialized Item is evaluated against its parent's thresholds independently:

| Field | Description |
|---|---|
| **Current Usage Cycles** | Completed pick-and-return cycles since the last service (or since creation, if never serviced). |
| **Current Usage Time** | Accumulated hours on a machine since the last service. |
| **Current Usage Cost** | Sum of usage cost lines posted against this specific piece since the last service. |
| **Last Service Performed at** | Timestamp of this piece's last completed service. |
| **Next Service Scheduled at** | Next planned service date, either set explicitly or derived from a Time Interval threshold plus Last Service Performed at. |
| **Need Service?** | Computed: turns on once any of the parent item's thresholds is breached for this specific piece. |

### Tabs

| Tab | Content |
|---|---|
| **Moves History** | Every recorded move for this piece — source, destination, and status. |
| **Usage History** | Usage cost lines posted against this specific piece, with machine and date. |

## Service trigger behavior

When any of the parent item's thresholds is breached for a piece, that Serialized Item's condition becomes **Need service**. There is no automatic condition change beyond this — moving the piece into an actual service workflow (and back to Refurbished on return) is a separate, manual step.