This is advice detailing what you can do when you run into an issue with your scanner.
This can be applicable to these scanners supported by Tower: Symbol / Metrologic / Motorola / Honeywell (1452g, 1472g, MS-7580g, MS-7120g), Element Bluetooth scanner, Zebra LI2208 or LS2208.
My scanner is scanning but it's not being scanned into the computer
Your scanner might be having a pairing issue with the computer. There are two things you can try:
- If it's a USB scanner, unplug the cable from the back of the computer and plug it into another USB port.
- If it's a handheld scanner, remove the battery from the scanner to fully restart it. Once the battery is placed back inside, place the scanner into cradle and wait for it to pair with the cradle again.
My scanner can't scan the product barcode
There can be two reasons why this is the case:
- If you're able to scan similar barcodes that have been previously printed out, there could be an issue with the alignment or interference of the label. You can try realigning the label settings based on what type of printer you use, such as Barcode Settings for A4 printer labels and Printer Settings -> Advanced Settings for Zebra label printers.
- If it's a new scanner or it has been factory reset, then you might need to scan some programming codes to allow to to read the current barcode symbology you're trying to scan. You can do this by searching online for the product manual of your specific scanner and use a barcode scanning app on your phone to determine what symbology you need to program
Retailer isn't finding the item when I scan the barcode but I can see it in the Point of Sale screen
- If you've just purchased a new scanner, you might need to scan the carriage return programming code for the scanner to then automatically press Enter after scanning a barcode. You can search online for your scanner's brand, model and add carriage return into the search to find relevant results. E.g Honeywell 7680g carriage return.
The scanner is 'disconnecting' or not activating when it hasn't been used for some time
Scanners can frequently have a power-saving mode or setting that will put the scanner to sleep or power down when it hasn't been used in a certain amount of time.
This can be changed by programming the scanner, and the steps to do this depend on the scanner model.
The manual for the scanner will have a barcode relating to power-saving or sleep or standby modes that needs to be scanned and possibly changed. Refer to the scanner manual for more information.
The scanner may also not appear to scan if the computer has gone to sleep or power-saving mode so make sure the computer hasn't done that.
Related Articles
Programming a Honeywell Barcode Scanner
Setting up a Honeywell scanner on a PC is very easy - you plug them in, wait for the battery to charge if handheld, and start using it - no install required. However, depending on the model, there may be some settings you need to change. Scanner ...
Common Stocktake Issues
Stocktake was closed and cannot reopen/find it When in the Stocktake screen (Stock Maintenance -> Stocktake -> Stocktake), click on Open Existing Stocktake at the top. Select the stocktake from the drop-down menu. If this stocktake was previously ...
Setting up the Honeywell Stocktake and Ordering PDE Scanner (EDA52)
Once your PDE scanner is delivered, you will need to follow the instructions below to set up the device and install the stocktaking program before it can be used for stocktaking or ordering. Device Setup 1. Remove the PDE device from its packaging. ...
Delay When Scanning Using a Honeywell PDE
As you use the stocktaking program on the Honeywell PDE, it may start slowing down and lagging after scanning barcodes. This is caused by a cache that builds up overtime that needs to be cleared. To solve this, the cache needs to be cleared. This ...
Common Epay issues
This advice sheet outlines some of the most common issues faced when using the Epay voucher system to sell or top up phone vouchers, digital wallets, and more, as well as the methods to resolve these issues. Error message appears saying ...