Choose a reader that supports the format
A built-in camera may recognise a QR code without recognising an EAN-13, Code 128 or Data Matrix symbol. This does not mean the other symbol is broken. Read the camera or scanning application's supported-format list before treating a failed attempt as a barcode failure. A dedicated barcode reader that displays the raw result is especially useful for internal identifiers.
On an iPhone, Apple's instructions describe scanning QR codes with the Camera app or Code Scanner. Frame the complete code and use the displayed action when appropriate. Other phones have their own camera and scanning features, and support can vary between models and software versions. Avoid assuming that every camera can decode every barcode simply because it can open a QR link.
For product barcodes, distinguish a decoder from a shopping app. A shopping app may search its own catalogue after reading the digits. No matching product in that catalogue is not the same as failure to decode. Look for a result screen that shows the number or text directly, so you can separate reading the symbol from looking up a product.
Keep an expected result beside the test
Before scanning, write down the exact value you intended to encode. For a retail number, keep leading zeros and the check digit. For an internal Code 128 label, preserve case, punctuation and spaces. For a QR link, include the full address and path. Comparing against memory is unreliable when several labels differ by only one character.
Generate a sample with the EAN-13 generator, UPC-A generator or Code 128 generator, depending on your actual workflow. If you entered a value without a check digit, compare the scanned result with the complete value displayed by the tool. The additional final digit is expected in that case.
Some readers report UPC-A as EAN-13 with a leading zero. Record that behaviour rather than silently changing the source record. If the number feeds another system, check which representation that system expects. Likewise, logistics readers may expose separator characters or format identifiers differently. A reader's presentation settings are part of the test context.
Run a simple on-screen test first
Use a second device to display the barcode if your reader cannot import an image from the same phone. Show the whole symbol with its surrounding clear space. Avoid reflections on the screen and keep brightness comfortable for the camera. Move the phone gradually until the camera focuses, rather than placing it so close that the code fills the frame and blurs.
Try a few distances and angles under normal light. For a long linear barcode, make sure both ends remain inside the image. For QR or Data Matrix, keep the full grid and clear border visible. A partially cropped pattern is not a useful test of the original export.
Record the decoded text, the reader used and whether the result was consistent across several attempts. If one reader fails, try another reader that explicitly supports the symbology before concluding the encoder is wrong. If two readers disagree, inspect their output and settings; do not choose whichever answer happens to match what you expected.
Then test the actual printed label
A screen test checks the digital image under one set of conditions. It does not test your printer, paper, packaging or final scale. Print a sample from the exported file using the intended label dimensions. Inspect the bars or modules for missing lines, smudges and blurred edges. Keep all quiet zones intact.
Attach the label to its real surface. A label on a flat sheet can behave differently when wrapped around a bottle or placed beneath glossy film. Scan in the lighting that staff or customers are likely to encounter. Try the ordinary holding distance rather than carefully arranging a perfect laboratory view that will never occur in use.
For a batch, sample labels with different lengths and content. Include one near the end of the print run so that alignment or print quality changes are more likely to be noticed. If you use the bulk generator, compare each tested label with its original row, not just with another label from the same sheet.
Check the action as well as the encoded text
With a QR code, decoding a URL and reaching the correct page are separate checks. Read the destination before opening it. Confirm the spelling, HTTPS address and final landing page. A correctly encoded old or mistyped address is still the wrong result for your customer.
For a Wi-Fi QR code, test the intended network name and security mode on a device that can join that network. A reader showing the correct text does not prove the password is valid or that the access point is reachable. Treat the printed code as access information: anyone who can read it may learn the credentials it contains.
For a vCard QR code, inspect the contact preview before saving. Check the person's name, phone number, email and website individually. Contact applications can interpret fields differently, so test on the devices important to your audience. Remove any test contact afterwards if you do not want it retained.
If the code will not scan
Work through a short sequence: confirm format support, clean the lens, show the entire symbol, improve even lighting, and adjust distance for focus. Next compare the original export with the printed copy. If the export reads and the paper does not, investigate scale, print quality, glare and material before changing the encoded value.
If neither reads, test a known working sample of the same format in the same application. That helps separate a reader limitation from a particular label problem. Reduce unnecessarily long QR content when possible, or increase the physical size while preserving proportions. Do not crop margins or stretch only one axis to make the code fit a small space.
The size and print guide explains module width and quiet zones. Keep notes of each change so the final fix is reproducible. A series of unrecorded changes can produce a working sample without explaining why it works or how to reproduce it next month.
Understand the limits of a phone test
A successful scan shows that a particular reader decoded that sample under those conditions. It is not a formal print-quality grade, a guarantee that every checkout scanner will accept the label, or proof that a warehouse application will map the value correctly. Test with the destination equipment and arrange formal verification when your trading partner requires it.
Generating or scanning a UPC or EAN does not register that number with GS1. This website does not allocate product identifiers or check their ownership in the GS1 registry. Identifier assignment, the barcode's encoded data, print quality and the receiving system's product record are four separate things to check. The UPC versus EAN guide explains how to choose the appropriate retail format.
Primary references
Last reviewed: · How we maintain these tools
Questions
Frequently asked questions
My phone camera reads QR codes but not Code 128. Is the barcode broken?
Not necessarily. Confirm that the application supports Code 128; built-in QR scanning does not imply support for every barcode format.
The app reads the number but cannot find a product. What does that mean?
Decoding and catalogue lookup are different operations. Compare the raw digits with your source, then investigate the catalogue or product record separately.
Does a phone scan replace barcode verification?
No. It is a practical decoding check, not a standards-based print-quality assessment or a guarantee of trading-partner acceptance.