Skip to content

Advanced Inventory Count

Wrong Part Number Populating on Scanner & Count Sheet

Viewing 3 posts – 1 through 3 (of 3 total)
  • Author
    Posts
  • #8846
    Jeffrey S.

    Having a an issue with a scan behaviour where the scanner / count sheet are populating a different Item No than what the label is physically displaying.

    This situation is happening on different part no which have the same lot no_ in our system:  (in some cases we generate a lot number based on the warehouse receipt….so multiple part numbers can be assigned the same lot no_)

    Example:

    Part 123 – Lot AAA will be populated on our count sheet.

    We will scan Part 123 – Lot AAA but it will show up on the scanner as part 456 LOT AAA.   The count sheet will reflect this with a new line generated,   as no matching is happening to the original line / part number.

    I have verified that the label information is correct,   and we have set the find line templates to match Item No, Lot No, SN (If applicable)

    I have been unable to find an issue with a specific scanner or item, as it has happened multiple times.   This is causing some significant issues with the Variance & Inventory accuracy as we are recording items on our count sheet which we are not physically scanning.      It is very difficult to catch this on the count sheet line after the fact……

    Please help!

    Jeffrey

    #10647
    Terri V.
    Insight Works

    Hello Jeffrey,

    It’s possible if you are scanning the tracking information only that the system is selecting the first Item No. that matches that Lot No., when it’s processing the scan. The string information in the barcode should contain both the Item No. and the Lot No.

    We would need to diagnose the scanner behavior to view the barcodes in use on a call to designate the problem.

    Please submit a support request to su*****@*******ks.com for further assistance.

    Thank you,

    #10648
    Jeffrey S.

    Thanks Terri,

     

    Will submit a support request through our IT group shortly,

    A few updates to this:   The barcode information is correct in all cases….

    It seems to be a problem with the scanner cache,  although everything is set to prevent this…..

    Clearing the cache on the scanner fixes the issues both in test and live DB….

    Thanks! 🙂

Viewing 3 posts – 1 through 3 (of 3 total)
  • Sign in below to reply.