Website QR codes — Delivery workflow

Worked example

Rename each export with destination and version, send SVG or 1440 px to the printer, and keep a sheet of which code points where.

Once the code is verified, the work is naming the files, choosing the right format for each recipient and keeping a record of what each code points to. Chatcument always saves with the file name chatcument-qr plus the extension, so rename immediately, for example menu-table-qr_v03_1440.png.

A cafe with three locations shows the problem: all three cards are exported with the same default name and one gets printed with the wrong address. Put the destination, the location and a version into every file name, and keep a small sheet that lists file name, address, size and the date you tested it. The sheet makes it easy to audit all printed codes when a page moves.

Pick the format by recipient. Give a print shop the SVG or a 1440 px PNG so they can scale it without blur; give a web editor a 720 px PNG or WebP for the page; paste the PNG into a slide at its native size and avoid stretching it, which blurs the edges. The Copy content button copies the address text itself, which helps when you need to send the plain URL beside the picture.

Because a static code cannot be edited, protect the destination instead. Point the code at an address on a domain you control, such as example.com/guide, and use a server-side redirect when the real page moves. If a campaign ends, leave a polite page at that address rather than a not-found error.

When you hand the files to others, include a one-line instruction: print at no less than 3 cm for table cards, keep the white margin, do not recolor or add effects, and send a printed proof before the full run. Ask for a photo of the proof being scanned, and file it with the sheet.

https://example.com/guide

QR encoding the same URL

Static codes cannot be edited; keep a record of which file points where, and control the destination address yourself.