Define whether the project needs a simple read, online inspection or formal verification, then connect the result to the correct line response.

A successful read confirms that one device decoded the symbol under its conditions. Online vision can check every pack for presence, content and position. Formal verification measures print-quality parameters against the applicable standard and reports a grade. The user requirement should state which level is needed rather than using the word “verification” for all three.
| Method | Typical purpose | Important limitation |
|---|---|---|
| Handheld or fixed scanner | Confirm that the encoded data can be decoded. | Does not by itself provide a standards-based print-quality grade. |
| Online vision or code reader | Inspect every pack for missing, wrong, unreadable or misplaced codes. | Performance depends on camera, lighting, trigger, software and validated challenge samples. |
| ISO/IEC-compliant verifier | Measure defined linear or 2D symbol-quality parameters and issue a report. | Normally samples production rather than controlling every pack online. |
GS1 states that GS1 DataMatrix print quality should be checked with an ISO/IEC-compliant verifier. Its guidance also distinguishes standards-based verification from ordinary scanning. See the official GS1 DataMatrix verification guidance.
Incorrect size, missing quiet zones, stretched cells, print growth, poor edge definition or coding across a seam, curve or corner.
Low contrast between mark and background, reflective packaging, coloured substrates, uneven lighting or transparent film over variable artwork.
Changing throw distance, product movement, printhead contamination, ink condition, condensation, dust, wrinkles or speed-dependent distortion.
Use the smallest production symbol, maximum line speed, greatest permitted print gap and the most difficult approved pack colour or surface. Include downstream rub, cold or condensation where those conditions occur in normal production.
The camera result is useful only when it is matched to the correct product and the line handles failures reliably. Define the distance from print to inspection, inspection to reject and reject to confirmation. Track product pitch through stops, gaps and speed changes.
Define good, no read, wrong data, missing code, poor position and camera fault as separate states where required.
Choose stop, reject, hold or alarm logic based on risk, product flow and the ability to confirm removal.
Record counts, rejected images, reason codes, operator actions and any batch-level reports needed by the quality system.
| Challenge sample | Expected inspection outcome | Expected line action |
|---|---|---|
| No print | Missing-code fault | Reject or stop according to the approved risk assessment. |
| Wrong but readable data | Content mismatch | Remove the product and prevent continuation with the wrong job. |
| Deliberately damaged symbol | No read or quality failure | Reject and retain the image or result where specified. |
| Reject bin full or reject not confirmed | Reject-system fault | Stop or hold production so failed packs cannot continue. |
| Camera disconnected | Inspection unavailable | Apply the defined fail-safe response rather than silently bypassing inspection. |
Provide the code standard, artwork, sample packs and required line response for an inspection review.
Discuss code verification