Skip to content
ReportArea
Help topics
Inventory and assets Advanced

Identified units, compatibility, and returns

ReportArea can control parts by quantity alone or track specific physical units. It also prevents incompatible installations and preserves the path of removed components.

Availability: inventory and asset staff according to their permissions; installation or replacement requires the current report assignee or an administrator. Level: Advanced.

Purpose

Use these features when you need to know which exact unit was delivered, what it replaced, whether it meets a position's requirements, and whether the removed part is returned, held for repair, or retired.

Requirements

  • An item must be classified with a component type before identified units can be created; serialized items always require this classification.
  • Compatibility suggestions require the template to define the type and any applicable rules.
  • To install or replace, the part must have been delivered or consumed for that report, and the asset must remain active and linked.

Tracking modes

  • By quantity: the warehouse total is authoritative. A subset within that total may be identified; this is the hybrid usage. An outgoing movement can mix exact units and anonymous quantity, but it cannot ignore identified units when the anonymous balance is insufficient.
  • Serialized: every available unit is identified. Receiving, transferring, consuming, or delivering requires selecting all exact units.

Compatibility and replacement

  1. Target the request at an asset, position, or component from the report.
  2. The system offers items of the same type and classifies them as compatible or as having incomplete information.
  3. A compatible result may continue. If information is missing, explicitly confirm it and enter a reason. An incompatible result is blocked.
  4. Inventory delivers the unit; this marks it as issued, not installed.
  5. Record the installation or replacement from the report. If the removed component has child parts, decide for each direct branch whether it moves to the new parent or is removed.
  6. Choose a destination for the removed part: pending return, repair/observation, retirement, or no location.

Rules and effects

  • A replacement requires the same component type.
  • Delivery and installation are separate, and stock is not deducted twice.
  • The previous component's identity and history are preserved.
  • A pending return does not increase stock until Inventory confirms receipt and the receiving warehouse.
  • A manufacturer serial number is optional and may be repeated; the system warns and requires confirmation.
  • Tracking mode cannot change while stock or an outstanding issued balance exists.

Required and optional information

Required: classification for serialized items; exact selection of serialized units; a reason when accepting incomplete compatibility; a destination for removed components. Optional: serial number, manufacturer, model, external identifiers, notes, and individual tracking within a quantity item.

Practical example

A drive is replaced in a device. The targeted request offers drives of the same type; one has its capacity recorded but is missing interface information. The technician confirms incomplete compatibility with a reason. Inventory delivers the exact unit, the technician installs it, and marks the old drive for return. Stock increases only after Inventory confirms its arrival.

Current limits

  • There is no complete supplier-return or external repair workflow.
  • Partial deliveries are not supported.
  • Items with stock cannot be converted between By quantity and Serialized.
  • Replacing with another type is not allowed, even if it could serve a similar function.

This guide describes the features currently available to organization users.