Software Value-Added Reseller Agreement
For Informational Purposes Only
A channel distribution agreement for software companies that sell through resellers, OEM partners, or white-label distributors — covering license rights, end-user terms, revenue share, IP, and exit planning.
What This Document Does
This agreement structures the relationship between a software company (the “Licensor”) and a value-added reseller (“VAR”) that distributes the software to end users, either embedded in the VAR’s own product, resold as a hosted service, or distributed as a standalone product through the VAR’s channel. It maps the complete rights chain from licensor to reseller to every end user.
The template covers three distribution models (embedded OEM, SaaS resale, and standalone sublicense), with tailored provisions for each. It includes the license grant and restrictions, mandatory end-user license terms, revenue mechanics and reporting, IP allocation, trademark usage, data and security responsibilities, warranty and indemnity flows, and detailed termination and end-user continuity provisions across six exhibits.
Why Startups Need This
Selling software through channel partners is one of the fastest ways to scale distribution without building a direct sales force. But channel relationships create layered legal complexity that a standard license agreement does not address. The licensor needs to control how its software reaches end users, ensure consistent license terms downstream, protect its IP, and maintain visibility into who is using the product. The VAR needs clear distribution rights, reasonable economics, and certainty about what happens to its customers if the relationship ends.
Without a well-structured agreement, common problems include: VARs making unauthorized representations about the software, unclear ownership of integration code, revenue disputes from bundled deals, and stranded end users when the channel relationship terminates. This template addresses each of these scenarios with specific, practical provisions.
Key Provisions Explained
Three Channel Model Elections
The agreement recognizes that “reselling software” can mean very different things. Under the Embedded OEM model, the VAR integrates the software into its own product — end users may not even know the underlying software exists. Under SaaS Resale, the VAR resells access to a hosted version, either white-labeled or co-branded. Under Standalone Sublicense, the VAR distributes the software as-is through its sales channel. Each model has different implications for who is the merchant of record, who provides support, and how the license chain flows.
Mandatory End-User License Terms
Every end user must accept a EULA that meets minimum requirements specified in Exhibit B. This protects the licensor even though it has no direct contract with end users. The EULA must include IP protections, use restrictions, warranty disclaimers, liability limits, and critically, the licensor’s right to enforce EULA terms as a third-party beneficiary. The VAR must maintain assent records for the duration of each end-user relationship plus three years.
Revenue Share and Audit Rights
The fee structure is fully configurable in Exhibit C — per-unit, percentage of net revenue, minimum commitments, or hybrids. The VAR must submit regular transaction reports with customer details, versions, and territory. The licensor has annual audit rights with a practical cost-shifting mechanism: the licensor pays unless the audit reveals underpayment exceeding 5%, in which case the VAR covers the audit cost plus the deficiency.
Bilateral Indemnification
The licensor indemnifies against IP infringement claims relating to the unmodified software. The VAR indemnifies for everything in its control — its integrated products, marketing claims, modifications, data practices, and legal compliance. This allocation reflects the practical reality: each party is best positioned to defend against claims arising from its own conduct and materials.
End-User Continuity on Termination
One of the most consequential provisions in any channel agreement is what happens to existing customers when the relationship ends. The template presents three options: end-user licenses survive for their current term, licenses terminate with notice, or customers migrate to a direct licensor relationship. The choice is made at signing and documented in Exhibit B, so neither party is surprised when the time comes. A limited sell-off period lets the VAR fulfill committed orders.
Emerging Provisions (2025–2026)
Franchise and Competition Law Gates
A VAR agreement that involves trademark licensing, territorial restrictions, required fees, and operational controls can inadvertently trigger franchise disclosure requirements in many states. The agreement includes an independent-contractor and no-franchise disclaimer, but more importantly, the structure is designed to avoid the substance of a franchise relationship. Counsel should review the specific combination of trademark use, control, fees, and territory before execution.
Data-Flow Role Mapping
Channel relationships create complex data-processing questions. Exhibit E requires the parties to map data flows, assign controller and processor roles, and document the lawful purpose for each flow. The VAR cannot transmit end-user data to the licensor unless both parties have documented why and under what authority. This structure reflects the accountability requirements of GDPR, CCPA, and emerging state privacy laws.
Tiered Termination Triggers
Not all breaches are equal. The agreement distinguishes between ordinary material breaches (which get a cure period), and immediate-termination events — unauthorized source-code access, material security threats, unlawful distribution, or conduct that damages the software brand. This tiered approach gives the licensor fast response tools for the most serious violations while preserving notice-and-cure for routine commercial disputes.
How to Use This Template
Start by selecting the channel model in the Agreement Summary — this drives the license grant, merchant-of-record allocation, and support structure throughout the document. Then work through the six exhibits, which contain the commercial and operational specifics: the software and integration specifications (A), minimum EULA terms (B), territory, fees, and reporting (C), support and warranty (D), data and security (E), and trademark guidelines (F).
If you are the software company, pay particular attention to the EULA requirements (Exhibit B) and the end-user continuity provisions — these protect your relationship with the end-user base regardless of what happens with the VAR. If you are the VAR, focus on the fee structure (Exhibit C), the exclusivity terms, and the termination provisions, particularly sell-off rights and customer continuity. Both sides should have counsel review the agreement before execution.
Related Forms
This template is provided by Montague Law for informational and educational purposes. It does not constitute legal advice and does not create an attorney-client relationship. Channel distribution agreements involve complex intellectual property, competition law, franchise law, and data-protection considerations. Consult qualified legal counsel before using this template. Montague Law is a Florida-based law firm focused on corporate, M&A, venture capital, and technology transactions.