White label qr codes without our brand
SmartQRCode editorial · Updated October 2026
White label qr codes hide the provider name from the person holding the phone. The printed modules still encode a hosted URL. The scanner-facing expired, paused, and deleted screens drop our header, footer, and trial button. A Canva static file is the honest one-off when you will never edit or count.
What white label qr codes actually hide
Those scanner-facing status pages are the expired paused deleted screens. The open graph site name is omitted. The hosted scan URL in the modules is a separate fact from that chrome.
White label qr codes are a scanner-facing change, not a reseller programme and not a logo on the account area. Two separate facts produce an unbranded scan. If the request arrives on the customer's own host, the page is already theirs, whatever the account holds. If the code still resolves on smart-qrcode.com, white-label scanning is the concept that strips our name from the surfaces a stranger sees after they point a camera at the ink.
The inventory is short on purpose. The expired, paused, and deleted screens lose the header, the footer, and the trial button. The landing-page title drops the product suffix. The Open Graph site name is omitted so a shared preview card does not advertise us. Redirect hops through a 302 and return no markup, so there is nothing to rebrand on that path. The landing-page body never carried a powered-by badge in the first place.
Paid options exist as $1.99, $29, $97, and $197. We do not sell an unpaid tier. A hosted scan URL is the trade for editing after print. The pattern you plate is still ISO/IEC 18004. Colour, logo, and frame are design settings. They do not decide whose name sits on a failed status page.
Use a website URL generator when the destination is a link you may move. Pair it with tracked QR codes if each placement needs its own count. A custom landing page is the block-based type when the scanner should stay on a page you author.
How to print a white-labelled scan surface
Decide the host before you send files. The encoded URL is written into pixels at create time. Changing the hostname later does not rewrite a carton that already shipped.
- Choose a redirect or landing-page type. Wi-Fi is the only static type here; it is not editable after printing and not trackable, so white label qr codes do not apply to it.
- Set the destination you will actually open on a phone, not a staging URL you plan to swap in the press room.
- If the brief needs the scanner to stay on a customer hostname, attach that host and wait until it is the live scan URL before you export. See custom scan domain for QR.
- Export SVG for vinyl or cutter work, and a 300 dpi PNG or PDF at the final millimetre size for toner. Do not screenshot the on-screen preview; that preview encodes /qr-preview, not the live payload.
- Keep a quiet zone of four empty modules on every side. Start the symbol at 2 cm across for a phone at about 30 cm.
- Print a first-surface proof on the real stock. Scan it with a phone that has never opened that destination.
- Confirm the failure path on purpose: pause the code, scan again, and read the status screen. The notice should be plain, without our trial button.
- Release the pause before the run ships. Pause is a separate state from archive; archived codes keep scanning.
For a launch pack that will be counted per channel, the product launch placements brief is the usual shape: one hosted code per printed object, not one static file reused on every SKU.
Does the scanner still see smart-qrcode.com
The phone reads modules. Those modules contain a URL. If you created the code on the platform host, that URL can still say smart-qrcode.com even when the status screens are unbranded. White-label scanning removes our name from pages. It does not rewrite ink.
A white label qr scan host is the other half of the same idea: the request itself lands on a hostname the customer owns. That is F80 and F84 together. The host gate then serves only scan routes on that name. Marketing pages and the account area 404 there, which is the point. You do not want a shopper on qr.example.com to walk into /pricing.
Agencies that print for several brands should not share one scan host. The certificate in the phone's padlock is the client's. Mixing tenants on one hostname is how a scanner sees the wrong company. The sibling on agency QR white label host covers that split.
Country and device still come from request headers when the type is hosted. Analytics cannot see a name, email, or GPS trace. White label qr codes do not add identity. They only change chrome.
What happens on paused and expired pages
Those three screens are why the feature exists. A code that has already failed is the moment a stranger is staring at a phone and a poster. The branded version used to put our trial button on their broken object. White label qr codes turn that into a plain notice: no header, no footer, no call to action.
Pause is something you set when a campaign should stop resolving without deleting the row. Archive is different: archived codes keep scanning. If you pause for a press check and forget to release it, the status page is what every scanner sees, branded or not. Test that path on the proof, not after 10,000 cartons leave the plant.
Expired and deleted screens follow the same rule. They are scanner-facing. Emails and invoices are not. Do not expect the PDF you send accounting to lose our marks.
A 301 on the live hop would cache the destination in browsers and freeze later edits. This product uses 302 so a destination change after print can still reach the next scan. White label qr codes do not change that hop. They change the HTML around the hop when HTML exists.
Failures that put our name back in view
Printing before the custom host is live leaves the platform URL in the modules. The status pages can be unbranded and the padlock still names us. That is not a renderer bug. That is create-time encoding.
Sending a screenshot of the wizard is the other classic miss. The preview payload is /qr-preview. Guests who scan the plate open a preview, not the campaign. Export PNG, JPG, SVG, or PDF from the paid file, at the size it will appear.
Covering a finder pattern with a logo larger than error correction can restore will fail the scan before branding matters. The three nested squares locate the symbol. If the camera never finds them, nobody sees a status page.
A provider shutdown, an unpaid invoice, or a pause stops a physically perfect print. That is the hosted trade. A static Canva file has no such dependency and no edit after ink.
Dark grounds without a true invert leave the finders unread. The failure then looks like "the code is broken" rather than "the brand leaked." Fix contrast before you argue about the host.
When Canva is the honest print job
A free static generator such as Canva, a Google demo tool, or the iOS camera-adjacent makers is the right job when the payload will never change and you do not need a count. A table tent that always opens the same PDF, a one-night poster, a personal Wi-Fi card for a guest suite: those do not need white label qr codes.
Using a hosted surface for a throwaway flyer pays for a redirect you will never edit. Using a static file for a menu you reprice weekly pays for reprints. State the trade and pick. We do not sell an unpaid tier; paid hosted work is $1.99, $29, $97, or $197.
If the brief is "the phone must never show another company's name," you still have to encode the right host in the modules. Chrome on a status page cannot unsay a URL that is already in ink.
Questions this raises
On a customer hostname the request is already theirs. On the platform host, white-label scanning strips our name and trial button from the expired, paused, and deleted screens, and from the landing-page title and Open Graph site name. The printed modules can still encode a smart-qrcode.com URL.
Those three screens are the ones that used to carry our header, footer, and a trial button in front of someone who just failed to open the destination. White label qr codes exist to make those failure pages a plain notice.
A Canva one-off or another free static generator is the right tool when the payload will never move and you will never count scans. White label qr codes only matter on a hosted surface the provider still resolves.
No. Emails, invoices, and the account area stay ours. The landing-page body already has no powered-by badge. The 302 redirect path has no markup to strip.
Yes for redirect and landing-page types, because the ink encodes a hosted URL, not the final page. A Wi-Fi code cannot be edited after printing and is not trackable. Any hosted code lasts only as long as the provider resolves it.
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.