Free Word download β’ Edit online β’ Save & share with Drive β’ Export to PDF
An OEM Reciprocal License Agreement is a legally binding contract in which two companies β each simultaneously acting as licensor and licensee β grant each other defined rights to use, integrate, and distribute their respective intellectual property within their own products and services. Unlike a standard one-way software or technology license, the reciprocal structure creates symmetrical obligations: each party both receives and provides IP rights, typically in exchange for royalties, cross-licensing consideration, or a combination of both. The agreement governs exactly what IP is licensed, to what products it may be applied, in which territories, and under what financial terms β and it does so for both directions of the exchange in a single enforceable instrument.
Operating an OEM technology partnership without a signed reciprocal license agreement exposes both parties to serious, concrete risks on multiple fronts. Without a field-of-use restriction, a partner who receives access to your technology can deploy it in markets you compete in directly β with no contractual basis to stop them. Without an explicit IP ownership and reservation-of-rights clause, a licensee may claim that broad license language implicitly transferred ownership of improvements or derivative works. Without mutual indemnification, a third-party patent infringement lawsuit targeting the integrated product can leave your company bearing full litigation costs and damages that should contractually belong to the party whose IP triggered the claim. And without a clear termination and post-termination clause, winding down a partnership can turn into a protracted dispute over what each party may continue to do with the other's technology. A properly structured OEM reciprocal license agreement closes all of these gaps before integration work begins β protecting your IP, your markets, and your ability to exit the arrangement cleanly if the partnership stops working.
| If your situation is⦠| Use this template |
|---|---|
| One-way license where only the OEM receives rights to use the vendor's technology | OEM License Agreement (Unilateral) |
| Software-only licensing with no hardware component | Software License Agreement |
| Two companies co-developing a new product and sharing resulting IP | Joint Development Agreement |
| Licensing a patent portfolio between competitors or partners | Patent License Agreement |
| Technology reseller rights without deep IP integration | Reseller Agreement |
| Distributing a branded product under another party's mark alongside the IP license | OEM Distribution Agreement |
| Short-term technology evaluation before committing to a full license | Technology Evaluation Agreement |
Why it matters: Without a field-of-use restriction, the licensee can argue it has the right to use the licensed IP in any product or market β including those the licensor competes in directly.
Fix: Define the field of use in a Schedule with positive grant language ('solely for use in [PRODUCT CATEGORY]') and an explicit exclusion of all other uses.
Why it matters: When both parties contribute IP of unequal commercial value, applying identical royalty rates in both directions creates a net transfer of value that one party did not intend.
Fix: Model the royalty flows in both directions before finalizing rates. A cross-license with a net royalty balancing payment is often more commercially accurate than mirrored percentages.
Why it matters: Joint IP ownership means neither party can license the jointly-owned work to a third party without the other's consent, which stalls revenue opportunities and creates leverage imbalances.
Fix: Assign derivative works to one party with a royalty-bearing license-back to the other, or establish a written commercialization committee with defined decision-making rules for joint works.
Why it matters: If a third party sues the licensee claiming the licensed IP infringes its patent or copyright, the licensee is exposed to litigation costs and damages with no contractual right to seek contribution from the licensor.
Fix: Include a mutual indemnification clause requiring each licensor to defend and hold harmless the other against third-party claims arising from the indemnifying party's own licensed IP.
Why it matters: A 1- or 2-year post-termination confidentiality window can expire while the licensed technology is still competitively sensitive, leaving proprietary trade secrets unprotected.
Fix: Set the general confidentiality survival period at 5 years post-termination, with trade secrets protected indefinitely or for as long as they qualify as trade secrets under applicable law.
Why it matters: Executing the contract after one or both parties has already used the other's IP raises a fresh-consideration problem and creates ambiguity about the retroactive scope of the license.
Fix: Execute the agreement before any IP is disclosed, delivered, or integrated. If integration has already begun, include a retroactive effective date clause and document the consideration for the existing use.
In plain language: Sets the context for the agreement, identifies the parties, and defines all key terms used throughout the contract so there is no ambiguity when a defined term appears later.
This OEM Reciprocal License Agreement ('Agreement') is entered into as of [DATE] between [PARTY A LEGAL NAME], a [STATE/COUNTRY] [ENTITY TYPE] ('Party A'), and [PARTY B LEGAL NAME], a [STATE/COUNTRY] [ENTITY TYPE] ('Party B'). Capitalized terms have the meanings set forth in Schedule 1.
Common mistake: Leaving key terms like 'Licensed Products,' 'Net Revenue,' or 'Derivative Works' undefined. Disputes almost always trace back to a term that each side interpreted differently because it was not defined in the contract.
In plain language: The core clause β each party grants the other a defined license to use its IP, specifying the scope, territory, exclusivity, and sublicensing rights.
Party A hereby grants to Party B a [non-exclusive / exclusive], non-transferable, royalty-bearing license to use, reproduce, and distribute the Party A Licensed IP solely within the Field of Use in the Territory. Party B hereby grants to Party A a [non-exclusive / exclusive], non-transferable license to use the Party B Licensed IP on the same terms.
Common mistake: Granting a license without specifying the field of use or territory. An unbounded license grant can be interpreted as a worldwide, unrestricted right, which is rarely what either party intends.
In plain language: Confirms that each party retains full ownership of its background IP and that no rights are transferred beyond those expressly granted.
Each party retains all right, title, and interest in and to its own Licensed IP. No rights are granted by implication, estoppel, or otherwise. All rights not expressly granted to the other party are reserved.
Common mistake: Omitting this clause entirely. Without it, a licensee may argue that the broad license language implicitly transferred ownership or created an implied license to use related IP not listed in the agreement.
In plain language: Addresses who owns any modifications, enhancements, or new works created by either party that are based on or incorporate the other party's licensed IP.
Any Derivative Works created by Party B that incorporate Party A Licensed IP shall be owned by [PARTY A / PARTY B / JOINTLY], and Party B hereby assigns all right, title, and interest in such Derivative Works to [OWNER]. Each party grants the other a [royalty-free / royalty-bearing] license to any Improvements to Licensed IP made during the Term.
Common mistake: Defaulting to joint ownership of derivative works without thinking through the operational consequences. Joint ownership means neither party can license the jointly-owned IP to a third party without the other's consent, which can paralyze commercialization.
In plain language: Defines how royalties are calculated for each direction of the license, when payments are due, and what records each party must keep to support royalty reporting.
Party B shall pay Party A a royalty of [X]% of Net Revenue from Licensed Products sold in the Territory, payable within [30] days after each calendar quarter. 'Net Revenue' means gross revenue from Licensed Products less [returns, taxes, shipping]. Each party shall maintain records sufficient to verify royalty calculations for [3] years.
Common mistake: Defining royalties on gross revenue instead of net revenue without specifying which deductions are permitted. This regularly creates calculation disputes because each party applies different deductions.
In plain language: States whether and how each party may grant sublicenses to contract manufacturers, distributors, or resellers, and what obligations flow down to those sublicensees.
Party B may sublicense the rights granted hereunder to its authorized contract manufacturers solely for the purpose of manufacturing Licensed Products on Party B's behalf, provided that each sublicense is in writing, contains terms no less protective of Party A's IP than this Agreement, and Party B remains liable for the sublicensee's compliance.
Common mistake: Permitting sublicensing without requiring that sublicensees be bound by confidentiality and IP protection terms at least as strict as the main agreement. A breach by an unsupervised sublicensee can expose the licensed IP to the public domain or a competitor.
In plain language: Obliges both parties to protect each other's confidential information β including source code, product roadmaps, and pricing β and limits use to the purposes of the agreement.
Each party agrees to hold the other's Confidential Information in strict confidence using no less than reasonable care, not to disclose it to any third party without prior written consent, and to use it solely to exercise the rights or fulfill the obligations under this Agreement. These obligations survive termination for [5] years.
Common mistake: Setting a confidentiality survival period of only 1 year. For technology licensing, trade secrets can retain commercial value for much longer β a short survival window leaves the disclosing party unprotected after termination.
In plain language: Each party warrants that it owns or has the right to license its IP, that the licensed IP does not infringe third-party rights, and agrees to indemnify the other party against IP infringement claims arising from its own IP.
Each party represents and warrants that: (a) it has full authority to grant the licenses herein; (b) the Licensed IP does not, to its knowledge, infringe any third-party intellectual property rights. Each party shall indemnify, defend, and hold harmless the other from any third-party claim alleging that the indemnifying party's Licensed IP infringes a third party's IP rights.
Common mistake: Omitting a mutual indemnification for IP infringement claims and relying only on an 'as-is' disclaimer. If a third party sues the licensee claiming the licensed IP infringes its patent, the licensee has no recourse against the licensor without an explicit indemnity clause.
In plain language: Sets the duration of the agreement, the conditions under which either party may terminate early (for cause or convenience), and the notice periods required.
This Agreement commences on the Effective Date and continues for [3] years ('Initial Term'), renewing automatically for successive [1]-year terms unless either party provides [90] days' written notice of non-renewal. Either party may terminate for cause upon [30] days' written notice if the other party materially breaches and fails to cure within the notice period.
Common mistake: No cure period for material breach before termination is permitted. Immediate termination rights are often disproportionate for a first breach and expose both parties to costly litigation over whether a breach was actually material.
In plain language: Governs what each party may and must do after the agreement ends β including inventory sell-off periods, return or destruction of confidential information, and survival of key clauses.
Upon termination, each party shall: (a) cease all use of the other party's Licensed IP within [30] days; (b) return or certify destruction of all Confidential Information; and (c) may sell existing inventory of Licensed Products for up to [90] days post-termination ('Sell-Off Period'), subject to continued royalty obligations. Sections [Ownership, Confidentiality, Indemnification, Governing Law] survive termination.
Common mistake: Failing to specify which clauses survive termination. Without explicit survival language, courts in some jurisdictions interpret termination as extinguishing all obligations β including confidentiality and indemnification β which defeats the purpose of those clauses.
Enter each company's registered legal name, jurisdiction of incorporation, and principal address. Confirm these against corporate registry filings before execution.
π‘ Using a trade name instead of the registered entity name can void the agreement or create enforcement gaps if the trade name is not formally registered.
Attach a Schedule listing each party's licensed IP by patent number, software product name and version, or trade secret category. Vague descriptions like 'all technology' create scope disputes.
π‘ For software, include version numbers and specify whether source code, object code, or both are licensed β the distinction has major implications for what the licensee can do with the IP.
Define exactly what products or applications the licensee may incorporate the IP into, and in which countries or regions. Use Schedule A for Party A's license terms and Schedule B for Party B's.
π‘ If the field of use is intended to be narrow, list the excluded uses explicitly β courts read ambiguity in favor of the licensee in most jurisdictions.
Agree on royalty percentages or per-unit fees for each direction of the license, define 'Net Revenue' precisely, and specify payment frequency, late-payment interest, and audit rights.
π‘ Build in an annual audit right allowing each party to inspect the other's royalty records on 30 days' notice β it rarely gets used but deters underreporting.
Decide before drafting whether derivative works belong to the creating party, the original IP owner, or are jointly owned. Document the decision in the clause and in the negotiation record.
π‘ Default to ownership by the creating party with a license-back to the original IP owner β this is the simplest structure and avoids joint-ownership deadlocks.
If either party needs to sublicense to contract manufacturers or distributors, specify that sublicenses must be in writing, contain equivalent IP protections, and that the sublicensor remains liable for sublicensee compliance.
π‘ Require written approval from the other party for any sublicense granted to a competitor β add a 'no sublicense to competitors' carve-out to protect both parties.
Set the initial term, auto-renewal intervals, notice periods for non-renewal, cure periods for material breach, and the sell-off window for existing inventory after termination.
π‘ A 90-day sell-off period is standard for hardware products; software licenses typically allow a shorter 30-day transition window.
Both authorized signatories must execute the agreement before any licensed IP is delivered, disclosed, or integrated. Post-facto signatures create consideration and enforceability problems for IP assignment and confidentiality clauses.
π‘ Use a countersignature process β send for signature in the order that creates the least negotiating leverage risk, typically having the party with less negotiating power sign first.
An OEM reciprocal license agreement is a contract between two companies in which each grants the other defined rights to use, integrate, and distribute its intellectual property within their respective products. Unlike a one-way license, both parties are simultaneously licensors and licensees, creating symmetrical rights and obligations. It is most commonly used when a hardware manufacturer and a software vendor are integrating each other's technology into a jointly sold or bundled product.
The terms are often used interchangeably, but a reciprocal license typically implies that the license grants are conditional on each other β meaning if one party's license is terminated, the other's terminates too. A cross-license is a broader term covering any arrangement where two parties license IP to each other, which may be structured independently so that each license stands alone. In practice, most OEM agreements use a reciprocal structure to preserve the mutual dependency that drove the partnership.
Use an OEM reciprocal license agreement when both parties are contributing IP that the other needs to integrate into their product. A standard software license is unilateral β one party grants rights to the other. If your arrangement involves mutual IP exchange, co-bundling, or technology integration flowing in both directions, a reciprocal structure is more appropriate and provides both parties with the protections they need.
No. A license agreement grants rights to use IP without transferring ownership. Each party retains full title to its own intellectual property. The reservation-of-rights clause confirms this explicitly. If you intend to transfer ownership β for example, of jointly created derivative works β you need an assignment clause in addition to the license grant, and the receiving party typically needs to provide separate consideration.
Not necessarily. Some reciprocal licenses are structured as royalty-free cross-licenses where both parties agree the exchange of IP rights is sufficient consideration. However, when the IP contributed by each party has meaningfully different commercial value, a royalty structure β often with a net balancing payment β more accurately reflects the economics of the deal. Royalty-free structures are more common between partners of comparable market position.
A field-of-use restriction limits the contexts in which a licensee may use the licensed IP β for example, 'only in consumer medical devices sold in the European Union.' It matters because without it, a licensee could use the IP in any product or market, including ones where the licensor competes directly. Narrowly drafted field-of-use clauses protect the licensor's other markets and revenue streams while still enabling the partnership.
Ownership of derivative works is one of the most negotiated provisions in OEM licensing. Common structures include: the creating party owns all derivative works with a license-back to the original IP owner; the original IP owner owns all derivatives created from its IP; or both parties jointly own derivatives. Joint ownership is the most problematic because it typically requires both parties' consent to commercialize the jointly owned work. Most practitioners recommend assigning derivatives to one party with a defined royalty-bearing or royalty-free license-back.
Yes, in most cases. OEM reciprocal license agreements involve complex IP rights that intersect with patent law, copyright law, trade secret protection, and β depending on the industry β export control regulations. The stakes of an error (unbounded license, loss of IP ownership, or unenforceable indemnity) are significant. For deals involving material IP, a 2β4 hour review by an IP attorney typically costs $600β$1,500 and is worthwhile. For straightforward arrangements between established partners, a well-structured template may be sufficient for initial terms.
Upon termination, both license grants typically end, and each party must cease using the other's IP β except during any negotiated sell-off period for existing inventory. Clauses covering confidentiality, indemnification, ownership, and governing law generally survive termination. The specific post-termination obligations should be enumerated explicitly in the agreement rather than relying on general survival language.
A unilateral OEM license grants rights in only one direction β the technology vendor licenses IP to the OEM, with no reciprocal rights flowing back. Use a unilateral agreement when only one party is contributing licensable IP and the other is purely a manufacturer or distributor. The reciprocal structure is necessary when both parties are integrating each other's technology and need symmetrical protections.
A software license agreement governs the right to use a specific software product and is typically unilateral β one licensor, one licensee. It does not contemplate mutual IP exchange, co-bundling of hardware and software, or reciprocal royalty flows. An OEM reciprocal license agreement is the appropriate instrument when the relationship involves integration of both parties' technology rather than a simple software purchase.
A joint development agreement governs the collaborative creation of new IP, allocating ownership of jointly developed output and setting contribution obligations. An OEM reciprocal license agreement governs the mutual use of each party's existing background IP in their respective products. Many partnerships need both: a joint development agreement for the co-creation phase and an OEM reciprocal license for the commercialization phase.
A technology transfer agreement typically involves the permanent assignment or deep disclosure of IP β including source code, manufacturing know-how, or patented methods β from one party to another. An OEM reciprocal license agreement grants use rights without transferring ownership. If your arrangement involves handing over source code or manufacturing processes as an ongoing operation rather than a licensed right, a technology transfer agreement is more appropriate.
Hardware OEMs license embedded software IP from technology vendors while granting access to hardware reference designs, requiring precise field-of-use and sublicense-to-contract-manufacturer provisions.
Vehicle manufacturers and Tier 1 suppliers exchange firmware, sensor algorithms, and connectivity software IP, often with export control compliance overlays and safety-critical warranty carve-outs.
Platform companies license APIs and SDKs to hardware OEM partners while receiving integration data or co-branding rights, with version-specific field-of-use restrictions and audit rights for usage reporting.
Medical device manufacturers and software companies exchanging diagnostic algorithms and hardware IP must address FDA 510(k) implications, HIPAA data use restrictions, and heightened indemnification for clinical liability.
US patent law allows the patent holder to grant field-of-use restricted licenses, which are fully enforceable. Non-compete provisions occasionally bundled into OEM agreements are subject to state-law variation β California and several other states restrict them significantly. The Defend Trade Secrets Act (DTSA) provides a federal cause of action for trade secret misappropriation, making robust confidentiality language especially valuable. Export Administration Regulations (EAR) and ITAR may apply if the licensed technology is subject to export controls.
Canadian intellectual property law follows common-law principles broadly similar to the US, but the Patent Act and Copyright Act have distinct provisions that can affect the scope of license grants. Quebec's civil law system may interpret contract terms differently from common-law provinces, so governing-law and dispute-resolution clauses should specify which provincial law applies. The Protecting Canadians from Online Crime Act and PIPEDA may impose additional obligations if the licensed technology processes personal data.
Post-Brexit, UK IP law is largely independent of EU frameworks, though it remains closely aligned in practice. The UK Patents Act 1977 and Copyright, Designs and Patents Act 1988 govern the underlying rights being licensed. Exclusivity provisions in OEM licenses may require notification to the Competition and Markets Authority if the parties have significant market shares. Consideration must be adequate under English law β royalty-free cross-licenses between parties of equivalent bargaining power are generally enforceable as mutual consideration.
The EU Technology Transfer Block Exemption Regulation (TTBER) provides a safe harbor for IP licensing agreements between non-competing parties with market shares below 30% each and between competitors below 20%. Agreements outside the safe harbor require individual assessment for EU competition law compliance. GDPR applies if the licensed software or technology processes personal data of EU residents, requiring data processing terms to be addressed separately or incorporated by reference. Field-of-use restrictions that segment EU member state markets may raise single-market concerns under Article 101 TFEU.
| Path | Best for | Cost | Time |
|---|---|---|---|
| Use the template | Early-stage technology partnerships with straightforward mutual IP exchange and limited royalty complexity | Free | 1β2 hours to complete |
| Template + legal review | Mid-market OEM deals involving material IP, meaningful royalty flows, or cross-border licensing between two established companies | $600β$1,500 for an IP attorney review | 3β7 days |
| Custom drafted | Complex multi-product licensing platforms, regulated industries (MedTech, automotive safety), deals with significant patent portfolios, or arrangements involving source code escrow | $3,000β$10,000+ | 2β6 weeks |
This document is one of 3,000+ business & legal templates included in Business in a Box.
Access over 3,000+ business and legal templates for any business task, project or initiative.
Customize your ready-made business document template and save it in the cloud.
Share your files and folders with your team. Create a space of seamless collaboration.
"Fantastic value! I'm not sure how I'd do without it. It's worth its weight in gold and paid back for itself many times."
"I have been using Business in a Box for years. It has been the most useful source of templates I have encountered. I recommend it to anyone."
"It has been a life saver so many times I have lost count. Business in a Box has saved me so much time and as you know, time is money."
Stop downloading documents. Start operating with clarity. Business in a Box gives you the Business Operating System used by over 250,000 companies worldwide to structure, run, and grow their business.
Start freeΒ Β·Β No credit card required
