What Is a QR Code Asset-Tracking System?

A QR Code asset-tracking system connects physical machinery and equipment to managed digital records.

Recommended System Architecture

Core components

• Asset identification rules
• Central asset database
• Stable domain and URL structure
• Authentication and permissions
• Mobile-friendly asset pages
• QR Code generation
• Durable physical tags
• Installation records
• Maintenance and audit workflows
• Backups and data-export capability

Define the Business Objectives First

Asset tracking should solve defined operational problems rather than merely digitising an existing list.

Possible objectives

• Identify each machine reliably
• Find equipment by site, department or status
• Reduce duplicate asset numbers
• Record movement between departments
• Access manuals and service documents
• Record preventive maintenance
• Report breakdowns
• Complete physical asset audits
• Track warranty and supplier information
• Control disposal and retirement

Define success measurements

Examples include the percentage of assets tagged, audit completion, missing-equipment rate, overdue maintenance, duplicate records, failed QR scans and the time required to find a machine record.

Choose the Suitable Asset-Tracking Platform

Start with the workflow, not the software brand

Document the required records, users, approvals, reports and lifecycle actions before selecting a platform.

Create a Unique and Stable Asset Identifier

Every physical asset should have one identifier that remains stable when the machine changes department, user or location.

Illustrative internal formats

Recommended characteristics

• Unique
• Consistent
• Easy to read
• Easy to search
• Not dependent on the current employee
• Not dependent on a temporary room number
• Not reused after retirement without a defined policy

Do not make the identifier too intelligent

A code containing department, location, custodian and equipment status may become misleading when those details change. Store changing attributes in separate database fields.

Internal Asset IDs vs GIAI

Internal identifier

Suitable when the asset is managed only within one organisation and external standards-based exchange is unnecessary.

Global Individual Asset Identifier

GIAI is a GS1 identification key that can uniquely identify an individual asset such as equipment, machinery, a vehicle, computer or spare part.

When GIAI may be considered

• Assets move between organisations
• Leasing or rental parties share records
• Supply-chain interoperability is required
• A customer or industry specification requires GS1 identification

Design the Asset Database

The database should contain enough structured information to support identification, maintenance, audits and lifecycle decisions without becoming unnecessarily difficult to maintain.

Use controlled fields where possible

Drop-down selections for category, status, location and department reduce inconsistent spelling and improve reporting.

Define Standard Asset Statuses

Status values should be clearly defined so different users interpret them consistently.

Possible status structure

• Pending Registration: record created but details incomplete
• Active: operating and available
• Under Maintenance: temporarily unavailable for service
• Out of Service: not approved for operation
• In Storage: retained but not currently deployed
• Transferred: ownership or site transfer in progress
• Missing: not found during audit
• Retired: removed from operational use
• Disposed: disposal completed and recorded

Avoid deleting historical assets

Retaining retired and disposed records helps prevent asset-number reuse and preserves audit history.

Use a Stable QR Code URL

The physical tag may remain on equipment for many years. The URL structure should survive changes to databases, software vendors and internal systems.

Recommended characteristics

• Organisation-controlled domain
• HTTPS connection
• Short and readable path
• Stable asset identifier
• No confidential information in the address
• No temporary session token
• No software-administration command

Avoid dependence on an uncontrolled URL shortener

A third-party short link may stop working, change ownership or introduce tracking and privacy concerns. A controlled organisation domain provides better long-term management.

Static Direct Links vs Managed Redirects

GS1 Digital Link context

Organisations using GS1 identification can consider GS1 Digital Link where the applicable identifier is represented in a web-compatible URI and managed online services are required.

Separate Authentication from Authorisation

Authentication

Confirms who the user is, such as through a company login, single sign-on or another approved identity method.

Authorisation

Determines which records and actions that authenticated person may access.

Possible user roles

Apply the minimum access needed

A user who can scan an asset does not automatically need permission to edit financial values, ownership, disposal status or other sensitive fields.

Public Landing Page vs Private Asset Record

Public or unauthenticated view

May show limited information such as:

• Asset number
• Organisation name
• “Property of” notice
• Lost-equipment reporting instructions
• General support contact

Authenticated internal view

May show:

• Location
• Custodian
• Maintenance records
• Documents
• Purchase and warranty data
• Audit history
• Permitted workflow actions

QR Asset-Tracking Security Controls

Anyone who can see a QR Code may be able to photograph or copy it. Security must be applied by the application, not assumed from the physical code.

Recommended controls

• HTTPS
• Company-controlled domain
• Strong account authentication
• Role-based authorisation
• Multi-factor authentication for sensitive accounts where appropriate
• Server-side permission checks
• Audit logs for important changes
• Session expiry and account removal procedures
• Regular software updates
• Backup and restoration testing

Never encode credentials

Do not place passwords, API keys, permanent login tokens or administrator commands inside the QR Code.

Protect edit actions

A scanned address should not allow unauthorised users to change location, approve disposal, close maintenance work or delete records.

Design a Practical Mobile Scanning Experience

Most QR asset workflows are performed on a phone or handheld device in a factory, office, warehouse or service area.

The first screen should show:

• Asset number
• Asset name
• Photograph
• Current status
• Current location
• Manufacturer and model
• Important safety or operational notice where approved

Common action buttons

• Report Problem
• Start Inspection
• View Maintenance History
• Transfer Asset
• Confirm Audit
• Open Manual

Mobile design priorities

• Fast loading
• Large buttons
• Readable text
• Minimal data entry
• Photo upload
• Clear success and error messages
• No desktop-only interface

Design the Physical Asset Tag

Recommended permanent content

• Organisation name or identifier
• Human-readable asset number
• QR Code
• Short scanning instruction
• Optional support contact

Keep changing information online

Do not permanently engrave the current employee, room, maintenance date or operating status unless the business process specifically requires it.

QR Code Production Requirements

Preserve the quiet zone

A standard QR Code needs a clear margin four modules wide on every side.

Use sufficient module size

There is no universal minimum physical size. Reliable scanning depends on data length, module count, tag material, marking process, surface reflection, viewing distance, camera and lighting.

Reduce unnecessary density

• Use a short asset URL
• Avoid unnecessary tracking parameters
• Do not encode the complete database record
• Use a stable asset identifier
• Increase physical size when necessary

Test every stage

1. Validate the source URL.
   Confirm that it opens the correct record.
2. Test the generated digital code.
   Confirm data and geometry before production.
3. Test the physical marked tag.
   Check contrast, glare and final size.
4. Test after installation.
   Check the normal scanning position and hardware clearance.

Select a Suitable Asset-Tag Material

Read How to Create Durable Metal Asset Tags for Equipment and Machinery for a detailed physical-tag guide.

Mount and Position the Tag Correctly

Possible mounting methods

• Industrial adhesive
• Rivets
• Screws
• Existing plate holder
• Approved wire or bracket mounting

The tag should be:

• Visible
• Safely accessible
• Away from moving parts
• Away from excessive heat
• Protected from direct impact
• Clear of manufacturer and safety labels
• Positioned for reliable scanning

Review Adhesive vs Rivet vs Screw Mounting for Metal Asset Tags and How to Install Metal Asset Tags on Machinery Safely and Correctly.

Generate Variable QR Codes and Asset Numbers

Each tag should be produced from approved variable data rather than edited manually one file at a time.

Recommended production columns

Batch-generation controls

• Preserve leading zeros
• Check duplicate asset IDs
• Check duplicate URLs
• Test all destinations
• Lock the approved file
• Record rejected and reprinted tags

xTool Studio context

Current xTool Studio batch tools can support external spreadsheet data, QR Code and barcode generation, and automatic numbering. Software automation does not replace physical scanning and record matching.

Use a Tag Production Manifest

A production manifest connects each database record to its physical tag and final installation.

Recommended manifest fields

• Asset ID
• QR URL
• Tag material
• Tag dimensions
• Production batch
• Quality-control result
• Packaging group
• Installation status
• Installer
• Installation photograph

Do not mix unlabelled tags

A valid QR Code installed on the wrong machine creates a serious data-integrity problem even when both the code and database function correctly.

New-Asset Onboarding Workflow

1. Receive the equipment.
   Record purchase, supplier and delivery information.
2. Create the asset identifier.
   Confirm uniqueness before issuing the number.
3. Create the database record.
   Add manufacturer, model, serial number and initial ownership data.
4. Assign category and criticality.
   Support maintenance and reporting priorities.
5. Create the stable asset URL.
   Confirm access and redirection behaviour.
6. Generate and produce the QR tag.
   Use the approved tag specification.
7. Scan and inspect the tag.
   Confirm code data and physical readability.
8. Install the tag safely.
   Record the position and mounting method.
9. Complete the activation check.
   Confirm the final record, photograph and operational status.

Connect QR Scanning to Maintenance

A technician scanning the equipment should reach the correct technical record without manually searching a long equipment list.

Possible maintenance functions

• Report a fault
• Create a work request
• View open work orders
• View maintenance history
• Open manuals and safety documents
• Record meter readings
• Upload photographs
• Record parts replaced
• Complete an inspection checklist

Record who changed what

Important maintenance and status updates should include the user, timestamp and previous value where appropriate.

Manage Asset Transfers and Location Changes

Moving equipment should update the database rather than require a new permanent asset ID.

A transfer workflow may require:

• Current location
• Destination location
• Requesting person
• Approver
• Transfer date
• Condition photograph
• New custodian
• Final receipt confirmation

Keep transfer history

The current location is important, but the system should also preserve previous locations and transfer dates for audit purposes.

Use QR Codes for Physical Asset Audits

A scan-based audit can reduce manual typing and improve matching between the physical asset and its record.

Recommended audit workflow

1. Select the audit scope.
   Choose site, department, category or asset group.
2. Generate the expected asset list.
   Record each asset’s expected location and status.
3. Scan each physical tag.
   Confirm identity and current condition.
4. Record actual location.
   Compare it with the expected database location.
5. Record exceptions.
   Note missing, damaged, untagged, duplicated or relocated assets.
6. Review and approve corrections.
   Do not automatically overwrite controlled records without review.
7. Close the audit.
   Save completion metrics and unresolved exceptions.

Useful audit evidence

• Scanning user
• Date and time
• Location
• Asset photograph
• Tag condition
• Exception notes

Retirement and Disposal Workflow

Assets should not simply disappear from the active list when sold, scrapped, donated or returned.

Recommended controls

• Disposal request
• Approval
• Data-removal or security check where relevant
• Final asset condition
• Buyer, recycler or recipient information
• Disposal date
• Financial treatment
• Tag removal or cancellation
• Final status update

Keep the historical record

Mark the record as retired or disposed rather than deleting it. The QR landing page can show a controlled inactive status where appropriate.

Replace Damaged or Missing QR Tags

Replacement steps

1. Verify the asset identity.
   Use the manufacturer serial number, database record and equipment photograph.
2. Confirm the original asset ID.
   Do not create a second asset merely because the tag is damaged.
3. Record the replacement reason.
   Note wear, damage, poor scanning, loss or mounting failure.
4. Reproduce the approved tag.
   Use the existing asset URL unless the system requires a controlled change.
5. Install and rescan.
   Confirm the correct record and update the replacement history.

Tag versioning

Recording the tag version or replacement count can help identify recurring material, mounting or environmental failures.

Plan System Integrations Carefully

Possible integrations

• Accounting fixed-asset register
• Procurement system
• CMMS or maintenance software
• ERP
• Helpdesk or ticketing platform
• Inventory or spare-parts system
• Identity and single sign-on
• Document storage

Define the system of record

Decide which platform owns each field. For example, the accounting system may own acquisition value while the maintenance system owns work history.

Avoid uncontrolled two-way updates

Integrations should define which system can create, edit or delete each item and how conflicts are resolved.

Plan for Low-Connectivity Areas

Some factories, basements, outdoor sites and remote facilities may have weak or unavailable network coverage.

Possible planning options

• Store the human-readable asset ID on every tag
• Allow the user to record the asset number manually
• Provide an approved offline audit mode
• Cache assigned work records where the platform supports it
• Synchronise completed actions after connectivity returns
• Prevent conflicting offline changes

Test the real facility

Do not assume reliable Wi-Fi or mobile coverage based only on an office test.

Backups, Export and Business Continuity

A physical tag remains useful only when its corresponding record and routing system remain available.

Continuity requirements may include:

• Scheduled database backups
• Independent data export
• Restoration testing
• Domain-renewal ownership
• Document backups
• Administrator succession
• Platform-exit plan
• Redirect migration plan

A backup is not proven until restoration is tested

The organisation should confirm that asset records, photographs, documents and URL routing can be restored using an approved recovery process.

Useful Asset-Tracking Metrics

Measure useful outcomes

A high number of QR scans does not automatically mean the asset-management process is effective. Focus on accurate records, completed maintenance, resolved exceptions and controlled lifecycle decisions.

Recommended Implementation Plan

1. Define the scope.
   Select asset types, sites, users and required workflows.
2. Clean the existing data.
   Remove duplicates and confirm manufacturer serial numbers.
3. Approve the identification structure.
   Define asset IDs, URL pattern and status rules.
4. Configure a prototype system.
   Build essential fields, permissions and mobile screens.
5. Create a small physical pilot.
   Use representative equipment, materials and mounting methods.
6. Test complete workflows.
   Cover scanning, maintenance, transfers, audits and replacement.
7. Train pilot users.
   Observe actual use and simplify unnecessary steps.
8. Correct data and process problems.
   Resolve duplicate IDs, permissions and scanning issues.
9. Approve the production specification.
   Lock the tag design, material, URL and variable-data file.
10. Roll out by controlled groups.
    Tag one site, department or asset category at a time.
11. Complete a post-installation audit.
    Confirm records, tags, positions and user access.
12. Review and improve.
    Monitor exceptions, broken links, maintenance use and audit results.

Common QR Asset-Tracking Mistakes

What Affects the Cost of a QR Asset-Tracking System?

Software and implementation factors

• Number of assets
• Number of users and locations
• Platform type
• Custom workflows
• Permissions and approvals
• Data cleaning and migration
• System integrations
• Document and photograph storage
• Offline requirements
• Reports and dashboards
• Training and support
• Cybersecurity and backup requirements

Physical tag factors

• Tag material
• Tag dimensions
• Marking or printing process
• Unique QR Codes and asset numbers
• Adhesive backing or holes
• Quality-control scanning
• Packaging by site or department
• Installation

Do not compare tag price alone

A low-cost label does not reduce the operational cost of incorrect records, failed links, duplicate identifiers, unsafe installation or an unusable mobile workflow.

Information Needed Before Planning the System

What Image Magic Recommends

Important System, Security and Durability Note

Frequently Asked Questions