Industrial machine vision integration across the UK
Camera and red lighting above wrapped packs on a conveyor.
Batch-code inspection

Keep every product linked to the correct production batch

Inspect variable batch codes in real time, compare the captured string with the current job and reject products that cannot be positively verified.

Practical answer
Job and trial evidence

How should batch-code inspection be tested through a job changeover?

Start with the authorised batch value and the rule linking it to the active product or order. Test a readable wrong batch separately from missing or unreadable print. Include the final old-job pack, first new-job pack, pauses and printer restart, with a defined batch decision for packs already between printing, inspection and rejection.

Record the batch authority

Identify the approved production value and whether a recipe, scanner, PLC or database provides it. Define job-selection validation and the response when the expected data is unavailable or stale.

Bound legitimate code variation

Provide every legitimate format, string length, delimiter and printer/font variation. Agree the actual OCR or OCV task and challenge acceptable, marginal and failed print with representative samples.

Retain the pack outcome

Test the decision with product tracking and removal, including closely spaced failures. Keep observed and expected values, job reference and reject result where the agreed records scope requires them.

For the next step, review known-string verification and prepare the complete inspection brief.

Protect end-to-end traceability
Purpose-built vision inspection

Verify the content, not just the presence of print

A simple contrast sensor can indicate that ink exists, but it cannot prove the printed batch is correct. Oxford Vision Systems applies OCR, OCV or pattern-based tools to read the defined field and compare it with authorised production data.

Batch-string reading

Capture letters, numbers and permitted symbols within a defined printed region.

Job-data comparison

Verify the result against a PLC, HMI recipe, database or scanned production order.

Character-level failure

Identify missing, substituted, merged or malformed characters that change the batch identity.

Traceable results

Create configurable records linking inspection status with time, product and batch.

System outcomes

Close the gap between production data and printed product

Automatic verification reduces the risk that a stale printer message or incorrect manual entry carries the wrong batch code into a new run.

01

Prevent message errors

Compare the physical print with the batch value authorised for the active order.

02

Improve recall precision

Protect the accuracy of batch information used for downstream traceability and investigation.

03

Simplify start-up checks

Use the same programmed validation logic from the first product to the last.

Camera and illuminated ring light above jars and cartons on a conveyor.
Physical code vs job data100% IN-LINE
Application engineering

Select the right verification method for the code

OCR is suited to reading an unknown string; OCV is often faster and more robust when the expected batch is known. We assess font consistency, print contrast, string length and changeover method before selecting the inspection tools.

  • Fixed and variable-length batch strings
  • Alphanumeric characters and delimiters
  • Product-to-batch recipe matching
  • PLC, scanner or database integration
Discuss your production line
Frequently asked questions

Batch-code inspection questions

Every inspection begins with real samples, representative print and the operating conditions found on your production line.

Can the batch code be compared with a barcode scan?

Yes. A production-order barcode or product code can be used to select or provide the authorised batch value, with suitable validation to prevent an incomplete or incorrect job selection.

What happens if the font changes?

Some OCR tools tolerate controlled font variation, while OCV generally relies on a known appearance. A font or printer change should be trialled and may require an updated inspection recipe.

Can the system read multiple batch-code lines?

Yes, provided the field of view and image resolution are sufficient. Separate regions can inspect batch, date, time and line identifiers within one captured image.

Oxford Vision Systems

Connect the printed batch to the active production order

Share examples of every legitimate code format and the data source that defines the correct batch. We will map the verification sequence.