What does white-label actually mean when you buy source code?
White-label means the licence allows you to remove the original vendor’s name and sell the software under your own brand, as if you had built it. It is a legal permission first and a feature second: a product can be technically easy to rebrand and still forbid it, or permit it and leave the vendor’s name in twenty places you have to find. Get the permission in writing on the invoice, then check the six places branding actually hides.
Written by ZoopCoder, who build and sell SaaS source code. That makes us an interested party in this answer, so we have kept it to things you can verify yourself.
The numbers
A licence term
Not a feature
Technically removable branding proves nothing about your right to remove it.
6 places
Where branding hides
Beyond the logo: emails, PDFs, meta tags, admin footer, error pages, source comments.
On the invoice
Where to get it in writing
Not in a chat message or a comment thread.
White-label, private-label, rebrandable and resale: which is which
These four terms are used interchangeably by sellers and mean different things in a contract. Ask which one you are being sold and get the answer written down.
| Term | What it normally grants | What it does not |
|---|---|---|
| Rebrandable | The technical ability to change the logo, colours and product name | Any legal right to do so, or to sell the result |
| White-label | The right to present the software as your own product to your customers | The right to sell the source code itself to other developers |
| Private-label | Usually a synonym for white-label; occasionally implies exclusivity in a territory or vertical | Exclusivity, unless the word “exclusive” appears |
| Resale / SaaS rights | The right to charge end users for access to a running instance | Automatically included in a standard marketplace licence — it is normally excluded |
The combination most buyers actually need is white-label and SaaS rights: your brand on the front, and permission to charge people to use it. Those are two separate grants, and a seller can give you one without the other.
The six places branding hides after you change the logo
Rebranding stops at the header for most buyers. Auditors, customers and Google all find the rest. Work down this list before launch.
- 1. Transactional email templates. Welcome, password reset, invoice and receipt mail is generated server-side and frequently keeps the original footer and sender name. Trigger every one of them and read it.
- 2. Generated PDFs. Invoices, reports and shipping labels often use a separate template with its own logo path and its own footer text.
- 3. Page titles, meta descriptions and Open Graph tags. Invisible on screen, visible in search results and every time someone shares a link.
- 4. The admin footer and the “powered by” line. Sometimes deliberately hard to remove, which is itself a licence signal — ask whether removing it is permitted, not just possible.
- 5. Error and maintenance pages. The 404, the 500 and the maintenance screen are rendered outside the theme on many stacks and keep the original branding.
- 6. The manifest, favicon and mobile app names. Progressive web apps carry a name and icon in the manifest; a mobile build carries them in the store listing and the launcher.
What to get in writing
One paragraph on the invoice settles almost every dispute in this area. Ask for wording that names all four permissions explicitly:
- That you may remove and replace all vendor branding in the interface, emails, documents and metadata.
- That you may present the software as your own product to your customers, without disclosing its origin.
- That you may operate it as a service and charge end users for access — the permission a standard marketplace licence withholds.
- How many deployments or domains the licence covers, and what a second one costs. This is the term most often left vague and most often disputed later.
If a seller will not put those four lines on an invoice, that is a complete answer to the question of whether the product is white-label.
Where to go next
These pages carry the detail this answer summarises.
Frequently asked questions
Does white-label mean I can resell the source code itself?
Usually not. White-label normally covers presenting the running software as your product to end users. Selling the codebase onward to other developers is a separate right, is rarely granted, and needs to be named explicitly if you want it.
Do I have to tell my customers the software is not mine?
Under a genuine white-label licence, no — that is the point of it. Keep the invoice and licence terms on file, because the obligation you do have is to be able to evidence your right to distribute it.
Is white-label the same as open source?
No. Open-source licences grant broad rights to use and modify but often require attribution or that derivative works stay under the same licence, which can conflict with presenting the software as proprietary. A commercial white-label licence is a private agreement with different terms.
Can the vendor revoke white-label rights later?
Not for a licence you have already bought, if the terms are in writing and perpetual. This is the practical reason to insist on the invoice wording: a permission granted verbally is difficult to rely on if the vendor changes their policy or their staff.
Get a quote or a guided demo
Tell us your use case and we'll send pricing, a live demo walkthrough and licensing options for SaaS source code. Usually a reply within one business day (IST).