Start with the job, the environment, and the application. The model is the last decision.
1. The job. Receiving at the dock is not picking at the face, and neither one is counting in a freezer. Write down the top three transactions and the scans per hour behind them. An hour on the floor with a tally will produce that list if nobody has it yet.
2. The environment. Indoor ambient, dusty production, cold chain, or yard. That drives the ingress-protection (IP) rating, the operating temperature range, and whether a glove-friendly key beats a large touch target. Ask the supplier for current IP and drop figures; an older brochure is not a current specification.
3. Data capture. One-dimensional (1D) codes on a shelf at one metre, dense two-dimensional (2D) codes on a crumpled label, direct part marking (DPM) on metal, and radio-frequency identification (RFID) on a pallet are four different capture jobs. Test the real labels at the real ranges. If 90% of scans are short-range 2D, specify for that work and give the exception users their own kit.
4. Form factor. Handheld, pistol grip, wearable, or vehicle mount. Shared devices want a grip and a replaceable battery. Personal devices can be lighter. Wearables earn their place when both hands are already full.
5. Power. Shift length plus the charging story. Overnight charging only works if the device actually returns to the cage.
6. The application. Browser, native application, or terminal emulation (TE). This decides the keyboard, the screen size, and whether dedicated terminal-emulation keys are needed. Bring the warehouse management system (WMS) owner into the first meeting.
7. Fleet management. Name the owner of the mobile device management (MDM) tenant, choose how devices enroll — zero-touch enrollment, quick response (QR) code, Samsung Knox, original equipment manufacturer (OEM) staging, or another controlled route — and decide what happens to a lost unit. Rugged hardware still needs a managed fleet around it.
8. Lifecycle. Record the Android version shipping today, the committed upgrades, and the date the OEM stops supporting that branch. Confirm how long accessories and batteries stay available across your planned service life. Unit price does not capture the cost of an operating system without a workable upgrade path.
What helps us prepare a useful first shortlist
Tell us the sites, the transaction list, the environment, the application type, the quantity, the spare policy, and any brand standard you already work to. We will come back with a device-class recommendation and a clear list of the questions still open.
Related: Enterprise mobility · Warehouse and logistics · Request a Quote