Guide
Start Small with 2D Codes: Dual-Code a Few SKUs First, Then Roll Out
Retailers are moving toward accepting 2D barcodes at the till alongside today’s EAN/UPC — the GS1 Sunrise 2027 milestone. A 1D barcode carries only the GTIN. A GS1 2D code carries the GTIN plus batch, expiry date, serial number and more, and it opens on a consumer’s phone while still scanning at the till.
The safest way to make that switch is not to re-label everything at once. Pick a few SKUs, carry both a 1D and a 2D code on them for a time, check what actually happens at the till and on the phone, then replicate the process across the rest of the range. This guide walks through exactly that.
Step 1: Pick a few SKUs to start with
Choose two or three SKUs that make a good test:
- A steady seller you print often, so you get scan feedback quickly.
- A product where batch or expiry matters — food, cosmetics, supplements, anything with a recall risk — because that is where the extra data in a 2D code earns its keep.
- A product whose packaging has room for a second symbol without shrinking either code below a scannable size.
Leave the rest of the range alone for now. The point of the pilot is to learn on a small surface before you commit print runs to it.
Step 2: Generate the 2D code for each pilot SKU
Keep the existing 1D barcode on the pack. Add the 2D code beside it, carrying the same GTIN.
- Enter the GTIN in the QR generator. It validates the check digit as you type, so a mistyped digit is caught before anything is printed.
- Add the data that matters for that product: batch or lot number, expiry date, serial number if you use one.
- Choose the encoding for where the pack will be scanned:
- GS1 Digital Link QR for consumer packaging. The code carries a web address, so a phone opens product information instantly and a GS1-capable scanner still reads the GTIN out of it.
- GS1 element string (GS1 QR Code) for warehouse and production labels, where scanners read the raw data string rather than a web page.
- Download the 2D QR code as PNG, free, with no sign-up — the free allowance covers 10 previews of different codes, enough to test the pilot SKUs and show the idea to colleagues.
Before anything goes to print, scan the code yourself: once with a 2D retail scanner and once with an ordinary phone camera. Keep dark modules on a light background, keep the quiet zone around the symbol intact, and for retail packs keep the module size at least at the GS1 minimum of 0.396 mm. A code that has not been test-scanned is not ready for a print run.
Step 3: Run both codes side by side for a time
This is the part most teams skip, and it is the whole point of starting small. For a few weeks, the pilot SKUs carry both symbols:
- The 1D code keeps every existing scanner, till and warehouse process working exactly as before.
- The 2D code gets scanned in the real world — at the till, in the warehouse, on a phone — so you find out what breaks before it matters.
While the pilot runs, watch for the things that actually decide a rollout:
- Do the 2D codes scan first time at the till, or do cashiers fall back to the 1D code?
- Does the phone open the right page for each product, batch and variant?
- Does the print hold up — contrast, size, placement — on your real packaging material, not just on screen?
- Does the batch and expiry data inside the code match what your own systems expect?
Write down what you find per SKU. That note is what turns a pilot into a repeatable process.
Step 4: Fix what the pilot exposed, then replicate
Adjust the weak points on the pilot SKUs first: a bigger symbol, a different placement, a corrected data field, a different resolver page. Re-test after each change. Only when the pilot SKUs scan cleanly in both worlds should you extend the same setup to the next group of products.
That is where bulk generation comes in. Instead of creating codes one by one, upload your product list and generate a whole batch at once:
- Bulk upload from CSV, Excel or Google Sheets — up to 3,000 rows per batch on the Pro plan, with the same GTIN, batch, expiry and serial handling as single codes.
- Before paying anything you can load your real list into the bulk generator, see which rows validate, and preview codes within the free allowance: 10 previews without an account, plus 10 more with a free account after email verification.
- For production, Pro adds print-ready SVG and PDF for every code, the bulk download itself, and GS1 DataMatrix with HRI — the format many logistics and healthcare buyers ask for.
The workflow stays the same as the pilot: same GTIN, same data fields, same test-scan before printing — just applied to a file instead of one product at a time. Repeat group by group until the range is covered, and keep the 1D code on pack until you are confident every scan point you sell through reads the 2D code.
For the full bulk workflow, see the companion guide: Bulk 2D QR Codes from Excel or CSV: Turn a Product List into 3,000 Codes.
A few practical rules for the whole rollout
- One GTIN, both symbols. The 2D code must carry the same GTIN as the 1D code it sits next to, or till and warehouse systems will disagree.
- Test-scan before every print run. Screen previews lie; scanners do not.
- Dark on light, always. Decorative colours and logos belong only on consumer-facing packs, and only with strong contrast and the quiet zone intact.
- Codes are static. Once downloaded, a code keeps working even if you cancel — the data is inside the symbol itself, not on a server. Product data is not stored: previews are drawn in your browser, and paid files are generated and discarded.
Try it on your first SKUs. Create and preview free, download a single 2D QR code as PNG free, and test it on one product today.