What is an OEM agreement

An original equipment manufacturer (OEM) agreement is a contract under which one company supplies a product, component, or piece of software that another company builds into, bundles with, or ships as part of its own finished product sold under its own brand. A laptop maker putting another company's solid-state drive inside a machine that ships with the laptop brand on the lid is the same shape of deal as a printer company embedding another vendor's page-description software so the printer can speak PostScript. The supplier keeps making and owning the thing it supplies. The other party decides what the finished product is called, what it costs, and who answers the phone when it breaks.

Two questions usually sit behind that definition. Which party is "the OEM", and who owns the intellectual property when the finished product is a mix of both parties' work.

The first question has no single answer, and that is the most useful thing to know about the term. In its original engineering sense, the OEM is the company that manufactures the part that ends up inside someone else's product. In common technology and channel usage the label has flipped: the computer maker that buys operating system licenses and drive mechanisms and assembles them into laptops is called the OEM, and the software vendor is its supplier. Both usages are current, often in the same industry. A document titled "OEM agreement" tells you the shape of the relationship, not which side of it either party is on. Read the operative clauses to find out who supplies, who integrates, and whose brand faces the customer.

The second question is answered in the next paragraph and then in detail below: ownership usually stays where it started, and the interesting risk moves with whoever wrote the specifications.

The vocabulary is loose. OEM supply agreement, OEM manufacturing agreement, OEM licensing agreement, and OEM distribution and license agreement all name the same instrument with different emphasis. Contract manufacturing agreement is the usual term when the buyer's own design is being built to order. Original design manufacturer (ODM) is a different arrangement: the ODM designs the product as well as builds it, so the buyer is licensing someone else's design rather than commissioning its own. Private label and white label describe a finished product resold whole under another brand, which is a related but distinct deal, covered under related contract types below.

There is no OEM statute. The agreement is assembled from a supply or license contract, a specification and quality regime, a trademark or attribution arrangement, and a support and warranty split. General commercial law fills the gaps the parties leave. This is general information about how these agreements work in the United States, not legal advice on a specific one.

Purpose and common uses of an OEM agreement

The integrator's reason is usually build-versus-buy. A print controller company does not want to write a page description language. A medical device company with a strong clinical design does not want to own a factory. Buying the piece it does not want to own lets it ship a complete product sooner and spend its engineering budget on whatever customers actually choose it for.

The supplier's reason is volume through someone else's channel, at a much lower cost of sale than selling the same component one customer at a time, while keeping the underlying technology.

Common settings include automotive and industrial components sold to vehicle and machine builders, contract manufacture of consumer goods to a brand owner's specification, software components embedded in hardware or in another vendor's platform, operating systems and drivers preinstalled on computers, and medical devices built by a contract manufacturer to a specification developer's design.

A filed example is worth reading if you want to see one. Adobe and Electronics for Imaging signed an OEM Distribution and License Agreement in 2005, filed with the Securities and Exchange Commission (SEC), which licenses Adobe software for use in defined EFI products and then works through grant, ownership, attribution, testing, support, term, and sell-off in the order a negotiation actually takes them [3]. It is old enough to be public and structurally the same as what gets signed now.

The arrangement stops making sense when the supplied piece is the whole product. At that point the deal is a reseller or white label arrangement, and it should be papered as one.

Parties involved in an OEM agreement

Two parties sign. Two more are affected and sign nothing.

The supplier manufactures the component or licenses the software. It is called the OEM, the manufacturer, the licensor, or the vendor depending on the industry. It normally keeps the intellectual property in what it supplies, controls its own roadmap, and carries defect and second-line obligations.

The integrator buys the component, combines it with its own work, brands the result, prices it, and sells it. Confusingly, it is also often called the OEM. In the Adobe agreement the integrator is additionally allowed to sublicense certain rights to its own "Remarketer Customers", so a channel can sit below it [3].

The end customer buys the finished product from the integrator, under the integrator's terms and warranty, and usually has no contract with the supplier at all.

The regulator is not a party but sets who is answerable. In FDA-regulated device work, the act of "initiation of specifications for devices that are manufactured by a second party for subsequent commercial distribution by the person initiating specifications" is itself manufacturing for establishment registration purposes [7]. A company that has never touched a production line can still be a manufacturer in the eyes of the rules that matter.

Responsibility	Typical owner	Worth confirming in the contract
Design of the supplied item	Supplier, unless built to the buyer's specification	Who furnished the specifications, in writing
Design of the finished product	Integrator	Whether the supplier must approve the integration
Quality and acceptance testing	Both, in sequence	Which test suite governs and who pays to re-run it
Branding of the finished product	Integrator	Where the supplier's name must and must not appear
Pricing to the end customer	Integrator	Any floors, caps, or most-favored terms
First-line support	Integrator	The escalation path and response times behind it
Defect fixes in the supplied item	Supplier	Service levels, and what happens at end of life
Warranty to the end customer	Integrator	Whether the supplier's warranty is long enough to back it
Labeling and origin claims	Integrator	Which party supplies the facts those claims rest on
Regulatory registration	Depends on sector	Which party is the manufacturer of record

Key terms and clauses in an OEM agreement

Grant of rights. For software, expect something narrow. The Adobe grant is "non-exclusive, non-transferable" and limited to the licensee's "use in EFI Products", with sublicensing to remarketers permitted only on consistent terms [3]. Check which finished products are covered, whether future products need an amendment, which territories are included, and whether affiliates are inside the grant.

Specifications, and who wrote them. This is the clause that decides where infringement risk lands, and the default surprises people. Under the Uniform Commercial Code a merchant seller warrants that goods arrive "free of the rightful claim of any third person by way of infringement or the like", but "a buyer who furnishes specifications to the seller must hold the seller harmless against any such claim which arises out of compliance with the specifications" [1]. Commission a part to your own drawing and the statutory default points the indemnity back at you. Record who supplied each specification, and make the indemnity match reality rather than assumption.

Ownership and modifications. Ownership normally stays put. The supplier remains "the sole and exclusive owners of all rights, title and interest" in what it licenses, while the integrator's own modifications vest in the integrator "subject to Adobe's ownership rights" [3]. That phrase is the one to read twice. Work the integrator paid for can still sit on top of a licence it does not control.

Attribution and trademarks. OEM deals usually run attribution in both directions. The supplier may require a line on the packaging, in the Adobe case "a phrase substantially similar to 'This product contains Adobe Technology'", plus compliance with trademark rules for announcements [3]. Where the integrator's mark goes onto goods someone else makes, quality control is not a formality. Under the Lanham Act a "related company" is one "whose use of a mark is controlled by the owner of the mark with respect to the nature and quality of the goods or services", and a mark can 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]. Branding goods nobody inspects is a risk to the brand.

Exclusivity, forecasts, and volumes. If the deal is exclusive, the code adds obligations the parties may not have written down: exclusive dealing "imposes unless otherwise agreed an obligation by the seller to use best efforts to supply the goods and by the buyer to use best efforts to promote their sale" [2]. Where quantity is set by the buyer's requirements or the seller's output, it means "such actual output or requirements as may occur in good faith", and cannot be unreasonably disproportionate to a stated estimate [2]. Non-binding forecasts are rarely as non-binding as their heading suggests.

Quality, acceptance, and certification. Manufacturing OEM deals turn on inspection rights, defect rates, change control, and who bears the cost of a failed lot. Software OEM deals turn on certification: the Adobe agreement requires testing against a named certification test suite before commercial shipment [3]. Either way, ask what happens when the supplier changes the item and the integrator has to re-certify.

Support and warranty split. In that agreement the integrator has "sole responsibility for supporting End Users", while the supplier's maintenance duties live in a separate exhibit, and the software warranty runs "ninety (90) days" from acceptance [3]. The integrator is meanwhile promising its customers something considerably longer. That gap is normal and needs to be priced, not discovered.

Indemnity, and its edges. Infringement indemnities are commonly capped by geography: in the filed example, only claims in a list of countries in an exhibit [3]. If the finished product sells outside that list, the integrator carries the difference.

Labeling and origin. Selling someone else's manufacture under your own name does not move the labeling duty to them. Imported articles must be marked to indicate "to an ultimate purchaser in the United States the English name of the country of origin" [5]. An unqualified "Made in the United States" claim requires that final assembly or processing occurs in the US, that all significant processing occurs there, and that all or virtually all ingredients or components are made and sourced there [6]. The integrator makes the claim; the supplier holds the facts. Put those facts in the contract as warranties and notice obligations.

Continuity. Change control, last-time-buy rights, end-of-life notice periods, and source code or tooling escrow. If the supplied item disappears, the finished product does too.

Important dates and lifecycle events

The date to get right at the start is which event the term runs from. Signature and first commercial shipment can be a year apart, and a term measured from the wrong one puts every downstream deadline in the wrong place.

The Adobe agreement runs for "five (5) years from the Effective Date", renews automatically for one year periods, and requires written notice "at least 180 days prior" to stop it [3]. A six month notice window on a five year term is easy to miss and expensive to miss.

Events worth holding as dates rather than as clauses:

• Effective date and first commercial shipment date, recorded separately, with a note of which one the term runs from.
• End of the initial term, and the notice deadline counted backwards from it. Diarise the deadline, not the expiry.
• Each renewal period and its own notice deadline, because automatic renewal makes this recur.
• Cure periods. Thirty days to cure a material breach after written notice, in the filed example, with termination effective at the end of that period if the breach remains uncured [3].
• Post-termination sell-off window. That agreement allows six months from termination to distribute remaining inventory and upgrades, with reporting and payment obligations continuing through it, but only where the agreement ended for something other than an uncured material breach [3].
• Royalty and volume reporting dates, and the audit rights attached to them.
• Forecast submission windows and the point at which a forecast becomes a commitment.
• Certification or re-qualification dates triggered by a new version of the supplied item.
• Price review windows and any indexation date.
• End-of-life and last-time-buy notice dates, on both sides.
• Regulatory registrations and certifications either party's product depends on, with their own renewal dates.
• Survival. Confidentiality, IP, indemnity, and liability terms normally outlive the agreement.

Risks and common mistakes

Reading the label instead of the clauses. Because "OEM" names both roles, people negotiate the wrong template. Establish direction of supply and direction of branding on the first call.

Furnishing specifications and keeping the supplier's indemnity. The statutory default already flips risk to the party that supplied the specification [1]. An indemnity copied from a standard supply contract will not survive contact with a custom part.

Backing a long customer warranty with a short supplier warranty. Ninety days behind a three year promise is an uninsured gap sitting on the integrator's balance sheet [3].

Territory-limited indemnity behind a global product. Check the exhibit, then check the sales plan.

No quality control over goods carrying your mark. Both a reputational exposure and, under US trademark law, a risk to the mark itself [4].

Assuming the manufacturer is the regulated party. In device work the company that initiates the specifications is manufacturing for registration purposes even though a second party builds the product [7].

Making origin claims on someone else's facts. Marking and Made in USA claims sit with the party whose name is on the product [5] [6].

Losing the notice window. A 180 day notice on an auto-renewing multi-year term extends the whole relationship by default [3].

No sell-off or transition rights. Without them, termination can leave finished inventory unsellable and installed customers unsupported.

No continuity plan for an embedded component. One supplier end-of-life notice can obsolete a product line.

Treating the forecast as decoration. Good faith and best efforts obligations attach to exclusive and requirements arrangements whether or not the parties discussed them [2].

Related contract types

Instrument	Whose brand the customer sees	What is supplied	Distinguishing feature
OEM agreement	The integrator's	A component, subassembly, or embedded software	The supplied item is part of a larger finished product
Contract manufacturing agreement	The buyer's	Manufacturing capacity	The buyer's own design is built to order
ODM agreement	The buyer's	Design and manufacture	The supplier owns the design being rebranded
White label agreement	The intermediary's	A finished product or service	Sold whole, supplier invisible by design
Reseller agreement	The vendor's	A finished product	The customer knows whose product it is
Distribution agreement	The vendor's	A finished product	Organized around territory and channel
Supply agreement	Either	Goods on recurring terms	Framework for volume, price, and delivery, brand neutral
Software license agreement	Either	Rights in software	The general category OEM software deals sit inside

Where the confusion usually bites is between OEM and white label. In a white label arrangement the supplier's finished product is sold as the brand owner's own, unchanged. In an OEM arrangement the supplied item is a part of something the integrator builds, and the integrator's product is genuinely its own. The practical test is whether the integrator adds anything the customer is paying for besides the brand.

Neighboring instruments worth reading about:

• What is a white label agreement. The comparison to make when the supplied product ships whole.
• Software reseller agreement. The right instrument when the vendor's brand stays on the product.
• What is a software license agreement. The licensing mechanics underneath most software OEM deals.
• What is a master service agreement. OEM terms are often a schedule under a framework agreement rather than a standalone contract.
• What is a franchise agreement. The opposite direction, where the operator adopts the brand owner's name and system.

Contract-management checklist

Capture at signature

1. Record the effective date and the first commercial shipment date as separate fields, and record which one the term runs from.
2. Calculate the notice deadline backwards from the end of the initial term and store that date, not the expiry date.
3. Record in one line who furnished the specifications for each supplied item, and which party's indemnity covers infringement in that item.
4. Record the exclusivity position: exclusive or not, in which territory, in which channel, and until when.
5. Put the supplier's warranty period and the customer-facing warranty period on the same record so the gap is visible without opening two files.
6. Record the countries in which the infringement indemnity applies, and compare them against the current sales territories.
7. Record which party is the manufacturer of record for each regulatory registration the product depends on, with that registration's own renewal date.
8. Attach the specification exhibits, the certification or test requirements, the trademark or attribution rules, and the price schedule to the same contract record as the main agreement.
9. Name an owner on each side: the internal product owner and the supplier's named account contact.
10. Record the end-of-life notice period, the last-time-buy right, and whether escrow exists.

Schedule reminders

11. A reminder on the notice deadline, plus an earlier one that leaves time to decide rather than react.
12. A reminder before each forecast or volume commitment is measured.
13. A reminder ahead of every price review or indexation window.
14. Reminders for royalty and volume reports due to the supplier, since missed reports are the usual trigger for an audit.
15. Reminders on the renewal of every regulatory registration and certification recorded in step 7.

Review on a cadence

16. Each quarter, check whether the supplied item has changed in ways the finished product's documentation, warranty, or certification no longer match.
17. Each quarter, compare delivered quality and lead times against the agreement, and check whether any credits or remedies were due and claimed.
18. Once a year, confirm the origin and labeling claims on the finished product still match what the supplier actually does and where.
19. Before every renewal, decide whether to build, re-source, or renew, and start that decision before the notice window opens rather than inside it.
20. Once a year, work through what happens to the product line if the supplier gives end-of-life notice tomorrow, 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 OEM agreements and their exhibits 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 first shipment date, who furnished the specifications, the indemnified territories, and the end-of-life notice period. Expiration reminders cover notice deadlines and renewals, and reporting shows the whole supplier 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] Uniform Commercial Code, UCC 2-312, warranty of title and against infringement (the merchant's infringement warranty, and the buyer who furnishes specifications holding the seller harmless). law.cornell.edu/ucc/2/2-312

[2] Uniform Commercial Code, UCC 2-306, output, requirements and exclusive dealings (good faith quantities and the mutual best efforts obligation in exclusive dealing). law.cornell.edu/ucc/2/2-306

[3] U.S. Securities and Exchange Commission, OEM Distribution and License Agreement between Adobe Systems and Electronics for Imaging, Inc., dated September 19, 2005 (filed exhibit used here as a worked example of grant, ownership, attribution, testing, support, warranty, term, notice, cure, and sell-off clauses). sec.gov/Archives/edgar/data/867374/000119312506056829/dex1022.htm

[4] U.S. Code, 15 U.S.C. 1127, Lanham Act definitions (related company control over nature and quality, and when a mark is deemed abandoned). law.cornell.edu/uscode/text/15/1127

[5] U.S. Code, 19 U.S.C. 1304 (marking imported articles with the English name of the country of origin for the ultimate purchaser in the United States). law.cornell.edu/uscode/text/19/1304

[6] Federal Trade Commission, 16 CFR 323.2, Made in USA Labeling Rule (the three conditions for an unqualified US origin claim). law.cornell.edu/cfr/text/16/323.2

[7] U.S. Food and Drug Administration, 21 CFR 807.3, device establishment registration definitions (initiating specifications for a device manufactured by a second party is itself manufacturing). law.cornell.edu/cfr/text/21/807.3

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