How to Hand Off QR Artwork to Print Without Errors
Most QR print errors are not design errors. They are handoff errors: the printer receives a folder of images with cryptic names, no record of what each code links to, and no note about where it goes or how big it should be. The printer guesses, the wrong code ends up on the wrong sign, and the mistake is discovered by a customer. A manifest fixes this by traveling with the artwork. It is a simple table, one row per file, recording the filename, the payload the code encodes, and the placement notes. Anyone who opens the ZIP can verify every code without asking a single question.
The payload column is the most valuable part of the manifest, because filenames cannot be trusted to describe content. A file named menu-final-v3 may encode last season's menu, a staging URL, or a link with a typo, and nothing in the filename will say so. Writing the intended destination next to each filename makes verification possible: the printer or designer can scan the code and compare the result against the manifest in seconds. Do this before you send the ZIP, not after, because a mismatch caught at your desk costs a minute and a mismatch caught after printing costs the whole run.
Notes should answer the three questions the printer will ask: where does this go, how big should it be, and how many do I print. Window, 150 millimeters, two copies is a complete instruction. Table tents, 60 millimeters, 40 copies is another. Include the material or finish if it matters, such as matte laminate for outdoor use, and flag anything unusual, such as a code that sits on a curved surface or behind glass. If a code has already been test-scanned at final size, say so in the notes; it tells the printer the artwork is approved and stops a well-meaning operator from resizing it to fit a layout.
File hygiene matters as much as the manifest. Send the highest-resolution files you have, keep filenames stable after the manifest is written, and never rename a file without updating its manifest row. Export for print in SVG or high-resolution PNG, and avoid JPEG, whose compression softens the module edges. If the handoff includes codes for several locations or campaigns, split them into clearly named folders or separate ZIPs rather than mixing them into one long manifest where a row can be skipped. A handoff that is boring to read is a handoff that works: every row identical in structure, every field filled, no surprises.
Keep a copy of the exact ZIP you sent. When a reprint is needed months later, the sent ZIP plus its manifest is the only reliable record of what was actually printed. If a destination URL changes, update the code, the manifest, and the stored ZIP together, and note the change in the manifest notes. That discipline turns QR artwork from a pile of disposable images into a controlled set of assets that can be audited, reprinted, and trusted.