Inventory

Inventory (/inventory) is the record of every physical machine your kiosks have ever booted — one row per machine, kept current automatically. Each boot sends a complete hardware report to your account, and this page is where you browse, filter, inspect, and push those machines.

How assets are recorded

You never create an asset by hand. When a kiosk boots and unlocks, it sends its once-per-boot hardware report, and AVERASE upserts one asset per physical machine per account:

  • Machines are keyed by their DMI identity — system UUID plus serial number — so a repeat boot of the same machine matches the existing row instead of creating a duplicate.
  • The first sighting records who reported it (the technician), which license token and download it came from, and the first-seen timestamp.
  • Every subsequent boot refreshes the row: the boot record id, engine version, the full fingerprint, the last-boot time, and the summary columns the grid displays (manufacturer, model, serial, CPU, memory, GPU, storage, battery health, firmware details, and more).

The same machine wiped on three different days is still one row — with three boots of history behind it.

The asset grid

A spreadsheet-style grid, paginated at 100 rows per page and ordered by last boot, newest first. Columns:

ColumnContents
AssetThe asset's id (asset_…) — click to open the drawer
VendorManufacturer
ModelProduct model
SerialSystem serial number
ChassisChassis type
CPUCPU model
CPU Speede.g. "3.4 GHz"
Memorye.g. "16.0 GB"
StorageTotal installed capacity, e.g. "512 GB" or "1.5 TB"
BatteryHealth percentage, e.g. "75%"
TouchYes / No / —
GPUGraphics adapter
HDMIHDMI presence
WFCWorld-facing camera presence
TechnicianThe user who first reported the machine
UpdatedLast update time

Toolbar

The toolbar sits in the app header above the grid: a search field ("Search inventory…"), then Filter, Sort, Push, and the pager ("Page N of M").

  • Search matches text across the visible rows.
  • Filter builds its own checkbox sections from the values actually present in the table — vendors, models, chassis types, and so on — so it always reflects your data.
  • Sort is a fixed list of whole-table reorders: Ascending / Descending by Updated, and A→Z / Z→A by Model. Clearing a sort restores the original order.
  • Push sends selected rows to a connected integration (below).
  • The pager steps through pages of 100.

The asset drawer

Clicking an asset id opens a right-side drawer next to the grid — the quick view. Its header shows the machine's identity: Manufacturer and Model, then the asset_… id, Serial, and Asset tag. Below that, sections for System, Motherboard, CPU, Memory, Graphics, Storage (each drive as model · capacity, with its Serial), Display (Touch and world-facing camera), Hardware Tests, and Notes.

The drawer deliberately mirrors the kiosk's default (non-Advanced) dashboard view — a technician looking at the machine on the kiosk and a teammate looking at it in the drawer see the same fields. The drawer header links to the full report page.

The full asset report

/inventory/:id renders the complete report. The left panel walks every fingerprint section in display order:

system, CPU, memory, storage, storage controllers, GPUs, network, Wi-Fi adapters, audio devices, batteries, displays, USB devices, ports, bluetooth, RAID controllers, thermals, fans, power adapters — plus an Other section for any fields that don't belong to a known section.

Formatting rules throughout: booleans render as Yes/No, byte counts are humanized, missing values show "—", and JEDEC memory manufacturer codes are expanded into readable Manufacturer / Assembled by / Manufacturer code lines.

The right column stacks three boxes:

  • Provenance — Reported by, License token (ltok_…), Engine version, Boot record, First seen, Last boot. This is the chain from a row in your inventory back to the exact stick and boot that produced it.
  • Hardware Tests — results of the kiosk's interactive test suite.
  • Notes — operator notes typed on the kiosk.

Hardware tests

Nine tests can report: Keyboard, Display, USB Ports, Battery, WiFi Adapter, Bluetooth, Webcam, Audio, Touchscreen. Each shows a status label:

StatusLabel
passedPass (green)
failedFail (red)
not_startedPending (orange)
not_applicableN/A
detectedDetected

A test's detail text, when present, renders after an em dash.

Bay map (hotswap chassis)

A machine that is a mapped hotswap chassis gets a Bay map section: a "Mapped bays: N" count with the date the map was last updated, then one line per bay translating the physical bay label into the lane behind it — for example, Bay A1 → "HBA 05:00.0 · phy 14", or Bay 3 → "SATA port 3". This is the saved chassis map the hotswap station fetches at every boot; see Chassis map.

Pushing assets to an integration

Select rows in the grid and use Push in the toolbar. Push is icon-only until rows are selected, then reads e.g. "3 Assets". The menu lists your connected integrations (RazorERP when connected); choosing one opens a dialog that live-loads your Razor lots and pushes the checked rows (up to 200 at a time). As the dialog notes: "Records already in Razor are updated in place — the lot only applies to newly created assets."

Was this page helpful?