What you are seeing
This fix restores the code to a size that scans at the real distance. You will measure the printed code, compare it with the size you designed, and either enlarge it, shorten the payload, or redesign the layout. Do not accept a code that only scans when the phone is pressed against it.
Likely causes
1.
Layout squeezed the code to fit — Quick test: measure the printed code and compare it with the designed size.
2.
Label or receipt template fixed the size — Quick test: check the template image box size against the code size.
3.
Payload too dense for the available space — Quick test: compare a short-payload version at the same printed size.
4.
Printer scaled the job to fit the page — Quick test: check the print settings and measure the printed output.
5.
Code placed where people stand far away — Quick test: scan the code from the real audience distance.
Step-by-step fix
Step 1: Measure the printed code and compare it with the size you designed. Note how much it shrank.
Step 2: Test the printed code at the real viewing distance on two phones.
Step 3: Shorten the payload as far as you can, then regenerate the code.
Step 4: Enlarge the code to the size that passes at the real distance, and check that the new size fits the layout.
Step 5: If the layout cannot fit the working size, redesign the layout: drop an element, move the code, or use a larger label.
Step 6: Check the print settings for any fit-to-page scaling, and switch it off.
Step 7: Reprint one proof at the corrected size and confirm it scans at the real distance on two phones.
Putting this into practice
In practice, write the minimum working size on the job file alongside the viewing distance. The next person to reuse the layout then knows the code cannot shrink below that size without breaking. Record the before-and-after behaviour with the job file, so the fix is provable rather than anecdotal. When the same failure appears again, that record tells you whether the old fix held or a new cause appeared.
Common mistakes to avoid
- Shrinking the code to fit a crowded layout instead of redesigning the layout to fit a readable code.
- Reprinting the full run before a single proof passes, which turns one failure into many.
- Testing on one phone in ideal conditions instead of two phones in the real conditions where a code that prints too small will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that prints too small.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The printed size matches the designed size
- The code scans at the real viewing distance on two phones
- No fit-to-page scaling shrinks the job
- The corrected proof passes on two phones in the real conditions
- The fix is recorded in the job file so the next reprint starts from a proven setup
- Every printed copy is checked against the approved proof
- The proof is retested after any later change to the link, design, or placement
Related tools and guides
- [QR minimum size checker](/qr-minimum-size-checker)
- [QR contrast checker](/qr-contrast-checker)
- [QR print proof checklist](/qr-print-proof-checklist)
- [QR DPI calculator](/qr-dpi-calculator)
- [QR quiet zone calculator](/qr-quiet-zone-calculator)
- [printed QR tester](/printed-qr-tester)
- [QR size calculator](/qr-size-calculator)
