Batch QR codes: best practices for retail and events

Coupons, booth traffic, and fixed-asset tags often mean hundreds or thousands of QR codes at once. Without consistent filenames and a single source of truth for data, reconciling scans, reprints, and analytics gets painful fast. Treat batch generation like a small ETL job: inputs (spreadsheet or database), transforms (URL rules, UTM policy), and outputs (PNG/SVG/ZIP) should each be versioned.

Before anyone prints, agree who owns the destination. Marketing may control the landing page; IT may own the short-link domain. If those roles drift, you get dead links on live signage or campaigns that cannot be traced back to a row in the sheet.

Customer scanning in a retail setting — Figure 1: Clear codes and good sightlines matter as much as the landing page.

Practical checklist

Maintain one row per code in a spreadsheet: sequence, target URL, human-readable label, owner, and expiry if any.
Name files with date and batch, e.g. 20250318-event-A-001.png; avoid spaces and ambiguous locales in filenames.
Before print runs, spot-check with the same phone models your audience uses; add one older Android if your crowd is mixed.
Store generated images in a folder per campaign; never hand-edit URLs in the sheet without regenerating matching graphics.

Organized products and labels — Figure 2: Store exports in folders by campaign so updates stay traceable.

Retail and events: field realities

For retail, tie each QR to a single SKU or shelf talker revision. When price changes weekly, prefer a stable short URL that routes server-side to the current offer so you are not reprinting aisle tags every Monday.

For events, Wi-Fi and lighting vary wildly—test scans from two meters away under yellow hall spots. If you use sequential codes for prize draws, seal the random seed and export list before doors open so disputes do not become “trust me” conversations.

Archiving and reprints

Keep the spreadsheet, the image bundle, and a README with print spec (size in mm, error correction level, margin). Six months later, someone will ask for “the same as last year”—without that bundle you will rebuild from memory and risk subtle mismatches.

If URLs must outlive a single campaign, consider dynamic QR or a managed short link so you can change the destination without reprinting every sticker.