Back to Help Center
teams
Documentation

White-Label QR Pages Explained: What It Means and How It Differs From Custom Domains

Understand exactly what white-label means in QR Code Pro, what branding control it gives you, and how it differs from domain branding.

White-Label QR Pages: Simple Definition

White-label means your QR experience looks and feels like your brand, not a generic platform experience.

In practice, that usually means control over visible brand elements on the QR landing experience, while the platform still powers the backend infrastructure and analytics.

Custom Domain vs White-Label: Not the Same Thing

These are related but different:

  • Custom domain: controls the URL people see (example: go.yourbrand.co.za).
  • White-label pages: controls the visual brand presentation of the landing experience.

Best outcome is using both together: branded URL + branded page experience.

What White-Label Helps You Achieve

  1. Higher trust at scan-time because users see consistent branding.
  2. Better campaign continuity from print asset to landing experience.
  3. Cleaner client delivery for agencies managing multiple branded campaigns.

Plan Notes

Custom domains are included from Pro+ upward. White-label page branding controls remain Team-tier workflows.

How to Use White-Label Features Effectively

  1. Align QR artwork with landing brand colors and tone.
  2. Use a custom domain so URL trust matches page trust.
  3. Keep CTA wording consistent between poster/package and destination.
  4. Validate on both Android and iOS before print deployment.

Common Misunderstandings

MisunderstandingReality
"Custom domain alone is full white-label"URL branding and page branding are separate controls
"White-label removes analytics"Analytics tracking remains active
"Pro plan includes Team branding behavior"Pro+ and above include custom domains; Team-tier is still required for full white-label workflows

Verification Checklist

  1. Scan your code and inspect visible brand consistency.
  2. Confirm URL domain is your custom domain where configured.
  3. Confirm scans still appear in analytics.
  4. Test fallback behavior if destination page changes.

Related Actions

  • Configure branded URL: custom-domains-complete-guide.
  • Compare plans clearly: team-vs-pro-plan-capabilities.
  • Track post-scan outcomes: tracking-your-scans.

Was this article helpful?

Your feedback helps us improve our documentation.

24/7 Support Available

Still have questions?

Our support team is available 24/7 to assist with technical integrations, billing, or design questions.