Retail IT teams buy PDAs three times: once for the pilot store, once for the rollout, and once again because the rollout bought the wrong accessory. This checklist is the difference between the first and the third purchase.
Match the device to the software stack
Modern retail stacks mix three clients on one device: the POS back-office app, an inventory or stocktake app, and increasingly a messaging tool for floor staff. Before shortlisting hardware, confirm:
- OS version policy — the app vendor's minimum Android version and their enterprise support window.
- Scanner integration — does the app read from the imager service, or does it need its own camera path? The first is faster and works with gloves.
- MDM compatibility — if the fleet is managed through an MDM, the PDA must be enrolable as a fully managed device.
A device that fails any of the three is cheap on the quote and expensive in the rollout.
The retail-specific specifications
| Requirement | What to specify | Where it fails otherwise |
|---|---|---|
| Shelf-edge scanning | Standard 2D imager, close-range optics | Scanning EAN at 8 cm distance |
| Price checks in aisle | Sunlight-readable display, 500 nit+ | Unreadable under track lighting |
| Full-shift battery | 4000 mAh+ or removable pack | Dead by the evening restock |
| Drop survival | 1.2 m to concrete, multiple times | Concrete floors end plastic phones |
| Hygiene | Sealed IP65 body, wipeable | Cannot disinfect between shifts |
Keypad or touch is a workflow decision: touch for price checks and shelf audits, keypad where gloves and speed matter.
Roll out in waves, keep the spares ratio
Roll out in store-waves with one spare per twenty units, and keep the spare pool centrally. The models we position for retail carry a documented firmware line and EOL notice, so the fleet you deploy this quarter is still serviceable when you open the next ten stores.
Send us the store format and the software names — we will come back with two models, the accessory list and a pilot quotation.
