It separates evidence dimensions
GS1 production candidates keep digital, physical, POS, and resolver observations separate, so a visual mockup or software screen is not confused with a print-approved asset.
pixie.codes
Sample / Pilot Evidence Packet
What a GS1 QR pilot evidence packet should show.
A credible GS1 QR pilot should preserve the asset, resolver, verification, scanner-risk, analytics, and decision evidence a packaging team needs before print planning continues.
Sample report state · six independent dimensions
Example evidence state before a limited physical/POS pilot
This sample uses the verifier’s real status vocabulary. It illustrates a report shape, not a result for your product and not GS1 certification, production approval, or a universal-scanning claim.
-
data_conformance
Data conformance
Status: Data-conformant
Evidence: The sample canonical Digital Link passed the recorded data-oracle source set.
Provenance/time: Source-set identity and observation time are report fields.
Next: Re-run if GTIN, qualifiers, or canonical payload changes.
-
qr_correctness
QR correctness
Status: QR-correct
Evidence: Exact encoder-declared bytes and structural observations match the bound subject grid.
Provenance/time: Encoder contract, grid hash, oracle versions, and observation time travel together.
Next: Invalidate after any exact-payload or module-grid change.
-
predictive_screen
Predictive screen
Status: Pass—predictive screen
Evidence: The bound digital candidate passed the stated synthetic screen and thresholds.
Provenance/time: Model, thresholds, render inputs, seed, and run time are recorded.
Next: Treat this only as a digital screen; gather matching physical evidence.
-
physical_print_quality
Physical print quality
Status: Indeterminate—physical verification required
Evidence need: A bound specimen from the intended printer, ink, substrate, size, and finish.
Provenance/time: No matching physical observation is present in this sample state.
Next: Produce and measure the controlled pilot specimen.
-
pos_performance
POS performance
Status: Indeterminate—missing evidence
Evidence need: Results from the named target devices, firmware, configuration, and acceptance contract.
Provenance/time: No compatible target-POS run is attached.
Next: Execute the agreed checkout protocol on the same specimen.
-
resolver_behavior
Resolver behavior
Status: Resolver behavior verified
Evidence: The sample’s default route and linkset behavior were observed for the stated request scope.
Provenance/time: Request, response, configuration identity, observation time, and expiry are required.
Next: Re-probe after configuration change or when the observation expires.
No aggregate PASS: digital conformance, QR correctness, predictive screening, physical print quality, POS performance, and resolver behavior answer different questions and remain independent.
Sample report summary
Pilot account
Example natural foods brand, first retail packaging refresh for Sunrise 2027 planning.
GTIN scope
5 pilot GTINs under a shared-domain resolver path, with one DEFAULT product-information destination per resource.
QR asset policy
Conservative dark-on-light baseline; no logo overlay; no pixel inversion; module-level styling limited to digitally screened variants.
Dimensioned evidence
The packet records data conformance, QR correctness, predictive screen, physical print quality, POS performance, and resolver behavior independently. Missing physical or POS observations remain indeterminate; there is no aggregate pass.
Resolver result
Default link configured; time-stamped route and linkset observations recorded for the tested resolver scope. These observations do not establish QR print quality or POS performance.
Owner decision
Proceed only to a limited physical/POS evidence pilot. Do not authorize packaging rollout or expand beyond 5 GTINs until the named physical and target-device acceptance criteria are met.
Evidence checklist
- Asset identity: release candidate name, canonical GS1 Digital Link URL, QR variant, and print profile.
- Scanner-risk controls: quiet zone, contrast, dark/light module policy, 660 nm risk review, and no unmanaged logo overlay.
- Resolver controls: domain, resource, DEFAULT link, linkset validation, routing simulation, and owner.
- Decision record: six independent statuses, remediation notes, exact candidate, owner, and conditions for scale.
Why this matters before print lock
It treats shortcuts as risk
The packet makes logo overlays, inversion, and weak color choices explicit scanner-risk topics instead of burying them in visual preference.
It keeps evidence portable
Packaging teams can share the same evidence with brand, printer, operations, and standards-aware stakeholders.
It narrows the decision
Stakeholders review one controlled release candidate and its evidence instead of reopening the whole design process.
Continue the evidence plan
Playbook
Agency rollout playbook
Coordinate candidate identity, evidence owners, and bounded handoffs across a rollout.
Workflow
Resolver analytics workflow
Review observed resolver activity without turning analytics into print or POS proof.
Guide
GS1 Sunrise 2027 guide
Map the standards transition to a scoped pilot and explicit owner decisions.
Guide
Dual-marking planning guide
Plan coexistence without assuming that a digital candidate is physically or operationally ready.
Guide
QR design and scannability
Use risk-aware design guidance while preserving separate physical and target-device evidence needs.
Use this evidence shape before print planning.
A scoped pilot is strongest when stakeholders can see the exact candidate, resolver observations, six dimension statuses, and remaining owner-controlled release conditions together.