Contents
This guide covers scanner hardware selection, what Inventory Pro Mobile actually expects from scan input, and the hardware checks that solve the most common field issues.
Use these questions to narrow down which scanner fits your operation:
| Question | Recommendation |
|---|---|
| Need to scan barcodes at distances over 30 feet? | Zebra MC9400 or Honeywell CT47 |
| Data encryption is a regulatory requirement? | Zebra TC53e (hardware Secure Element) |
| Need the longest possible vendor support window? | Honeywell CT37 (through 2033) |
| Budget is the primary concern? | Zebra TC22 (lowest-cost entry) |
| Devices see heavy physical use with frequent charging? | Datalogic Memor 35 (wireless charging) |
Treat the devices below as reference models, not an official certification list. Final compatibility depends on Chrome behavior, HTTPS camera access, OEM scanner-profile setup, and Wi-Fi quality in your environment.
| Model | Vendor | Support End | Android | Screen | Drop Rating | Best For |
|---|---|---|---|---|---|---|
| Zebra MC9400 | Zebra | 2031 | A13-A17 | 4.3” | 12 ft | Heavy DC, cold storage, gloved use |
| Honeywell CT47 | Honeywell | 2030 | A12-A15 | 5.5” | 8 ft* | Near/far scanning (3 in to 40+ ft) |
| Zebra TC53e | Zebra | 2032 | A13-A17 | 6.0” | 8 ft* | Mid-market, data-sensitive supply chains |
| Honeywell CT37 | Honeywell | 2033 | A14-A18 | 6.0” | 6 ft* | Small-mid ops, longest support lifecycle |
| Zebra TC22 | Zebra | 2030 | A13-A16 | 6.0” | 5 ft* | Small business, budget entry |
| Datalogic Memor 35 | Datalogic | 2033 | A13-A18 | 6.0” | 6 ft* | Healthcare, cleanroom, wireless charging |
* Drop rating with rubber boot/case. Support windows, drop ratings, and feature bundles are vendor-reported and not guaranteed.
Contact manufacturers or authorized resellers for current pricing.
| Requirement | Details |
|---|---|
| OS | Android 12 or later |
| Browser | Chrome (latest two major versions) |
| Screen | 5 inches or larger preferred |
| Connectivity | Wi-Fi required; cellular data works as fallback |
| Scan Input | Keyboard wedge or browser camera scanning; vendor-specific browser injection may also work |
Inventory Pro Mobile runs in a browser. In the validated Mobile UI, the reliable paths are scanned data entering the active browser field and the built-in on-screen camera scanner. Treat any OEM intent workflow as a deployment-specific integration that should be validated on the actual device profile before rollout.
| Surface | What it exposes |
|---|---|
| Settings | No scanner controls; only Test Signature, Reset Cache, and Clear Transactions |
| Transaction Scan buttons | Open the built-in camera scanner on supported devices or let wedge input fill the active field |
| Inventory -> Scanner Issue | Dedicated Scan and Review tabs for scan-first issue workflows |
There is no validated user-facing scanner setup page inside Inventory Pro Mobile.
Most dedicated scanners should be configured so barcode data lands in the active browser field as keyboard input. In this mode, the scan behaves like typed input and works with Inventory Pro Mobile without adding an in-app scanner profile.
If the user taps the on-screen Scan button, Inventory Pro Mobile can open a built-in camera scanner. That path requires HTTPS plus browser camera support.
Some devices also support intent-based scanning, but Inventory Pro does not expose a dedicated intent-configuration screen in Mobile Settings. Treat intent mode as a vendor-specific deployment choice and validate it with the OEM or your MDM profile before relying on it in production.
Scanner performance depends heavily on Wi-Fi reliability. In warehouse environments, dropped connections and sticky clients are the most common complaints.
| Setting | Value | Why |
|---|---|---|
| Roaming threshold | -65 to -70 dBm | Forces handoff before signal degrades |
| Band | 5 GHz preferred | Less interference from Bluetooth and other 2.4 GHz devices |
| Battery saver | Disabled for browser and Wi-Fi | Prevents Android from throttling the connection |
| AP density | One AP per 5,000-8,000 sq ft | Depends on racking height and materials |
If operators lose connection when walking between areas, the scanner is likely holding onto a weak access point. Set the roaming aggressiveness to “high” in the device Wi-Fi advanced settings, and configure your wireless controller to set a minimum RSSI threshold.
Dirty lens - This is the cause roughly 90% of the time. Dust, adhesive residue, and warehouse grime build up on the scanner window. Wipe with a lint-free cloth and a small amount of isopropyl alcohol (99%).
Aimer misalignment - Extended-range scanners have a minimum focal distance, usually around 5 inches. If you are holding the scanner too close, move back.
Illumination conflict - High-bay warehouse lighting can wash out the scanner laser. Try scanning at a slight angle rather than straight-on.
On-screen Scan button does nothing - Confirm the site is running over HTTPS and that the device browser has camera permission. The built-in camera scanner is not the same thing as an OEM hardware scanner profile.
Wi-Fi sticky client - The device is holding onto a weak AP. See Wi-Fi Configuration above.
Battery saver mode - Android battery optimization can throttle background processes and Wi-Fi. Disable it for the browser app.
Pending transactions - If the connection drops mid-scan, Inventory Pro Mobile queues the transaction. Check Utilities > Pending Transactions after reconnecting.
Hot-swapping - The MC9400, CT47, and TC53e support battery swap without closing the app. You have a 30-60 second window on internal capacitor power.
Contact cleaning - For pin-based charging cradles, clean the contacts with a pencil eraser if charging becomes unreliable. Oxidation builds up over time.
Battery replacement - Enterprise scanner batteries are replaceable. Budget for spare batteries rather than spare devices.
On this page