Product Website Domain

Your DPP Site Builder creates product landing pages that consumers see when scanning QR codes (via the gs1:pip redirect). By default these are hosted on Netlify at a TrackVision subdomain, but you can use your own domain — e.g., products.mybrand.com.

How It Works

Consumer scans QR code
        │
        ▼
https://dpp.mybrand.com/01/{gtin}     ← Resolver (custom resolver domain)
        │
        │  gs1:pip → 302 redirect
        ▼
https://products.mybrand.com/{id}      ← Product website (this domain)

The resolver redirects consumers to your product website. The website domain is where your DPP landing pages live — product info, sustainability data, certifications, and supply chain transparency.

Step 1: Get Your Netlify Site Address

Your product website is deployed to Netlify and managed by TrackVision. The default address is shown in the TrackVision platform under Web Sites → your site → Settings.

It follows the format:

{site-name}.netlify.app

For example: acme-dpp.netlify.app

Step 2: Add a DNS Record

In your DNS provider's control panel, add a CNAME record pointing to your Netlify site:

Type	Name	Value	TTL
CNAME	products	acme-dpp.netlify.app	3600

This makes products.mybrand.com point to your Netlify-hosted product website.

Root domains

For root domains (e.g., mybrand.com without a subdomain), use an ALIAS or ANAME record instead of CNAME. Check your DNS provider's documentation — not all providers support this.

Step 3: Let TrackVision Know

Once you've added the CNAME record, contact TrackVision support with:

1. Your custom domain — e.g., products.mybrand.com
2. Your site name — shown in the platform under Web Sites

We'll add the custom domain to your Netlify deployment and Netlify will automatically provision a free TLS certificate. You don't need access to Netlify yourself — we handle the configuration on our end.

SSL is automatic

Netlify provisions and renews TLS certificates automatically once the CNAME is verified. Your site will be accessible via HTTPS with no additional setup on your part.

Step 4: Update the Resolver Redirect

In the TrackVision platform, update the redirect URL so QR code scans land on your custom domain instead of the Netlify default:

1. Go to Settings → Reference URLs
2. Set Redirect Base URL to https://products.mybrand.com
3. Click Save

Now when consumers scan a QR code, the resolver redirects to https://products.mybrand.com/{product-id}.

Step 5: Verify

Wait for DNS propagation (typically a few minutes to a few hours), then test:

# Check DNS resolves
dig products.mybrand.com CNAME
# Should show CNAME pointing to acme-dpp.netlify.app

# Check the site loads
curl -I https://products.mybrand.com
# Should return HTTP 200

# Test the full QR scan flow
curl -I https://dpp.mybrand.com/01/09506000134352
# Should return HTTP 302 with Location: https://products.mybrand.com/{product-id}

Common Domain Choices

Domain	Notes
products.mybrand.com	Clear purpose
dpp.mybrand.com	If not using a separate resolver domain
sustainability.mybrand.com	Consumer-friendly

Summary: Two Custom Domains

You'll typically have two custom domains:

Domain	Purpose	CNAME target	Managed by
dpp.mybrand.com	QR code resolver (GS1 Digital Links)	{account}.tvai.me	You add CNAME, we configure
products.mybrand.com	Product landing pages	{site}.netlify.app	You add CNAME, we configure

The resolver domain is what's printed on products (in QR codes). The website domain is where consumers land after scanning. See QR Code Resolver Domain for resolver setup.

Both require the same process from your side: add a CNAME record in your DNS, then let TrackVision know so we can configure SSL and routing.