How to Draft a SaaS Reseller Agreement (2026 Template and Clauses)

A SaaS reseller agreement is the contract between a software vendor and a partner who sells the vendor's subscription software to end customers. It is different from reselling physical goods, because the product is a continuing cloud service with subscriptions, renewals, usage based pricing, service levels and personal data flowing through it. Getting the agreement right means handling the recurring revenue model, the chain of terms that must reach the end customer, who controls the customer relationship, and how data protection obligations flow down. This guide explains what a SaaS reseller agreement must cover, the clauses that cause the most disputes, and gives a usable drafting skeleton. It is general information and not legal advice; data protection and competition rules apply to distribution, so confirm the local position before relying on any clause. ## What is a SaaS reseller agreement, and which model are you using? Use a SaaS reseller agreement when a partner will sell your subscription software to its own customers (or when you are the partner selling someone else's). Before drafting, choose the model, because it changes who contracts with the end customer and who recognises the revenue. - Reseller (buy and resell): the partner buys subscriptions from the vendor and resells them to end customers at its own price, usually contracting directly with the end customer. The partner carries credit risk and owns the customer relationship.

• Referral or agent: the partner introduces customers and earns a commission; the vendor contracts with and bills the end customer. Lower risk for the partner, less control.
• Distributor (two tier): the partner sells on to sub resellers rather than to end customers.
• White label or OEM: the partner sells the software under its own brand. (This is a distinct contract type with its own branding, support and IP terms.) State the model clearly, because it determines flow of contract, billing, data controller or processor roles, and liability. ## What clauses must a SaaS reseller agreement contain? A strong SaaS reseller agreement covers the following. ### Parties, term and appointment Identify the parties, set the term and renewal, and define the appointment: the products, the territory, the customer segments, and whether the appointment is exclusive or non exclusive. ### Grant of rights Grant the partner the right to market and resell the subscriptions (and to use trademarks for that purpose), within defined limits. Make clear the partner gets no rights in the software itself beyond reselling access. ### The end customer terms and flow down Critical for SaaS. The vendor's end user licence or subscription terms, acceptable use policy, and service levels must reach and bind the end customer. State whether the partner must pass through the vendor's terms, incorporate them, or use its own terms that are no less protective of the vendor. A gap here leaves the vendor exposed to an end customer it has no contract with. ### Pricing, discounts, billing and renewals Set the wholesale price or discount to the partner, whether the partner sets the end price, the billing model (upfront, monthly, usage based), and how subscriptions renew. Define what happens to pricing on renewal and on uplift, and who handles end customer billing and collection. ### Orders, provisioning and the subscription lifecycle Define how orders are placed and provisioned, how subscriptions are activated, suspended, upgraded, downgraded and terminated, and how mid term changes are handled. The recurring lifecycle is what makes SaaS reselling different from a one off sale. ### Service levels, support and escalation State the service levels for the platform, who provides first line and second line support (often the partner front line, the vendor back line), and the escalation path. Align the service credits the vendor gives with what the partner promises end customers. ### Data protection and security Because personal data flows through the software, define the data protection roles (controller, processor, sub processor) and attach a data processing agreement. Address security obligations, breach notification, sub processing and data location. Comply with the applicable regimes (for example the Digital Personal Data Protection Act 2023 in India, the GDPR in Europe, UK GDPR, and others). The vendor confirms it does not reuse customer data beyond providing the service; state the position clearly. ### Intellectual property and feedback Confirm the vendor owns the software and IP, the limited trademark licence for resale, and ownership of any feedback or configuration. ### Partner obligations and conduct Set minimum commitments (if any), sales and marketing conduct, accurate representation of the product (no promises beyond the published capabilities), certification or training requirements, and compliance with law (anti bribery, sanctions, competition). ### Confidentiality Protect each party's confidential information, including pricing and the customer and prospect data shared. ### Warranties, liability and indemnity Set the vendor's platform warranty and the partner's conduct warranties, limitation of liability (usually capping direct liability and excluding consequential loss, with carve outs for IP infringement, data breach and confidentiality), and indemnities (the vendor for IP infringement of the software, the partner for its own misrepresentations and unauthorised promises). ### Term, termination and transition of customers Grounds for termination, notice, and the single most important SaaS specific issue: what happens to live end customer subscriptions on termination. Define whether subscriptions transfer to the vendor or another partner, continuity of service for end customers, data export and handover, and run off of in term subscriptions so customers are not cut off. ### Dispute resolution and governing law Governing law, jurisdiction, and arbitration or court. ## A usable SaaS reseller agreement skeleton 1. Title and date

2. Parties
3. Recitals
4. Definitions and interpretation
5. Appointment, model and term (reseller, referral or distributor)
6. Grant of rights and restrictions
7. End customer terms and flow down
8. Pricing, discounts, billing and renewals
9. Orders, provisioning and subscription lifecycle
10. Service levels, support and escalation
11. Data protection, security and the data processing agreement
12. Intellectual property and trademark licence
13. Partner obligations, certification and compliance
14. Confidentiality
15. Warranties, limitation of liability and indemnities
16. Term and termination
17. Transition of end customers on termination (continuity, data export, run off)
18. Dispute resolution and governing law
19. General clauses (notices, assignment, entire agreement, variation)
20. Schedules (products and pricing, SLA, support model, data processing agreement, trademark guidelines) ## How does a SaaS reseller agreement differ by jurisdiction? The structure is broadly consistent, but two areas vary sharply. - Data protection: the controller and processor roles, the required contract terms, breach notification timelines and cross border transfer rules differ by regime (for example the Digital Personal Data Protection Act 2023 in India, the GDPR and UK GDPR in Europe and the UK, and others). The data processing agreement must match the applicable law.

• Competition and distribution law: exclusivity, resale price maintenance, territory and customer restrictions can be limited by competition law, which differs by country (the EU has detailed rules on vertical agreements). Overly tight restrictions can be unenforceable. Confirm the data protection regime and the competition limits before relying on your drafting, and verify the depth of local support where you resell across markets. ## Drafting, reviewing and tracking a SaaS reseller agreement in one workspace Drafting a SaaS reseller agreement from a reliable template, reading a partner's or vendor's draft clause by clause for the risky terms (end customer flow down, data protection roles, liability caps, customer transition on exit), keeping versions straight through negotiation, and then tracking the obligations once signed (renewal dates, minimum commitments, certification deadlines, term and notice windows) is work most commercial and legal teams do by hand across documents and spreadsheets. It is also work an AI contract workspace can hold in one place. A system like Adira can draft from a brief and your preferred positions, read a draft and flag where flow down, data protection, liability or termination terms sit against your interests clause by clause, let you edit clauses in plain language with a clear diff, and pull the dated obligations (renewals, commitments, certification, notice windows) into a tracked timeline with reminders. The idea is simple: the drafting, review, version control and tracking a reseller relationship needs can live in one workspace tuned to how your company contracts, rather than scattered tools. Have the final agreement reviewed by qualified counsel before signing.