What Is an OEM Partnership? OEM, White-Label and Embedded Deals Explained

Most partner programs are built around selling. A reseller buys your product and sells it under your name. A referral partner points a prospect your way and collects a fee. In an OEM partnership, nobody is trying to sell your product as yours. Another company takes your technology, builds it into its own offering, and sells the result as part of something bigger.

That changes almost everything about the relationship: who the customer belongs to, who answers the phone when something breaks, how the money flows, and what happens if one side walks away. This article defines the terms people use for these deals (OEM, white-label, private-label, embedded), separates them from resale and referral, walks through the common commercial structures, lists what an OEM agreement has to settle, and covers the risks on both sides.

One scope note. The word OEM also describes manufacturing relationships, where a supplier builds parts or finished goods to another firm's specification. That's covered in OEM relationship management. This article is about the software and B2B partner-program sense: one company licenses a product or component to another, which embeds or rebrands it. The two overlap in vocabulary but not in contract mechanics.

What an OEM Partnership Is

An original equipment manufacturer (OEM) partnership is an agreement under which one company (the supplier, or technology provider) licenses its product or component to another company (the OEM partner, or integrator), who incorporates it into its own product and sells the combined offering to end customers.

The defining features:

• The partner owns the customer relationship. The end customer buys from the OEM partner, usually under the partner's contract and brand.
• The supplier is largely invisible. The customer may never learn the supplier exists, or may see a "powered by" line.
• The product is changed by being embedded. The component becomes one part of a larger offering, rather than a standalone item on a price list.
• The supplier is paid by the partner, not the end customer. Pricing is negotiated between the two companies, and the end price is set by the partner.

Software history gives the cleanest example. Microsoft's OEM system builder license lets a PC builder preinstall Windows on a machine it sells. Microsoft's own licensing FAQ states that for OEM system builder product, the license terms are an agreement between the system builder and the end user, and that system builders may distribute licenses either preinstalled on a new PC or as unopened packs passed to other system builders. The builder sells the PC, and the operating system comes with it. That is the pattern, whatever the product: supplier's technology, partner's offering, partner's customer.

The Vocabulary: OEM, White-Label, Private-Label, Embedded

These terms get used loosely, and contracts that use them loosely cause disputes. Here's how they're most commonly distinguished in practice. These are working definitions, not legal categories, so any contract should define the term it relies on.

Two distinctions matter more than the labels:

1. Does the product change? In a classic OEM deal the supplier's component is integrated into a different product. In a white-label deal it's mostly the same product with a different logo.
2. Who's visible? The more visible the supplier is, the more it looks like a co-marketing or independent software vendor relationship. The less visible, the more the supplier depends on the partner's execution and honesty.

OEM vs Resale vs Referral

The three models answer different questions, and mixing them up leads to the wrong contract.

The practical difference is where the margin lives. A reseller earns a discount on a product that carries the supplier's price list. An OEM partner prices its own offering, and the supplier's component is a cost line inside it. That is why OEM deals can feel strategic and uncomfortable at once: the partner gains control, and the supplier gives up price visibility and customer contact. For the reseller models, see distributor vs reseller and referral vs affiliate vs reseller. For where OEM sits among the wider channel options, see the channel sales model.

Commercial Structures

There's no single OEM price model. Most deals use one of four structures, or a blend.

Most agreements add a minimum commitment: a guaranteed annual payment the partner owes even if sales fall short. It protects the supplier's investment in supporting the partner, and it filters out partners who sign and then never ship.

This article deliberately doesn't quote typical royalty percentages. Rates vary enormously by product, volume and bargaining position, and no authoritative public benchmark exists that holds across industries. Treat any single "standard rate" you read as a rumour, and anchor negotiation on your own cost to serve, your partner's alternatives and the value the component adds to their price.

How the money is booked

Accounting treatment shapes how a supplier reports an OEM deal, so it's worth knowing the outline. Under US GAAP's revenue standard (ASC 606), licenses of intellectual property have a special rule for royalties. Deloitte's technical guide explains that sales- or usage-based royalties on a license are recognized only when the later of two events occurs: the subsequent sale or usage happens, or the performance obligation the royalty is allocated to has been satisfied. The same guide states that the exception applies where the license is the predominant item the royalty relates to, and that it doesn't apply to fixed consideration. So a guaranteed minimum is treated as fixed consideration, and only the royalties above it fall under the exception.

For a supplier, that has a practical effect. Per-unit and revenue-share royalties tend to be recognized as the partner sells, while a flat fee or a minimum payment can be recognized earlier, depending on the nature of the license. Whether your own arrangement is a license, a service or a mix is an accounting judgement, so confirm it with your auditors before you fix the pricing model. None of this is accounting advice.

What an OEM Agreement Must Address

An OEM relationship is only as workable as its contract. The topics below are common practice rather than a legal template, and a lawyer should draft the final terms. The general mechanics of partner contracts are covered in partner agreement. OEM deals add the following.

1. License scope

What exactly is being licensed, and what isn't? The grant should specify:

• The licensed technology: which version, modules and documentation.
• Permitted use: embed and distribute as part of the partner's product only, or also resell stand-alone?
• Territory and customer type: global, or limited to defined regions or segments.
• Modification rights: can the partner change the code or configuration, and who owns the result?
• Sublicensing: does the end customer receive a license directly from the supplier, or only from the partner?

2. Branding

Decide who appears where. Options run from full removal of the supplier's name, through a "powered by" credit, to a prominent co-brand. Specify logo usage, attribution wording, and what happens to references in documentation, error messages and legal notices.

3. Support tiers

When an embedded product fails, the end customer calls the partner. The agreement has to say what the partner handles and what it can escalate. A common arrangement splits support into levels:

Define severity levels, response times, escalation contacts and what the partner must do before escalating (such as reproducing the fault and supplying logs). Microsoft's FAQ shows the logic in an OEM setting: it says the system builder is required to support the software on the original PC, because the license terms are granted to the end user by the PC maker. In other words, the party that owns the customer relationship owns the front line.

4. Roadmap and end-of-life

An embedded component gets baked into someone else's product, so changes to it ripple outward. The contract should cover:

• How much notice the supplier gives before deprecating a feature or API.
• How long the partner can keep shipping an old version.
• How long security fixes continue for versions already deployed.
• What the partner can expect on roadmap commitments (usually "none guaranteed," which is why the other points matter).
• What happens if the supplier is acquired, discontinues the product or stops supporting it.

Many OEM agreements address the last point with a source-code escrow or a continuity clause. Whether that's proportionate depends on how critical the component is.

5. Exclusivity

Exclusivity can run in several directions: the supplier agrees not to license a competitor in a segment, the partner agrees not to embed a rival component, or both. It has real value to the partner and a real cost to the supplier, so it normally comes with a minimum commitment, a limited term and clear field-of-use limits. Competition law may also apply to restrictions on resale, territory and customers. The European Commission's vertical block exemption page records that Regulation (EU) 2022/720, the current rules on vertical agreements, entered into force on 1 June 2022. If your deal restricts who the partner can sell to, where, or at what price, get competition advice for the markets involved.

6. Audit rights

With per-unit or revenue-based pricing, the supplier is relying on the partner's own numbers. Audit rights let the supplier verify them. A workable clause covers how often audits can occur, how much notice is required, who performs them (often an independent third party), what records the partner keeps, who pays if underpayment exceeds a stated threshold, and how disputes are resolved. On the other side, partners should ask for confidentiality protections, so the supplier can't use audit access to learn their customers and pricing.

Risks of OEM Partnerships

Dependency

The partner builds its product around the supplier's component. If the supplier raises prices, changes direction or fails, the partner faces an expensive replacement project. The supplier has its own version: if one partner accounts for a large share of revenue, losing that partner hurts disproportionately. Mitigate it with term length, transition rights, escrow, and by not letting one deal carry the business.

Margin squeeze

When the partner controls the end price, the supplier's share can be eroded without any change in the contract. Discounting by the partner reduces a revenue-share royalty directly. A rate that looked generous at signing may look thin once the partner bundles the component into a cheaper package. Per-unit royalties and minimums give more protection than percentage deals, and a pricing review clause helps both sides.

Channel conflict

The supplier may also sell directly, or through resellers, to some of the same customers the OEM partner targets. An embedded product and a stand-alone product can end up competing for the same buyer. Decide up front which segments the partner owns, what the supplier will and won't sell directly, and how overlapping deals are handled. The mechanics are in channel conflict, and the same problem shapes how any partner-led growth program is designed.

Key Facts

• Under US GAAP's revenue standard, sales- or usage-based royalties on a license of intellectual property are recognized when the later of the subsequent sale or usage, or satisfaction of the related performance obligation, occurs (Deloitte DART).
• The royalty exception applies where the license is the predominant item the royalty relates to, and it does not apply to fixed consideration such as a guaranteed minimum (Deloitte DART).
• Microsoft states that under its OEM system builder license, the license terms are an agreement between the system builder and the end user, and that the system builder is required to support the software on the original PC (Microsoft device partner licensing FAQ).
• Microsoft lets system builders distribute Windows licenses preinstalled on a new PC, or as unopened packs passed to other system builders (Microsoft device partner licensing FAQ).
• Regulation (EU) 2022/720, the EU's block exemption for vertical agreements, entered into force on 1 June 2022 (European Commission).

Related Reading

• What is a partner ecosystem?
• Cloud and app marketplace listings
• OEM relationship management
• Independent software vendor
• Distributor vs reseller
• Referral vs affiliate vs reseller
• Partner agreement
• Channel conflict
• Channel sales model
• Partner-led growth