When a consumer scans a QR code on a product, two URLs are involved in the experience:
This page explains how these two URLs relate and why this architecture is used.
The URL encoded in a QR code, NFC tag, or RFID payload follows the GS1 Digital Link standard:
This URL identifies the product using internationally recognised identifiers:
/01/<GTIN> — Global Trade Item Number/10/<lot> — Batch or lot number (optional)/21/<serial> — Serial number (optional)The scan URL is the standards-compatible entry point. It ensures interoperability with GS1 systems and regulatory frameworks such as the EU Digital Product Passport.
When the scan URL is accessed:
This redirect is transparent — the consumer sees the passport page load directly.
The rendered passport page uses a canonical application path:
This is the page where the consumer views the full Digital Product Passport, including product details, sustainability data, and provenance information.
The passport page URL is the rendering destination, not the identifier. The QR code always encodes the GS1-compatible resolver path, not the passport page path.
tieback supports both platform subdomains and custom hostnames for the full scan-to-passport flow:
Every brand receives a subdomain automatically:
Brands can configure a custom hostname for a branded experience:
Custom hostnames require a DNS CNAME to the brand’s platform subdomain. See the DNS Setup Guide for instructions.
The QR code encodes a GS1-compatible resolver URL that follows international identification standards. The resolver validates the identifier and redirects to the passport page. This ensures the QR code remains standards-compliant while the passport page can be optimised for presentation.
Yes. GS1 Digital Link compatibility is defined by the scan URL — the URL encoded in the QR code. That URL follows the GS1 Digital Link URI standard. The destination page after redirect is outside the scope of the specification.
Yes. tieback supports custom hostnames such as passport.brand.com. Once the DNS CNAME is configured and the hostname is verified, the custom domain serves the full resolver and passport flow.
The platform subdomain (brand.tieback.io) remains available at all times. You can use it while your custom hostname is being verified.
No. The redirect is a single HTTP 302 response, typically completed in under 100ms. The passport page loads immediately after.