What you are seeing
This fix restores a full quiet zone around the printed code. You will inspect all four sides of the proof, find what is eating the margin, and move the code, the trim, or the nearby text until the margin is clear. Verify the proof on two phones, because a margin that looks adequate to the eye can still be too tight for the scanner.
Likely causes
1.
Code placed too close to the trim edge — Quick test: compare the proof with the design file and check the margin at the trim side.
2.
Text or graphics crowding the code — Quick test: look for any ink inside the margin on any side.
3.
Background pattern reaching the code — Quick test: check whether the background behind the code is plain.
4.
Code scaled without its margin — Quick test: compare the proof margin with the margin in the exported file.
5.
Bleed or trim shift in production — Quick test: check several copies from the run, not just one.
Step-by-step fix
Step 1: Inspect all four sides of the proof and mark every side where the margin is missing or tight.
Step 2: Move any text, rule, or graphic away from the code on the affected sides.
Step 3: Move the code away from the trim edge, or add trim allowance so the margin survives cutting.
Step 4: If a background pattern reaches the code, place the code on a plain background panel with a clear margin.
Step 5: Re-export the code with its margin included, and check that the layout does not crop the image to the symbol.
Step 6: Reprint one proof and check the margin on all four sides, then scan it on two phones.
Step 7: Check several copies from the run for trim shift, and keep the proof as the reference.
Putting this into practice
In practice, add a margin check to the proof routine: four sides, every copy you inspect. Trim shift means the first copy off the printer is not proof that the last copy is fine, so check more than one. 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
- Cropping the code image tight to the symbol in the layout and deleting the margin the scanner needs.
- 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 with a cut-off quiet zone will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that prints with a cut-off quiet zone.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- A clear margin surrounds the code on all four sides
- No text, rule, or pattern sits inside the margin
- Several copies from the run keep the margin after trimming
- 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)
