- Spoke article

OCR and barcode verification on the line. Grades, retailer requirements, and the WMS handshake.

ISO 15416 (1D) and ISO 15415 (2D) verification grades explained, the GS1 retailer requirements Coles and Woolworths actually enforce, fixed-versus-handheld decisions, and the WMS integration patterns that consistently work.

01 / read-vs-verify

Read versus verify — the difference that matters.

Have you ever had a load rejected at a customer DC for unreadable barcodes that scanned fine on your own line?

Key takeaways

Reading is pass/fail. Verifying grades print quality. A code that reads on your line at A grade may read at D grade after a humid week in the warehouse. A code that already reads at D ships at the edge of unreadability, and downstream scanners will not be as patient as yours.
Coles and Woolworths require GS1 verification reports. Not by law, by supplier agreement. For new products or new packaging the verification report is typically required before the line ships. Failed codes mean refused loads.
Fixed and handheld verifiers do different jobs. Fixed sits on the line and grades every code. Handheld is the benchtop tool for sample testing, complaint investigation, and initial GS1 reports. Plants whose customers run incoming-goods scanners on every case need the fixed verifier; plants doing occasional reports get away with handheld.

The difference between a reader and a verifier is the difference between "this code can be decoded right now" and "this code will be decoded everywhere for the rest of its useful life." A reader gives a pass/fail. A verifier gives a graded score, A through F, against the ISO standard. Codes that read at the supplier's plant but verify at D or below routinely fail at retailer distribution centres where lighting, angle, or scanner gain differs.

The cost of the difference is concrete. A refused load at the DC means the truck turns around, the goods sit in cold storage, and the supplier explains in writing why it happened. The verification report is the document that prevents the explanation.

02 / standards

ISO 15416 and ISO 15415 explained.

Two standards govern verification. They are similar in spirit and different in detail.

ISO/IEC 15416 — 1D barcodes.

The print-quality test specification for linear (1D) barcode symbols: UPC, EAN-13, Code 128, ITF-14, and others. The standard takes 10 individual scan lines across the height of the code and grades each against six parameters: minimum reflectance, edge contrast, modulation, defects, decode, and decodability. The first three parameters are pass-or-fail; if a scan line fails any of them, the entire scan line is graded F. The remaining parameters are graded A through F. The ten scan-line grades are averaged to produce the formal grade.

ISO/IEC 15415 — 2D matrix codes.

The print-quality test specification for 2D matrix codes: Data Matrix, QR Code, Aztec, and similar. The methodology adapts to 2D geometry but follows the same A-to-F grading philosophy, evaluating contrast, modulation, decode, axial non-uniformity, grid non-uniformity, fixed-pattern damage, and unused error correction. 2D codes are more tolerant of damage than 1D codes because they include error-correction, but verification still flags codes that have used too much of the available correction overhead.

The GS1 grading scale.

GS1 (the standards body for retail barcodes) uses a scale where A, B, C, and D are all passes and F is the only failure. The minimum acceptable grade for most retail applications is C; some retailers require B or better for specific high-volume SKUs. Plants targeting Coles and Woolworths supply should plan for B-grade minimum on the master code and design the print process to deliver A-grade typical.

03 / retailers

What Coles and Woolworths actually require.

The Australian major-retailer barcode-compliance picture is concrete enough to plan around.

GS1 membership.

Both Coles and Woolworths require suppliers to be GS1 Australia members. The membership gives the supplier authorised barcode prefixes and access to GS1's verification service. Woolworths' vendor agreement explicitly requires new vendors to supply a letter from GS1 confirming current membership before goods can be received.

Verification reports.

For new product lines and new packaging variants, both retailers may require a GS1 Verification Report demonstrating that the barcodes on the product meet the passing grade threshold. The verification report typically grades the consumer-unit barcode (the UPC/EAN-13 on the retail pack) and the master code (the ITF-14 or GS1-128 on the case or pallet). A passing report covers both, with the grade visible.

The escalation path.

Loads with codes that fail at the retailer DC are typically refused or held. Repeat failures lead to vendor-compliance escalation: written warnings, chargebacks for the rejected loads, and in serious cases removal from the vendor list. The economic case for in-line verification is rarely the cost of one rejected load; it is the cumulative reputation cost of being the supplier whose codes the DC team has to chase.

The export overlay.

Australian manufacturers exporting to GS1-aligned retailers in other markets (Walmart and Target in the US, Tesco and Sainsbury's in the UK, Costco globally) face the same verification requirements with slightly stricter grade thresholds in some cases. The print process that satisfies Coles and Woolworths usually satisfies the export side, but plants entering a new export market should verify the specific retailer's grade threshold during commercial onboarding rather than after the first shipment.

04 / fixed-vs-handheld

Fixed in-line verifier or handheld.

Two product categories serve different parts of the verification workflow.

Fixed in-line verifier.

Mounted on the production line, the fixed verifier grades every code in real time as the product passes. The grade is published to the PLC; codes below the configured threshold trigger a reject. The cost is higher upfront and the integration is a real engineering project. The benefit is 100% verification at line speed, which is the only model that catches drift before it ships a load. Plants whose retailers run incoming-goods scanners on every case (the major DCs do) need in-line verification to keep ahead of the problem.

Handheld verifier.

A benchtop or hand-held device that grades a sample code on demand. Used for sample testing during a production run, initial GS1 verification reports for new SKUs, complaint investigation, and audit-evidence collection. Lower upfront cost. Lower coverage: a handheld checking ten codes a shift will not catch the drift that affects the other 19,990 codes from the same shift.

The right answer.

Plants with a single-SKU run-rate that justifies the in-line cost should default to fixed verification. Plants with high-changeover, multi-SKU lines where the fixed verifier would need re-aiming on every changeover often start with handheld and add fixed verification only on the lines where complaint volume justifies it. Many plants run both: fixed verification on the highest-volume lines, handheld for sample testing on the rest.

05 / wms

WMS integration — the handshake that fails quietly.

A verifier that grades a code without publishing the grade to the WMS is a verifier delivering a fraction of its value.

The integration that works:

Decoded data published to the PLC and the WMS. The code itself (the GS1 string, the UPC, the ITF-14) goes into the WMS pallet record. Pallet identity is now linked to the actual code printed on it.
Grade published alongside the decoded data. Not as a pass/fail summary. The actual A/B/C/D grade per parameter, recorded against the same pallet record.
Timestamp, operator, and image. The pallet record carries the time of code generation, the operator on shift, and (in good implementations) the verifier's captured image of the code for forensic review.
PLC reject on threshold. The PLC reads the grade and rejects the pallet if it drops below the threshold (typically C or B). The grade is enforced at the line, not just logged in the database.

The failure mode that turns up: a verifier configured to publish only the decoded data, with the grade dropped silently. Codes that scanned correctly but verified at D enter the warehouse looking identical to A-grade codes. The first sign of trouble is a customer complaint two weeks later. The fix is in the configuration, not the equipment.

06 / ocr-ocv

OCR and OCV for date codes.

Verification is mostly a barcode conversation. The adjacent inspection (date code and batch code legibility) is OCR/OCV territory, and the two are usually solved on the same camera platform.

OCR versus OCV.

OCR (Optical Character Recognition) reads characters from an image without a known expected string. OCV (Optical Character Verification) checks a printed string against an expected pattern provided in advance. On a production line, OCV is almost always the right tool: the date code format is known, the batch code template is known, and the inspection is whether what got printed matches what should have been printed. OCR is reserved for cases where the expected string varies in a way the system cannot predict.

Standards for date codes.

There is no equivalent of ISO 15416 for printed date codes. The closest is GS1 Application Identifier 17 (use-by date) when the date is encoded in a GS1-128 barcode; in that case the barcode grading applies. Plain-text date codes are inspected for legibility and for matching the expected format; the standard is "operationally readable" rather than a graded numeric score.

The integration with the line.

The same vision platform (Cognex DataMan, Keyence IV3, or a general-purpose CV-X) typically handles both the barcode read/verify and the OCV on the date code. One camera position, one inspection trigger, two inspections published to the PLC. The integration handshake is the same as for any other vision-to-PLC inspection (see the machine vision spoke). The decision rule for separate cameras versus one combined inspection depends mainly on whether the barcode and the date code share a viewing angle that supports both.

07 / faq

Common questions.

What is the difference between read/no-read and verification?

A reader confirms the code can be decoded — pass or fail. A verifier grades the code's print quality against an ISO standard (ISO 15416 for 1D, ISO 15415 for 2D), producing an A-to-F grade. A code that scans today might verify at grade D, meaning it is at the edge of unreadability and will likely fail at a downstream scanner with marginal lighting or angle. Verification catches the marginal codes before they reach the customer; readers catch only the fully broken ones.

When is verification mandatory in Australia?

It is not strictly mandatory under Australian law, but the major retailers make it a commercial requirement. Coles and Woolworths require suppliers to be GS1 members and, in many cases, to supply a GS1 Verification Report demonstrating that barcodes meet a passing grade (A through D on the GS1 scale, F is the only failure). For new product lines or new packaging variants, the verification report is typically required before the line ships. The legal lever is contract law via the supplier agreement, not regulation.

Fixed verifier or handheld verifier?

Different jobs. A fixed in-line verifier sits on the production line and grades every code in real time, allowing the PLC to reject any code that drops below a target grade (typically C or better). A handheld verifier is a benchtop tool used for sample testing during run setup, customer-complaint investigation, or initial GS1 verification reports. Plants that need both bought both. Plants whose retailers ask for occasional reports usually start with a handheld; plants whose customers run incoming-goods scanners on every case usually need a fixed in-line solution.

How does barcode verification integrate with WMS?

The verifier publishes the decoded data and the grade to a discrete output and to the WMS via either Ethernet/IP, OPC UA, or a database write. The PLC handles the reject if the grade falls below the threshold. The WMS records the code, the grade, the timestamp, the operator, and (in good implementations) an image of the code for later forensic review. The integration that consistently fails is the one that publishes the decoded data without the grade. A code that scanned correctly but verified at D is information the WMS should retain, not discard.

- sources

Sources and further reading.

Standards body and retailer references for the verification claims above. Retrieved 18 May 2026.

ISO. ISO/IEC 15416:2016 — Automatic identification and data capture techniques — Bar code print quality test specification — Linear symbols. iso.org
GS1 Australia. Retailer requirements for packaging and barcodes. gs1au.org
GS1 Australia. High Quality GS1 Barcodes & Solutions. gs1au.org
Woolworths Group. Packaging and Barcodes — Partner Hub. partnerhub.woolworthsgroup.com.au
Cognex. Understanding the 1D Barcode Grading Process: ISO 15416 Explained. cognex.com

This article sits under Pac Technologies' industrial vision service. For the platform comparison underneath most verification projects, see the Cognex vs Keyence spoke. For the food-line application of vision generally, see the machine vision for food packaging article.