The Complete Guide to Drafting Value-Added Reseller (VAR) Agreements

A detailed guide on creating a Value Added Reseller (VAR) Agreement using foundation, primary, secondary and schedule building blocks.
Value Added Reseller (VAR) Agreement Building Blocks


Value Added Reseller Agreement

A Value Added Reseller (VAR) agreement for software is like a partnership between two companies: one that makes the software (let’s call them “Software Company”) and another that wants to sell it (let’s call them “Reseller Company”).

Here’s how it works:

The Software Company creates a software product. The Reseller Company sees the software and thinks it would be useful for their customers, but they also see a chance to add even more value. This could be in the form of additional features, services like training or support, or packaging it with their own products.

They come to an agreement, which is the VAR agreement. In this agreement, the Reseller Company gets the rights to sell the Software Company’s software, usually along with their added value.

So, to put it simply, a VAR agreement for software is a deal where one company can sell another company’s software, often with their own enhancements, and they share the revenue from those sales. This is beneficial for both companies. The Software Company gets more sales and exposure, and the Reseller Company can offer a more valuable product to their customers.

Different types of Value Added Reseller Agreements

  • System Integrator VAR: A system integrator VAR is a company that not only resells the software but also integrates it into the existing systems of the customer. This means they make sure the software works well with the customer’s current setup and helps achieve their business goals. They often deal with complex IT projects that involve various software products and systems.

  • Solutions Provider VAR: A solutions provider VAR goes beyond just reselling software. They package the software with other products and services to create a complete solution for the customer’s problem. This might include hardware, additional software, or services like training and support. The goal here is to provide an all-in-one solution to meet the specific needs of the customer.

  • Managed Service Provider VAR: A Managed Service Provider (MSP) VAR is a company that manages and operates the software for the customer as part of their service. This often includes ongoing support, maintenance, and optimization of the software. This is often used for complex or specialized software that requires expert knowledge to manage effectively.

  • Consultant VAR: A consultant VAR provides expert advice and guidance on how to best use the software to achieve the customer’s goals. They might also provide services like training, implementation, and ongoing support. The consultant VAR will typically have deep knowledge of the industry or business processes related to the software.

  • Customization VAR: A customization VAR modifies the original software to better fit the specific needs of the customer. This might involve adding new features, changing the user interface, or integrating with other systems the customer uses. This can be especially valuable when the customer has unique needs that aren’t met by the standard version of the software.

What is the difference between an OEM Agreement and a VAR Agreement?

Original Equipment Manufacturer (OEM) agreements and Value-Added Reseller (VAR) agreements are both licensing agreements in the IT world, allowing a company to bundle another company’s software with its own product. However, there are key differences between these two types of agreements.

In an OEM agreement, the distributor is often a manufacturer of hardware equipment. This type of agreement is for a company to license its software products to an original equipment manufacturer. The OEM can then bundle the licensor’s software with its own products, which can include hardware, software, mobile devices, or other technology. The resulting integrated product is then resold to customers, typically under the OEM’s brand name.

For example, a computer manufacturer like Dell might enter into an OEM agreement with Microsoft to include Microsoft’s Windows operating system pre-installed on its computers. When you buy a Dell computer, it comes with Windows already installed. In this case, Dell is the OEM and the computers are sold under Dell’s brand name.

On the other hand, a VAR agreement involves a company, known as a value-added reseller, that adds features or services to an existing product, then resells it as an integrated product or complete “turn-key” solution. This could involve either hardware or software. Similar to an OEM agreement, a VAR agreement allows a software company to license its software products to a value-added reseller. The VAR can bundle the licensor’s software with other products or components and sell the integrated product to end-users, typically under the licensor’s brand name.

For instance, a VAR might take a CRM (Customer Relationship Management) software, add custom features or integrations specific to a certain industry, and then sell the whole package to businesses in that industry. In this case, the product is usually sold under the original software licensor’s brand name.

In summary, while both OEM and VAR agreements involve bundling and reselling products, the key differences lie in the nature of the distributor (equipment manufacturer vs value-added reseller), the type of products involved (typically hardware for OEMs and potentially both hardware and software for VARs), and the branding under which the final product is typically sold (OEM’s brand for OEM agreements and licensor’s brand for VAR agreements).

Build your own custom VAR Agreement now!

Foundation blocks


The typical parties to a Value Added Reseller (VAR) agreement are the software developer/manufacturer/provider, and the Value Added Reseller (VAR) itself.

  • Software Developer/Provider: This party is typically the creator or owner of the software product that will be resold. They may be referred to in the VAR agreement as the “Provider”, “Licensor”, “Manufacturer”, or “Developer”, depending on the context.

  • Value Added Reseller (VAR): This is the party that adds features or services to the existing product, then resells it as a combined product or complete “turn-key” solution. They may be referred to as the “Reseller”, “Distributor”, “Partner”, or “VAR”.

Background / recitals

Preamble sections offer a glimpse into the background and aim of the Value Added Reseller (VAR) agreement. While they’re not a legal necessity and don’t carry direct legal consequences, they can be invaluable in clarifying the interpretations of the agreement’s active terms should a disagreement arise.

This VAR agreement outlines fundamental preamble elements pertinent to any software reselling arrangement. Given the specific nature and terms of the arrangement, the parties might decide to include more detailed information or choose to omit the fundamental preamble elements.

VAR appointment

There are a number of different parts making up the foundation block of a VAR. These parts include –

  • Appointment: This is where the agreement formally designates the VAR as a reseller of the software. It outlines the rights and responsibilities of the VAR, and sets out the terms under which the VAR is allowed to sell the software. It’s important because it establishes the official relationship between the two companies.

  • Software and Documentation License Grant: This section gives the VAR the rights to use the software and related documentation. It’s usually necessary so the VAR can understand the software, demonstrate it to potential customers, and provide support.

  • Restrictions: This part details any limitations on the VAR’s use and resale of the software. This could include restrictions on selling in certain regions, to certain types of customers, or in certain ways. It’s needed to protect the software company’s interests and control how their software is sold and used.

  • End User License Agreement (EULA): This outlines the rights and responsibilities of the end users of the software. It’s often provided by the software company and must be agreed to by the customers of the VAR. It’s crucial for setting out the legal terms of using the software and protecting the rights of both the software company and the VAR.

  • Marketing Guidelines: This section explains how the VAR is allowed to market and advertise the software. This can include rules about using the software company’s trademarks and branding. It helps ensure the software is represented accurately and professionally.

  • Integration: This part details the rights and responsibilities of the VAR in terms of integrating the software with other systems. This is often relevant for system integrator VARs or customization VARs. It’s important because it sets out what the VAR is allowed to do in terms of modifying or connecting the software to other systems.

  • Testing: This section can outline any requirements for the VAR to test the software, particularly if they’re integrating it with other systems or modifying it in any way. It helps ensure the software works correctly and meets certain standards.

  • Change to Software: This part outlines the software company’s right to make changes to the software and the requirements relating to notice which needs to be given to the VAR.

  • New Versions: This part describes how the agreement applies to new versions of the software released by the software company. It’s necessary to ensure that the VAR and their customers can benefit from updates and improvements to the software.

  • Maintenance Releases: This part details how maintenance updates (bug fixes, security patches, etc.) are handled. It might specify whether the VAR or the software company is responsible for providing these updates to the end users. It’s vital for keeping the software secure and working correctly.

Primary Blocks

Limitation of liability

[View detailed guide on limitation of liability provisions ↗]

In the realm of Value Added Reseller (VAR) agreements, limitation of liability blocks play a crucial role for both software companies and VARs. These blocks provide a mechanism to manage risk and limit potential financial exposure that could arise due to the execution of the contract. Let’s delve into why both parties might want to include these blocks in their VAR agreements:


Why Software Companies want Limitation of Liability Blocks in VAR Agreements:

  • Protection from Excessive Financial Liability: Software creation and distribution come with potential risks and unexpected problems. Limitation of liability blocks shield software companies from excessive financial responsibility, which could prove calamitous in the event of a major issue.
  • Allocation of Risk: With these blocks, software companies can distribute risk more equitably between themselves and the VAR. This approach helps ensure that the software company isn’t solely accountable for all potential issues that could crop up during the resale or use of the software.
  • Predictability: Understanding their maximum liability allows software companies to manage their finances more effectively. This level of predictability aids them in making informed business decisions and allocating resources appropriately.
  • Focus on Core Competencies: Limiting their liability allows software companies to concentrate on their key competencies, like developing and updating software, assured that there’s a safety net to protect them from excessive claims.

Why VARs want Limitation of Liability Blocks in VAR Agreements:

  • Allocation of Risk: Similar to software companies, VARs also profit from an equitable risk distribution. These blocks help protect VARs from being held accountable for issues outside of their control, such as software bugs or unanticipated technical problems.
  • Financial Certainty: By knowing the extent of the software company’s liability, VARs can plan more effectively for any potential financial exposure related to their resale of the software. This helps them manage resources and budgets more effectively.

To summarize, limitation of liability blocks are advantageous for both software companies and VARs within VAR agreements. These blocks help manage risk, foster trust, and provide financial certainty for both parties, ultimately leading to a more successful and efficient software reselling process.


[View the detailed guide on indemnities ↗]

In the realm of Value-Added Reseller (VAR) agreements in the tech industry, indemnity clauses perform a crucial role. They control risk, provide protection against potential liabilities, and establish the foundation for managing unexpected issues during the resale of technology products and services. Here’s a high-level overview on why a reseller would want to include indemnity blocks in their agreements:

  • Intellectual property infringement: Indemnities for third-party intellectual property infringement claims are pivotal in safeguarding the reseller from potential legal issues if the technology product or service they are reselling infringes on existing patents, copyrights, trademarks, or trade secrets. For instance, if a technology provider unintentionally incorporates a patented algorithm into their product, the indemnity block shields the reseller from financial liability resulting from a third-party infringement lawsuit.
  • Third-party claims: Partnerships with other entities, such as other technology providers or third-party service providers, are commonplace in VAR scenarios. Indemnities against third-party claims can shield the reseller from financial liability if a collaborator alleges that the provider’s actions resulted in harm or loss. For instance, if a technology provider violates an agreement with a third-party software provider, leading to a lawsuit against the reseller, the indemnity block would obligate the provider to cover the reseller’s legal costs and any awarded damages.



[View the detailed guide on termination provisions ↗]

Incorporating detailed termination provisions in Value Added Reseller (VAR) agreements in the tech sector is crucial for an array of reasons. These blocks offer a well-defined structure for addressing potential concerns, safeguarding the interests of all parties involved, and ensuring a systematic and cordial end to the business relationship. Here are the critical reasons to include termination provisions in tech VAR agreements:


  • Transparency and predictability: Termination blocks specify the situations under which the agreement may be terminated and the processes to be adhered to. This transparency assists both parties in understanding their responsibilities, rights, and anticipations, thus minimizing the likelihood of misinterpretations and disputes.
  • Securing interests: Termination blocks help protect the interests of all parties in instances of contract breaches, subpar performance, or alterations in business requirements. For instance, a reseller might wish to dissolve the agreement if the tech provider doesn’t meet their obligations regarding support and assistance. On the other hand, a tech provider might opt to cancel the contract if the reseller doesn’t make prompt payments or meet expected sales quotas.
  • Adaptability: A termination for convenience part ensure adaptability in the business relationship, allowing either party to exit the agreement if circumstances change or the partnership no longer proves advantageous. For example, a reseller might need to terminate due to a change in market demand, while a tech provider might wish to end the agreement due to better opportunities or resource limitations.
  • Risk management: Termination blocks aid in managing risks related to the unpredictable and potentially challenging tech sector. By setting forth clear termination criteria, all parties can lessen potential damages and losses if unforeseen issues arise.
  • Supporting smooth transitions: Termination blocks often incorporate stipulations for transition assistance, such as the handover of product inventories, proprietary technology, or sales data. These provisions assure that all parties can effectively disengage from the agreement, minimizing disruptions to current operations, and facilitating a smoother transition to new arrangements or partners.
  • Legal compliance: Termination blocks can help respond to changes in legal or regulatory landscapes, allowing parties to dissolve the agreement if adherence becomes unfeasible or excessively difficult. For instance, if new cybersecurity regulations make it challenging for a reseller to continue marketing the tech products, a termination clause can offer an exit strategy for both parties.


[View the detailed guide on warranties ↗]

Including warranty blocks in a value-added reseller (VAR) agreement in the tech space is crucial for a multitude of reasons. These provisions play a pivotal role in forming a robust basis for the business relationship, safeguarding the interests of all parties involved, and ensuring the successful provision of tech products and related services. Here are several reasons why warranty provisions are significant in a VAR agreement:

  • Quality assurance: Warranty provisions in a VAR agreement assure that the resold technology products and related services meet specific quality standards, are free from substantial defects, and perform as described in the agreement. This promise bolsters confidence in the client and promotes a cooperative business relationship.
  • Clear performance expectations: Warranty provisions establish clear expectations for the performance of tech products and related services, ensuring that both the VAR and the client understand the minimum requirements for a successful agreement. This clarity helps avoid misinterpretations or disputes about the functionality or performance of the products or services.
  • Defined remedies: Warranty provisions specify the remedies available should the technology products or related services fail to meet the agreed-upon specifications or performance criteria. Remedies might include product replacements, service corrections, or even refunds in certain situations. Clearly defining these remedies can expedite the resolution process and preclude lengthy disputes or legal issues.
  • Risk allocation: Incorporating warranty provisions in a VAR agreement assists in dividing risks between the VAR and the client. The VAR is responsible for providing functional products and services that meet the defined requirements, while the client is obliged to provide accurate and complete product specifications and usage requirements. This division of risk establishes an equitable and transparent business relationship.
  • Legal protection: Warranty provisions offer legal safeguards for both parties in the event of disagreements or breaches. If a dispute arises, the warranty terms act as a guiding point for defining each party’s responsibilities and the suitable course of action to solve the problem.
  • Enhancing reputation: For VARs, providing warranties can improve their professional standing, reflecting their dedication to quality and client satisfaction. This commitment can foster increased trust and potentially open up further business opportunities.

Intellectual property

[View the detailed guide on intellectual property ↗]

Including intellectual property (IP) provisions in a value added reseller (VAR) agreement is pivotal for several key reasons. These provisions offer clarity on IP ownership, safeguard the interests of all parties involved, ensure correct use and governance of the IP, and create a framework for resolving any potential disputes.

  • Ownership and control: IP provisions in a VAR agreement delineate the ownership and control of intellectual property rights for both the products resold and the value-added components. For the products resold, the tech vendor typically retains ownership of all IP rights associated with the product, while the VAR is given a license to sell these products. For the value-added components, the VAR often retains ownership and provides the customer a license to use them under the terms of the agreement.
  • Protection of interests: Clearly outlined IP provisions help to secure the interests of both parties. The VAR’s interests are safeguarded as they acquire the necessary rights to sell and integrate the tech products to meet customer needs. The tech vendor’s interests are protected by maintaining ownership of their original IP and by preserving the capacity to license their IP to other resellers or use it for other purposes.
  • Proper use and commercialization: IP provisions in a VAR agreement enable the correct use and monetization of the resold tech products and value-added components. The VAR can sell, customize, or integrate the tech products within their solutions as per the license terms, while the tech vendor maintains the ability to license the product to other resellers or use it for their own projects.
  • Dispute resolution: IP provisions can also aid in resolving disputes related to the ownership and usage of the intellectual property. A meticulously crafted agreement can provide a clear comprehension of the rights and duties of each party, lessening the chances of disputes. In case of a disagreement, the provisions can serve as a foundation for resolving the issue, potentially circumventing expensive legal disputes.


[View the detailed guide on confidentiality ↗]

Incorporating a confidentiality block in a Value Added Reseller (VAR) agreement is critical for a variety of reasons. This block safeguards sensitive details, retain a competitive edge, protect intellectual property rights, and foster trust and cooperation between the involved parties. Here’s why confidentiality clauses are vital in a VAR agreement:

  1. Securing sensitive information: VAR arrangements often involve sharing valuable and confidential details, such as product features, technical documentation, pricing structures, and business plans. A confidentiality block obliges both parties to guard this information against unauthorized exposure or misuse, thus mitigating the potential risk of harm or misappropriation.

  2. Preserving competitive advantage: A company’s competitive advantage often hinges on the privacy of its proprietary technologies, processes, and strategies. By integrating a confidentiality block into a VAR agreement, parties can protect their unique offerings and trade secrets, helping them retain their competitive stance in the marketplace.

  3. Protecting Intellectual Property Rights: A confidentiality block contributes to the protection of the intellectual property rights of both parties in the VAR relationship.

  4. Promoting trust and collaboration: Confidentiality clauses help cultivate trust and collaboration between the VAR and the software provider. By mutually agreeing to safeguard each other’s confidential information, parties can freely exchange insights, knowledge, and expertise, cultivating a cooperative environment that is conducive to innovation and mutual success.

  5. Legal recourse for breaches: In the event of a confidentiality clause breach, the affected party can pursue legal action, including damages and injunctive relief, to remedy the harm caused by unauthorized disclosure or use of confidential data. This offers a safety measure for both parties and underscores the importance of adhering to confidentiality responsibilities.

Dispute resolution

[View the detailed guide on dispute resolution ↗]

Including a dispute resolution block in a Value-Added Reseller (VAR) agreement within the tech industry is vital for a multitude of reasons. It provides a distinct structure for solving disputes that may materialize during the agreement’s term, assuring that all parties comprehend their rights and responsibilities in the event of a disagreement. Below are key reasons why incorporating a dispute resolution block is critical in a VAR agreement:

  • Clear expectations: A dispute resolution block details the process to be followed should a dispute arise, including issues like contract breaches, intellectual property conflicts, or differences over product scope or pricing. This clarity simplifies the steps to take in case of a disagreement, reducing misunderstanding and allowing a more efficient resolution.
  • Efficiency in time and cost: Alternative dispute resolution (ADR) techniques, like arbitration or mediation, are generally swifter and more cost-effective than traditional litigation. By prescribing an ADR method in the dispute resolution block, parties can evade drawn-out legal battles, conserving time and resources by concentrating on resolving the dispute through a more simplified procedure.
  • Protection of confidentiality: ADR approaches such as arbitration and mediation usually offer more confidentiality than court litigation. Including a dispute resolution clause that mandates the use of an ADR method can safeguard sensitive data, including proprietary technology, confidential business strategies, or trade secrets, from public exposure during the dispute resolution process.
  • Control over procedure: A dispute resolution block provides parties the opportunity to customize the dispute resolution process to suit their particular needs. They can choose aspects such as governing law, location of dispute resolution, and the qualifications of the arbitrator or mediator. This adaptability allows the parties to choose a process that aligns best with the VAR agreement’s nature and their specific prerequisites.
  • Maintaining business relationships: ADR procedures are generally less confrontational than litigation, with an emphasis on collaborative problem-solving and achieving a mutually beneficial resolution. By incorporating a dispute resolution clause that fosters negotiation, mediation, or arbitration, parties can strive to resolve disputes amicably, preserving their business relationships.
  • Enforceability: A thoroughly composed dispute resolution clause can support the enforceability of any decision or settlement reached through the dispute resolution process in court. This offers both parties greater assurance and faith in the dispute resolution process’s outcome.

Force majeure

[View the detailed guide on force majeure ↗]

Incorporating a force majeure block into value added reseller (VAR) agreements in the tech industry is crucial due to the various risks and uncertainties that can arise in this dynamic sector. These provisions help manage the rights and responsibilities of the involved parties should unexpected circumstances beyond their control arise, potentially affecting their ability to fulfill their obligations under the agreement. Here are some reasons why it’s important to include force majeure provisions in VAR agreements:

  • Risk management: Force majeure provisions help distribute the risks linked with unforeseen events amongst the parties, making certain that no party is unjustly penalized for situations beyond their control. This supports a balanced and fair contractual relationship, thus promoting a productive business connection between the parties.
  • Legal shielding: If a force majeure incident arises, these provisions provide legal protection to the party affected, safeguarding them from liability for non-fulfillment or delayed execution of their contractual duties.
  • Establishing clear guidelines: These provisions set clear guidelines regarding the parties’ rights and duties in the face of force majeure events. This clarity reduces potential disputes and contributes to the stability of the contractual relationship.
  • Business continuity: Force majeure provisions often involve duties for the impacted party to minimize the effect of the event, such as implementing alternative solutions or contingency plans. This assists in maintaining business continuity for all parties and decreases the adverse consequences of unanticipated disruptions.
  • Termination provisions: In situations where a force majeure event persists for a prolonged period or makes performance impossible or commercially unfeasible, these provisions may allow for the agreement’s termination. This gives both parties an exit strategy, enabling them to reconsider their options and seek other arrangements if necessary.

Secondary Blocks

Software escrow

[View the detailed guide on source code escrows ↗]

Value added reseller (VAR) agreements in the tech space, much like software development agreements, involve a key element of dependency.

If the VAR agreement includes an source code escrow block, it offers an added layer of protection for the end user. In this case, the source code of the software will have been stored with a neutral third-party escrow agent. Should the VAR cease operations or fail to meet its contractual obligations— events typically specified as triggers in the agreement—the escrow agent would release the source code to the VAR. They could then engage other developers to maintain and update the software, ensuring the continuity of their operations.

Non-solicitation of key personnel

[View the detailed guide on non-solicitation of key employees ↗]

A non-solicitation of key employee block incorporated into value-added reseller agreement (VAR) aims to deter one party from trying to hire or recruit the other party’s essential personnel during the contract period or for a predetermined time following its conclusion. These provisions aim to safeguard the interests of both parties involved in the software development project and ensure the continued stability of their respective businesses.


[View the detailed guide on sub-contracting ↗]

This block outlines the terms and conditions under which a party can engage third-party contractors or subcontractors to perform specific obligations under the agreement. It may include requirements for notifying and obtaining approval from the other party and may define the primary party’s liability for the work of the subcontractor.

Financial stability

[View the detailed guide on financial stability ↗]

This block refers to the financial health of the parties involved in the value-added reseller (VAR) agreement. It may require each party to maintain a certain level of financial stability to ensure the project’s successful completion and mitigate risks associated with insolvency or financial distress.


[View the detailed guide on audits ↗]

An audit block allows one party to inspect and review the other party’s records, processes, and systems related to the contract. This is done to ensure compliance with the agreement, identify issues or discrepancies, and verify the quality of work. The block may specify the frequency, scope, and requirements for conducting audits.


[View the detailed guide on insurance ↗]

This block requires the parties to maintain adequate insurance coverage to protect against potential risks and liabilities arising during the course of the agreement. It may specify the types and minimum amounts of insurance, such as professional liability, general liability, or cyber liability insurance.

Compliance with laws and regulations

[View the detailed guide on compliance with laws ↗]

This block requires the parties to adhere to all applicable laws, regulations, and industry standards related to the value-added reseller (VAR) agreement. This may include data protection laws, intellectual property laws, and employment laws.


[View the detailed guide on boilerplate ↗]

Boilerplate bocks, while often considered standard, play a vital role in shaping the overall legal framework of a contract. As such, it is imperative to give these provisions careful consideration and ensure they align with the parties’ intentions and objectives. Neglecting the importance of boilerplate block can lead to unforeseen consequences and potential litigation.

Schedules blocks

Obligation schedule

Often the cause of disputes, the obligation schedule is likely one of the most important aspects of the value added reseller agreement. These schedules must be specifically tailored to the relationship with the aim to create clarity in respect of the various intricacies involved with a value added reseller agreement.  Here are a couple of obligations generally addresses as part of the obligation schedule-

  1. Marketing Obligations: The VAR is usually responsible for marketing the software to its customers. This could include obligations to use the software company’s trademarks correctly, to represent the software accurately, and to comply with any advertising or marketing guidelines set by the software company. The purpose of these obligations is to ensure that the software is marketed professionally and consistently.

  2. Business Operations: This could cover a wide range of obligations, such as maintaining adequate staffing levels, complying with relevant laws and regulations, providing a high standard of customer service, and maintaining the necessary infrastructure or systems to sell and support the software. These obligations ensure that the VAR is capable of selling the software and providing a good experience for the customers.

  3. Customers: The VAR might have obligations related to its customers, such as ensuring the customers agree to an End User License Agreement (EULA), providing adequate support and training to the customers, and maintaining a certain level of customer satisfaction. These obligations protect the rights of the software company and the customers, and ensure that the customers have a positive experience with the software.

  4. Financial Matters: This could include obligations for the VAR to pay the software company certain fees or royalties, to report on sales, and to manage any financial risks related to the resale of the software. These obligations ensure that the software company is compensated fairly for the software and has visibility into the VAR’s sales.

  5. Reporting: The VAR might be required to provide regular reports to the software company about sales, customer issues, market trends, or other relevant information. The purpose of these obligations is to provide the software company with visibility into how their software is being sold and used, and to ensure that the VAR is meeting its other obligations.

It’s important to tailor the obligations in a VAR agreement to the specific relationship because every VAR relationship is unique. The VAR might be selling the software in a different market, to different types of customers, or in combination with different services or products. The VAR’s capabilities, resources, and business practices might also vary. By tailoring the agreement to the specific relationship, both parties can ensure that their interests are protected, that the agreement is fair and realistic, and that they are setting the foundation for a successful partnership.

Fees and payment schedule

The fees and payment schedule in a Value Added Reseller (VAR) agreement lay out the financial terms of the relationship between the software provider and the VAR. Here are some parts that are commonly included:

  1. Reseller fees: This is the amount the VAR pays to the software provider for each copy of the software that they sell. It’s often a percentage of the software’s list price, but it could also be a flat fee. The purpose of this fee is to compensate the software provider for each sale.

  2. Payment terms: This specifies when the VAR must pay the reseller fees to the software provider. For example, the VAR might need to pay the fees within 30 days of the end of the month in which the software was sold.

  3. Reporting requirements: The VAR might be required to provide regular reports to the software provider detailing their sales of the software, which would include information like the number of copies sold, the price at which they were sold, and the total reseller fees owed.

  4. Late payment terms: If the VAR doesn’t pay the reseller fees on time, there might be late payment penalties, such as interest charges.

  5. Audit rights: The software provider might have the right to audit the VAR’s records to verify that the VAR has been reporting sales accurately and paying the correct amount of reseller fees.

The purpose of having a clear fees and payment schedule is to ensure that both parties understand their financial obligations, to compensate the software provider fairly for the use of their software, and to provide a mechanism to resolve any disputes about payments. This part of the agreement needs to be carefully negotiated to ensure that the relationship is profitable for both parties.

Error correction service level schedule

[View the detailed guide on service levels ↗]

Error correction service levels are critical in value-added reseller (VARs) agreements because they establish a clear process and timeline for addressing and rectifying any defects or malfunctions in the software product once the warranty and software maintenance phase is entered.

The nature of software is such that even with rigorous testing and quality assurance, errors can still occur once the software is in use. These errors can disrupt the VAR’s operations, resulting in potential financial loss and damage to their reputation.

By establishing error correction service levels, both parties agree on the expected response times and corrective actions, thereby minimizing the impact of any software issues on the customer’s operations. Furthermore, these service levels provide assurance to the customer about the provider’s commitment to maintaining the quality and reliability of their software product, which can foster trust and confidence in the business relationship.

EULA schedule

Often a then current EULA relating to the Software is attached to the value-added reseller agreement. This is the EULA contains the terms that the end-users agree to when using the Software.

Contract Builder

Build your own custom VAR Agreement now!

Ninja holding a laptop explaining tech contracts

Interested in our Contract Builder?

Table of Contents

Master contracts now
Elevate your career!

Try for free. No credit card required.

Elevate your legal game with ContractNinja.

Form part of the spearhead movement of shaping the global standard for tech contracts.