Barcodes & Static Passes
For everything already printed.
The same optical scanner that reads dynamic QR also reads 1D barcodes and static codes, so printed visitor badges, event tickets, student cards and delivery manifests all work as credentials without new hardware.
Not every credential needs to be clever. A conference badge, a school library card, a one-day contractor slip — these need to be cheap, printable, and readable by the same scanner already in the panel.
How it works
The detail that decides whether this survives contact with a real building.
- Symbologies
- Code 128, Code 39, EAN, UPC, plus QR, Data Matrix and PDF417
- Validity
- Bounded by a start and end time on the pass, not by the printed paper
- Revocation
- Cancel a printed pass from the console and the next scan is refused
- Bulk issue
- Generate a batch for an event and hand them out at the gate
- Honest limit
- A static code can be photographed and shared — use it where convenience outranks assurance
One scanner, every symbology
The optical module that reads dynamic QR also reads Code 128, Code 39, EAN, UPC, Data Matrix and PDF417. Existing printed stock — badges, tickets, manifests, student cards — becomes usable without buying anything.
Validity lives on the server, not on the paper
The printed code is only an identifier. What it is allowed to open, and until when, sits on the pass record. Change the record and the same piece of paper behaves differently at the next scan.
Revoke a printed pass
A badge that walks out of the building can be cancelled from the console, and the next scan is refused. This is the difference between a printed pass and a physical key.
Batch issue for events
Generate a run of passes for a conference, a school open day or a site induction, hand them out at the gate, and let them all expire together at a time you set in advance.
Deliveries and manifests
A courier's existing consignment barcode can be accepted at a loading bay as a one-shot credential, which removes the intercom call and the guard walking out in the rain.
The honest limitation
A static code can be photographed and shared, and no amount of marketing changes that. Use it where convenience outranks assurance, and use dynamic QR everywhere else. The same reader does both, so choosing correctly costs nothing.
Where this fits
Events, printed visitor badges, schools, and short-lived one-day access.
Because every channel resolves to the same holder record, this does not have to be the only way in. A person can hold this alongside a card, a PIN and a plate, and the audit trail still reads as one identity.
Questions about barcodes & static passes
Which barcode formats are supported?
Code 128, Code 39, EAN and UPC for 1D, plus QR, Data Matrix and PDF417 for 2D — all on the same scanner module that handles dynamic QR.
Can a printed pass be cancelled?
Yes. The paper only carries an identifier; the entitlement lives on the pass record. Cancel the record and the next scan is refused.
Is a printed barcode secure enough for a main entrance?
Generally not, because it can be photographed and shared. Use it for low-consequence and short-lived access, and use dynamic QR, cards or biometrics where the door justifies it.
Can I issue a batch of passes for an event?
Yes — generate them together with a common expiry, distribute them at the gate, and let them lapse as a group.
The other ways in
One access list, one console, one audit trail — whichever of these a person happens to be carrying.
Face Recognition
Walk up, look up, walk through.
UltraPASS-VehicleVehicle Plate Recognition
The car is the credential.
UltraPASS-BioBiometric Access
A credential that cannot be lent.
UltraPASS-DoorNFC, MIFARE & HID Cards
Keep the cards you already issued.
UltraPASS-DoorBluetooth & BLE
The phone stays in the pocket.
UltraPASS-DoorDynamic QR Codes
A key that expires while you watch it.
UltraPASS-DoorPIN & Keypad
The fallback that always works.
Put barcodes & static passes on your doors
Talk to Patrick about what is already installed and what it would take to move it onto xSERVA.
Book a Demo