Presence and readability
Confirm that a supported code is present and decodes inside the production window.
1D and 2D code inspection
In-line barcode and Data Matrix verification
Read every presented code, compare its data with the active production job and trigger a controlled response to no-read or wrong-code results.
✓ 1D and 2D codes✓ Job-data matching✓ Reject integration
What can an in-line barcode verification system check?
An in-line code system captures the symbol on every presented pack or label. It can decode the value, confirm the expected symbology, compare product, batch or serial data with the active job and separate “no read” from “readable but wrong”.
Barcode reading, production-data validation and formal print-quality grading are related but different. A scanner that decodes a symbol does not automatically prove ISO/IEC grading conformity; formal grading must be specified and carried out with a suitable compliant verifier.
Expected data
Compare GTIN, product, batch, serial or other fields with the active job.
Quality requirement
Separate routine reading from formal verification and grading requirements.
Controlled outcome
Reject, stop, alarm or record each defined no-read or mismatch state.
GS1 UK explains that printed barcode quality is assessed with a suitable verifier. See GS1 UK’s barcode-quality guidance. Oxford Vision Systems will distinguish production reading from formal verification in the project specification.
Prove the reading window
Code size, contrast and presentation set the margin
Trials must reflect the final code after it is printed and applied to the real product.
- Common linear 1D barcode applications
- QR code and Data Matrix applications
- Codes on labels, cartons, sleeves and containers
- Curved, glossy, reflective or low-contrast surfaces
- Fixed-position and variable-orientation presentation
- Human-readable text checked alongside the symbol
Production decisions
Turn a decoded symbol into a useful line result
The inspection must define what happens when the code is absent, unreadable, readable but wrong, duplicated or outside the expected format.
| Result | Meaning | Typical controlled response |
|---|---|---|
| No read | Missing, damaged, obscured or outside proven imaging conditions | Reject, alarm or line stop |
| Wrong read | Decodes successfully but does not match the active job | Contained reject plus mismatch record |
| Correct read | Expected value confirmed inside the defined decision time | Pass and optional production record |
| Quality failure | Agreed grade or quality rule is not met | Response defined separately from decode success |
Practical answers
Barcode and Data Matrix questions
What is the difference between barcode reading and verification?
Reading decodes the symbol. Production validation may also compare that value with the active job. Formal print-quality verification uses a specified method and suitable compliant verifier and must be stated separately.
Can one system inspect 1D and 2D codes?
Yes, when the selected reader supports the symbols and sample trials confirm adequate module size, contrast, orientation tolerance and exposure time.
Can the code result reject the pack automatically?
Yes. A no-read, wrong-code or defined quality failure can drive a tracked reject, line stop or alarm, with optional confirmation that the failed pack entered the reject route.
Can a code be compared with a PLC recipe or database?
Yes, where the expected data source, interface, response time and behaviour during communications loss are defined during specification.
Application review
Request a project reviewSend code samples, expected data and line conditions
We will review symbol size, print contrast, pack presentation, speed and how the result should interact with the active production recipe.