A QR code can look perfectly neat in a design file and still disappoint on paper. The code may be too small for its placement, crowded by artwork, or linked to a page that nobody checked on a phone.
Treat the printed proof as the final test. A screenshot is a useful draft, but it cannot show how the paper, lighting, or finished layout will affect the experience.
Check the destination first
Open the address without your own account session. Confirm that it shows the correct offer and has a clear next action. If the flyer promises a booking page, do not send readers to a general homepage and expect them to find it.
Use a stable destination that will remain useful for the expected lifetime of the flyer. If you encode a short link, keep a record of the exact address stored in the QR code and who controls it.
Changing a short link's destination can help maintain an existing printed campaign where your service supports that feature. It cannot help if the printed code encoded a different address.
Preserve the empty border
The QR code design guidance from DENSO WAVE specifies an empty margin four modules wide around the symbol. Keep that border clear of captions, patterns, photographs, and decorative frames.
A module is one small square in the code. The required margin is based on those squares, not a fixed measurement that works for every design. Ask your designer to keep the exported code's border intact when placing it on the flyer.
Do not crop the image tightly just to make the visible pattern appear larger. You may remove the space the scanner needs to recognize its edges.
Test the finished size and placement
Print a proof at the actual production size. Scan it from the distance a reader is likely to use. Try more than one phone and test in lighting that resembles the real setting.
A hand-held flyer and a poster behind a counter create different scanning situations. Do not rely on one universal minimum size to cover both. Increase the code's size or simplify the placement if the proof feels awkward to scan.
Leave the code away from folds, curved edges, and areas likely to be covered by another object. The relevant question is whether a reader can get a clear view of it.
Tell people what scanning will do
Place a short label beside the code: “View the workshop dates” or “See the full catalogue.” Match that wording to the first screen of the destination.
Include a readable web address as an alternative. Someone may be using a device without a convenient scanner, or may prefer to type the address later.
Sign off with evidence
- The final destination works on mobile.
- The clear border remains intact.
- The actual printed proof scans on multiple phones.
- The surrounding label explains the action.
- A readable fallback address is present.
- The campaign owner has saved the QR file and destination.
Should you print thousands after one successful scan?
One scan is a starting point, not a reliable acceptance test. Repeat the check across the conditions that matter for your flyer. A short test session costs much less than replacing a print run that sends readers to the wrong page.
Decide what the flyer needs to accomplish
A flyer works better when its QR code has one clear job. A restaurant opening flyer might lead to the opening hours and menu. A workshop flyer might lead to registration. A property viewing flyer might lead to publicly available viewing information. Trying to put every business activity behind one unstructured destination makes scanning less useful.
Write the expected action before designing the code. “See workshop dates and register” gives both the designer and tester a concrete task. “Find out more” leaves the destination open to interpretation. The instruction printed beside the code should help the reader understand what will happen after scanning.
Choose a page that can remain useful for the flyer's expected life. A temporary file stored in an employee's personal account may be inconvenient to maintain. A public page controlled by the organization is easier to review, update, and hand over. The code should belong to a maintained route, not just a design asset somebody generated once.
Understand the address inside the code
A QR code encodes data. When it contains a website address, scanning reveals that address. It does not automatically provide editable destination management. A code containing the final page address continues to contain that address after the design is printed.
A code containing a maintained redirect route can keep the same printed pattern while the route's destination is changed, if the service and account support editing. Confirm that ability before relying on it. Check subscription requirements, link expiry settings, ownership, and any conditions that could stop the route from working later.
For an illustrative flyer, the encoded address might be a short route leading to https://example.com/workshop. Save both the encoded address and the intended destination in the print record. If a colleague scans the design and sees something different, the record provides a clear reference for investigation.
Do not describe a code as editable simply because a design tool lets you replace its image. Replacing the digital image does nothing for copies already printed. Destination management must happen behind the same encoded route.
Preserve the clear boundary around the pattern
The empty boundary around a QR code helps a scanner distinguish the code from surrounding artwork. DENSO WAVE's QR code generation guidance explains the required quiet zone. Treat that space as part of the code rather than spare room for a decorative border or small caption.
Busy textures, touching graphics, or tight cropping can interfere with recognition. Keep the code in a clear area and review the actual exported file. A layout that looks spacious in the design application may become crowded after another person crops or resizes the image for printing.
Avoid assuming that decorative customization will work because the unmodified code did. Rounded modules, inserted logos, gradients, and unusual color treatments are design changes that require testing. Keep an unmodified fallback version available until the finished output has passed checks.
Strong contrast and a clean background make a sensible starting point. The precise usable size depends on the encoded data, printing quality, viewing distance, lighting, and scanning conditions. There is no single size recommendation that validates every flyer. Test the intended output rather than relying on a universal number copied from an unrelated example.
Export for the actual production process
Ask the printer what file format and production settings it needs. A vector QR asset can preserve crisp edges when scaled, but the entire export workflow still matters. A low-resolution screenshot inserted into a high-quality document remains a low-resolution source.
Review the final PDF or other supplied artwork at a realistic size. Look for softened edges, compression artifacts, cropped boundaries, and color changes. If the printer provides a proof, test that proof. Your earlier test of a separate code image does not verify the assembled flyer.
Keep the source file, final print file, encoded address, destination, and approval date together. Name versions clearly. A common avoidable error is sending an earlier export after the destination or artwork has changed. A print approval record should identify the exact file, not merely say “QR checked.”
If the printer modifies the design, request a new proof and repeat the scan check. Scaling a code down to make room for copy is a functional change, even if the layout looks more balanced.
Test in conditions that resemble use
Start with a clean test on a phone, then make the conditions more realistic. Print a sample at the intended size. Place it where a reader would encounter the flyer. Scan from the likely distance and angle under representative lighting.
A flyer placed behind reflective glass presents different conditions from one handed directly to a reader. A noticeboard can create distance and visual clutter. A folded leaflet may curve through the code. These details deserve testing because the camera sees the physical object, not the flat design preview.
Try more than one phone when practical, especially if the campaign will reach a broad audience. Do not require every tester to install a special scanning application unless that is genuinely part of the intended audience's workflow. Record which devices and conditions were checked rather than writing “works on all phones.”
After scanning, continue through the destination action. A code that opens a slow page or an inaccessible form has passed only the first stage. Check the page in a browser without the owner's session and ensure the promised information is visible.
Provide another way to reach the information
Print a readable address near the QR code when the task matters. A short address offers a route for people who cannot or prefer not to scan. It also gives readers a clue about the destination and organization.
Make the fallback legible at the printed size. Avoid a long URL full of tracking parameters that nobody can reasonably type. If you use a short route, verify that the printed spelling matches the encoded address or deliberately document why the two routes differ.
The fallback should lead to an equally useful experience. Do not make scanning the only way to reach essential event details, accessibility information, or registration instructions. A person may be using a device without a suitable camera or may be unable to point it comfortably at the flyer.
For an illustrative workshop design, the caption could read “View dates and register,” followed by a readable example address. The exact wording should reflect the real page. An instruction promising a discount should not lead to a generic homepage that makes visitors search for it.
An illustrative proofing session
Imagine a local repair workshop preparing a flyer for a weekend class. The team encodes a maintained short route pointing to a public registration page. It prints a single proof at the final size and places it on the noticeboard where the campaign will run.
One tester scans while standing close, another tries from the expected reading distance, and both complete a test registration using a clearly designated test process. They confirm that the page shows the correct date and venue. The team also types the printed fallback address to catch spelling errors.
The proof reveals that a decorative frame sits too close to the code. The designer removes it, exports a new version, and repeats the test. The print record now identifies the approved export, route, destination, owner, and review date. These are illustrative steps, not claimed results from a real print campaign.
After the class closes, the owner plans to leave a truthful closed-registration notice at the destination. That decision matters because flyers may remain on noticeboards after the promotion ends. A late scan should provide context rather than a confusing error.
Troubleshoot a code that scans inconsistently
If the code fails before opening a browser, investigate the physical pattern first. Check quiet space, contrast, size, focus, glare, distortion, and export quality. Compare the final printed code with the original generated asset. If the original scans and the print does not, the production process is a useful starting point.
If the code is recognized but the wrong page opens, decode or inspect the address and compare it with the print record. The wrong asset may have been inserted into the layout. A redirect destination may also have changed. Identify which layer is wrong before recreating the whole design.
If the correct page opens but the action fails, inspect the destination. Permissions, expired forms, missing files, or an overloaded page are not QR pattern problems. Fix the page or maintained route where possible, then repeat the full journey.
Do not approve a large print run based on one successful scan after several unexplained failures. Inconsistent behavior is a reason to simplify the design and investigate, not evidence that the code is reliable enough.
Print approval questions
Can I make the QR code smaller to fit the layout?
Possibly, but test the new final size in realistic conditions. A scan from a computer screen or a larger proof does not validate the smaller printed version. If space is tight, shorten the encoded address where appropriate and simplify the artwork before sacrificing readability.
Can I add a logo in the middle?
Customization can affect scanning, and the usable result depends on the design and code. Keep the logo treatment modest, preserve a clean pattern, and test the finished print. Error correction is not permission to obscure any area without limits. Retain a plain version if the branded treatment is inconsistent.
Should the QR code and typed address have different tracking labels?
They can, if you need to compare scanning with typed visits and can maintain both routes. Record that choice explicitly. Otherwise, using the same route simplifies the design and testing. Decide which distinction matters before producing extra addresses.
What is the final approval standard?
Approve the exact production file after checking the pattern, printed fallback, destination, and main action. Keep the owner and maintenance plan in the record. A technically scannable code is only useful when it takes readers to accurate information they can act on.
