Migration guide / dual-marking

Keep the UPC until the evidence says otherwise

For most Sunrise 2027 migrants, dual-marking is the prudent default: keep the linear barcode that already works, add a GS1 QR Code powered by GS1, and change pack strategy only after retailer readiness and scan evidence support it.

Open pilot checklist Read the full Sunrise hub

Dual-marking is usually the safest transition posture Do not remove a working UPC on assumption alone Use pilot evidence before widening scope

When dual-marking is the right default

Dual-marking is not indecision. It is an operational hedge while 2D acceptance, store readiness, and workflow maturity vary by retailer, lane, market, and packaging condition.

Checkout continuity

Preserve the scan path that already works

If a current linear barcode already performs reliably at POS, there is little upside in removing it before the new path is proven in the environments that matter.

Pilot discipline

Learn on a small SKU set before broad rollout

Dual-marking lets teams test 2D behavior without turning every packaging decision into a one-way bet.

Cross-functional safety

Reduce organizational disagreement later

Keeping both codes buys time for brand, packaging, IT, and operations to align around data, ownership, and launch controls.

Do this

Use dual-marking to buy evidence, not to avoid decisions

Keep the current checkout path intact while you validate the 2D path on real packaging.
Document which channels, scanners, and operating conditions have actually passed.
Assign owners for GTIN rules, destinations, and post-print changes before widening rollout.

Avoid this

Do not let strategy outrun checkout reality

Removing the UPC because the long-term direction feels obvious.
Treating a retailer announcement as proof that your exact pack and lane are ready.
Using dual-marking as a holding pattern while ownership and evidence stay unresolved.

When should you consider changing the pack strategy?

A change away from dual-marking should be evidence-based. The operative question is not whether 2D is strategically important. It is whether the operating environment is ready for that specific product and channel.

Question	Prudent default	What would justify a different decision
Is the retailer or channel 2D-ready?	Assume readiness is mixed.	Specific confirmation from the relevant channel, equipment, and process owners.
Has the code been validated on real packaging?	Keep both until real packaging tests pass.	Repeatable pass results on the actual substrate, finish, and pack size.
Are destinations and ownership stable?	Keep both while governance hardens.	Named owners, clear change rules, and a durable destination/resolver model.
Does the team need consumer engagement now?	Add the GS1 QR while retaining the UPC.	Only consider a one-code strategy after both consumer and POS use cases are well proven.

What to validate before pack approval

A credible dual-marking decision is less about opinion and more about collected evidence.

Evidence matrix

Final placement works with quiet zones and nearby artwork.
Print size is adequate for the payload and intended scan distance.
Relevant scanners and smartphones have been tested in the actual environments that matter.
Curved, glossy, reflective, or small-format packaging has been tested explicitly.
Human-readable identifiers remain usable when operators need them.

Go/no-go threshold

If any critical checkout path still depends on the linear barcode, keep dual-marking. A pack strategy change is only justified when the new 2D path is repeatably safe on the real pack, in the real channel, with the real owners in place.

GTIN and payload rules are documented.
Destination ownership and redirect policy are explicit.
The pilot has a named decision-maker and a clear rule for widening rollout.

Why tooling matters

Keep pack strategy, destinations, and evidence in the same workflow

pixie.codes keeps payload rules, destination ownership, and scan evidence tied together so dual-marking decisions are based on real rollout evidence instead of improvised handoffs.

Frequently asked dual-marking questions

Is dual-marking just a temporary compromise?

No. It is usually the most prudent transition strategy while POS readiness and operational maturity are still uneven.

Should every product keep both codes?

Not necessarily forever. But most programs should start there until product-specific evidence justifies a different pack decision.

What is the most common mistake?

Removing the linear barcode too early because the strategic direction feels obvious. Strategy is not the same thing as operational readiness.

Where should we go next?

If your next question is about styling safely, read the design and scannability guide. If your next question is execution, open the pilot checklist or generator.

Next step

Use dual-marking as the safe bridge, not the final answer.

Once the team accepts the transition posture, the next work is styling safely, testing rigorously, and running a disciplined pilot instead of changing pack strategy on intuition.

Read design + scannability guide See implementation tools