What is a white label agreement

A white label agreement is a contract in which one company supplies a finished product or service and another company sells it to end customers under its own brand, as though it built the thing itself. The supplier stays out of view. The name on the product, the invoice, and the support address belongs to the other party.

Two questions usually sit behind that definition: how the arrangement differs from a reseller or OEM deal, and who ends up owning the customer. The short answers are these. In a white label arrangement the brand owner is the party the customer buys from, contracts with, and complains to, while the supplier's only counterparty is the brand owner. A reseller normally sells under the vendor's brand, so the customer knows whose product it is. OEM usually describes a supply relationship in which the supplier's product is built into or bundled with someone else's finished product rather than sold whole. The section on related contract types works through the edges.

There is no white label statute. The agreement is assembled from three familiar pieces: a license or supply contract for the product, a trademark license running the other way so the supplier can apply the brand owner's marks, and a services layer covering hosting, support, and service levels. Almost every question worth asking is about how those pieces fit together.

The vocabulary is loose. White label agreement, white labeling agreement, white label partner agreement, and white label services agreement all name the same instrument. Private label agreement is the usual term when the product is physical goods, and it is a term of art in US consumer product law. The Consumer Product Safety Act defines a private labeler as "an owner of a brand or trademark on the label of a consumer product which bears a private label", and treats a product as bearing a private label when it is labeled with the brand of someone other than a manufacturer, that person authorized the labeling, and the manufacturer's own brand does not appear on the label [1]. In retail practice, private label often describes a line made for one retailer's own brand while white label describes a common product sold to several brands, but that split is a trade convention, not a legal distinction. The exclusivity clause is what tells you which one you actually have.

The instrument shows up in several shapes. White label manufacturing covers goods made to a supplier's recipe and sold under a buyer's brand. White label software licenses a platform that the licensee presents as its own product. White label services cover an agency subcontracting delivery while remaining the client's counterparty. White label financial products put a licensed institution behind a branded app. The commercial mechanics differ, but the contract questions are the same in all of them.

This is general information about how these agreements are built, not legal advice on a specific one.

Purpose and common uses

The brand owner's reason is usually time. Building a payments stack, a learning platform, or a supplement production line takes quarters or years. Licensing a working one takes weeks, and the brand owner spends its money on distribution instead of engineering. It also lets a company close a gap in its portfolio without committing to owning that gap forever.

The supplier's reason is reach. It gets volume through someone else's sales channel without paying for brand building, and it keeps the underlying intellectual property. In software the developer "retains all of its rights in the source code", and the arrangement lets the licensee "use its own brand and logo on the product and present the software as their own to the end-users, almost the opposite of franchising" [2]. That comparison is worth holding on to. A franchisee operates under someone else's brand. A white label licensee operates under its own.

Common settings include retailer store brands and contract food manufacturing, agencies subcontracting web development or bookkeeping, SaaS platforms resold by consultancies, telecom operators reselling network capacity, ATM and card programs fronted by non-banks, and marketplaces that put a partner's fulfillment behind their own checkout.

The arrangement stops making sense when the product is the differentiator. If customers are buying the thing itself rather than the brand, the relationship, or the bundle around it, white labeling means paying a margin to a supplier who can sell the same product to a competitor next quarter.

Parties in a white label agreement

Two parties sign. A third is affected by everything they agree and signs nothing.

The supplier builds, hosts, and maintains the product. It is also called the producer, the provider, the licensor, or the manufacturer. It usually keeps the product IP, sets the technical roadmap, and carries the infrastructure obligations.

The brand owner buys the product, applies its own marks, sets the retail price, and faces the customer. It is also called the licensee, the reseller, the partner, or the private labeler. Confusingly, both sides are often called "the white label partner" in the same negotiation, so contracts define the roles explicitly.

The end customer is not a party. It contracts with the brand owner under the brand owner's terms of service, and in a well built arrangement it never learns the supplier exists.

The division of labor varies more than the labels suggest, and it is worth writing down before anyone drafts.

Responsibility	Typical owner	Worth confirming in the contract
Product development and roadmap	Supplier	Whether the brand owner can request or block changes
Hosting and infrastructure	Supplier	Who pays, and whether costs are passed through at cost
Branding and marketing	Brand owner	Where the supplier's name may and may not appear
Pricing to the end customer	Brand owner	Any floors, caps, or minimum commitments
First-line customer support	Brand owner	Escalation path and response times behind it
Second-line and defect fixes	Supplier	Service levels and credits
Customer data	Split in practice	Who holds it, who controls it, who gets it back
Regulatory permissions	Depends on sector	Which party's license covers the activity

Key terms and clauses

Grant of rights. This clause decides what the brand owner may actually do. A real example filed with the SEC grants an "exclusive, non-transferable, non-sub-licensable" right in defined territories, then adds that the supplier "does not transfer any other right, title or interest" beyond that grant [3]. Check exclusivity, territory, permitted channels, whether affiliates are covered, and whether sublicensing to a group company needs consent.

Trademark license and quality control. The brand owner licenses its marks to the supplier so the supplier can apply them. Quality control rights in that license are not boilerplate. Under US trademark law, use by a related company benefits the mark owner where that use "is controlled by the registrant or applicant for registration of the mark with respect to the nature and quality of the goods or services", and a related company is defined by exactly that control [4]. A mark can also be deemed abandoned when a course of conduct by the owner, "including acts of omission as well as commission", causes it to lose its significance as a mark [4]. Licensing a brand onto a product the brand owner never inspects is a risk to the brand itself.

Branding and attribution. Set out where the supplier may be named, whether a "powered by" line is permitted, what happens in source code, email headers, and API responses, and who owns the domain. Attribution creep undoes the point of the arrangement.

Commercials. Wholesale pricing, revenue share, minimum commitments, and price change mechanics. Restrictions on what the brand owner may charge its own customers raise competition law questions in most jurisdictions and belong with counsel rather than in a template.

Support and service levels. The brand owner promises the customer something. The supplier promises the brand owner something. If the second promise is weaker than the first, the brand owner absorbs the difference. Compare the two documents side by side rather than reading them apart.

Data and privacy. Decide who is controller and who is processor, where data is hosted, what the supplier may do with aggregate data, and what the brand owner gets back on exit. In the SEC-filed agreement the supplier is "responsible for capturing and recording, processing and storing all End User Data" and warrants that its collection, retention, and use of that data will comply with the privacy policy and applicable law [3]. Brand ownership and data possession sit in different places, which is why this clause matters more than its length suggests. If personal data is involved, a data processing agreement usually sits alongside.

Intellectual property. Expect the supplier to keep the product and every enhancement to it, and the brand owner to keep its own marks and content. The same agreement records that developments and derivatives "will be deemed to constitute part of" the licensed product and remain the supplier's property, while the supplier acknowledges it acquires no interest in the brand owner's IP [3]. Custom work paid for by the brand owner is the clause to read twice.

Indemnities and liability. Third party IP infringement claims usually flow back to the supplier, often with the supplier holding the option to procure a license, modify the product, replace it, or terminate [3]. That last option is a real outcome for the brand owner, so check what happens to its customers when the supplier exercises it.

Regulatory responsibility. In licensed sectors, name which party holds which permission and what happens when a regulator objects. The SEC-filed agreement lets the brand owner terminate immediately if the supplier does anything that it "reasonably believes will expose the EST Group to the risk of adverse legal, regulatory or economic repercussions", if a regulator orders the relationship ended, or if its gaming licenses are put in jeopardy [3].

Exclusivity and non-compete. Whether the supplier may serve competitors, whether the brand owner may run a second supplier, and what either restriction costs.

Term, termination, and transition. Covered next, because these are the dates that get missed.

Important dates and lifecycle events

The date that catches people out is the start date. In the SEC-filed agreement the term does not run from signature. It runs for a fixed number of months "from the Launch Date", with automatic renewal unless either party gives written notice a set number of days before the end of the initial or renewal period [3]. Sign in January, launch in June, and the renewal math moves with the launch.

The events worth holding as dates rather than as clauses:

• Commencement date and launch date, separately, plus the trigger that converts one into the other.
• End of the initial period, and the notice deadline calculated backwards from it. The deadline is the date to diarise, not the expiry.
• Each renewal period and its own notice deadline, since auto-renewal makes this recur indefinitely.
• Cure periods. The same agreement gives ten days to remedy a remediable material breach, and lists specific warranty breaches that are treated as irremediable [3].
• Take-down period. After termination the brand owner has thirty days to remove licensed marketing material from channels under its control [3]. That is an operational project, not a formality.
• Return or deletion of confidential information, due within fourteen days of termination in that agreement [3].
• Survival. Confidentiality, IP, liability, and indemnity clauses usually outlive the agreement. Know which ones.
• Price review and minimum volume measurement dates, which decide whether a commitment was met before anyone notices it was not.
• Regulatory license renewals on either side, since the supplier's lapse can end the brand owner's product.
• Customer migration window if the arrangement ends and the end customers have to go somewhere.

Risks and common mistakes

The back-to-back gap. The most common failure is promising customers a service level the supplier has not promised the brand owner. Uptime, response times, data recovery, and liability caps all need comparing across both contracts before the customer-facing terms are published.

No quality control. Brand owners sometimes treat the trademark license as a formality and never inspect what ships under their name. That is both a reputational exposure and, under US trademark law, a risk to the mark [4].

Not knowing who the warrantor is. Under the Magnuson-Moss Warranty Act a warrantor is "any supplier or other person who gives or offers to give a written warranty or who is or may be obligated under an implied warranty", and a supplier is "any person engaged in the business of making a consumer product directly or indirectly available to consumers" [5]. A company that never manufactured anything can still be the party on the hook for the written warranty it issued under its own brand.

Assuming someone else's license covers the activity. In regulated sectors this is the expensive mistake. US banking regulators put it plainly: a banking organization's use of third parties "does not diminish or remove a banking organization's responsibility to perform all activities in a safe and sound manner, in compliance with applicable laws and regulations, including those related to consumer protection and security of customer information" [6]. Fronting a regulated product does not move the regulatory duty, and being the invisible supplier behind one does not remove it either.

Customer data held with no exit right. If the supplier holds the records and the contract is silent on export format, timing, and cost, the brand owner's customer list is effectively the supplier's.

Termination that strands customers. Termination clauses tend to be written about the two signatories. The end customers are not parties, so nothing protects them unless someone drafts it: a transition period, continued service during migration, or an escrow arrangement.

Missing exclusivity. Without it, the same product can appear under a competitor's brand at a different price, which turns the brand owner's marketing spend into category education.

Losing the renewal. Auto-renewal plus a notice window measured from a launch date nobody recorded is how a two year commitment gets extended by accident.

Related contract types

Instrument	Whose brand the customer sees	Who the customer buys from	Distinguishing feature
White label agreement	The intermediary's	The intermediary	The supplier is invisible by design
Private label agreement	The intermediary's	The intermediary	Same idea, standard term for physical goods
Reseller agreement	The vendor's	Usually the reseller	The customer knows whose product it is
Distribution agreement	The vendor's	A distributor or a retailer below it	Organized around territory and channel
OEM supply	The integrator's	The integrator	The supplier's product is a component or a bundle, not the whole
Franchise agreement	The franchisor's	The franchisee	The operator adopts someone else's brand and system
Licensing agreement	Either	Either	The general category all of these sit inside

OEM deserves a warning. The abbreviation is used inconsistently: in one usage it names the company that makes a component ending up inside someone else's finished product, and in channel usage it names the brand owner buying those components. Because both usages are current, treat the label as a hint and read the operative clauses to work out which direction the product and the brand are traveling.

Neighboring instruments worth reading about:

• Franchise agreement. The mirror image. The operator runs under the brand owner's name and system rather than its own.
• Master service agreement. A white label arrangement is often papered as an MSA with a white label schedule rather than as a standalone document.
• Statement of work. The right instrument for bespoke development commissioned under the white label relationship.
• Software reseller agreement. The comparison to make when deciding whether the vendor's brand should stay on the product.
• Data processing agreement. Required alongside most white label arrangements that touch personal data.
• White label agreement template. A starting structure covering the grant of rights, branding, support, data, IP, and termination clauses described above.

Contract-management checklist

Capture at signature

1. Record both the commencement date and the launch date as separate fields, and record which one the term runs from.
2. Calculate the notice deadline backwards from the end of the initial period and store that date, not the expiry date.
3. Record the exclusivity position in one line: exclusive or not, in which territory, in which channel, and until when.
4. Copy the customer-facing service level and the supplier's service level onto the same record so the gap between them is visible without opening two files.
5. Record who holds customer data, in what format it can be exported, and how many days the supplier has to return or delete it.
6. Attach the trademark license, the data processing agreement, and any schedules to the same contract record as the main agreement.
7. Name an owner on each side: the internal commercial owner, and the supplier's named account contact.
8. Record which party holds each regulatory permission the product depends on, with that permission's own expiry date.

Schedule reminders

9. A reminder on the notice deadline, plus an earlier one that leaves time to decide rather than react.
10. A reminder before each minimum volume or revenue commitment is measured.
11. A reminder ahead of any price review window in which either side may propose a change.
12. Reminders on the expiry of every regulatory license recorded in step 8, on both sides.
13. A recurring reminder to run the quality inspection the trademark license entitles the brand owner to carry out.

Review on a cadence

14. Every quarter, compare what the supplier delivered against the service level, and check whether any credits were due and claimed.
15. Every quarter, check whether the supplier's product has changed in ways the customer-facing terms no longer describe accurately.
16. Before every renewal, decide whether the margin still justifies the arrangement and whether the exclusivity position still holds.
17. Once a year, walk through what would happen to the end customers if the agreement ended in thirty days, and fix whatever that exposes.

Most of the failures above are record-keeping failures rather than drafting failures. The clause was there; nobody was watching the date. Contracko keeps white label agreements and their schedules in one searchable repository, uses AI to extract parties, dates, terms, and obligations from the documents, and supports custom fields for the things this contract type needs tracked that a generic contract does not: the launch date, the exclusivity position, the data export deadline, and the permission each party holds. Expiration reminders cover notice deadlines and renewals, and reporting shows the whole partner portfolio rather than one agreement at a time. There is a free trial if you want to load a live agreement and see what it extracts.

Sources

[1] U.S. Code, 15 U.S.C. 2052, Consumer Product Safety Act definitions (statutory definitions of private labeler and private label). law.cornell.edu/uscode/text/15/2052

[2] Morgan Lewis. Practitioner overview of white-label arrangements in software, including branding rights and the developer's retained source code rights. morganlewis.com/blogs/sourcingatmorganlewis/2023/06/wheres-the-money-options-for-commercializing-technology-part-2-white-label-arrangements

[3] U.S. Securities and Exchange Commission, White Label Agreement between Splash Technology Limited and Esports Technologies, Inc. (filed exhibit used here as a worked example of grant, IP, data, term, termination, and regulatory clauses). sec.gov/Archives/edgar/data/1829966/000168316821001303/esports_ex1012.htm

[4] U.S. Code, 15 U.S.C. 1055 and 1127, Lanham Act (use by related companies, the control test, and when a mark is deemed abandoned). law.cornell.edu/uscode/text/15/1055

[5] U.S. Code, 15 U.S.C. 2301, Magnuson-Moss Warranty Act definitions (who counts as a supplier and a warrantor). law.cornell.edu/uscode/text/15/2301

[6] Federal Deposit Insurance Corporation, FIL-29-2023, Interagency Guidance on Third-Party Relationships: Risk Management (using a third party does not remove a banking organization's own responsibility). fdic.gov/news/financial-institution-letters/2023/fil23029.html

Images in this article were generated with the assistance of AI.