QR codes on product packaging: best practices that actually work.

A QR code on packaging is one of the few design decisions that is simultaneously cheap, permanent and easy to get wrong. These are the practices that survive contact with real phones, real lighting and real print processes.

Placement: the box or the product?

Both, for different jobs. Packaging is read once, at unboxing, when setup questions occur. The product is read for years, when cleaning and troubleshooting questions occur. If you can only print one code, put it on the product.

Size and quiet zone.

• Start at 2 cm square — A reliable minimum for handheld scanning on packaging.
• Scale with distance — Rough rule: code width of about one tenth of the intended scanning distance. Machinery read from two meters needs a much larger code.
• Protect the quiet zone — Leave clear space of at least four module widths around the code. Crowding it with artwork is the most common cause of failed scans.
• Keep the URL short — Long URLs create denser codes that need to be printed larger to stay readable.

Contrast, color and finish.

• Dark code, light background — Inverted codes are read inconsistently. Do not risk it on a print run.
• Avoid low-contrast brand palettes — A tasteful beige-on-cream code is a code nobody can scan.
• Prefer matte over gloss — High-gloss laminate under a ceiling light produces a specular hotspot straight across the code.
• Mind the substrate — Kraft board, textured plastic and powder-coated metal all reduce edge definition. Test the actual material.
• Keep it flat — Codes on tight curves and folds distort. Place away from creases and seams.

The label matters as much as the code.

People scan when they know what they will get. A code with no explanation is asking for blind trust. Write the benefit, not the mechanism:

• "Scan for setup instructions" — Clear, immediate, matched to the moment of unboxing.
• "Need help? Scan here" — Good for troubleshooting placements on the product itself.
• "Scan to see how to clean it" — Specific tasks convert better than generic invitations.
• Add the short URL — Print it underneath for people who prefer typing, and as a fallback.
• Avoid "Scan me" — It says nothing about what happens next.

What the code should link to.

A mobile page you control that answers the question the label promised. Not your home page, not a PDF, not a marketing campaign that will be retired next quarter, and not an app store listing. If the label says setup, the first thing on screen should be step one.

Print production notes.

• Supply vector art — An SVG or EPS scales without softening the module edges. Never upscale a small PNG.
• Use pure black — Rich black builds can misregister and blur the pattern. Single-channel black is safer.
• Watch small-format processes — Flexo and direct-to-substrate printing spread ink; increase size slightly for those.
• Check die lines — Confirm the code is not near a fold, glue flap, tear strip or window.

Test before you commit.

• Print a physical proof — On the real material, with the real finish. Screen tests prove nothing.
• Multiple phones — Include an older handset and both major camera apps.
• Bad conditions — Dim room, harsh downlight, arm's length, slight angle, one-handed.
• A first-time user — Hand it to someone who has never seen the product and watch where they hesitate.
• Check the landing page on 4G — A slow, heavy page undoes a perfect scan.

Common mistakes.

• Only on the outer box — The code is recycled before most questions arrive.
• No explanatory text — Scan rates drop when nobody knows what the code offers.
• Linking to the home page — The customer now has to navigate a site to find step one.
• Linking to a PDF — Pinch, zoom, and a document that can never be corrected once downloaded.
• Requiring an app or account — A login wall in front of setup instructions creates tickets.
• Third-party short links — Someone else's domain, someone else's uptime, and possibly a paywall on your scan data.