Square Champion

Bug in search functionality with specific barcodes for stock transfer when using scanner

  • Issue 1: Barcode Scanning Inconsistency:
    • Certain barcodes (specifically Alcott Collar products) are not recognized by the search function during stock transfers.
    • Workaround:
      • Removing the last digit of the barcode allows the system to recognize the product.
      • Re-entering the full barcode also sometimes allows recognition.
  • Issue 2: Clunky Stock Transfer Process:
    • The current stock transfer process requires manual entry of product information after scanning, which is inefficient and prone to errors. 
    • A true stock transfer function should allow for seamless "add to transfer" directly from a scanned barcode. Increasing Qty with each scan

Impact:

  • Issue 1:
    • Delays stock transfer operations.
    • Increases the risk of human error in product identification.
  • Issue 2:
    • Reduces efficiency and productivity during stock transfers.
    • Increases the potential for data entry errors.
    • Makes the stock transfer process more time-consuming.

Steps to Reproduce:

  1. Initiate a stock transfer in the Square app or dashboard.
  2. Scan a barcode from a Alcott as demonstrated in video
  3. Observe that the product is not recognized in the search results.
  4. Try removing the last digit of the barcode and rescanning. Observe that the product is now recognized.

Expected Behavior:

  • All barcodes should be accurately scanned and recognized by the search function during stock transfers.
  • A seamless "add to transfer" feature should be available directly from a scanned barcode, eliminating the need for manual entry.

Request:

  • Please investigate and resolve the barcode scanning inconsistency for Alcott (some) products.
  • Implement a more streamlined stock transfer process that supports direct "add to transfer" from scanned barcodes.

 

Thank you!

@Summer2024 for vis

461 Views
Message 1 of 2
Report
1 REPLY 1
Alumni

Hi @JTPets,

 

Thanks for flagging this, and apologies for the delay in getting back to you. 

 

I've gone ahead and reached out to our product team to ask that they look into this for you. I appreciate you sharing the video on this occasion, it should certainly help in trying to determine the cause of this behaviour.

 

I've also highlighted the areas for improvement that you've noted, and asked the team to let me know if there are any planned updates that might address these concerns. 

 

I'll reach out here, as soon as I have a response. 

354 Views
Message 2 of 2
Report