The answer you need before the purchase order.
Integration notes, compatibility questions and configuration details that normally take three emails and a distributor to resolve.
Software compatibility
What the device assumes, and how to check your app against it before you order: API level, GMS, scanner output mode, and the Windows client question.
Read the notes→Pre-dispatch configuration
Kiosk lockdown, Wi-Fi profiles, scanner keyboard-wedge settings, locale and time zone set before the unit leaves the warehouse.
What we can pre-set→Model availability
How long a model stays in production, how firmware revisions are tracked, and what happens to a deployed fleet when a model reaches end of life.
EOL policy→SDK pack, evaluation unit, pre-install build
What the firmware does out of the box, what needs a requirement and a confirmation, and how to get a unit configured for your app before the rollout.
The four questions that decide a rollout
1. Android API level and GMS
An app built for API 30 will not run on a device locked to an older level without a rebuild. Google Mobile Services are present on most of our Android models; for deployments that must avoid them, the same hardware ships with non-GMS firmware. Confirm which you need in writing.
2. How the scanner delivers data
Three modes exist and they are not interchangeable:
- Keyboard wedge — the scan appears as typed characters. Works with any app, no integration.
- Intent broadcast — Android delivers the scan to a listening app. Requires a small app change.
- SDK — full control over the engine, including aiming and illumination. Requires real integration work.
Most failures come from an app that expects one mode and a device configured for another. Tell us which mode the software uses and we will configure the unit to match before dispatch.
3. Windows client on mobile hardware
If the client is a Win32 application, two routes exist: a Windows device (M10J, M80J, M87J, V10J, EM-I61J) or a remote session from an Android device. The first is more robust offline; the second is cheaper per seat but depends on connectivity. Both should be tested on a sample.
4. Peripherals
Printers, cradles and external scanners are where integration projects actually stall. Send the peripheral models with the device enquiry — Bluetooth printer pairing behaviour in particular varies by printer firmware, and it is worth testing on the sample rather than at rollout.
Model matrix
The models we quote most for integration projects — the full range has 144 models.
| Model | Form | OS | Scan | Sealing | Best for |
|---|---|---|---|---|---|
| BH-I61J | Handhelds | Windows | 2D | IP65 | 6.5" Windows rugged handheld, IP65, -20 °C~60 °C. |
| BH-BX6200 | ID terminals | Android 10.0 | 2D | IP65 | ID-terminal PDA, 5.5" · IP65. |
| BT-I20J | Tablets | Windows | 2D | IP65 | 12.2" Windows rugged tablet, IP65, -20 °C ~ 60 °C. |
| BN-X15A | Laptops | Windows | — | IP65 | 15.6" Windows rugged notebook, IP65, -20 °C~60 °C. |
| BPC-P15A | Panel PCs | Windows | 2D | IP65 | 15.6" Windows rugged panel PC, IP65, -20 °C ~ 60 °C. |
| BH-F1 | Handhelds | Android | 2D | IP67 | 4.0" Android 11 rugged handheld, IP67 and 1.5 m drop, 5000 mAh battery, 2D imager and numeric keypad. |
| BH-F2 | Handhelds | Android | 2D | IP67 | 6.0" Android rugged handheld, IP67 and 1.5 m drop, 5050 mAh battery, NFC and 2D imager. |
| BH-F5 | Handhelds | Android | 2D | IP67 | 6.0" Android rugged handheld, IP67 and 1.5 m drop, 5050 mAh battery, NFC, ID-card reading and 2D imager. |
| BTM-14A | Tablets | Windows | 2D | IP65 | 14" Windows 11 Pro rugged tablet, IP65 and MIL-STD-810H, Intel Core Ultra platform, optional 2D imager. |
| BP-T1 | Outdoor | Android | — | IP68 | 8.68" Android rugged outdoor device, IP68, -20 °C~60 °C. |
| BN15M | Laptops | Windows | — | IP65 | 15" Windows 11 Pro rugged AI PC, IP65 and MIL-STD-810H, Intel Core Ultra platform, optional touch panel. |
| BV-V10J | Vehicle mount | Linux | — | IP65 | 10.1" Linux rugged vehicle terminal, IP65, -20 °C~60 °C. |
| BT-I10A | Tablets | Linux | 2D | IP65 | 10.1" Linux rugged tablet, IP65, -20 °C~60 °C. |
| BH-T40 | Handhelds | Android | 2D | IP65 | 4" Android rugged handheld, IP65, -10 °C~50 °C. |
| S300 Pro | PoC Radios | Android | — | — | Professional smart PoC terminal with a full Android app stack. |
| BH-C6100 | RFID | Android 10 / 13 | 2D | IP65 | UHF RFID handheld, 20 m class · IP65. |
| BH-C6200 | ID terminals | Android 10.0 | 2D | IP65 | ID-verification handheld, 5.5" · IP65. |
| BV-V10T-10 | Vehicle mount | Android | — | IP65 | 10.1" Android rugged vehicle terminal, IP65, -20 °C~60 °C. |
| BN-A14-AI | Laptops | Windows | — | IP65 | 14" Windows rugged notebook, IP65, -20 °C~60 °C. |
| BPC-B10A | Panel PCs | Windows | 2D | IP65 | IP65, -20 °C ~ 60 °C. |
Answered before the sample ships
The questions developers ask on the first call, written down so the call can be shorter.
All questions01Do the Android units ship with GMS?
02What about MDM and Android Enterprise?
03Is there an SDK?
04Will my existing app run on it?
05Can the scanner be used as a keyboard wedge?
Send the software profile.
Client name, version, OS requirement and scanner mode. We will confirm compatibility on a real unit before you commit.