Warehouse projects do not fail because the PDA is too slow. They fail because the PDA arrives after the software contract is signed, and nobody checked how the two would talk. This is the sequence that avoids that.
Start from the software, not the catalogue
Every WMS, ERP app and custom Android client falls into one of three data patterns:
- Keyboard-wedge style — the app expects scan data typed into a field. Almost any Android PDA with a 2D imager works; the risk is low.
- SDK or service integration — the app listens to a broadcast, an intent or a vendor SDK. The PDA brand must be on the software vendor's supported list, or you own the glue code.
- Browser or terminal emulation — Telnet-style legacy clients and web apps. Keyboard remapping and key macros decide the day, not processor speed.
Ask the software vendor which pattern applies, and get the answer in writing. It changes the PDA shortlist more than any specification sheet.
The four hardware questions that follow
Once the integration pattern is known, four hardware questions remain.
| Question | Why it matters | Typical answer |
|---|---|---|
| Screen size | Forms and pick lists differ | 5.5–6" for full forms, keypad units for pure scanning |
| Scan distance | Shelf edge vs high rack | Standard imager up to 3 m, long-range head beyond |
| Battery strategy | Shift length | Removable pack for two-shift operations |
| Sealing and drops | Dock and yard work | IP65+ and 1.5 m drops cover most warehouses |
A mid-range Android PDA with a proper imager outlives a flagship phone with a camera pretending to be one. The imager, not the CPU, is the part your operators touch ten thousand times a day.
Pilot structure that finds the truth
Run the pilot on the busiest process, not the easiest one. Receiving docks expose keyboard handling problems, cycle counts expose scan-distance problems, and dispatch exposes battery problems. Twenty units for two weeks on real orders tells you more than a demo table ever will.
We pre-configure pilot units with the scanner mode, keyboard layout and kiosk settings your software needs, so the test starts on day one instead of day four. Send us the software name and version — we will tell you which models are already running on it.
