White label qr scan host, defined
SmartQRCode editorial · Updated October 2026
A white label qr scan host is a hostname the customer owns that answers scan requests instead of smart-qrcode.com. The phone's padlock names that host. Scanner-facing pages on it carry no product header. Encode the host before you plate. A Canva static file still wins when you will never edit or count.
What a white label qr scan host changes
A customer hostname for scans is what the host gate allowlist protects. The certificate in the padlock names it. A platform URL still in ink will keep showing smart-qrcode.com until you reprint.
The printed pattern stores a URL. On the default path that URL uses the product apex. A white label qr scan host swaps the host in that URL at create time, so every later 302 or landing page is requested on a name the customer controls. That is the difference guests can see without opening our site.
The host gate is strict. On a customer hostname the app serves scan routes and 404s the rest. /pricing, /create, and the account area are not a storefront you want on qr.brand.com. Attaching a hostname to the project would otherwise serve the whole application there. The gate exists so a shopper scanning a shelf tag never lands in an admin login.
SSL is part of the same object. Browsers warn on a host that is not yet verified. Print after the host is active, not while DNS is still drifting. The sibling on custom scan domain and SSL walks those statuses. Creation that falls back to the platform host after a lookup failure would silently encode the wrong name into pixels. Refusing is the safer miss.
Tracked QR codes and a website URL generator are the usual pair on a retail shelf: a hosted link you can retarget, counted per facing. Dynamic QR codes are the same class when the brief is "change the destination without reprinting." For shelf-edge work see retail marketing codes.
White-label scanning on a customer host does not require a second switch. The request arriving there is already unbranded. The entitlement path matters when codes still resolve on smart-qrcode.com. Read white label qr codes for that split.
Does a custom hostname replace branding by itself
For pages served on that host, yes. Expired, paused, and deleted screens on qr.example.com are the customer's pages. The landing-page title does not append our product name. Shared link previews omit our Open Graph site name.
For ink that already encodes smart-qrcode.com, no. Modules do not update when DNS does. A reprint is the only way to change the host inside the symbol. That is why create-time resolution of the base URL is a permanence rule, not a display preference.
Agencies: one white label qr scan host per client, not one host with a path prefix you hope nobody notices. Certificates do not do path prefixes. The agency QR white label host note is the same rule written for retainers.
A hosted code still depends on the provider continuing to resolve it. Moving the host does not remove that dependency. It only changes which name the phone shows while the provider is up.
What white label does not rebrand
Account chrome stays ours. The person who pays sees invoices, mail, and the signed-in product with SmartQRCode marks. That is deliberate. White label is for scanners, not for the operator.
The redirect path returns a 302 and an empty body. There is no footer to hide. Do not promise a branded interstitial on a pure redirect; the hop is meant to be fast and cache-safe. A 301 would freeze destinations in some clients.
Landing-page templates do not inject a powered-by badge. If the brief was "remove the badge," there was never one. What you can still leak is the platform hostname in the encoded URL, or our trial button on a branded status page when the code is still on smart-qrcode.com without white-label scanning.
Paid hosted work uses $1.99, $29, $97, or $197. We do not sell an unpaid tier.
Skip the host when a static file is enough
A Canva one-off, a Google chart-style maker, or the in-phone generators are enough when the destination is frozen and you do not need country or device counts. A church bake-sale poster that always opens the same form does not need a white label qr scan host.
The host is extra moving parts: DNS, certificates, a gate, and a provider that must stay up. If none of those buy you an edit or a count, skip them. Print a static file at 2 cm or larger, keep the quiet zone, and stop.
If the carton will outlive a campaign URL, you still want a hosted type on some host. Whether that host is ours or theirs is a brand question, not a scanning question. ISO/IEC 18004 does not care which name is in the URL. Shoppers do.
Questions this raises
Yes for scanner-facing pages served on that host. A request that arrives on the customer hostname is already theirs. Codes still encoded with the platform URL keep showing smart-qrcode.com in the modules until you reprint.
The dashboard, emails, and invoices stay ours. The 302 hop has no HTML. The landing-page body never had a powered-by badge. White label is the scanner, not the account holder.
Skip it when a Canva one-off or other free static generator will do: the payload will never move and you will not count scans. A host is a hosted dependency.
They should not. The certificate names the host. A scanner who sees the wrong company in the padlock has been sent to the wrong tenant. Give each brand its own hostname.
Keep going
The tools and playbooks this post refers to, one click away.
Make the code this post is about
$1.99 for 7 days, then a paid plan. Pick a type, brand it, and edit the destination whenever you like, even after it is printed.