Assets

Equipment installed at a customer (boiler, pump, generator, panel, machine — not HVAC-only). Work orders, forms, findings, and Field job sheets can point at these records. An asset is not a catalog product and not a stock item.

Customers → Assets · /app/w/{workspace}/assets · capability customer_assets · assets.view / create / update / delete (Archive)

If the capability is off, the Assets nav item is hidden. Catalog items are sellable SKUs; inventory is stock; assets are the customer’s installed base.

What an Asset is

An asset belongs to a Customer (required). It may belong to a Site of that same customer — Site is optional. You can save equipment without a site; that is allowed and usually a poor fit for field work (technicians then lack a service address on the asset itself). There is no parent/child hierarchy and no QR or barcode scanner on this record. Serial numbers may duplicate in the workspace.

Veldriq assigns Asset number automatically as AST-YYYY-######. Customer cannot change after create.

Assets are not stock

Van parts live under Inventory. Do not create an asset for every spare filter.

Create an asset

1. Capability customer_assets on (Settings → Modules if your plan allows). Optional types: Settings → Asset types (asset_types.manage).
2. Customers → Assets → Add asset, or Customer show → Assets → Add asset, or Site show → Add asset.
3. Customer (required). Site (optional, same customer) — recommended for service location.
4. Name (required) — short label technicians recognize. Optional Asset type, Manufacturer, Model, Serial number.
5. Status: Active, Inactive, or Retired when office creates the asset. Portal-created assets start as Pending review.
6. Installation date, warranty start / end (dates). Description and internal notes. Tags and required custom fields. Save. Number is filled.

Profile and service history

Sections typically: Overview · Covered by · Maintenance plans · Upcoming maintenance · Service history (visits where this equipment was in scope; empty until work references it) · Tags · Comments · Files · Activity.

Header actions: Edit, Retire, Archive / Restore.

Action	Meaning
Inactive	Status; row still in the live list unless filtered.
Retire	Business status (“This is a business status, not an archive.”). History remains.
Archive	Soft-delete to the Archived tab. Prefer Retire or Inactive if you still need the serial in pickers.

Portal-created assets wait as Pending review until office Approve / Reject (list, show page, or customer panel).

Work orders, Field, inspections

On a work order, attach assets with the transfer list (same customer). Field shows an Equipment section: open a row for serial, warranty, type. Forms can bind an instance to an asset. Findings can reference the asset when recorded from a check.

Moving an asset to another site: edit the record and pick another site of the same customer. Customer stays locked. Historical work orders keep whatever assets they already attached; they do not auto-rewrite.

What-if

If the nav is hidden: capability customer_assets off.

If you cannot save: Customer and Name required. Site from another customer — picker is scoped.

If Service history is empty: no visit has referenced this asset yet. Veldriq does not invent automatic history.

If you expect barcode/QR scanning: not implemented on this record.

Related: Customers, Sites, Work orders, concept Asset.