White label

White Label MLM Software

White label means your brand on someone else's platform. It is a legitimate and often sensible arrangement, and it is sold with more ambiguity than almost anything else in this category — because the interesting questions are not about the logo. They are about what happens to your data, your plan and your customers if you leave.

What you get

Outcomes operators report after moving onto the platform.

  • Your domain, your brand, throughout

    Corporate site, storefront, distributor back office and transactional email all on your domains, with no vendor branding visible to your field.

  • Email from your domain

    Authenticated sending on your own domain with your own SPF, DKIM and DMARC records, so deliverability reputation is yours to build.

  • Plan implemented, not adopted

    Your compensation plan configured to your rules. White label does not mean inheriting the vendor's plan with your colours on it.

  • Your data, exportable on demand

    Full export of distributors, orders, genealogy, commission history and documents, in a documented format, without a support request.

  • Data controller obligations clear

    You are the controller, the platform is a processor, and the processing agreement says so — which is what GDPR and POPIA require of you.

  • Theming beyond the logo

    Colours, typography, component styling, email templates and document layouts, from a token set rather than by overriding stylesheets.

The logo is the easy part

Every vendor in this category can put your logo on a dashboard. The word “white label” is doing almost no work when it is used that way, which is why it appears in so much marketing without a specification attached.

The questions that determine whether a white label arrangement is good for you are about ownership, configurability and exit. All three are contractual as much as technical, and all three are easiest to settle before money changes hands.

What is branded here

Every surface your field and your customers see: the marketing site, the storefront, replicated distributor sites, the distributor back office, the corporate console, transactional email, and the PDF layouts for commission statements and invoices.

All on your domains — including the authenticated back office and the replicated site pattern. Email authenticated from your domain with your own SPF, DKIM and DMARC records, so the sending reputation you build belongs to you and does not depend on how a shared sending domain is treated.

Theming works from a token set — colour, typography, spacing, component styling — rather than by layering overrides on top of a stylesheet, because the override approach breaks quietly every time the underlying platform changes.

Where vendor identification legitimately remains: privacy documentation that must name the processor, and the support channel if support is delivered by the vendor. Both are honest and both should be disclosed rather than discovered. What should not remain is a vendor mark in a back office footer or on a statement PDF.

The configurability question, asked precisely

“Is the plan configurable” gets a yes from everybody. A more useful question:

Can the plan add a commission component the platform does not currently support, and what does that cost and how long does it take?

The answers separate two genuinely different products. A platform implements your plan, including components it has not seen before, as configuration or as scoped development against your tenant. A brandable product offers you the parameters the vendor already exposed, and anything outside them is not available at any price.

Both can be the right purchase. They are not the same purchase, and they should not carry the same price. What drives cost is on the pricing page.

Data ownership and processing

You are the controller — or under POPIA, the responsible party — for your distributors’ and your customers’ personal information, whoever hosts it. The obligations are yours and cannot be delegated by contract.

What that requires in practice:

  • a written processing agreement naming you as controller and the platform as processor,
  • a list of sub-processors with the countries data is stored and processed in,
  • a route to satisfy access, correction and deletion requests within statutory timeframes,
  • and breach notification terms that let you meet your own reporting deadlines.

A white label vendor without these has not addressed a problem that is legally yours rather than theirs.

Exit, settled at the start

TermThe answer to look for
What exportsdistributors, orders, both trees, full commission history, documents, content
Howself-service, documented format, any time
FormatCSV and JSON, with a published schema
At terminationa defined transition window, then certified deletion

Export by support ticket under thirty days’ notice is not an export feature; it is a negotiating position. The same reasoning, applied to platforms generally, is on the MLM platform page.

At a glance

Branded surfacesMarketing site, storefront, replicated sites, distributor back office, corporate console, transactional email, PDF statements and invoices
DomainsYour domains throughout, including the replicated site pattern and the authenticated back office
ThemingDesign tokens for colour, type and spacing; component-level overrides; per-locale asset sets
Plan configurationYour plan, your rates, your qualifications — configured per company rather than shared across tenants
Data exportSelf-service full export in CSV and JSON, plus scheduled delivery to storage you control
Data processingWritten processing agreement naming you as controller, with sub-processors listed and locations stated
ExitDocumented export, a defined transition window, and deletion certified on completion
FAQ

Questions operators ask before they switch

Straight answers on plan mechanics, migration risk and compliance. If yours is not here, ask us directly.

What is genuinely white label and what is not?

Genuinely rebrandable: every surface your field and your customers see, on your domains, with your typography and colours, and transactional email authenticated from your domain. Not rebrandable, and worth checking: the platform's own status pages, the support channel if support is provided by the vendor, and the notices in privacy documentation that must name the processor. Those are legitimate exceptions. The illegitimate version is a vendor logo remaining in the distributor back office footer or in commission statement PDFs, which your field will find and ask about.

Does white label mean we inherit the vendor's compensation plan?

It should not, and this is where white label offers vary most. Some vendors mean a rebrandable interface over a plan engine configured per company, which is what you want. Others mean a rebrandable interface over one fixed plan, where your options are the parameters the vendor exposed. The question that separates them is specific: can the plan add a component the platform does not currently have, and what does that cost and take. If the answer is that the plan is what it is, you are buying a brandable product, not a platform, and you should price it as one.

Who owns the data in a white label arrangement?

You do, and the contract should say it in those terms rather than granting you a licence to access it. Under GDPR and South Africa's POPIA you are the responsible party or controller for your distributors' and customers' personal information regardless of who hosts it, which means the obligations sit with you and the platform is your processor. That relationship needs a written processing agreement listing sub-processors and the countries data is stored in. A vendor who cannot produce one has not thought about a problem that is legally yours.

What should the exit terms say?

Three things, in writing, before you sign. What you can export — distributors, orders, full genealogy including both placement and sponsorship trees, complete commission history, uploaded documents and content. How you export it: self-service in a documented format is the answer you want, because export by support request under notice is leverage rather than a feature. And what happens at termination: a defined transition window during which export still works, followed by certified deletion. Companies negotiate this at the end of a procurement when they have no leverage. It belongs at the beginning.

Ready to Transform Your Direct Selling Business?

Send us your plan rules and we will run a live commission cycle against them, on your numbers, before you commit to anything.

  • Configured in a sandbox before the call, usually within two business days
  • No slide deck and no card — you watch your own plan pay out
  • Your plan document stays confidential and is deleted on request

Prefer a longer conversation? Open the full enquiry form

required

Prefer email? Write to us at sales@mlmsoftwarepro.com