News

UV-Printed QR Code Acceptance: What to Check Beyond a Successful Scan

Check QR-code margins, print quality, variable data and actual reading conditions, and distinguish a successful scan from a quality grade or confirmation that the data is correct.

A successful phone scan of a UV-printed sample is useful, but acceptance is not complete. Consider a hypothetical case: an order requires the current batch number, yet the sample contains the previous batch. The code may be clear and readable while the data is still wrong for the order. Record what was decoded, the print quality and whether the information belongs to that item separately.

1. Define the purpose. Opening a consumer webpage, collecting a warehouse batch number and reading a line serial number involve different equipment and downstream processing. Record the symbology, data format, intended reader and expected result. A general web-address QR code and a code using GS1 business rules are not interchangeable. Apply the relevant GS1 data requirements when the project uses that system.

2. Check the complete code area. DENSO WAVE specifies a clear margin four modules wide on every side of a QR Code. A module is one small square in the symbol. Include this margin when measuring the available print area. Check for surrounding text, background patterns or cut edges that intrude into it. This value applies to QR Code and should not be transferred automatically to another symbology.

3. Separate visual checks from quality grading. Inspect contrast, spots, missing elements and interference from package seams or wrinkles. A phone or ordinary reader primarily provides a decode result, not a barcode quality grade. If a formal grade is required, use suitable barcode verification equipment. GS1 guidance notes that minimum quality requirements vary by application, so one grade should not be assumed to apply to every project.

4. Compare the data with the approved source. Place the source record, decoded print content and receiving-system result in one comparison row. Check the product identifier, batch, date or serial number actually used by the project. For serialised items, test duplicate handling and reprint rules; a shared batch number is not inherently an error. If the code opens a website, check the destination separately. Barcode verification does not establish that the landing page is correct.

5. Test the actual package state. Print on production material, complete the downstream packaging operations that apply, and inspect it in the intended reading conditions. Cover expected operating states such as normal speed and line restarts, recording which state produced each sample. Keep UV ink and curing settings with the sample record as well. The subject of acceptance is the resulting code, and a single stationary sample does not establish whole-line performance.

6. Agree on a traceable acceptance record. Suggested fields are sample ID, material batch, file version, expected data, decoded result, reader and conditions, verification-report reference, exceptions and their resolution. Establish sampling, acceptance criteria and retesting before the test. Mark untested items as pending. If inline inspection or rejection is required, confirm its configuration and test results separately; the ability to print QR codes does not establish that these functions are included.

For a Dengshilang QR-printing discussion, prepare real packaging, anonymised example data and the receiving party's acceptance requirements. Agree on samples, data and inspection methods, then use recorded results to discuss equipment configuration and process adjustments.

References: GS1, 2D Barcodes at Retail Point-of-Sale Implementation Guideline, sections 5.7.2 and 7.6; GS1 2D Barcode Playbook for Creation and Printing, release 1.0.1, June 2026; DENSO WAVE, Point for determining the code area. These project suggestions do not replace applicable standards or the agreed acceptance documents.