INDUSTRIAL HANDHELD DATA-CAPTURE PILOT Purpose: prove that capture produces the intended business record. Use: run in an approved test environment with disposable transactions. Record expected results before testing, then compare device and server records. Reviewer / date / workflow owner: Device, OS, scan engine, application and scanner-profile versions: Capture method and supported label/tag types: Identifier meaning (product, serial, lot, logistics unit): Packaging and unit of measure: Required sequence of location, item, quantity and confirmation: For every test record: input, expected outcome, actual device feedback, actual server record, evidence location, pass/fail, owner and retest. [ ] Correct label at working distance in normal lighting. [ ] Difficult or damaged label, with defined manual exception path. [ ] Wrong location and wrong item rejected before inventory changes. [ ] Wrong packaging level detected. [ ] Leading zeros preserved through every receiving system. [ ] Keyboard-style scan output tested after focus changes and dialogs. [ ] A repeated transmission recognized by stable transaction identifier. [ ] A legitimate second receipt retains a new transaction identity. [ ] Pending work survives approved application/device restart. [ ] Reconnection confirms work or exposes a resolvable conflict. [ ] A second worker understands and resolves an exception. ILLUSTRATIVE RECEIVING TEST (not a vendor benchmark) Order expects 24 units of item A at location B. Record 12 units online, then 12 offline if permitted by the workflow. Reconnect and resend one of those submissions with its original identifier. Expected: two legitimate receipts of 12; final quantity 24; no extra receipt. Results: transaction time, first-attempt reads, corrections, outstanding work: Training observations: Decision and unresolved issues: Recheck after application, profile, label or OS changes. Yenra guide and source context: https://yenra.com/industrial-handheld/ Prepared October 6, 2026. Recheck exact model/version documentation.