Barcode Scanner Interfaces: Keyboard Wedge, USB HID and Serial
A barcode scanner reads the code the same way whatever it is plugged into. What changes, and what causes most of the integration problems, is how it hands that data to the application. The same scanner can behave as a keyboard, as a serial port, or as a device your software talks to directly, and the mode it is in decides whether the deployment is trivial or a week of debugging.
This guide covers the interface modes you will meet, which one to choose for a given application, the character-mangling problem that catches out international deployments, and how to change a scanner from one mode to another.
USB HID keyboard emulation
This is the default on almost every scanner sold today, and for most people it is the right answer. The scanner presents itself to the operating system as a USB keyboard. Whatever it decodes is typed into whichever field currently has focus, as fast as a very quick typist.
Why it wins: no drivers, no configuration on the host, no application changes. It works in a browser form, a terminal emulator, Excel, a legacy Windows application and a point of sale package without any of them knowing a scanner exists.
What you give up: the connection is one way. The application cannot tell the scanner to beep, change its illumination, enable a symbology or report its battery level, because keyboards do not accept that kind of instruction. You also have no way to distinguish scanned input from typed input, which matters if you need to validate that a value came from a real barcode.
The focus problem. Because data goes to whatever has focus, a scan triggered while the cursor sits in the wrong field puts a part number into a quantity box. In high-volume environments this is a genuine source of data errors, and no amount of scanner configuration fixes it.
The keyboard layout trap
This is the single most common scanner deployment failure outside the US, and it looks like a broken scanner when it is nothing of the sort.
In keyboard emulation the scanner does not send characters. It sends key codes, exactly as a physical keyboard does, and the operating system converts those key codes into characters using whatever keyboard layout is configured. If the scanner is emulating a US layout and the workstation is set to German, French or UK, the characters that arrive will not match the barcode.
Numbers usually survive. What breaks is punctuation and symbols: hyphens, slashes, brackets, the at sign, and on French layouts the digits themselves can require a shift. A barcode containing a hyphen decodes correctly and then arrives in the application as something else entirely.
The fix is to set the scanner's country or keyboard layout setting to match the workstation, not to replace the scanner. Every major scanner supports this and it is usually a single programming barcode. If you run mixed layouts across sites, standardise, because this problem reappears every time a machine is rebuilt.
Serial: RS-232 and USB virtual COM
Serial mode gives the application a real conversation with the scanner instead of a stream of keystrokes.
True RS-232 uses a physical serial port and is still common on older point of sale systems, industrial controllers, weighing equipment and machines that predate USB. It needs matching baud rate, data bits, parity and stop bits at both ends, and a mismatch produces garbage characters rather than an error.
USB virtual COM, sometimes called USB CDC, gives you the same programming model over a USB cable. The scanner appears as a COM port, the application opens it and reads from it.
Why choose serial: the application knows the data came from the scanner, focus is irrelevant, communication is bidirectional so you can trigger scans and control indicators from software, and you can handle errors properly instead of hoping. For any purpose-built application, this is the more robust choice.
The cost: the application has to be written to open and read a port, which rules it out for web forms and off-the-shelf software that expects keyboard input.
Our guide on printer connectivity covers the equivalent decision on the printing side, where the same trade-offs apply.
Legacy keyboard wedge
The original keyboard wedge was a physical splitter: the scanner sat between the PS/2 keyboard and the computer, passing keystrokes through and injecting its own. The term survives as a description of behaviour, which is why USB HID mode is still called keyboard wedge in a lot of documentation.
Genuine PS/2 wedge hardware only matters now if you are maintaining equipment old enough to require it. If you are, the Y-cable is a specific part and frequently missing from used listings. Our guide on identifying scanner variants covers the cable and cradle question, which is where most used scanner purchases go wrong.
Retail POS interfaces
Supermarket and large retail systems often use interfaces that exist nowhere else: IBM 46xx, OCIA and similar. These are not generic, and a scanner has to be ordered or configured for the specific till system.
If you are adding scanners to an existing lane, find out what the current ones are set to before ordering anything. A scanner that is physically identical but configured for the wrong POS interface will not work and cannot always be converted. Our guide on retail front-of-store hardware covers the lane environment.
Bluetooth: HID or SPP
Cordless scanners repeat the same split wirelessly.
Bluetooth HID pairs the scanner as a keyboard. Simple, driverless, and the same focus and layout caveats apply.
Bluetooth SPP gives a serial port over Bluetooth, with the same bidirectional benefits as wired serial.
The cradle is not just a charger. On most cordless scanners the base station is the interface, and it holds the host connection and often the pairing. A scanner bought without its base may be unusable rather than merely inconvenient, and bases are frequently sold separately.
Batch mode matters more than people expect. A cordless scanner out of range that silently drops scans is worse than one that stores them and uploads on return. Confirm the behaviour rather than assuming, and see warehouse Wi-Fi for scanners for coverage planning.
Prefixes, suffixes and timing
Two configuration details cause a disproportionate share of support calls.
Terminators. Most applications expect a carriage return after the scan so the form submits or the cursor advances. Some want a Tab to move to the next field. Some want nothing. A scanner sending Enter into an application that wanted Tab will submit a half-filled form on every scan.
Inter-character delay. Scanners in keyboard mode send characters faster than some applications can accept them, particularly older software, remote desktop sessions and browser fields with JavaScript validation on every keystroke. The symptom is characters dropped from the middle of otherwise correct scans. The fix is a small inter-character delay in the scanner configuration. People replace scanners over this; the setting is free.
Our guides on scanner configuration and fleet deployment and barcode not scanning troubleshooting cover both in practice.
Changing the interface
Scanners are configured by scanning programming barcodes out of the manufacturer's configuration guide, and interface mode is one of the first settings in every such guide. Vendors also provide configuration software that generates a single barcode or a file carrying a whole profile.
For a fleet, build one configuration and apply it to every unit. A sheet of programming barcodes that sets interface, country layout, terminator, delay and enabled symbologies takes seconds per scanner and removes an entire class of inconsistency. Keep that sheet with the device documentation, because the next person to replace a failed scanner will need it.
Some cables also carry the interface identity, so on certain models swapping the cable changes the mode. Check before assuming a scanner is faulty.
Sourcing
We supply corded, cordless, rugged and presentation barcode scanners from Zebra, Honeywell and Datalogic, with cables and cradles matched. If you are replacing scanners on an existing system, send us the current model or the till system and we will confirm the interface and supply the right cable rather than leaving you to work it out. Request a bulk quote or email sarah.jane@techsellerusa.com.
Common questions
What is keyboard wedge mode?
It means the scanner presents itself as a keyboard, so decoded data is typed into whatever field has focus. The name comes from original PS/2 scanners that physically wedged between the keyboard and the computer. Today the same behaviour is delivered over USB as HID keyboard emulation, and it remains the default because it works with any application without drivers or code changes.
My scanner types the wrong characters. Is it broken?
Almost certainly not. In keyboard mode the scanner sends key codes, and the operating system converts them using the configured keyboard layout. If the scanner is set to a US layout and the machine is set to UK, German or French, punctuation and symbols will come out wrong while digits mostly survive. Set the scanner's country or keyboard layout setting to match the workstation, usually with a single programming barcode.
When should I use serial or virtual COM instead of keyboard mode?
When you control the application and want reliability. Serial mode means the software knows the data came from the scanner, field focus becomes irrelevant, the connection is bidirectional so you can trigger scans and control indicators, and errors can be handled properly. The trade-off is that the application must open and read a port, so it is not an option for web forms or off-the-shelf software expecting keyboard input.
Characters are missing from the middle of my scans. Why?
The scanner is sending keystrokes faster than the application can accept them. This is common with older software, remote desktop sessions, and browser fields running validation on every keystroke. The fix is to add a small inter-character delay in the scanner configuration, which is a free setting change. People replace perfectly good scanners over this symptom, so try the delay before concluding the hardware is at fault.
Can I change a scanner from one interface to another?
In most cases yes, by scanning programming barcodes from the manufacturer's configuration guide, or by using the vendor's configuration software. Interface mode is usually one of the first settings in the guide. Two caveats: on some models the cable itself carries the interface identity, so the mode changes when you change the cable, and some retail POS interfaces such as IBM 46xx require specific hardware that cannot be configured in.
Do I need the cradle with a cordless scanner?
Usually yes, and this is the most common problem with used cordless scanners. On most models the base station is the host interface as well as the charger, holding the cable connection to the computer and often the pairing relationship. A cordless scanner bought without its base can be unusable rather than merely inconvenient. Confirm the base is included, and that it is the correct base for that model, before buying.
If you are replacing scanners on a system someone else set up, send us the existing model and we will confirm the interface and cable before you order.
