White-label is one word for three different things, and most buyers only need one of them. This post separates the parts, says which matter for agencies, resellers and platforms, and is plain about what AriaQR does and does not offer today.
The three parts of white-label
The code: does the printed code carry the vendor's logo, frame or mark? The redirect: when someone scans, does the address bar flash the vendor's domain before landing on yours? The dashboard: if your client logs in to see analytics, whose logo is on the page?
Agencies mostly care about the first and, for cautious clients, the second. Platforms embedding codes into their own product care about all three, or avoid the dashboard entirely by pulling analytics through an API into their own interface.
What the broad platforms generally offer
Uniqode, QR TIGER, Flowcode, Scanova and QRCodeChimp are generally known to offer white-label options on higher tiers: custom short domains, branded dashboards or client portals, and reseller programs. The codes themselves are styled grids. Check each site for current details, because the specifics sit behind sales conversations.
Where AriaQR stands, part by part
The code: unbranded. The code is the client's own artwork, verified before download, with no AriaQR mark, frame or footer. This is the part clients see on every pack and poster, and it is fully yours.
The redirect: ariaqr.com/r today. The short link is deliberately short so the code stays sparse and scans small. A custom short domain per enterprise account is on the roadmap; tell us on the business form if it is the deciding factor.
The dashboard: AriaQR-branded today. Most agencies never show it to a client; they pull the CSV or the numbers into their own report. Platforms use the API to read analytics into their own interface, which is white-label by construction. A branded client portal is on the enterprise roadmap.
Everything around it that resellers need does exist: teams to keep each client's work in its own workspace, bulk upload for a whole campaign at once, an API and an MCP server, invoices issued to your company, no restriction on reselling, and a one-line claim to hand a code to a client's own account when the engagement ends.
Side by side
| Broad platforms (higher tiers) | AriaQR | |
|---|---|---|
| Unbranded code | Generally yes, styled grid | Yes, the client's artwork is the code |
| Custom short domain | Generally yes | Roadmap |
| Branded client dashboard | Some | Roadmap; API-driven reporting today |
| Resell allowed | Check their terms | Yes |
| Client workspaces | Yes | Teams, every plan |
| Transfer codes to a client | Check their terms | Yes, one-line claim |
| Verified before download | Rarely advertised | Yes, every code |
| Pricing | Enterprise tiers, check their sites | Plan for agencies; custom terms for platforms (see pricing) |
Which part do you actually need?
If your client sees only the printed code and your report, AriaQR is white-label enough today: the code is theirs and the report is yours. If your product must own the redirect domain and the analytics screen, use the API to build the screen, and ask about the custom domain. If a fully branded portal is a hard requirement this quarter, a broad platform ships it today, with a styled-grid code and without verification.
The honest recommendation
Decide which of the three parts your client will ever see. For most agencies the answer is the code and the report, and AriaQR covers both with verification and the client's own artwork. For platforms, the API covers the dashboard and the custom domain is a conversation. The business page has the form.