Bulk Creation & Edits
This page explains how to create or update many QR codes at once inside a campaign using CSV import. Bulk operations help teams launch large initiatives, migrate existing codes, and keep destinations and UTMs consistent at scale.
When to use bulk
• Large launches — Create many codes for a campaign in one step.
• Remediation — Correct destinations or UTMs across multiple live codes.
• Variant management — Generate channel or creative variants that share a common goal and naming pattern.
• Migrations — Move from legacy links to new destinations without reprinting.
Pre-import checklist
• Campaign ready — Create or select the campaign that will contain the codes.
• Naming pattern — Apply Campaign Naming Standards so codes are easy to locate and report on.
• Destination readiness — Confirm each destination URL is live, HTTPS, and mobile-friendly.
• UTM plan — Finalize source/medium/campaign (and optional content/term) so tagging is consistent.
• Template — Download the Bulk Import Template (link placeholder) and review its column requirements.
Bulk create (new codes)
• Prepare the CSV — Use the template to add a row per code. Provide the destination URL and any UTM parameters you intend to use.
• Upload — From the campaign, choose Bulk Import and upload the CSV.
• Validate — Review the preview/validation results and resolve any row errors.
• Create — Confirm to generate QR codes. Codes are immediately available for export (SVG/PNG/JPG) and testing.
Bulk update (existing codes)
• Follow the template — The template explains how to reference existing codes for updates (for example, by including the required identifier and the fields you want to change).
• Common updates — Replace destination URLs, revise UTM parameters, or set status to Active/Inactive across many codes in one import.
• Apply and verify — Run the import, review the results, and test a sample of updated codes.
Template and formatting guidelines
• File format — CSV, UTF-8, with a single header row; avoid formulas and special formatting.
• Destinations — Provide full URLs. If you include UTMs, ensure they are correctly appended and URL-encoded.
• UTMs — Use a consistent pattern (for example, source=retail, medium=endcap, campaign=2025_q2_eventseries, content=variant_a) so GA4 reporting aligns with BaseQR scans.
• Status — If supported by the template, set status to Active or Inactive to control availability at import time.
• Required columns — Refer to the Bulk Import Template for the authoritative list of required and optional fields.
Validation and quality checks
• Resolve errors — Fix any reported row errors and re-import the corrected rows.
• Spot-check scans — Test a sample of created/updated codes on different devices and networks.
• Confirm attribution — Verify UTM parameters in the final URLs and check GA4 Real-Time to ensure events are flowing as expected.
Best practices
• Standardize naming — Consistent names make codes easier to find and reduce duplicates.
• Stage complex changes — For large edits, update a subset first, validate, then roll out to the rest.
• Retain a source file — Keep the CSV and import results for operational traceability.