Overview
When a QR code opens the wrong Location or fails to reveal a Checklist, first identify what the code is supposed to do. A code that navigates to a Location or Asset is different from an answer validated by a Scanner Question.
Keep the printed label and the expected Location or Asset available while you compare the configuration.
At a glance |
|
Who can do this | Super Users or Locations › Modify for Location codes; appropriate Asset or Checklist editing access for other changes. |
Where | Locations, Assets and the Checklist’s Scanner Question |
Works on | Backend (web) |
Availability | All organizations |
💡 Why this matters: Diagnosing the code’s purpose prevents unnecessary Schedule changes when the issue is a label, target or scanning method.
Identify the scanning context
Where it is scanned | Expected purpose |
Location scanner in Mobaro | Find the matching Location or Asset in the User’s app data. |
Scanner Question | Record a scan and validate it using the question’s configured rule. |
Phone camera outside Mobaro | Follow the link encoded in the label; this is not the same as answering a question. |
A Location or Asset code takes the User to the relevant Location Overview context. It does not create scheduled work or give access to a Checklist that is otherwise unavailable. See using scanner codes.
Compare the label and target
1. Check the configured code
Open the intended Location or Asset in the Backend and inspect Custom Scanner Code. Compare it with the code represented by the physical label. When no custom code is set, generated codes use the item’s Mobaro ID.
2. Check other possible matches
If the wrong Location opens, inspect both Locations and Assets that may have been given that code. The editor’s availability check covers both item types. Record the exact code and ask Support to help identify its owner if you cannot find the conflicting item.
3. Check the User’s access
If the app reports No Location Found, confirm that the intended Location or Asset is available to that User in the app. Check Location membership, the active organization and whether the device has received current data. A valid label alone does not grant access.
Check question validation
For a Scanner Question, compare the scanned code with its Validation setting. Location checks the Checklist’s Location, Asset checks its Asset and Specific checks the configured code. None still requires a nonempty scan.
Also check the configured scanning method. A QR label and an NFC tag are different inputs; use NFC tags with Scanner Questions when the question uses NFC.
⚠️ Heads-up: A code can be valid for navigation and still fail a Scanner Question that expects a different target or a specific value. Check the question’s rule before replacing the label.
Verify before replacing labels
Test a corrected configuration with the affected User and the intended scan method. If navigation works but no Checklist is available, move to missing Checklist troubleshooting.
🛑 Critical: Changing a Custom Scanner Code can invalidate labels printed with its previous custom value. Labels based on the item’s Mobaro ID keep working. Plan and verify any label replacement before the labels are needed.
Before replacing labels throughout an area, confirm one example. Send Support the code, intended target, actual result, scanning surface and any validation message.
Best practices
Keep a record of custom code assignments alongside the physical labels.
Test a label at its intended Location or Asset before making copies.
Check navigation and question validation as separate steps.
Frequently asked questions
How do I find which Location an existing QR code belongs to?
Compare the code with Custom Scanner Code on the likely Locations and Assets. If you cannot identify the match, send Support the exact code and organization. Do not reassign it before checking both item types.
Why does scanning with the phone camera not open my Checklist?
Check what the label encodes and test it with Mobaro’s intended scanner. A Location code opens a Location context, not an unrestricted Checklist. The User still needs access and available work.
Can a Location QR code open a RideOps Checklist on someone’s personal phone?
Do not treat a Location code as a RideOps session or operator sign-in link. It navigates within the Mobaro app context. See scanner codes and RideOps setup for the separate workflows.