A barcode scanner can read a symbol correctly and still send the wrong data to the business application. The cause is often not the scan engine itself, but a configuration setting: a disabled symbology, an unexpected check digit, a Code ID prefix, or a formatting rule that changes the decoded string before transmission.
This guide explains the barcode scanner symbology settings that matter most during deployment. It is written for retailers, warehouses, manufacturers, software integrators and OEM teams that need predictable data from handheld scanners, desktop readers or embedded scan engines.
What is a barcode symbology?
A symbology is the rule set used to encode data into a barcode. Common 1D examples include Code 128, Code 39, EAN-13, UPC-A and Interleaved 2 of 5. Common 2D examples include QR Code, Data Matrix, PDF417 and Aztec.
Two labels can contain the same visible number while using different symbologies. That distinction matters because each format has its own character set, length rules, check-digit behavior and common applications. A scanner must recognize the symbol, decode it and then transmit the result in the format expected by the host system.
Why scanners do not always output the visible characters
The characters printed below a barcode are called human-readable interpretation. They are useful for operators, but they do not always show every encoded or transmitted character. A scanner may add a symbology identifier, include or remove a check digit, convert a UPC code to an EAN format, transmit start or stop information differently, or apply a prefix and suffix.
For that reason, compare the scanner output with the application specification—not only with the characters printed on the label. Use a plain text editor during initial testing so that hidden formatting and application logic do not confuse the result.
The settings that most often affect barcode data
1. Enable and disable symbologies
Many scanners arrive with common retail and logistics formats enabled, while less common formats are disabled. Enabling every available symbology may seem convenient, but it can increase the chance of unintended reads and make validation harder.
A better approach is to enable only the barcode types used in the project. A retail checkout might need EAN-13, EAN-8, UPC-A, UPC-E, Code 128, QR Code and Data Matrix. A warehouse may rely on Code 128, GS1-128, Data Matrix and PDF417. A ticketing system may prioritize QR Code or Aztec.
2. Minimum and maximum length
Some symbologies allow variable-length data. Length restrictions help reject partial, damaged or unrelated codes. If a warehouse item number is always 10 characters, setting an appropriate length range can reduce accidental reads of short internal labels nearby.
Do not apply a length rule without checking all valid production samples. The same symbology may carry different data lengths across suppliers, package sizes or business units.
3. Check-digit transmission
A check digit is calculated from the other characters and helps detect read or printing errors. Depending on the barcode type and scanner setting, the scanner may validate the digit but either transmit it or remove it from the output.
This frequently causes a one-character mismatch between the label and the database. Confirm whether the host application stores the full code, expects the check digit to be present, or calculates it independently. Test UPC, EAN, Code 39 and Interleaved 2 of 5 settings carefully because their check-digit conventions can differ.
4. Code ID or symbology identifier
A Code ID is a short prefix that tells the application which symbology was decoded. Scanner vendors may provide proprietary identifiers, while AIM identifiers use a standardized format. For example, the application can use the identifier to distinguish a Code 128 result from a QR Code result even when both contain similar characters.
Code IDs are valuable when one input field accepts several formats or when software needs different parsing rules. They should be disabled when the application expects only the raw data and has no logic to remove the prefix.
5. UPC and EAN conversion
UPC-A, UPC-E, EAN-13 and EAN-8 are closely related retail formats. Some scanners can expand UPC-E, convert UPC-A to EAN-13 by adding a leading zero, or transmit supplemental two- or five-digit add-ons.
A conversion may make product lookup more consistent across markets, but it can also break a database that stores the original form. Decide on one canonical format and configure every scanner in the rollout the same way.
6. GS1 handling
GS1-128, GS1 DataMatrix and GS1 QR can contain multiple application identifiers such as GTIN, lot number, serial number and expiration date. Some elements have fixed length; others use a separator. The scanner may transmit the raw element string, an AIM identifier, a visible separator replacement or formatted output.
The application must understand the exact transmitted representation. Test variable-length fields and separator behavior with real GS1 labels before deployment. Avoid treating a GS1 DataMatrix as an ordinary Data Matrix if the downstream software needs structured product data.
7. Prefix, suffix and data editing
A scanner can add Enter, Tab or custom characters before or after the barcode. More advanced models can keep selected characters, remove a known prefix, insert delimiters or route different symbologies to different outputs.
Use these features only when the required transformation is stable and documented. If business rules change frequently, it is usually easier to manage parsing in the application than to update hundreds of scanners in the field.
Barcode scanner configuration comparison
| Setting | Why it is used | Common failure if misconfigured |
|---|---|---|
| Symbology enable/disable | Allow only required barcode types | Valid labels do not scan, or unrelated codes scan |
| Length limits | Reject unexpected data lengths | Valid variants are blocked or partial data is accepted |
| Check-digit transmission | Match database and application rules | One missing or extra digit |
| Code ID | Identify the decoded symbology | Unexpected leading characters |
| UPC/EAN conversion | Normalize retail identifiers | Leading zero or expanded code mismatch |
| GS1 separator handling | Preserve structured field boundaries | Lot, serial or date fields merge incorrectly |
| Prefix/suffix | Control application workflow | Premature submission or cursor movement |
A practical configuration and testing workflow
- List every required barcode type. Collect actual labels from products, cartons, screens, documents and suppliers.
- Define the expected output. Record the exact characters, length, case, Code ID, check digit, separators and suffix expected by the application.
- Start from a known configuration. Restore factory defaults or use an approved configuration file before applying project settings.
- Enable only required symbologies. Add length restrictions only after reviewing the complete valid range.
- Test in a plain text editor. Compare raw output character by character before testing business software.
- Test the real application. Confirm lookup, field navigation, duplicate handling and error messages.
- Test difficult samples. Include small, curved, reflective, damaged and screen-displayed codes where relevant.
- Export and label the approved configuration. Record scanner model, firmware version, interface mode and configuration revision.
- Verify production units. Scan a controlled test card after configuration and before shipment or installation.
How to diagnose common output problems
The scanner reads a QR code but not a product barcode
Check whether the product symbology is enabled. Then inspect minimum and maximum length settings and confirm the scanner supports the printed density and size.
The scanner adds characters at the beginning
Disable the Code ID, AIM identifier or custom prefix if the application expects raw data. If the leading character is a zero, review UPC-to-EAN conversion.
The scanned code is one digit shorter
Check whether the symbology's check digit is being validated but not transmitted. Compare the scanner manual, configuration and application requirement.
One scanner works but another identical unit does not
Compare firmware, interface mode and the complete configuration—not only the model number. Use an approved configuration barcode sequence or management tool to standardize the fleet.
Deployment checklist
- Required 1D and 2D symbologies documented
- Expected raw output saved for each test code
- Check-digit rules confirmed
- Code ID or AIM identifier decision recorded
- UPC/EAN and GS1 behavior tested
- Prefix, suffix and formatting rules documented
- Host interface and keyboard layout verified
- Approved settings backed up with a revision number
- Production acceptance test prepared
Frequently asked questions
Should every barcode symbology be enabled?
Usually not. Enable the formats required by the workflow and test them with real samples. A controlled set reduces unintended reads and simplifies support.
What is the difference between a Code ID and a prefix?
A Code ID identifies the decoded symbology and may follow a vendor or AIM convention. A custom prefix is an arbitrary string configured for the application. Both appear before the barcode data, but they serve different purposes.
Why does a UPC code gain a leading zero?
The scanner may be converting UPC-A to its compatible EAN-13 representation. Disable the conversion or normalize the database if the extra zero is not expected.
Can scanners parse GS1 application identifiers?
Many 2D scanners can read GS1 symbols, but output and parsing capabilities vary. Confirm separator handling and whether parsing occurs in the scanner, SDK or host application.
How should configuration be copied to many scanners?
Use the manufacturer's approved programming barcodes, configuration utility or device-management method. Keep a version-controlled master configuration and verify each unit with a known test card.
Choose a scanner that supports the complete data workflow
Read performance is only the first step. A reliable deployment also requires the right symbology controls, output formatting, host interface and configuration method. Review our industrial and commercial barcode scanners, compare handheld scanner options, or contact WODEMAX with your barcode samples, expected output, host system and project quantity.