What context will DataWedge have as to whether a scan is "good" or "bad". DataWedge can provide feedback when it successfully decodes a barcode but isn't going to be aware of whether the data it has extracted from the barcode is good or bad. By the time your application determines that the barcode data is "bad" for whatever reason the scan decode beep feedback has already been emitted. You could explore turning off the scan beep in DataWedge and then have your application provide "good" and "bad" feedback beeps but that will likely introduce some sort of validation delay that may affect the end user confidence in the barcode decode process.