Guide
Bulk 2D QR Codes from Excel or CSV: Turn a Product List into 3,000 Codes
A single 2D QR code is fine for one product. It is the wrong tool when you have a catalogue: hundreds of SKUs, each with its own GTIN, batch and expiry date, and a print deadline. Typing each one by hand is slow, and every re-typed GTIN is a chance to print a wrong code on a whole run.
Bulk generation solves exactly that. You prepare one product list, upload it, and get a code for every row — up to 3,000 rows per batch on the Pro plan, from CSV, Excel or Google Sheets. The same validation that runs on a single code runs on every row: the GTIN check digit is verified, the data is checked against the GS1 General Specifications, and the symbol is rendered to ISO/IEC 18004.
This guide walks through the whole flow: prepare the file, upload it, choose the encoding, download print-ready files, and test-scan before anything goes to print.
Step 1: Prepare the file — one row per code
Start from the product list you already have. One row is one code. The downloadable template on the bulk generator uses these columns, in this order: name, gtin, cpv, batch, serial, expiry, url, 240. Leave a cell empty to omit that AI.
| Column | What it is | Format |
|---|---|---|
name | Label for the file (optional) | The downloaded files are named after this column, or after the GTIN when it is empty. |
gtin | The product GTIN | Required on every row. 8, 12, 13 or 14 digits; shorter GTINs are zero-padded to GTIN-14, including GTINs whose leading zeros a spreadsheet dropped. The check digit of every row is verified on upload, so a mistyped digit is caught before printing. |
cpv | Consumer product variant (AI 22) | Optional. CSET 82 characters (see below), no spaces. |
batch | Batch or lot number (AI 10) | Optional. CSET 82 characters, no spaces. A column named lot works too. |
serial | Serial number (AI 21) | Optional. CSET 82 characters, no spaces. |
expiry | Expiry date (AI 17) | Optional. Six digits, YYMMDD — for example 261231 for 31 December 2026. |
url | Plain QR URL (optional) | When filled, the row encodes this URL as a plain QR code instead of a GS1 Digital Link. The row still needs a valid GTIN. |
240 | Additional product identification (AI 240) | Optional. An example of a column named by its AI number. |
Any other AI is a column named by its number — for example 400, or 3103 for net weight in kg. The extra date columns best_before (AI 15), prod_date (AI 11) and pack_date (AI 13) also take YYMMDD. Every column is validated against the GS1 table for length and character set.
Allowed characters for the qualifier values are CSET 82: letters, digits and ! " % & ' * + , - . / : ; < = > ? _, no spaces. That is the most common reason a row is rejected: a space in a batch number, or a serial with a character outside the set.
A worked example — three rows, demo GTIN only
The rows below use GS1’s own demo GTIN, 09506000134352, so you can see the shape of the file without risking a real product. Replace it with your own GTINs before uploading.
| name | gtin | cpv | batch | serial | expiry | url | 240 |
|---|---|---|---|---|---|---|---|
| Demo product | 09506000134352 | ABC123 | SN001 | 261231 | |||
| Demo product | 09506000134352 | ABC123 | SN002 | 261231 | |||
| Demo product | 09506000134352 | DEF456 | SN003 | 270630 |
Three practical rules before you upload:
- One GTIN, one product. The 2D code must carry the same GTIN as the 1D barcode already on the pack, or till and warehouse systems will disagree.
- Write expiry as YYMMDD. 261231, not “31 Dec 2026”. A date in words is rejected. Dates such as 2026-12-31 or 31/12/2026 are converted automatically and flagged in the table — check that the converted value is the date you meant.
- Keep the file to 3,000 rows per batch. If your catalogue is bigger, split it into batches of 3,000. Pro also has a fair-use limit of 20,000 codes per 24 hours, which covers normal production use.
If you are not sure the file is right, test it small first: upload 3 to 5 rows, generate them, and check the results before sending the full list.
Step 2: Upload the file
Bring the list from a file, a shared Google Sheet, or straight from the clipboard — no reformatting is needed beyond the columns above. The bulk generator accepts CSV, TSV, Excel (.xlsx, .xls) and Google Sheets, or a paste straight from a spreadsheet. Every row is checked as soon as the list is loaded, and the table shows which rows are ready and which need fixing.
Before you pay anything, you can try the tools for free: 10 previews of different codes without an account, plus 10 more with a free account after email verification, and a single 2D QR code downloads as PNG while you preview it. Bulk generation itself is part of Pro, so downloading the full batch needs a Pro plan — see the current Pro terms on the pricing page.
Step 3: Choose the encoding — Digital Link or element string
The same GS1 data can be encoded in two GS1-recognised ways. Pick the one that matches where the code will be scanned.
- GS1 Digital Link URI, for consumer packaging. The QR carries a web address, for example
https://id.gs1.org/01/09506000134352/10/ABC123/21/SN001?17=261231. Phones open it instantly, and a GS1-capable scanner still reads the GTIN out of it. This is the recommended encoding for Sunrise 2027, the GS1 industry milestone by which retailers worldwide aim to accept 2D barcodes at the point of sale, alongside today’s EAN/UPC. - GS1 element string (GS1 QR Code), for warehouse and production labels. The QR starts with FNC1 and carries the raw AI string — in human-readable form
(01)09506000134352(17)261231(10)ABC123(21)SN001. Scanners read the raw data string rather than a web page. Consumer phones usually cannot open it.
One thing to know about the resolver, the server that answers when a code is scanned: id.gs1.org only redirects GTINs whose brand has registered links with GS1 — an unregistered GTIN returns “not found”. For your own products, use a domain you control, for example qr.yourbrand.com, and run, or subscribe to, a GS1-conformant resolver there. QR-DigitalCode only creates the codes; it does not host resolvers or product data.
Step 4: Download print-ready files
For a print run, a PNG is not enough. Pro gives you print-ready files for every code in the batch:
- SVG for packaging artwork, and PDF for a quick proof.
- GS1 DataMatrix with HRI — PNG, SVG, ZIP and PDF grid — the format many logistics and healthcare buyers ask for, and the right choice for small packs where a QR would be too big. See the DataMatrix generator.
Downloaded codes are static: the GTIN, batch, expiry or URL is inside the symbol itself, so a code keeps scanning even if you cancel. Product data is not stored — previews are drawn in your browser, and paid files are generated on the server and discarded.
Step 5: Test-scan before you print
This is the step that saves a print run. Screen previews lie; scanners do not. Before the batch goes to print:
- Print a sample of the batch, not just one code — include a code with the longest batch number and one with a serial, because longer data makes a denser symbol.
- Scan it once with a 2D retail scanner and once with an ordinary phone camera.
- Check the print: dark modules on a light background, square modules, the quiet zone around the symbol intact, and for retail packs a module size of at least the GS1 minimum of 0.396 mm. A code that has not been test-scanned is not ready for a print run.
- Check the data inside the code, not just that it scans: does the batch and expiry in the code match what your own systems expect for that row?
Only when the sample scans cleanly in both worlds should the full batch go to print.
Common bulk errors, and how to fix them
- Check digit fails on one row. The GTIN in that row is mistyped. Fix the GTIN, not the code — the generator is telling you the product number is wrong.
- A row is rejected for characters. Look for a space, or a character outside CSET 82, in the batch, serial or variant value.
- The expiry is rejected or flagged as converted. A date in words is rejected; a date such as 2026-12-31 is converted to YYMMDD and flagged. Write expiry as six digits to avoid surprises.
- A column called weight is ignored. Columns the generator does not recognise are skipped without an error, so the value never reaches the code. Put net weight in a column named after its AI number,
3103. - The phone opens “not found”. The code is fine; the resolver is not. The GTIN has no registered link on
id.gs1.org. Use your own resolver domain for your own products. - The code scans on a phone but not at the till. Check the encoding and the print size. Consumer packs want a Digital Link; warehouse labels want an element string. And check the module size is at least 0.396 mm for retail.
If you are starting from a single product rather than a list, start with the companion guide: Start Small with 2D Codes: Dual-Code a Few SKUs First, Then Roll Out.
Try it on a small batch first. Upload 3 to 5 rows to check that every row validates and to preview the first code free, then go Pro to download the full catalogue.