Help & Documentation

Scanning is wired into specific flows. There is no global 'tracker' page.

• Sub-rental Scanner View — scan gear in/out against the transaction's items.
• Sub-rental delivery and return notes — 'Scan items' above the handover checklist ticks the row a scanned QR code or serial belongs to; 'Scan fills' picks which column a scan ticks.
• Project Prep checklist — 'Scan to tick' ticks the prep item for the scanned piece of gear.
• Gear-list category → Scan QR to add — the camera reads a gear QR label and adds that item (or a whole gear set, after a confirmation) to the category. This one is camera-only.
• QR labels themselves are printed one at a time: 'Print Label' in an owned-gear item's editor, or 'Print Set Label' in a gear set's editor.
• The scanner view, the note scan bars and the Prep checklist share the same hardware-scanner and camera input — behavior is identical.
• Three inputs, one vocabulary: those three surfaces offer a hardware/keyboard-wedge scanner, the phone camera, and NFC tag tap. All three feed the same matcher, so a tag, a barcode and a typed code resolve identically. The NFC button appears only where Web NFC exists — Android Chrome over https — and is simply absent on desktop, on iOS and over plain http rather than shown as a dead control. Declining the NFC permission prompt is treated as a cancellation, not an error. NFC is one tag per tap at a few centimetres; it does not read a closed flight case in bulk.

Three input paths cover desktop and mobile use.

Camera scanner

— Full-screen viewfinder. Prefers the rear camera.

Hardware scanner (USB / Bluetooth)

— Listens for keyboard-emitting USB / Bluetooth scanners. Focus does not need to be in a text field — but typing in another input takes priority.

Native scanner (iPhone and Android apps only)

— The iPhone and Android apps use the phone's own barcode scanner, which is faster and easier on the battery.

In the sub-rental Scanner View a scanned code is looked up in this order — the first match wins.

1. Already-scanned guard: the scanned code is trimmed first, then compared against what is already checked in on the transaction — a stray space from a scanner's prefix/suffix no longer reads as a different label, so re-scanning the same unit is rejected with an 'already scanned' warning instead of filling a second slot.
2. A QR label printed by the app names its gear item directly — current labels as a link, labels from older versions as a 'cpp:gear:…' code.
3. Any other code is compared with the Asset Tag, the RFID tag ID and the serial numbers of your Owned Gear items. So the Asset Tag you type on an item is scannable — put the number from your inventory sticker there. A field left empty on the gear record never matches — an absent serial is not a code.
4. The gear item found this way is matched against the transaction's items (skipping items already fully checked in).
5. Still no match: the code is compared with the barcode stored on each item of the transaction.
6. Still no match: open the 'Unknown Code' dialog to map the barcode to an item manually.

Scanning a code the resolver doesn't recognize opens the 'Unknown Code' modal so you can map it.

1. Scan an unrecognized code.
2. The modal lists the manifest items in the transaction.
3. Pick the item the scanned code belongs to.
4. That item is checked in for this scan ('Mapped and Checked In'): a serialized item stores the scanned code on its fulfillment row, a bulk item counts up by one.

Two kinds of label: a scannable QR label per item or gear set, and Avery sheets of text labels from the Print Gear Labels window.

• QR label: open an owned-gear item and use 'Print Label' (or 'Print Set Label' in a gear set). The QR code encodes the deep-link URL for that record, so future scans resolve without manual mapping. A rental house's gear has the same QR label.
• Avery sheets: 'Print Labels' in the Owned Gear header (offering the items your current filters show), a project's Rental tab, or a rental house's gear opens Print Gear Labels. Step 1, Select: tick the items — Select All, Clear, or cases only. Step 2, Customize: production name, camera letter and colour, owner / rental, phone number and the Avery template. These labels carry no QR code.
• Both print via the standard browser print dialog — send to a printer or Save as PDF.

Scanning works fully offline. Resolution data — items in the transaction, owned-gear records — comes from local IndexedDB caches.

• Camera decoding runs in the browser (or in the phone's own scanner in the iPhone and Android apps) — no network call.
• Check-ins, including ones made through the Unknown Code dialog, save to local state and sync to the cloud once online.
• An Asset Tag or serial number added on another device only resolves here once that change has synced.