GS1 Sunrise 2027: getting your 2D barcodes print-ready

Requirements and timelines change. This page was last verified against GS1 and GS1 US on 18 July 2026. Always confirm the current version with GS1 — and your own retailer's supplier portal for its adoption timeline — before you rely on it. This is general guidance, not legal or compliance advice.

What the GS1 Sunrise 2027 actually is

For decades the barcode at the register has been the linear UPC (or EAN outside North America): a Global Trade Item Number — the GTIN — encoded as vertical stripes. GS1, the global standards body that issues those numbers, has publicized an industry effort commonly referred to as the Sunrise 2027 initiative: the goal of preparing retail point-of-sale systems to also read 2D barcodes such as QR codes and Data Matrix. The widely published ambition is that, by around the target in the initiative's name, retail scanners can accept a 2D code at checkout. Treat the exact scope and dates as something to confirm — the current specifications and milestones live with GS1, not in a blog post, and each retailer decides how fast it moves.

The word "sunrise" describes a coordinated readiness date rather than a hard switch-off. The transition is meant to be gradual: 2D codes and the linear UPC are expected to coexist for a stretch so that a product keeps scanning wherever a register can still only read the old symbol. In practice that means many packs will carry both for a while. This article is part of our broader guide to US packaging compliance, and it focuses on the one piece the standards documents tend to gloss over: making the code actually reproduce on a printed package.

Registration — how precisely the printed layers and the die line up on the finished package. It matters for a 2D code because a symbol placed near a fold, seal, or trimmed edge depends on tight registration to keep its quiet zone clear and its modules undistorted. See more terms in the packaging glossary.

Why brands care about one 2D code

Today a lot of packaging carries two codes: a UPC for the register and a separate marketing QR that a shopper can scan with a phone. A 2D code built to the GS1 framework promises to collapse those into a single symbol that does both jobs. That consolidation is the practical draw, and it opens a few doors that a striped UPC never could:

• One code, two audiences — the point-of-sale system reads the GTIN for checkout, and a phone opens a linked web experience from the same symbol.
• Consumer engagement — product provenance, how-to content, authenticity, promotions, and recycling instructions can live behind the scan.
• Traceability — 2D codes can carry batch or lot and expiry data, which supports recalls and freshness handling far better than a plain GTIN.
• Cleaner artwork — replacing two codes with one frees panel space and removes a competing visual element.

None of that value survives if the printed code won't scan — which is exactly where most of the real work sits, and where standards documents go quiet.

QR with GS1 Digital Link vs Data Matrix

Two 2D symbologies come up most in retail conversations. They are different tools, and the right one depends on the product, the space, and what your retailers accept — confirm the current guidance with GS1 before you commit.

Format	What it is	Where it tends to fit
QR Code (with GS1 Digital Link)	A square matrix code with high data capacity that consumers already recognize and phones scan natively.	Consumer-facing packaging where you want checkout plus a web link from the same symbol.
GS1 Data Matrix	A compact square matrix that stays robust at very small sizes and encodes structured GS1 data.	Space-constrained or regulated items — small packs, healthcare, and where a phone link is secondary.
Linear UPC / EAN	The traditional striped GTIN symbol that virtually every register reads today.	The incumbent — expect it to run in parallel during the transition.

GS1 Digital Link is the piece that makes the QR route interesting: it structures the data in the code as a web address that also contains the product's GTIN. One symbol, two behaviors — a scanner can pull the GTIN for checkout, and a shopper's phone can open the linked page. The important honesty here is that the encoding rules, the way the GTIN is expressed, and what point-of-sale systems will accept are all defined by GS1 and are still evolving. Get the code itself from the authoritative source; don't hand-build a URL and hope a register reads it.

The print-execution gap standards docs skip

A specification tells you what a valid code is. It rarely tells you how ordinary printing quietly destroys one. This is the gap we see most often — a code that verifies perfectly as a digital file and then fails on the finished package. The physics of ink on a substrate are unforgiving, and a 2D matrix is less tolerant of it than the striped UPC ever was.

• Quiet zone. Every 2D code needs a clear margin all the way around it. A clear border of several modules is commonly published as a minimum — verify the exact requirement with GS1 — and crowding it with artwork, a border, or a fold is one of the most frequent reasons a code stops scanning.
• Module size / X-dimension. The smallest cell in the matrix has to be large enough for both the press and the scanner to resolve. Shrinking a code to squeeze it onto a panel is the classic own-goal: below the process's reliable minimum, modules blur together. Confirm the minimum X-dimension for your symbology and print method with GS1.
• Contrast. Scanners need dark modules on a light background. Low-contrast color pairs, reversing the code (light on dark), or laying it over a busy image can all fall below what a reader can decode.
• Color and "brand" recoloring. Recoloring a code to match a palette, adding gradients, or dropping a logo into the center can push it out of spec. Any of that has to be validated, not assumed.
• Substrate and process. On flexible film, kraft, or an uncoated stock, ink spread — dot gain — can fill in the fine gaps between modules. Foil, metallic, and high-gloss varnish create reflections that blind a scanner. See packaging color management for how substrate and process shift what actually prints.
• Distortion. Stretching a code non-proportionally to fit a space warps the matrix geometry. Scale proportionally or not at all.
• Placement. A code crossing a seam, seal, fold, or a tight curve — or sitting inside the bleed or trim zone — reads unreliably. Keep it on a flat area with margin to spare; our notes on label dieline and bleed specs cover where content should and shouldn't sit relative to the cut.

Almost every one of these is a build decision made before the file goes to press, which is why we treat a barcode as production art rather than a graphic. The same discipline that keeps a linear UPC readable applies, only with less margin for error — the fundamentals are covered in barcode basics for packaging, and the file-level rules in our guide to a print-ready PDF for packaging.

A pre-print checklist for a 2D code that scans

Run this before the artwork goes to production. It won't tell you whether you need a 2D code — that is a GS1 and retailer question — but it will keep the one you place from failing on press.

1. Get the code from the right source. Use GS1 for the GTIN and the Digital Link structure; don't fabricate the encoded data.
2. Keep it vector, generated at final size. A vector symbol placed at print size holds its geometry; a low-resolution raster or an up-scaled image does not.
3. Hold the full quiet zone. Keep artwork, borders, and folds out of the clear margin around the code.
4. Preserve contrast; don't recolor. Dark modules on a light field. Skip gradients, tints, and center logos unless they've been validated.
5. Don't stretch or distort. Scale proportionally so the matrix stays square and even.
6. Mind the substrate. Allow for dot gain on film, kraft, and uncoated stock, and avoid placing the code over foil, metallic, or heavy varnish.
7. Place it flat and clear. Put it on a flat panel away from seams, seals, and tight curves, and outside the bleed and trim zones.
8. Test-scan the printed piece. Scan a real production sample with more than one phone and scanner before you commit to the run. A code that scans off a monitor is not proof it scans off the shelf.

How PackOS keeps your 2D codes print-ready

PackOS treats a barcode as a structural element of the file, not decoration. When you upload artwork, its preflight looks at whether the code is vector, whether it holds a clear quiet zone, whether its contrast and placement work against the reconstructed dieline, and whether it sits clear of seams, folds, and the trim — the same production checks a converter would run, applied in about a minute. You can see how that quality layer works on the technology page. The transition to 2D is coming on the industry's timeline; the part you control is making sure the code you print is the code that scans. Start with a real file and Quick Quote, and confirm the standard and your retailer's schedule with GS1.