Choose a rugged handheld by the work it must complete: reading the right labels, surviving the documented environment, lasting through the shift and staying supported for the planned service life. Start with a one-page job description, then ask suppliers to show how a specific configuration meets it.
This guide is for operations and IT teams comparing handheld computers for warehouses, delivery and field service. You will need representative labels, the intended application, a description of working conditions and access to a trial unit. A specification sheet narrows the shortlist; a field pilot establishes whether the complete system works for your people.
Write the requirements before comparing models
Describe the full transaction, including the awkward parts. A receiving worker may scan a small label at arm's length, enter a quantity while wearing gloves and confirm a storage location. A service technician may need to read diagrams outdoors, take a photograph and finish a report beyond cellular coverage. Those jobs can favor different screens, controls, scan engines and carrying arrangements.
Scroll the table horizontally to see every column. Keyboard users can focus the table region and use the arrow keys.
| Requirement | Record for your operation | Evidence to request |
|---|---|---|
| Capture | Barcode types, smallest label, reading distance, damaged or reflective packaging | Scan-engine specification plus results using your actual labels |
| Environment | Temperature range, dust, rain, condensation, cleaning products and handling | Exact test conditions, operating limits and cleaning instructions |
| Human use | Gloves, hand sizes, repetitive scans, sunlight, holsters and carrying time | Worker trial with the complete battery, case and grip configuration |
| Continuity | Shift length, charging windows, coverage gaps and spare-device access | Measured shift consumption, replacement procedure and offline demonstration |
| Service life | Planned retirement date, update policy, repair turnaround and spare supply | Written model-specific support dates and service terms |
Mark requirements as essential, desirable or irrelevant. A device that fails an essential workflow should be removed from the shortlist before optional features receive scores. Record the exact SKU, battery, scanner and accessories: two configurations carrying the same family name can behave differently.
Read each durability claim in its own context
The IEC 60529 standard classifies protection provided by enclosures. An IP rating addresses ingress; drop and tumble results answer different questions. Ask what configuration was tested, which openings must be closed, and what exposure conditions apply. Use the manufacturer's instructions for washing, charging and battery access.
A useful example is the Zebra TC73/TC78 specification sheet. It lists separate sealing, drop, tumble and temperature entries. Its drop claims distinguish room-temperature tests from tests over the operating-temperature range. The lesson is to compare the complete conditions beside each number. A single large drop height leaves out information needed for a purchasing decision.
Ask the supplier to explain any gap between your environment and its evidence. Repeated moves between a cold room and a warm loading area deserve a specific discussion of condensation. Routine exposure to a cleaning chemical requires compatibility guidance. Where a workplace requires hazardous-location certification, obtain the relevant approval for the exact equipment and location through the site's responsible specialist.
Use an ordinary operating trial to evaluate handling and usability. Arrange any destructive or environmental testing with the supplier and a qualified test facility; dropping or soaking a loan unit is a poor substitute for a documented test plan.
Plan power, updates and recovery together
Battery capacity is one input to runtime. Screen brightness, scan frequency, radio use, temperature and battery condition all belong in the trial record. Measure a demanding shift with the intended application and accessories. If the plan includes changing batteries, verify what happens to the active transaction, network session and unsent data during the documented replacement procedure.
Distinguish operating-system availability from security-update entitlement. Zebra's LifeGuard FAQ, for example, describes update access and transition policies tied to its products and coverage arrangements. Request the policy for the candidate model and contract, including the end date, deployment method and who is responsible for installing updates.
For a legacy migration, inventory the old application's dependencies before choosing replacement hardware: operating system, scanner integration, authentication, printers and back-end interfaces. Microsoft's Windows Embedded Compact 2013 lifecycle records the end of extended support in October 2023. Check the exact OS on your fleet; a similar product-family name does not establish its support status.
Budget for chargers, spare batteries, grips, cases, repairs, provisioning and worker training. Specify how a replacement device receives its configuration and how a user resumes unfinished work. For the data-capture and application side, use the industrial handheld workflow guide.
Run a pilot with pass criteria agreed in advance
- Choose representative work. Include routine jobs, difficult labels, coverage gaps and the busiest shift. Obtain approval before testing against production systems.
- Establish a baseline. Record transaction time, retries, corrections and current failure patterns using the same definitions you will apply to the candidate.
- Observe several users. Watch where they change grip, repeat a scan, misread feedback or set the device down. Include both experienced and newer workers.
- Exercise recovery. In a controlled test, restart the application, lose connectivity and perform the approved battery change. Verify the final records in the back-end system.
- Review by requirement. Record pass, fail or unresolved, with evidence. Assign each unresolved issue an owner before purchase.
A purchase decision should identify which configuration passed, what remains conditional, who owns updates and what happens when a unit fails. For route work, also check the delivery handheld and offline-event guide.
Keep a requirements record you can revisit
Download the handheld requirements and pilot worksheet (plain text). It includes spaces for conditions, supplier evidence, measured results, unresolved issues and a decision owner. Complete one copy per candidate using the same workload and units.
Revisit the record when the application, label stock, working environment or support policy changes. Those changes can matter as much as a new hardware model.
Explore handheld computing
Handheld computers: work devices, accessories and classic PDAs
Sources are linked beside the claims they support. Product and software documentation should be checked for the exact model and version before applying a procedure.