How Imports and Scan Work

What each is for

Imports create a usable workspace faster by bringing in structured data such as asset spreadsheets, facility lists, and equipment metadata. Scan captures or connects information quickly in the field, helping users identify assets, start work from the right record, and reduce manual lookup. Imports build the initial structure; scan helps people use and maintain it during real work.

Import review flow

Import turns source files into reviewed operational records. Upload the file, confirm column mapping, fix errors, resolve duplicates, inspect the commit preview, and commit only when the summary matches your onboarding goal. Don't treat the import as finished until records are easy to find in Assets. Imports alone don't create a healthy workspace; data must be reviewed, corrected, and used consistently.

Import-to-scan checklist

Scan works best after import cleanup, since a QR label is only useful when it points to the correct asset, facility, and location.

1. 01Import or create a clean asset set.
2. 02Confirm facility, location, asset tag, and serial context.
3. 03Resolve duplicate candidates.
4. 04Filter the asset list to records that should receive labels.
5. 05Print labels from the visible list.
6. 06Place labels in durable, easy-to-scan locations.
7. 07Scan a sample before rolling out facility-wide.

If a scan opens the wrong record, stop using that label and fix the asset mapping by checking for duplicates, retired records, or old labels.