Bulk qr code naming rules before print
SmartQRCode editorial · Updated October 2026
Bulk qr code naming rules are how a spreadsheet stays searchable after 5,000 hosted codes exist. Put the human string in the label column, not in the modules. Names do not change print density. A Canva one-off needs no scheme when you have one frozen URL and will not count scans.
What bulk qr code naming rules should encode
Keep the label column not modules. The parser already knows headers label name campaign title. Put sku in the name not the url. Then names survive a destination patch.
The name is an operator label. The destination is a URL. Mixing them is the classic plant failure: column A is the SKU, the mapper treats it as a link, every code creates, and the first scan from a carton goes nowhere. label column not modules is the rule to write at the top of the sheet.
headers label name campaign title are the spellings the parser already accepts for that column, plus campaign_name and description. If your export says "SKU" or "Internal ID," rename the header or you will fight the mapper. Destination headers are a different list: url, link, destination, website, and the rest in bulk QR from CSV upload.
sku in the name not the url keeps merchandising searchable without turning the SKU into a 302 target. UTMs still belong on the hosted destination; see UTM QR code parameter plan. The queue that drains the sheet is bulk QR code batch jobs.
Paid options are $1.99, $29, $97, and $197. We do not sell an unpaid tier. Tracked QR codes, the website URL generator, and dynamic QR codes are the hosted faces. Retail marketing codes are why a name like "Aisle 4 facing 12" beats "QR-9921."
names survive a destination patch. When spring becomes autumn, the row is still "Aisle 4 facing 12." The plant folder still finds the file.
Label versus destination in the CSV
Label versus destination in the csv is two columns with two failure modes. A pretty name in the URL field 404s. A raw URL in the name field makes the list unreadable. Both rows can still be "successful" creates.
Quoted commas in a product name are legal CSV. Hand-splitting the file in a text editor is how names and URLs shift one column to the right from row 400 down. The batch then looks random. Re-export from the spreadsheet instead.
Duplicate names are allowed by the parser and hated by humans. If two people must pick an SVG, make the name unique on purpose: brand, SKU, language, location.
Wi-Fi does not belong in this naming scheme. It is not editable and not trackable. A sheet of SSIDs is a reprint programme.
Do names change the printed modules
They do not. Density follows the hosted URL, not the label. You can rename after print. You cannot rename a static Canva payload without reprinting, because that payload is the URL itself.
ISO/IEC 18004 does not have a "title" field. Anything you want the camera to open has to be in the encoded string. Anything you want a colleague to find has to be on the row.
Provider pause still stops scans regardless of how well you named the batch. F91 is not a taxonomy problem.
A good name is boring: brand, SKU, language, location, version. A clever name is a riddle at 5am in a plant. If the CSV came from a PIM, keep the PIM primary key in the label even if humans never say it out loud. When two rows share a pretty title, the key still splits them.
If you localise later, do not rename by editing pixels. Rename the row. The modules stay put. That is the whole benefit of hosted codes over a Canva file named "final_v7_really.png".
Skip naming when you have one static file
One poster, never edited, never counted: Canva or another free static generator. Bulk qr code naming rules would be a style guide for a single PNG.
Thousands of hosted facings: name like a warehouse, map SKU to short code, keep UTMs on the destination, and export real print files. The name is how you still find the object when the person who uploaded the CSV has left.
Questions this raises
Destination is the hosted URL, including any UTMs. Label is the human name. Headers for names include label, name, campaign, and title. Putting a SKU in the URL column mints codes that point at nothing.
No. Modules encode the scan URL. names survive a destination patch because they live on the row, not in the pixels.
When you have one frozen URL and will not count. A Canva one-off needs no scheme. Bulk qr code naming rules exist so a 5,000-row job remains searchable.
Both can create. You will not be able to tell them apart in a list. Uniqueness belongs in the name if humans have to pick a file for the plant.
Keep going
The tools and playbooks this post refers to, one click away.
Make the code this post is about
$1.99 for 7 days, then a paid plan. Pick a type, brand it, and edit the destination whenever you like, even after it is printed.