The types barcode scanners pos counters use differ less in their engines than in the one setting each needs confirmed. The types themselves are described in the five scanner types.
Key Takeaways
- A scanner that appears dead is usually missing a line ending.
- A presentation stand needs hands free mode enabled.
- A wireless scanner needs its pairing to survive a restart.
- A fixed mount unit needs a continuous trigger.
- Support for a symbology is not the same as enabled.
- None of these six symptoms is a hardware fault.
Why the types barcode scanners pos counters use need configuring
Scanners are among the most reliable devices on a counter and among the most often returned, which is a contradiction worth explaining.
The engine itself rarely fails. What fails is the assumption that a device works correctly at the settings a maker shipped it with.
Scanner support documentation publishes symbology support and interface options, and supported is a different word from enabled.
So a scanner can be entirely capable of reading a code and still refuse it, because that particular family was left switched off.
Six settings cover almost every complaint, and each corresponds to one type of installation rather than to a brand.
Confirming them takes minutes at installation and is the single cheapest thing a dealer can do for you.
So the types barcode scanners pos counters use are best distinguished by the setting each depends on rather than by the engine inside them.
| Assumption | Reality | Consequence |
|---|---|---|
| It works out of the box | Defaults are generic | One setting missing |
| Supported means enabled | They are different | A code family refused |
| Pairing is permanent | It may not survive a restart | Dead on Monday |
| A stand reads continuously | Hands free is a setting | Trigger pressed by hand |
| Any field receives the scan | The app needs focus | Codes in the wrong box |
Terms used in scanner configuration
Five expressions recur when the types barcode scanners pos counters use are configured, and each denotes one setting.
Keyboard emulation denotes a scanner presenting decoded data as typed characters, which is why no driver is required.
A line ending denotes the character appended after the code, which tells the terminal that the entry is complete.
A prefix or suffix denotes characters added before or after the code, occasionally required by a particular billing application.
A symbology denotes a family of code patterns, which must be both supported by the engine and enabled in the configuration.
Hands free mode denotes continuous reading without a trigger, which is the behaviour a presentation stand is bought for.
- Keyboard emulation: typed characters, no driver.
- Line ending: tells the terminal the entry is complete.
- Prefix or suffix: sometimes required by the software.
- Symbology: must be supported and enabled.
- Hands free mode: continuous reading, a setting.
Type one: the corded handheld
This is the commonest type at a small counter and the one whose single setting causes the most wasted support calls.
It presents itself as a keyboard, which means the decoded number arrives exactly as though somebody had typed it.
That arrangement needs no driver, which is why the type has become conventional, and it depends entirely on one thing after the number.
The scanner must append a line ending, or the terminal sits waiting for a keystroke that never arrives.
So the symptom is a scan that appears to do nothing, with a beep from the scanner and no reaction from the screen.
Confirm it at the dealer by scanning into a plain text field and watching whether the cursor moves to a new line.
- Scan into a plain text field at the dealer.
- Watch whether the cursor moves to a new line.
- If it does not, ask for the setting to be changed.
- Ask for the configuration sheet to take away.
- Repeat the test at your own counter after installation.
Type two: the presentation stand
This type is an ordinary scanner in a cradle, and the behaviour people buy it for is a setting rather than a property.
Hands free mode makes the unit read continuously whatever passes in front of it, which is the whole reason a grocery wants one.
Left at a trigger default, the same device reads only when the button is pressed, which removes the benefit entirely.
So the symptom is a stand that works and does not help, and the shop concludes the type was oversold.
Confirm it by passing a label across the unit without touching it, in the stand it will actually sit in.
Ask about the beep volume while you are there, because a continuously reading unit at a busy counter beeps a great deal more than a handheld does.
Why defaults are wrong for a counter
Manufacturers ship configurations intended for a general international market rather than for any particular counter, which is a reasonable decision with predictable consequences.
A general default enables the most widely used symbologies and disables the remainder, because enabling everything slows decoding and increases misreads.
A general default similarly selects a conservative terminating character, since different host systems expect different behaviour after a code.
An Indian counter consequently arrives requiring at least two deviations, one for the payment code family and one for whatever its weighing instrument prints.
Neither deviation is a fault, and neither is documented anywhere the shop will look, which is why both surface as complaints during the first fortnight.
Requesting a configuration sheet at purchase resolves the whole category, and no dealer objects because producing one costs a printout.
| Default chosen for | Why | What a counter needs |
|---|---|---|
| Common symbologies only | Speed and fewer misreads | Payment codes enabled |
| A conservative line ending | Hosts differ | Whatever your terminal expects |
| Trigger reading | It suits handhelds | Hands free for a stand |
| Conservative pairing | It suits many hosts | Persistence across restarts |
| Moderate beep volume | General environments | Louder or quieter, as suits |
Type three: the wireless unit with a cradle
This type adds reach and adds two things to maintain, and the second is not the battery.
The pairing between the scanner and its cradle is the setting that matters, and its behaviour across a power cycle differs by model.
On some models the pairing survives a restart, and on others it must be re established, which produces a scanner that is dead every Monday morning.
So the symptom looks like a failing device with a weekly pattern, and the pattern is the clue rather than the fault.
Confirm it at the dealer by powering everything down and back up, which takes a minute and settles the question permanently.
Insist on the charging cradle rather than a cable, because a scanner charged by habit is maintained and one charged by memory is not.
Type four: the fixed mount unit
This type lives inside a counter slot and depends on a trigger setting that no operator can reach.
A continuous trigger is what makes it read goods passed over the glass, and there is no button to press if that setting is wrong.
So the symptom is a unit that reads nothing at all, which looks like an installation fault and is a configuration one.
Confirm it before the counter carpentry is finished, because reaching the unit afterwards is considerably harder.
Ask also how the unit is reconfigured later, since a fixed mount device usually accepts configuration scans and sometimes only through a cable.
Keep the configuration sheet with the counter photograph, because the person who needs it in three years will not be the person who installed it.
Type five: the scanner paired to a tablet
This type appears wherever a tablet based counter exists, and its setting question is about software rather than the scanner.
The decoded number goes wherever the operating system is currently sending keystrokes, which means the billing application must have focus.
So the symptom is codes landing in the wrong field, or in no field, whenever a notification or another app has taken the foreground.
Confirm the behaviour with a notification arriving mid scan, which is the situation that produces the complaint in real use.
Ask whether the billing application can be locked to the foreground, since that single setting removes the whole category of problem.
Ask about pairing persistence as well, because a tablet paired scanner combines the wireless question with this one.
- Confirm the billing app can hold the foreground.
- Test with a notification arriving mid scan.
- Confirm pairing survives a tablet restart.
- Keep one corded unit as a fallback.
Type six: reading your own scale labels
The last type is not a device but a use, and it is the one most often discovered to be unsupported after installation.
Legal Metrology requires weighing instruments used in trade to be verified and stamped, and the label carrying weight and price is printed at the instrument.
That label frequently uses a different symbology from a shelf barcode, and the difference is invisible to the eye.
GS1 India issues and administers the numbering system used by Indian products, which is the family most counters have enabled by default.
So the symptom is a scanner that reads everything on the shelves and refuses the shop’s own labels, which usually gets blamed on the scale.
Confirm it with an actual scale label at the dealer, and ask for the symbology to be enabled rather than accepting that the label is at fault.
The setting that applies to every type
One requirement crosses all six types and has become the clearest dividing line at an Indian counter.
UPI payment codes are two dimensional, which means a one dimensional engine cannot read them under any circumstances.
Where the engine is two dimensional, the relevant family must also be enabled, since support and enablement are different states.
So test a payment code on your own phone with every candidate, and treat a refusal as decisive rather than as a configuration question.
Where it reads with a setting change, ask for that change to be made and recorded on the configuration sheet.
Rule 46 of the CGST Rules lists the invoice particulars, and none of this affects them, because the catalogue behind the number supplies those.
Reconfiguring later, without a visit
Settings occasionally have to change after installation, and knowing how in advance saves a support call for something that takes a minute.
Most counter scanners accept configuration by scanning a printed barcode from the maker’s documentation, which needs no software at all.
So ask for the relevant configuration codes to be printed and kept with the counter record rather than left in an online manual.
The codes most worth having are the line ending, the hands free toggle and the enable code for any symbology you might add later.
Some models instead require a cable and a utility, which is worth knowing before a fixed mount unit disappears into counter carpentry.
Write which method applies on the configuration sheet, because the person needing it in three years will not be the person who installed the counter.
- Ask which method the model uses to reconfigure.
- Ask for the key configuration codes, printed.
- Keep them with the counter record, not online.
- Note the method on the configuration sheet.
- Test one change at installation, so you know it works.
- Line ending code: resolves apparent dead scanners.
- Hands free toggle: resolves a stand read by hand.
- Symbology enable codes: resolve refused labels.
- Factory reset code: the last resort, worth having.
A configuration sheet for any of the types barcode scanners pos counters use
One sheet records every setting and is worth more than the manual, because it describes your installation rather than a general one.
Write the scanner model and the type it is, since the type determines which of the six settings apply.
Write whether a line ending is sent and what it is, because that single line resolves most future complaints in seconds.
Write which symbologies are enabled, including the one your scale prints, and write the date they were enabled.
Write the pairing behaviour across a restart for any wireless unit, and write how the unit is reconfigured if it needs to be.
Keep the sheet with the counter photograph and the measurement slip, because the three together are a complete record of the counter.
| Line on the sheet | Why it matters | When you need it |
|---|---|---|
| Model and type | Determines which settings apply | Any complaint |
| Line ending sent | Resolves apparent dead scanners | First week, and later |
| Symbologies enabled | Scale labels and payment codes | When a label is refused |
| Pairing across a restart | Explains Monday failures | Any wireless unit |
| How to reconfigure | Fixed mount units especially | Years later |
Testing a scanner properly at the dealer
Five tests confirm all six settings, and together they take about ten minutes.
Scan into a plain text field and watch for the new line, which settles the commonest complaint before it exists.
Pass a label across the unit without touching it, in the stand it will occupy, which settles hands free mode.
Power everything down and up again, which settles pairing persistence in one minute.
Scan one of your own scale labels and a payment code from your own phone, which settles both symbology questions.
Then scan one difficult label twenty times and count hesitations, which is the only test on this page about the engine rather than the settings.
The fuller label based test is in the six label test.
What no setting can fix
Three problems survive every configuration change, and recognising them saves a wasted afternoon.
A one dimensional engine cannot be configured into reading a two dimensional code, because the limitation is optical rather than logical.
A code printed below its minimum bar width cannot be recovered by any reader, because the printed pattern lacks the information.
A faint label is a printing problem, and a fresh ribbon or roll in whatever produced it is the only remedy.
So the honest sequence is settings first, because they are free, and then labels, and only then the device.
The selection criteria behind the device choice are in choosing a scanner for your counter.
Wrong fit: scanner assumptions that disappoint
Five assumptions recur. Each is a wrong fit, with the honest version beside it.
| Assumption | Why it is a wrong fit | Honest version |
|---|---|---|
| It works out of the box | Wrong fit: defaults are generic | Confirm six settings |
| Supported means enabled | Wrong fit: they are different states | Ask which are enabled |
| A stand reads continuously | Wrong fit: hands free is a setting | Pass a label without touching it |
| Pairing is permanent | Wrong fit: it may not survive a restart | Power everything down and up |
| The scale label is at fault | Wrong fit: the symbology is off | Ask for it to be enabled |
The device level version of these errors is catalogued in common POS hardware mistakes.
Six types, six settings, and almost every scanner complaint at a counter turns out to be one of the six left unconfirmed.
Written on one sheet, the types barcode scanners pos counters use stop producing mysteries and start producing answers in seconds.
Conclusion
Confirm the line ending, hands free mode, pairing persistence, the continuous trigger, the application focus and every symbology you need, including the one your scale prints. Write them all on one sheet. The buying order for a counter is in the buying order for a counter.
Sources and method
Device information comes from maker docs. Zebra Technologies publishes symbology support and interface options on its scanner support pages. The rules and standards are primary. GS1 India issues and administers the barcode numbering system. Rule 46 of the CGST Rules sets the invoice particulars, and NPCI documents the two dimensional UPI code. The Legal Metrology division covers weighing instruments used in trade.
What we could not verify: no model specific setting names or menu paths are given, because they differ by maker and revision and must come from the unit’s own documentation.
This is general guidance. Confirm your GST position with your accountant, and verification cycles with your state Legal Metrology office.
Written by Aman raj for Clonet Technologies, a manufacturer of printers, weighing scales and point-of-sale equipment.
Frequently asked questions
Why does my scanner appear to do nothing?
Usually because it is not sending a line ending after the code. The terminal waits for a keystroke that never arrives, so a working scanner looks dead.
What is keyboard emulation?
The scanner presents the decoded number as though it had been typed. That is why most counter scanners need no driver, and why the line ending setting matters so much.
My presentation scanner only reads when I press the button. Why?
Hands free mode is not enabled. A stand is an ordinary scanner in a cradle, and the continuous reading behaviour is a setting rather than a property.
My wireless scanner is dead every Monday. What is wrong?
The pairing is not surviving a power cycle. Confirm that behaviour at the dealer, because it is a setting on some models and a limitation on others.
The scanner reads shelf labels but not my scale labels. Why?
The symbology your scale prints is probably not enabled. Support is not the same as enabled, and enabling it is usually a single configuration scan.