Set a maximum allowed price for items
The item price field allows for high values to be entered into it. Which means things like item barcodes or ISBN numbers can set the price of an item in the billions. This incorrect price can then appear in places like "you saved" receipts for patrons and on other reports that are then difficult to correct.
In addition to offering the ability to set the maximum price, I think this feature should be enabled by default with a price of $9,999 and then a record set should be created at upgrade time for staff to review for any titles that are over this amount.
Wes Osborn
shared this idea
-
Carl Ratz
commented
I agree. There should be a default price as well as a max price that can be used, and the ability to override the max price by permission.
-
Beth Lane
commented
This is a good idea. I've run across items with a barcode in the item price, which causes temporary "sticker shock" for customers if they lose an item, and problems when running valuation reports for site insurance.
-
Amy Mihelich
commented
We just did a check for high-priced items and found many where the price for a hardback book was $3800 (the decimal hadn't been entered correctly) and one Minecraft manual that was over $9 million (ISBN had been scanned into the price field). A little pop-up reminder like the one that warns you if your record set is going to be over 10,000 items would be nice in cases like this, since there is a possibility if the patron gets a "Lost" notification it could look really terrifying.
-
Daniel Messer
commented
We had this very problem with one of our libraries in California. They needed a report based on You Saved data and it came back that a couple of patrons had saved millions of dollars because a couple of books were in the system with six digit prices. It threw off the You Saved amounts for multiple patrons.