Define the data comparison
Record the symbology, agreed syntax and selected product, date, batch, lot or serial fields. Identify the authoritative expected values and which human-readable fields must agree with encoded data.
1D and 2D packaging codes
Cross-check barcode and Data Matrix data with the printed date and batch
Read machine-readable codes in line, validate encoded product, batch, lot and expiry data, compare human-readable text and reject wrong, missing or no-read packs.
Practical answer
Job and trial evidence
Why does a successful barcode or Data Matrix read not establish a pass?
A successful decode returns the data carried by the symbol. Content validation asks whether the selected fields agree with the approved product and production job. Formal print-quality grading is a separate requirement. Define these outcomes before choosing the reader or treating a scan as acceptance.
Include readable wrong-code samples
Challenge unexpected content as well as missing or no-read symbols. Retain separate read/no-read and content-match outcomes so an apparently readable code cannot hide the wrong production value.
Complete the production decision
Agree reject, quarantine or line-stop behaviour and the required tracking and records. State any formal symbol-quality grading requirement separately, with the applicable verification method and reporting scope.
For the next step, define the expected-value check and review packaging and code identity.
One source of truth
Barcode and Data Matrix inspection
Make the encoded data agree with the physical pack
Inline barcode and Data Matrix inspection decodes the symbol on each presented pack and compares selected fields with the active product recipe or production record. Where the code carries batch, lot, expiry, manufacturing date or serial data, those values can be checked individually rather than treating any successful scan as a pass.
The same vision station may also read the human-readable date or batch printed beside the symbol. This creates a cross-check between the product, machine-readable data and visible text, subject to field of view, resolution and line presentation.
Code presence and read
Confirm that the required 1D or 2D symbol is present and can be decoded at production speed.
Content validation
Check GTIN, batch, lot, expiry, production date or serial data against the active job.
Text-to-code match
Compare encoded fields with OCR-read human-readable information printed on the pack.
Wrong-code rejection
Stop or remove products carrying an unexpected, duplicate, missing or unreadable code.
Important terminology
Reading, validation and ISO grading are different tasks
Defining the required outcome prevents a simple successful decode from being mistaken for proof of correct data or formal symbol quality.
Barcode reading
Decode the information carried by a 1D or 2D symbol and return read or no-read.
Content validation
Compare decoded identifiers and attributes with the expected product and production data.
Print-quality grading
Assess symbol quality against an applicable standard using suitable verification hardware and conditions.
GS1-enabled checks
Validate the fields that matter to traceability
GS1 barcodes can carry identifiers and production attributes. The exact Application Identifiers and permitted values are agreed for each product family.
| Data field | Typical inspection | Production decision |
|---|---|---|
| Product identifier | Compare GTIN or agreed product code with the active recipe | Reject the wrong product or packaging |
| Expiry / best-before | Decode the date and compare it with the expected value or date rule | Reject wrong, malformed or out-of-window dates |
| Batch / lot | Match the encoded string with the current production record | Reject stale or incorrect traceability data |
| Serial number | Check syntax, range, database response or duplicate policy where required | Quarantine or reject an invalid item |
| Human-readable text | Use OCR to compare visible print with selected encoded fields | Reject any text-to-code mismatch |
Application engineering
Specify the code, syntax and pass rule before choosing the reader
We establish the symbology, code size, quiet zone, print method, packaging surface, viewing angle, speed and range of expected content. The system is then trialled on representative print quality and deliberate wrong-code samples.
If formal barcode quality grading is required, this must be stated explicitly. Inline reading and data validation do not automatically equal ISO/IEC verification; the project scope should identify the applicable standard, verifier performance and reporting requirement.
- Symbology and code dimensions
- GS1 Application Identifiers
- Expected product and batch data
- Human-readable fields to compare
- Read, validation or formal grading scope
- Reject, quarantine and result records
GS1 UK explains that 2D codes can carry information including expiry dates, serial numbers, batch and lot numbers. See the official GS1 UK 2D barcode guidance.
Related inspection systems
Continue from code reading to production control
Use the related pages to define the recognition method, source of expected data and physical line response.
Frequently asked questions
Barcode & Data Matrix inspection questions
Final performance is established with representative products, deliberate faults and the operating conditions found on your production line.
Can one camera inspect a Data Matrix code and printed expiry date?
Often, yes, when both fields fit within the field of view at sufficient resolution. Separate tools can decode the symbol, read the visible date and compare selected values.
Is barcode validation the same as barcode quality verification?
No. Validation checks whether decoded content is correct for the job. Formal verification grades symbol quality against an applicable standard using suitable verification equipment and controlled methods.
Can the system check GS1 batch and expiry Application Identifiers?
Yes, where the code uses the agreed GS1 syntax. The required identifiers, date interpretation, permitted values and error handling are documented before configuration.
What happens when the code reads but contains the wrong product?
A successful decode is not automatically a pass. The decoded identifier can be compared with the active recipe, and a mismatch can trigger reject, quarantine or line stop.
Oxford Vision Systems
Turn a successful scan into a verified production decision
Send sample codes, data syntax, expected fields, pack photographs and line speed. We will define the read, validation and rejection scope.
Continue planning