Prove the right value
Verify expiry, best-before, use-by, batch and lot information against a recipe, calculated shelf-life date, PLC or production database.
Explore expiry-date verification →
Date code inspection & verification systems UK
Date code inspection. For production lines.
Date code inspection uses OCR to read printed dates and batch data, and OCV to verify expected characters against the active job. Define expiry-date content, readability and missing-print checks together with the trigger, product tracking and reject response for your bottle or packaging line.
Built for production certainty
01100% in-line inspection
02Recipe-controlled checks
03Automatic failed-code reject
04Audit-ready result records
Inline code verification
Date code inspection and verification systems for UK production lines
A date code inspection system captures the printed code on every presented product, checks whether it is present and readable, verifies its content against the active job, then signals pass, reject or line stop.
Prove the print is usable
Find missing print, incomplete characters, weak contrast, smudging, doubled print and codes outside the permitted area.
Explore print-quality inspection →Control every failure
Track the failed pack to a reject point, confirm removal and retain counters or failure images where the production risk requires evidence.
Explore reject integration →
Prevent coding errors at source
Inspect what matters—not simply whether ink is present
A code can be visible and still be wrong. Oxford Vision Systems configures inspection around the exact risk on your line: missing characters, an incorrect date, weak contrast, the wrong batch, displaced print or a code that cannot be reliably read.
- Correct date and format
- Code presence and position
- Character legibility
- Batch or lot agreement
- Print contrast and integrity
- Product-to-code matching
Date and variable-code inspection
One specialist system for every critical code check
Configure a targeted inspection or combine multiple checks in one vision station. Each solution is engineered around your substrate, printer, presentation and production speed.
01
Best-before-date inspection
Confirm the date is present, readable and correct for the active product recipe.
Explore best-before inspection 02Use-by-date inspection
Control safety-critical expiry information and reject packs with missing or invalid dates.
Explore use-by inspection 03Batch-code inspection
Read and compare variable batch strings to protect traceability through every run.
Explore batch-code inspection 04Lot-code verification
Check lot identity against the job, PLC or database before product leaves the line.
Explore lot-code verification 05Inkjet-code inspection
Detect blocked nozzles, smudging, low contrast, missing characters and displaced print.
Inspect inkjet codes 06Laser-code inspection
Verify permanent marks across glass, plastic, board and foil under controlled illumination.
Inspect laser codes 07Thermal-transfer inspection
Check variable print on flexible film, labels and pouches before the pack moves downstream.
Inspect thermal-transfer print 08OCR inspection
Read unknown character strings and compare captured results with the expected data.
Understand OCR inspection 09OCV verification
Verify printed characters against a known value or taught reference for fast, robust control.
Understand OCV verification 10Date-code rejection systems
Remove every non-conforming product with confirmed reject and locked-bin options.
Explore reject integration
Inspection sequence
From trigger to reject in milliseconds
A reliable result depends on more than the camera. Product handling, lighting, timing, inspection logic and reject confirmation are engineered as one coordinated system.
Present
Guide and space each product so the printed area enters the inspection window consistently.
Capture
Trigger the camera and controlled light to freeze the code at production speed.
Verify
Read or compare the code against the recipe, date logic or external production data.
Act
Pass conforming packs, reject failures and record the result for traceability.
OCRRead variable strings where the printed content can change.
OCVCompare each character with a known, expected value.
PLCExchange recipes, pass/fail states and counters with line controls.
DATAStore images, results, timestamps and reject events where required.
Close the quality loop
Finding a coding fault is only half the job
The inspection system tracks the failed product from camera to reject point, activates the correct device and—where the risk assessment requires it—confirms that the pack entered a secure reject container.
- Air blast, pusher, drop flap or conveyor-divert rejection
- Reject confirmation and full-bin monitoring
- Locked, tamper-resistant reject collection
- Line stop if the reject sequence is not confirmed
Applications
Inspection designed around the production risk
Variable-code requirements differ by sector, pack and process. We adapt the optics, software and reject strategy to the consequence of a coding error.
High-speed production
Food & beverage
Best-before and use-by control across packs, trays, pouches, jars, bottles and sleeves.
Traceability-ledPharmaceutical
Batch, lot and expiry verification with controlled records and secure failed-pack handling.
Brand protectionCosmetics & personal care
Inspect discreet codes on cartons, labels, tubes, jars and premium finished surfaces.
Industrial traceabilityChemical & manufacturing
Match lot, batch and date information with the correct product, label or production order.
Wider code-control requirements
Close the gaps around the printed date
A practical inspection may need to verify the manufacturing date, packaging identity, encoded 2D data or camera architecture as well as the visible expiry or batch string.
01
Manufacturing-date inspection
Verify MFG, production and packed-on dates, including Julian codes and shelf-life relationships.
Inspect production dates 02AI OCR date-code inspection
Evaluate AI-assisted recognition for variable fonts, curved packs and difficult low-contrast print.
Compare AI OCR methods 03Barcode & Data Matrix inspection
Validate encoded product, date, batch, lot and serial data and cross-check visible text.
Inspect 1D and 2D codes 04Label & date verification
Confirm that the correct packaging and variable code are on the right product.
Control packaging identity 05Date-code cameras & readers
Specify smart-camera, reader or multi-camera systems around your code, speed and reject risk.
Choose a camera systemPlanning resources
Specify the inspection around the risk on your line
Use these practical guides to define what the code must prove, how products will be presented and what should happen when a check fails.
Frequently asked questions
Planning a date-code inspection system
Early trials with real products and print samples help establish the correct optics, lighting and pass/fail tolerance.
Can one camera inspect a date, batch code and barcode?
Often, yes. If all markings are visible within a suitable field of view, one image can support OCR or OCV checks alongside 1D or 2D code reading. Multiple cameras may be preferable when codes sit on different faces or pack orientation varies.
Does date-code inspection work with inkjet, laser and thermal-transfer printers?
Yes. The camera, lens, lighting and image-processing tools are selected for the substrate and print method. Reflective foil, curved bottles, transparent film and low-contrast laser marks require different optical arrangements.
Can the system confirm that the date is logically correct?
Yes. A read date can be compared with a fixed recipe value, a date calculated from the production date and shelf-life rules, a PLC value or information supplied from another database or line system.
What happens when a printed code fails inspection?
The system can stop the line or track the product to an automatic reject device. Reject confirmation, full-bin detection and secure reject access can be included according to the line risk assessment.
Can an inspection system be retrofitted to an existing conveyor?
In many cases, yes. We assess available space, product presentation, line speed, controls, guarding and reject requirements. A standalone frame or conveyor module can be supplied where the existing line does not offer a stable inspection area.
What is the difference between date code inspection and date code verification?
Inspection is the overall process of capturing and assessing the printed code. Verification is the decision step that compares the observed date, batch or lot value with the expected value, permitted format or taught reference.
Can expiry dates and batch numbers be checked in the same image?
Yes, when both fields are visible at suitable resolution. The system can apply separate rules to the expiry date, batch string and print quality before returning one pass or fail result.
Which date code faults can be rejected automatically?
Typical failures include no print, incomplete characters, weak contrast, an incorrect date, the wrong batch or lot, displaced print, an invalid format and a code that cannot be read reliably.
When is AI vision considered instead of OCR or OCV?
OCR or OCV is often the clearest choice for controlled formats. AI-assisted vision may be evaluated when fonts, pack presentation or print appearance vary too widely for a stable rule-based inspection. Representative trials determine the appropriate method.
Start with your products
Send us your packs, print samples and line details
We will review the application and recommend a practical route to inspect the code, manage changeovers and remove failed products.
A readable date can still be the wrong date
Date-code inspection should answer three separate questions: was the code seen, was it interpreted reliably, and does the observed value match the authorised production job?
Define the expected value independently
Identify the approved source for the date, batch and format. A camera reading the same incorrect value sent to a printer is not an independent check of the production rule. Describe how the job is approved and how the expected data reaches inspection.
Choose reading and comparison separately
Use OCR when the task needs a captured character string and OCV when it needs comparison with an expected message. Confirm the actual tool behaviour in a representative trial rather than assuming the method name proves suitability.
Give no-read a defined outcome
Keep an unreadable image separate from a readable but incorrect value. A shifted pack, missing print and a wrong batch can all require rejection, but distinct result categories make production investigation more useful. Review the print-quality checks against real acceptable variation.
Test the transition between jobs
Include the final old-job pack, the first new-job pack, a pause and a restarted printer in the agreed challenge. Confirm which job applies to products already between printing, inspection and rejection so a changeover cannot create ambiguous packs.
Prove the pack reached the reject route
Test the decision together with product tracking and removal confirmation, including closely spaced failures. Retain the observed code, expected value, job reference and reject outcome where the agreed record scope requires them. The reject integration page explains the downstream part of the specification.