GS1 Sunrise 2027: What 2D Barcodes Change on Your Label
Every phone in the office reads the new QR code. The register scanner never will. The difference is 660 nanometers: point-of-sale imagers illuminate the label with red light, red ink reflects red light, and a red 2D code disappears into its own background. GS1's 2D Barcode Colour & Quality Guide shows the result side by side: a crisp red QR under a phone camera, a blank grey square under POS illumination.
That trap sits inside a larger change. What Sunrise 2027 is, why it lands on your product data before your packaging, and what to do in what order is covered in the site's Sunrise 2027 guide. This piece is about the few square centimeters of it that land on the label itself: which code goes on pack, where it sits, what it may look like, and who grades it.
The UPC stays, and the new code sits 50 millimeters from it
Nothing comes off the label. GS1's implementation guideline for 2D at retail accepts three symbologies at the register: a QR Code carrying a GS1 Digital Link URI, a Data Matrix carrying the same URI syntax, or a GS1 DataMatrix. And it keeps the linear barcode mandatory alongside any of them until 90% of POS scanning solutions can read the 2D code and pull a GTIN out of it. Dual marking is not a courtesy to old registers; it is the published transition state, with a published exit condition.
Placement is specified too. GS1's scan-speed testing put the working limit at 50 millimeters, about two inches, between the 2D code and the center of the linear barcode; farther apart, the scanner cannot catch both in one presentation and the register's items-per-minute target slips. Both codes resolve to the same GTIN, necessarily: if they disagreed, the price would depend on which symbol the scanner found first. For Cinderhaven Provisions, whose fifty jar labels carry the UPC low on the back panel beside the nutrition block, the rule draws a two-inch circle around every UPC and says: the new code lives in here. Cinderhaven Provisions is a fictional company and its labels are a synthetic dataset; the 50-millimeter rule and everything else those labels are about to run into are GS1's, published and checkable.
The marketing QR that already sits on many packs does not get a sibling. GS1 US's guidance is to rebuild existing QR codes on GS1 Digital Link syntax, so one square answers both audiences: a GTIN for the register, a product page for the phone. One code doing both jobs beats two codes competing for the same corner of the panel.
The register reads red as white
Color behaves differently under a scanner than in a design review. POS imagers and verifiers work in red light, the 630-680 nanometer band. Under that light, red ink and white substrate reflect almost identically. So a red code has no contrast at all, while a red background behaves like white and sits on GS1's approved list. Red is the one color that is simultaneously a compliant background and a fatal foreground.
The rest of the palette follows the same physics. Dark works for the code: black, dark blue, dark green, dark brown, matte for preference. Light works behind it: white, yellow, light orange, red. Reverse printing, a light code on a dark ground, is permitted for the 2D symbol; the linear code stays dark-on-light. Gradients fail. The guide wants at least 30% symbol contrast to reach the minimum grade and recommends about 50%, where plain black-on-white carton typically measures above 70%.
For a chili-pepper brand this is not an abstract palette question. Cinderhaven's Artisan Sauce labels are built on reds, and the brand-consistent color for the new code, the one a designer reaches for first, is the one wavelength the register cannot see. The code goes dark on a light patch, and the patch is a design element now, quiet zone included: four modules of clear space on every side of a QR, one module for a Data Matrix.
The palette decision is settled by a light source, not the brand book.
"It scans on my phone" is not a test
The specs make the label a graded print job. Module size, the X-dimension of one square in the matrix, runs from 0.396 millimeters minimum to 0.990 maximum, with 0.495 as the target. Print quality is graded under ISO/IEC 15415 with a floor of 1.5, measured through a 0.30-millimeter aperture at 660 nanometers: the 1.5/12/660 line that starts appearing on artwork approvals.
A phone cannot run that test. A smartphone camera works through an aperture of roughly 1.875 to 2.5 millimeters, six to eight times wider than the verification aperture, under broadband white light instead of narrow-band red. It forgives low contrast, crowded quiet zones, and color choices the register refuses. The office scan test passes labels the verifier fails, in exactly the cases that matter. Verification is the discipline the unreadable GS1-128 shipping label already taught on the case level, moved to the consumer unit.
Substrate closes the spec. Glossy and metallized surfaces mirror the scanner's own light back at it, so a code on foil or high-sheen film goes onto a matte white patch, dark code on top. Transparent packaging gets the same treatment: for Cinderhaven's 11-SKU refrigerated fresh-salsa line, a matte opaque white patch prints first and the code prints on the patch, so the salsa behind the film stops being part of the symbol.
| Spec | Requirement at retail POS |
|---|---|
| Symbologies | QR Code or Data Matrix with GS1 Digital Link URI; GS1 DataMatrix |
| Linear barcode | Stays on pack until 90% of POS can read 2D and capture the GTIN |
| Placement | 2D within 50 mm of the linear barcode's center |
| Module size | 0.396-0.990 mm; 0.495 mm target |
| Quiet zone | 4 modules (QR) or 1 module (Data Matrix), all sides |
| Color | Dark code on light ground, or true reverse; never a red code; no gradients |
| Print grade | 1.5 minimum under ISO/IEC 15415, 0.30 mm aperture, 660 nm |
The verifier is the register's advocate at the design review.
The artwork now contains your master data
A UPC encodes twelve digits. A Digital Link QR encodes a URI built on the GTIN, with room for batch, expiry, and serial data behind it. Everything in that URI comes out of the product master, the record the GDSN guide for the food industry traces from data pool to retailer, and once the plates run, it is fixed in film. A wrong attribute in a portal is an edit; the GDSN attribute errors that bounce items today become artwork errors under Sunrise 2027, and the master data fields that already drive chargebacks get printed. The 2D code is the product master with a print run behind it.
That is the sequencing argument in one line: the data gets right before the plates get made. A portal error costs an edit. The same error in artwork costs a reprint.
Put the label on the bench before the printer
Pull one label: your best seller's current artwork and the GTIN behind it. I will mark where the 2D code fits inside the 50-millimeter rule, which of your colors survive 660 nanometers, and whether the GTIN you are about to fix in film matches the one your data pool serves. One dieline is enough to start.
Next step — Chargebacks you can't trace
Find out what it is costing you. Free, no call.
The offers below run this on your own data — the scan is free, and the Snapshot credits in full toward the audit.
Private, expiring upload — never email. Mutual NDA before anything moves. Files destroyed within 30 days of delivery, with a certificate. Methods published, tools open source.