Barcode, QR and OCR Verification
Read and match codes, serial numbers and expiry dates at line speed.
Reading a code is easy; reading it on a glossy metal surface, at an oblique angle and at a thousand items a minute is engineering.
The system reads barcodes, QR and dot-peen codes, decodes printed characters with OCR and compares the value against order, batch or recipe data. A product that does not match does not move on. Polarised lighting and multiple views are used on glossy surfaces, and unreadable codes are logged too — because the no-read rate is the earliest indicator of print quality.
How it works
Triggered acquisition
The code area is imaged with a short exposure the moment a sensor detects the product.
Barcode, QR and OCR
The code family is detected automatically; character fields are read and verified with OCR.
Compare with the expected value
If the read value does not match order or batch data, the product is rejected and the event logged.
The no-read rate is an early warning about print quality
The most valuable data a code-reading system produces is not the successful reads but the failed attempts. A rising no-read rate usually says a print head needs cleaning or a ribbon needs changing weeks before the code becomes unreadable.
| 1D barcode | 99.9% |
| QR code | 99.7% |
| Dot-peen code | 98.6% |
| OCR · date field | 99.2% |
| OCR · metal surface | 97.4% |
OCR success on metal depends directly on the lighting angle; a polarising filter and dual views raise the rate noticeably.
| d1 | 0.1 |
| d2 | 0.1 |
| d3 | 0.2 |
| d4 | 0.3 |
| d5 | 0.5 |
| d6 | 0.7 |
| d7 | 0.8 |
| d8 | 0.9 |
A maintenance request is raised before the threshold is crossed; the print head is cleaned during planned downtime and the line keeps running.
Use cases
Date verification
Reading and matching production and expiry dates.
Product separation
Separating different products on the line by barcode.
Codes on glossy surfaces
Reading dot-peen codes with polarised lighting.
High-speed reading
Code reading in flows up to 1,000 items per minute.
Technical requirements
| Camera | High-resolution triggered camera; optics chosen per code area |
| Lighting | Polarised or angled lighting; glare suppressed |
| Code families | 1D barcode, QR, DataMatrix, dot-peen code and printed characters |
| Verification | Comparison with order, batch or recipe data; non-matching product rejected |
| Integration | REST API, MES/ERP, PLC digital output, event archive |
Frequently asked questions
How does Barcode, QR and OCR Verification work?
Reading a code is easy; reading it on a glossy metal surface, at an oblique angle and at a thousand items a minute is engineering.
Are our existing cameras suitable for this solution?
Required camera specification: High-resolution triggered camera; optics chosen per code area. Before installation we assess your camera inventory free of charge and report which points are suitable and, if needed, which camera should be added.
What results and indicators does it provide?
Key indicators: First-read success rate: 99.8%; Reading speed: 1,000 items/min; Supported code families: 4. OCR success on metal depends directly on the lighting angle; a polarising filter and dual views raise the rate noticeably. Thresholds are calibrated on your own site during the pilot.
Which systems does it integrate with?
REST API, MES/ERP, PLC digital output, event archive. Events are published over REST API and MQTT, so it connects to your existing MES, ERP, VMS and alarm infrastructure.
Is it compliant with KVKK, Türkiye's data-protection law?
Footage is processed on an edge server inside your facility; raw video is not sent to the cloud. Facial recognition is not used; analytics outputs are anonymous and event clips are deleted automatically when the defined retention period ends.