QR
Scannable public workflow sample
This first-party code opens FleetTrestle's public field landing. Customer labels use the same generator but target one authorized vehicle record.
Encoded target
https://fleettrestle.com/field
First-party mobile QR workflow
Scan a real FleetTrestle QR code. Print authorized vehicle labels.
The sample below is a working first-party QR code for the public field landing. Signed-in fleet managers can generate vehicle-specific label sheets; every vehicle scan still requires authentication and tenant authorization.
Scan and print evidence
The public sample and customer label path use the same QR renderer.
What the sample provesA first-party, high-contrast QR image is generated from the displayed HTTPS FleetTrestle target and can be opened or printed from this page.
What requires an accountVehicle-specific codes, unit labels, fleet label sheets, and field actions use authenticated organization data and are not exposed by this public sample.
Denial behaviorAn unsigned scan is routed to sign-in with the vehicle return path. A signed-in user outside the vehicle's organization receives the unavailable state, not the vehicle record.
Print boundaryFleetTrestle requests the browser print dialog. The browser, printer, label stock, camera, lighting, and physical placement determine final print and scan quality.
Vehicle workflow
From label generation to an authorized field action.
1
Generate inside FleetTrestle
Authorized managers open the vehicle roster and create printable labels. Vehicle destinations are encoded by FleetTrestle rather than sent to an external QR service.
2
Print and place the correct label
The label sheet identifies the unit, keeps a high-contrast quiet zone, avoids splitting a label across print pages, and shows the encoded destination for verification.
3
Scan beside the vehicle
A phone camera opens the encoded FleetTrestle field route. Possessing the label never creates a session or grants organization access.
4
Authenticate and continue
FleetTrestle preserves the vehicle-specific return path through sign-in, then checks the user, organization, vehicle, and permitted field actions.
Supported field actions include vehicle lookup, mileage entry, inspection start, and issue reporting when the signed-in role and organization permit them. The QR code is only a routing shortcut.