Force Rescan at Checkout when Item is not Cataloged

Bug #1990015 reported by Michele Morgan
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Wishlist
Unassigned

Bug Description

In an effort to reduce the number of misscanned barcodes that end up as precat items at checkout, it would be useful to require the user to rescan any barcode that is not in the database before being allowed to create a precataloged item.

Currently, when Strict Barcode is UNchecked and a barcode misscans, the user is immediately presented with a popup to add precataloged item information, and options: Precat Checkout or Cancel

When Strict Barcode is checked and a barcode misscans, the intermediate Bad Barcode popup is presented. Text suggests that they Cancel and try scanning again. Options: Accept Barcode or Cancel. If Accept Barcode is chosen, the user is then presented with the popup to add precataloged item information.

If the user was forced to rescan the item prior to entering the precat item information, the number of misscans that end up as precats would be reduced

Here's how the requirement to rescan the barcode could work:

Strict Barcode UNchecked:

A Rescan Barcode popup appears with a box to rescan the barcode or Cancel
Cancel returns the user to the checkout screen
Rescanning the barcode attempts the checkout with the rescanned barcode
If a valid item is found, the checkout proceeds, if not, the precat screen is presented.

Strict Barcode checked:

Bad Barcode popup appears as it does now, options to Accept or Cancel
Cancel returns the user to the checkout screen
Accept brings up the Rescan Barcode popup with a box to rescan the barcode or Cancel
Cancel returns the user to the checkout screen
Rescanning the barcode attempts the checkout with the rescanned barcode
If a valid item is found, the checkout proceeds, if not, the precat screen is presented.

Changed in evergreen:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Elaine Hardy (ehardy) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.