GS1 Pilot Checklist

Shared domain pilot fastest

Best when you want a working pilot today with minimal operational overhead.

Sign in and pick an organization Open /resolver, select your org, and confirm you can see the shared domain.

Create a GS1 identifier resource (GTIN + optional qualifiers) Add a default destination link and (optionally) typed links for richer experiences.

Create a GS1 QR asset and export print artifacts Open /create, generate the GS1 Digital Link URL, style conservatively, then export.

Verify scan reliability and resolver behavior Run verification, simulate resolution, and confirm the default redirect + linkset look correct.

Collect pilot evidence for stakeholders Export the verification report and keep a canonical list of test GTINs + outcomes.

Best when your program requires a brand-owned hostname (for governance, trust, and analytics invariants).

Add your resolver domain Example: id.brand.com (hostname only, no scheme/path).

Verify ownership (TXT record) Create the required TXT record and re-run verification until it passes.

Verify routing to pixie.codes (CNAME/A) Point the hostname to the expected target and confirm /.well-known/gs1resolver is reachable.

Bulk import identifiers + links Run CSV dry-run first, then import. Re-running the same file should be safe.

Run conformance and archive evidence Save conformance output, verification reports, and export artifacts for launch review.