Hub
Use this hub as the Sunrise 2027 migration map
Start here for the overview, then take the branch that matches the decision in front of your team. The goal is not to read everything. It is to move from broad understanding into the specific guidance that unblocks the next operational choice.
Pack strategy
Decide whether dual-marking is still the prudent default
Use the dual-marking guide when the live question is whether to keep the UPC, what evidence justifies that choice, and when not to remove the linear barcode.
Design + validation
Learn how to style safely without giving away scan margin
Use the design and scannability guide when the team needs practical rules for contrast, quiet zones, print conditions, and confirmation before packaging lock.
Software + governance
Use the software path when the question is operating control after print
When the real issue is resolver behavior, redirect ownership, analytics continuity, or destination governance, move from general guidance into the Digital Link software path.
Execution path
Move from guidance into the checklist, generator, or pilot workflow
When the next need is execution instead of education, use the implementation tools, pilot checklist, or the guided Sunrise 2027 pilot path.
Section 1
What teams need in place for Sunrise 2027
Teams do not need every system decision finished before they start. They do need a disciplined operating model: standards-aware code design, destination ownership, pilot evidence, and a way to keep packaging decisions and digital changes aligned over time.
Standards-aware code design
Build the 2D code around product identity, not just a destination URL
Use GTIN-centric structure and only the qualifiers the use case actually needs so the code stays durable as requirements expand.
Destination governance
Decide who owns post-print destination changes
Packaging can stay fixed while digital destinations evolve, but only if ownership, redirect policy, and auditability are explicit.
Pilot-safe rollout
Move from a narrow pilot to wider rollout deliberately
Start with a small SKU set, dual-mark, test hard, and widen only after operations, retailer readiness, and evidence support the next step.
Scan and evidence discipline
Keep test results and approval evidence attached to the same rollout
Teams should preserve scan results, warnings, conformance output, and reviewer decisions instead of relying on one-off screenshot proof.
Packaging-safe iteration
Make controlled digital changes without restarting packaging work
That matters when content changes, product data evolves, or rollout constraints shift after artwork is already locked.
Define the product identity
Start with GTIN and only the qualifiers the use case actually requires. Keep payload design tight from the beginning.
Generate the GS1 QR
Create a scannability-first QR variant that respects quiet zones, contrast, and packaging constraints before artwork lock.
Verify and route safely
Set destination policy, validate resolver behavior, and confirm the code performs on real packaging and scanner conditions.
Launch and learn
Scale only when pilot evidence supports it, then preserve continuity through governed changes instead of reprinting packaging.
| Category |
Under-governed rollout |
Disciplined Sunrise 2027 rollout |
| Payload model |
A QR chosen for convenience, often with limited product identity structure. |
Standards-aware GS1 QR creation aligned to product identity and future operating needs. |
| Post-print change control |
Destination changes happen ad hoc, with unclear ownership. |
Named owners, clearer routing policy, and safer packaging permanence. |
| Rollout evidence |
Limited to screenshots, assumptions, or campaign metrics. |
Operational evidence for pilots: verification, scan tests, governance, and readiness checks. |
| Packaging readiness |
Creative review is treated as enough. |
Scannability, testing, and launch controls are treated as gating decisions. |
Section 2
What is GS1 Sunrise 2027?
Sunrise 2027 is the industry target for widespread ability to scan and process 2D barcodes at point-of-sale and point-of-care. In practice, it means brand owners should be preparing for a world where one standards-based code can do more than a linear barcode while still protecting checkout behavior during transition.
It is
A transition to richer, standards-based product identification
GS1 QR Codes and Data Matrix symbols can carry a Digital Link URI that supports product data, consumer experiences, batch and serial context, and future regulatory use cases.
It is not
A signal to rip out every UPC immediately
Retailer readiness is uneven. For most brands, the prudent operating model is dual-marking until specific partners and lanes are actually ready for 2D at POS.
Why now
Packaging cycles and system work take longer than teams expect
Artwork changes, data cleanup, resolver policy, retailer coordination, and scan validation all take time. Waiting compresses the riskiest work into the shortest window.
Practical interpretation
If your team asks what to do this quarter, the answer is not to replace every code. The answer is to pilot the right format, keep checkout safe, and establish governance so future packaging changes do not require a second redesign.
Section 3
Who needs to act now
Sunrise 2027 is cross-functional. If one owner carries the whole effort, the rollout usually fails late: at packaging lock, retailer onboarding, or QA.
Brand and product teams
Own the destination and the customer promise
- Define whether the code is for POS, engagement, regulated data, or all three.
- Keep destination content durable enough to survive packaging lead times.
- Plan consumer-facing pages that load fast and match product context.
Packaging and creative
Balance brand expression with scan confirmation
- Hold quiet zones, contrast, substrate, and final print conditions as hard constraints.
- Style deliberately, then validate that the final treatment still performs on real devices and print conditions.
- Lock a repeatable review checklist before art approval.
IT and data owners
Control identifiers, destinations, and redirects
- Govern GTIN quality, optional qualifiers, and change management.
- Decide whether redirects are direct, managed, or organization-governed.
- Prevent orphaned links, duplicated identifiers, and unowned landing pages.
Retail and operations
Validate the environments that actually matter
- Test actual scanners, lanes, glare conditions, and packaging finishes.
- Coordinate retailer-specific expectations before removing the linear code.
- Define go/no-go rules based on scan performance, not optimism.
Section 4
What should go on pack for Sunrise 2027?
The best on-pack strategy is usually boring in the right places: standards-compliant identification, predictable placement, and enough redundancy to keep checkout moving while you learn.
| Decision |
Most prudent default |
Why it matters |
| Linear barcode during transition |
Keep it on pack until partner readiness is confirmed. |
Dual-marking is the safest path while 2D acceptance varies by retailer, lane, and equipment stack. |
| 2D format choice |
Use a GS1 QR Code powered by GS1 when you need consumer engagement plus standards-based product identity. |
It is easier to align marketing, product data, and future link management under one standards-aware code. |
| Human-readable text |
Keep key product identifiers readable outside the code. |
Operational teams still need backup paths when devices, lighting, or print quality are imperfect. |
| Destination ownership |
Use a governed resolver or direct destination policy with named owners. |
Packaging lasts longer than campaign pages. Ownership gaps become broken scans in market. |
Minimum viable pack spec
- One standards-based GS1 QR with approved payload and resolver policy.
- Linear barcode retained during transition where POS certainty matters.
- Artwork review that treats print conditions and placement as functional requirements.
- Landing destination that matches the packaging promise and does not require a second scan.
Common mistakes
-
Removing the UPC too early
Retail readiness is not uniform, and assumptions here create avoidable checkout failures.
-
Pointing the code at a campaign page with no governance
The page changes, disappears, or underperforms while the packaging stays on shelf.
-
Letting art direction outrank scan physics
Stylized modules, gradients, low contrast, and crowded placement hurt actual performance.
Section 5
How GS1 QR Codes powered by GS1 work
The operational value is not just that a QR code can open a page. It is that a standards-based URI can carry product identity cleanly, support richer experiences, and stay governable as destinations evolve.
Identify the product
Start with the GTIN and add only the qualifiers you actually need, such as batch, lot, serial, or date data. Keep payload design disciplined.
Encode a Digital Link URI
The QR code should resolve from a standards-aware URI pattern, not an ad hoc shortener that obscures product meaning and governance.
Route with control
Use a resolver strategy that lets you update destinations, preserve analytics, and separate packaging permanence from page-level experimentation.
Deliver the right outcome
For consumers that might be product data or engagement. For operations it might be traceability, regulated data, or future scanning workflows.
What your tooling needs to handle
However you implement the program, your toolchain needs to support standards-aware QR generation, destination governance, and controlled rollout changes without breaking the relationship between packaging, routing, and scan evidence.
Section 6
How to keep GS1 QR Codes POS-safe and scan-safe
Most failed QR rollouts are not caused by the standard. They are caused by layout compromises, poor contrast, bad printing conditions, or insufficient testing under real-world conditions.
Do this
Hold the non-negotiables
- Maintain strong contrast and clear quiet zones.
- Test final printed packaging, not only screen mockups.
- Validate at likely scan distances and angles.
- Check glossy, curved, reflective, and small-format packages separately.
Avoid this
Do not assume style equals readiness
- Softened modules and color effects without empirical scan margin.
- Embedding the code inside busy imagery or low-contrast substrates.
- Passing design review without actual device and scanner validation.
- Changing payload size late without revisiting size and error correction.
Scan test matrix
- Consumer smartphones across iOS and Android.
- Retail or warehouse scanning equipment where relevant.
- Low light, glare, motion, and shelf-distance scenarios.
- Multiple print batches and substrate variations.
Go/no-go threshold
If the code only works under ideal conditions, it is not ready for production packaging. Treat scan reliability like any other launch-critical KPI.
Section 7
A phased rollout plan for Sunrise 2027
The safest Sunrise 2027 program is phased. Brands that skip phases usually rediscover them later under more pressure.
Phase 1
Align the program
- Name functional owners across packaging, data, brand, and operations.
- Define success metrics: scan rate, redirect governance, packaging readiness, retailer sign-off.
- Pick the SKU set that is worth learning on but safe to pilot.
Phase 2
Build the data foundation
- Clean GTIN records and define payload rules.
- Choose resolver ownership, redirect policy, and analytics conventions.
- Confirm the landing experience and fallback behavior.
Phase 3
Dual-mark and test
- Print the GS1 QR alongside the incumbent linear code.
- Run scan tests on real packaging and representative equipment.
- Fix quiet zone, size, contrast, and destination defects before scale.
Phase 4
Scale with evidence
- Expand only after scan performance and retailer readiness are validated.
- Instrument analytics so packaging decisions can be revisited with real data.
- Document the operating standard so future SKUs follow the same rules.
Execution handoff
Once the team is aligned on payload, ownership, testing, and rollout phases, move into the execution path that matches your stage: checklist-led preparation, hands-on QR generation, or a guided pilot program.
Section 8
Sources and standards
Sunrise 2027 is standards-driven. These public references anchor the guidance on this page.
GS1 US
Sunrise 2027 overview
GS1
Digital Link standard
- GS1 Digital LinkStandards background for identity, structure, and broader ecosystem use.
Retail implementation
POS transition guidance
Reference model
Resolver and syntax references
Reviewed and synthesized by pixie.codes for practical rollout guidance. For definitive standard language, use the official GS1 references above.
Section 9
Frequently asked Sunrise 2027 questions
Do we need to replace our UPC barcode now?
Usually no. The prudent default is dual-marking until your relevant retailers, lanes, and equipment are confirmed ready for 2D at POS. Removing the linear barcode too early creates avoidable operational risk.
What is the difference between a normal QR code and a GS1 QR Code powered by GS1?
A normal QR code can point anywhere. A GS1 QR Code powered by GS1 encodes a standards-based Digital Link URI that preserves product identity more cleanly and is better suited to governed, scalable product experiences.
Do we need a resolver?
If you want durable governance, redirects, analytics continuity, and the ability to change destinations after packaging is printed, a resolver strategy is usually the right answer. Direct destinations are simpler, but they are less forgiving operationally.
What belongs in a GS1 rollout tool versus PIM or DAM?
A rollout tool should handle QR generation, resolver or destination control, scan evidence, and governed iteration close to packaging execution. Core master-data systems still matter; PIM, DAM, and ERP remain the system of record for broader product content and asset management.
How should we start if we are late?
Pick a limited SKU set, keep dual-marking, define ownership clearly, and test hard. A disciplined pilot is safer than a broad, under-governed rollout. If you are past planning and need structured execution support, use the pilot resources next.
Where should we go next?
If you need software detail, go to the Digital Link software page. If you need an implementation view, go to the GS1 QR generator page. If you need a rollout path, go to the Sunrise 2027 pilot page.
pixie.codes