Barcode issues

Troubleshooting Barcode Scanning Issues at POS

Overview

Barcode scanning issues at POS can occur for a number of reasons. Common problems include:

  • Leading zeros missing (e.g., scanning 0123456789012 as 123456789012)

  • Extra characters being added before or after the barcode

  • Barcodes not recognised in POS but working in Acumatica

  • Different results on different POS PCs due to varying scanner configurations

  • Incorrect barcode types being scanned (EAN-13, UPC-A, Code128, etc.)

Most of these issues are not faults with Acumatica or POS itself, but with scanner settings or mismatched barcode formats from suppliers. This guide outlines a process of elimination to identify where the problem lies.

Step 1: Test the Scanner (Notepad)

  1. On the POS computer where the issue occurs, open Notepad.

  2. Scan the problematic barcode.

  3. Check the result:

    • If the output matches the barcode exactly → the scanner is working correctly.

    • If characters are missing (e.g., leading zero dropped), extra characters appear, or the barcode doesn’t scan at all → the issue is with the scanner configuration.

⚠️ Note: Scanners can have different settings per POS PC. One may work fine while another does not.

Step 2: Test in MYOB Acumatica

  1. In Acumatica, open any search or lookup field.

  2. Scan the same barcode.

  3. Check the result:

    • If the code scans correctly in Notepad but fails here → the issue may be with the field or formatting in Acumatica.

    • Provide details of the screen/field to support for further investigation.

Step 3: Test in 1Retail POS

  1. In POS, open the item search or sales screen.

  2. Scan the barcode.

  3. Check the result:

    • If it works in Notepad and Acumatica but fails in POS → this indicates a POS configuration issue.

Additional Considerations

  • Supplier barcodes: Some suppliers issue barcodes in unusual formats. Confirm if the barcode itself is valid and consistent with your system requirements.

  • Spot-checking: If only one POS PC has issues, start with that unit. If multiple PCs show the same issue, settings may need to be standardised across all scanners.

  • Barcode types: Different formats (EAN-13, UPC-A, Code128, etc.) may behave differently depending on scanner setup. Reference guide:
    Barcode Types – Seagull Scientific

Scanner Brand and Model

To provide accurate troubleshooting and configuration steps, support will need the brand and model of your scanner.

  • Check the device label or look under Device Manager → Human Interface Devices in Windows.

  • Common configuration settings to review include:

    • UPC-A leading zero suppression

    • EAN-13 to UPC-A conversion

    • Prefix/suffix characters

Summary

  • Start with Notepad to confirm scanner behaviour.

  • Test in Acumatica to check ERP recognition.

  • Test in POS to confirm configuration.

  • Gather scanner brand/model details for targeted fixes.

  • Barcode issues are typically resolved by adjusting scanner settings or aligning with the correct barcode format.