Skip to content
Fenwix
TRGoogle Play

QR and barcode inspections

CURRENT

Scan the asset, then inspect the right record

Fenwix uses QR codes and barcodes as field identifiers for asset-centred inspections. A scan can locate a known local asset or start a deliberate registration path for an unknown code, reducing manual lookup while keeping the resulting inspection attached to the intended equipment history.

Try Fenwix on Google PlaySee asset inspection history →
QR and barcode flow showing an asset scan resolving the correct record before inspection.

Faster lookup

Move from the physical label to the local asset record without searching long lists.

Controlled registration

Treat an unknown code as a registration decision, not an automatic trusted record.

Linked history

Start the inspection from the asset so results remain connected to prior and future checks.

Scan-to-inspection path

  1. Scan code
  2. Match or register
  3. Confirm asset
  4. Run checklist
  5. Save linked history

What happens after a scan?

When a code matches a local asset, Fenwix opens the asset context. If it is new, the user can create a record and provide the meaningful name, site and inspection context instead of silently trusting an arbitrary label.

  • Recognize supported QR and barcode values
  • Confirm the asset before starting work
  • Create a local asset when the code is unknown
  • Carry asset context into the inspection

Use labels as identifiers, not proof

A printed code can be copied, damaged or attached to the wrong object. Scanning improves speed and reduces typing, but the inspector still confirms the physical equipment and its context before relying on the record.

  • Check the visible asset identity
  • Replace unreadable or ambiguous labels under your procedure
  • Do not treat a successful scan as calibration or compliance proof
  • Record discrepancies as findings when appropriate

Current local scope

Scanning works with the local Fenwix asset register. It is not currently a lookup into a shared enterprise ERP, CMMS or cloud asset database, and no background cross-device synchronization is claimed.

  • Current: local asset match and history
  • Current: inspection start from asset context
  • Not current: enterprise master-data connector
  • Not current: centralized label provisioning

QR and barcode boundary

  • A code identifies a record; it does not authenticate the asset
  • Label design, placement and lifecycle remain an operational responsibility
  • Sensitive identifiers should follow the organization's information-security rules

QR and barcode inspection questions

Can Fenwix scan an existing equipment label?

Fenwix can use supported QR or barcode values to match or register a local asset record.

What happens if the code is not known?

The user can deliberately create and describe a new local asset instead of accepting an unverified automatic match.

Does scanning prove I inspected the physical asset?

No. It helps identify a record. The inspector must still confirm the object and perform the inspection.

Does Fenwix connect to our CMMS today?

No current CMMS or enterprise asset connector is claimed.

Continue from identification to evidence

Asset and equipment inspections →Photo evidence →Inspection reports →Connector status →

Test the label-to-record path

Scan one real asset, confirm its identity and complete an inspection to verify that the history stays attached to the intended equipment.

Try Fenwix on Google Play

Content status: CURRENT · Last reviewed: 2026-08-16

Claim basis: Fenwix current application flow · Fenwix product decision record · Fenwix.app aligned master brief