Rate on it's own implies speed, so scanning rate would be how fast the scans are done - scanning success rate would be closer, but I personally don't like the expression "scanning probability" much either. Is it the chance that something got scanned, the chances of a detected error, the chances of an undetected error, etc.
Sorry in advance for a technical digression on a language usage site but, to my mind, incorrect and imprecise usage of technical language is inexcusable and in some contexts it can actually be criminal.
As I see it there are a number of possibilities that really should be covered when talking about a bar code reader:
- Good Bar Code is correctly accepted - this is one form of success - True Positive
- Bad Bar Code is correctly rejected - also success - True Negative
- Good Bar Code is rejected - failure - False Negative
- Bad Bar Code is incorrectly accepted - failure - False Positive
- Good Bar Code is accepted but with the wrong value returned - Incorrect Value
- None Bar Code is accepted as a valid bar code - Spurious Returns
These would normally be denoted in terms of the 100% achieved on a single scan.
All of the above will be measures of the reliability of the results of scanning and for a really meaningful picture of how useful the scanner is all 4 need to be enumerated, e.g. if a scanner is to be used to track drugs administered to patients you would rather have to scan more than once to get the correct results than have any erroneous input.
There can also be, for some coding schemes such as QR Code, a percentage of damage to the bar code that can be sustained and still give the True & Accurate results above. This is normally stated as a measure of the robustness and redundancy of the encoding scheme.