Skip to content

Hundreds of codes for variable data printing

One code per copy, per store or per badge: how to name your codes, import them from a CSV file and check everything before the job goes to press.

When one code is not enough

Many QR codes are printed by the thousand, all identical. But some jobs need a different code on every item. A retail chain wants each store’s window poster to lead to that store’s page. An event organizer prints a personal code on every badge. A publisher numbers each copy of a limited edition, and a hotel wants one code per room for its service menu.

This is variable data printing: the layout stays the same, but a piece of content changes on every copy. When that piece is a QR code, the work moves from design to organization. Creating three hundred codes by hand is slow and error-prone. The method below keeps the job under control from the spreadsheet to the press.

Decide what one code stands for

Start by answering a simple question: one code per what? Per store, per table, per participant, per copy, per delivery address? The answer sets how many codes you need, what each destination should be, and what you will be able to measure later.

Think about the future too. If the codes go on badges for a single event, they can all point to pages that will close afterwards. If they go on store signage or product inserts, they will live for years, and each destination may need to change when a store moves or a page is redesigned.

Name your codes before you create them

With hundreds of codes, names are what keep you sane. Pick a pattern and stick to it: a prefix for the campaign, then the identifier of the item. For example, Store poster, Lyon Part-Dieu or Badge 2026, A-0147. Use the same identifiers as the print data file, so that each code can be matched to its record without guessing.

Avoid names that only make sense today, such as new or test. In six months, you should still be able to look at a name and know exactly which printed item it belongs to.

Prepare the CSV file

A CSV file is a plain spreadsheet saved as text, with one row per code. It is the usual way to create codes in bulk. Check the exact columns your tool expects; usually at least a name and a destination address for each row.

Spreadsheets have habits that can quietly damage a bulk import. Watch for these before you upload.

  • Leading zeros disappear when a cell is treated as a number: 0147 becomes 147.
  • Dragging a cell down can increase a number you wanted to keep, or copy one you wanted to change.
  • Accented characters can turn into strange symbols if the file is not saved in UTF-8.
  • Destination addresses must be complete, starting with https, with no spaces before or after.
  • Duplicate rows create duplicate codes, which are hard to tell apart once printed.

Match codes to the print data

Your printer’s variable data software needs to know which code image goes with which record. The simplest way is to name each code file with the same identifier as its row in the print data, so the software can place them automatically.

Ask your printer which file format they prefer. Vector SVG files stay sharp at any size and suit most professional workflows; high-resolution PNG files at the real print size work too. Agree on the size and the quiet zone around each code before anything is exported, so the layout does not need to be adjusted record by record.

Check before you send to the press

A mistake on a single code is a nuisance. A shift by one row, where every badge carries its neighbor’s code, ruins the whole job. A few checks on the proofs avoid this.

  1. Scan the first, the last and a handful of codes picked at random in the middle.
  2. For each one, check that the page it opens matches the name or number printed next to it.
  3. Count the codes in the file and the records in the print data: the two numbers must match.
  4. Open a sample of destinations on a phone to make sure the pages load and read well.
  5. Print one proof at the real size and scan it in real conditions, as described in our checklist for testing a QR code before printing.

Bulk codes with Lumberjack

On the paid plans, Lumberjack lets you create codes in bulk from a CSV file. Each code is read by a real QR reader before you can download it, and you can export it as vector SVG or as a 300 dpi PNG at print size. Each destination can be changed after printing, which is useful when one store moves while the others stay put, and every code has its own statistics. For agencies and printers working for several clients, the Studio plan adds a team, sub-accounts and white label.

Whatever tool you use, the order of the work stays the same: decide what one code stands for, name before creating, clean the spreadsheet, match files to records, and check the proofs before the presses start.