In this guide 6 sections
Build a white label platform when partners must sell under their own name, with their own logo, domain and customers kept apart. If they only need to place orders, check stock and download price lists, a reseller portal is enough, cheaper and quicker to run.
What white label actually means
Customers never see your name. They see the partner’s logo, colours, web address and email sender, while one shared platform behind that front quietly serves every partner on your books.
That differs from a portal. In a portal your dealer logs in, works inside your brand, places orders and checks statements, and never runs a business of their own on top of you.
Start with one question. Does the partner’s customer ever touch the product directly, through a booking screen, a tracking link or a receipt carrying a name? If yes, branding matters. If not, it probably does not.
- Partner logo and colour theme
- Custom domain and sender email
- Partner named on invoices and receipts
- Partner’s own login page and welcome text
Data separation is the harder half
Each partner must see only their own customers, orders and reports, because a franchisee reading a rival’s customer list ends the relationship at once. That is a breach, not a bug.
There are two ways to build it. A shared database tags every record with a partner identifier, which costs less and updates all partners together, while a separate database per partner isolates better.
Ask which one your partners’ agreements need. Do it before anyone writes code.
- Row level partner identifier on every table
- Separate backups and export per partner
- Role rights inside each partner account
- Audit log of who viewed what
Price control decides who earns what
Resellers set a selling price above your wholesale price, so the platform must hold both, show margin to the partner and hide your cost from buyers.
Decide the rules in writing. Can a partner discount below a floor? Do you cap the retail price? Are tiers based on volume? Each answer becomes a setting that someone must test before release, and every setting multiplies the cases a tester has to cover.
If partners invoice their customers themselves, the platform must produce invoices carrying their name and tax registration number, then settle with you separately.
When a reseller portal is enough
Many businesses ask for white label when all they want is ordering, and a distributor with forty dealers usually needs login, catalogue, dealer price lists, order history and statements. No dealer needs a private logo on it.
A portal costs less to build and carries one codebase to maintain, and you can add a logo option later if dealers ask for one. Start with what partners do on day one.
Resist building for the partner you hope to sign next year, because the five you already have are the ones who will test the design from week one.
- Dealer login and price list by dealer
- Order entry, order tracking and statements
- Download of brochures and certificates
- Support request form
Count the running cost, not just the build
Every new partner needs onboarding with a domain, SPF and DKIM email records, a theme, user accounts and a price list. One developer day per partner does not scale. Plan a back office screen that lets your own staff finish domain, theme, users and price list without raising a ticket for anyone.
Each release must be tested across several brandings. A button that looks fine in blue can vanish against a partner’s pale yellow, and certificates on custom domains also expire, so someone must own the renewal calendar.
Onboard two paper partners on a spreadsheet. Note every step, because that list becomes your specification and the first estimate of what each new partner will cost you in staff time.
White label decision worksheet
One worksheet, three blocks. Block one lists eight yes or no questions on branding, domains and invoicing, while block two is a table of partner types with columns for separation and price rule. Block three scores portal against white label. Decision and date go at the bottom.
Open a blank worksheet to printQuestions owners ask
What is the difference between white label and multi-tenant?
White label is about branding, meaning the partner’s name and colours sit on a product that every other partner also shares behind the scenes. Multi-tenant is about architecture. It means many customers share one system while their data stays separated, and a white label platform is usually multi-tenant underneath.
Can I start with a portal and move to white label later?
Yes, provided the portal tags its data with partner identifiers from the first day, because retrofitting separation into tables that never had them means rewriting queries, reports and backups. Plan for it early.
Do partners need their own domain?
Only when their customers see the platform. A custom domain also needs a certificate and sender authentication records, and someone on your team must set both up and renew the certificate before it lapses.
Who owns the customer data?
Settle this in the partner agreement before building. The platform must then support export of each partner’s records on request, and removal of them when a partner leaves the programme and the contract ends.