PartnersWatch
Agreements and policies

SaaS reseller agreement template

A free SaaS reseller agreement with the clauses generic ones skip, from who bills the customer and owns the data to price notice, white-label and exit.

By PartnersWatch ResearchPublished Reviewed

On this page
  1. When this agreement fits
  2. What reseller programs leave to the contract
  3. The template
  4. How to fill in each part
  5. Mistakes to avoid

Use this when a reseller is about to sell your software to its own customers and you both need something to sign. It covers the clauses that generic reseller agreements, many written for physical goods, leave out: who bills the customer, who owns the account and its data, provisioning, price-change notice, white-label, deal registration, support and the reseller's exit.

Wherever a clause offers options in square brackets, keep one and delete the rest. Fill in the braces, attach the three schedules, and have a lawyer in your jurisdiction review the result before anyone signs it.

When this agreement fits

It fits a reseller who sells your product to customers it already has a relationship with, such as an MSP adding your tool to the stack it manages for clients, or an agency bundling your software with its own services. The reseller signs up customers, and either bills them or earns a margin while you bill. If you're still deciding which partner model you need, affiliate vs referral vs reseller sets them side by side.

It doesn't fit partners who only send you leads. They don't provision accounts or support customers, so most of this agreement is dead weight for them. Use the affiliate program terms template for link-based partners, and a short referral agreement for people who make introductions.

What reseller programs leave to the contract

We checked the 87 reseller listings in the PartnersWatch directory for the topics this template covers. Each listing records what the brand's own partner page said on 2 October 2026. Of the 87, 42 publish any commission or margin terms, and only six put a number on the reseller track itself. Three mention white-label, four mention deal registration or deal protection, and none of the listings records anything about territories or exclusivity.

So the public page is a pitch, and the agreement is where the deal actually lives. Resellers who've signed with a few vendors will ask about every clause below, and it's faster to have an answer written down than to improvise one on the call. SaaS reseller programs has the full breakdown of what those 87 programs publish, and the reseller listings show each one.

The template

Template
{Vendor} Reseller Agreement
Agreement date: {date}

Between {Vendor legal name}, {address} ("Vendor")
and {Reseller legal name}, {address} ("Reseller").

1. Definitions
1.1 "Service" means {product name}, the hosted software Vendor provides by
    subscription, as described at {documentation URL}.
1.2 "Customer" means an organisation that subscribes to the Service through
    Reseller under this agreement.
1.3 "Customer Data" means any data a Customer or its users put into the Service.
1.4 "Price Book" means Schedule A: the plans, list prices and Reseller prices
    for the Service, with an effective date, as updated under section 6.
1.5 "Registered Deal" means an opportunity Vendor has approved under section 8.
1.6 "Territory" means {countries or regions / worldwide}.

2. Appointment
2.1 Vendor appoints Reseller as a [non-exclusive] / [exclusive, for {customer
    segment}, for {12} months and only while Reseller meets section 10]
    reseller of the Service in the Territory.
2.2 Unless 2.1 makes the appointment exclusive, Vendor may sell directly and
    appoint other resellers in the Territory, subject to section 8.
2.3 Reseller may not appoint sub-resellers or agents without Vendor's written
    consent.
2.4 Reseller is an independent business. It may not sign contracts, make
    commitments or accept liability on Vendor's behalf.

3. Customer terms
3.1 Before using the Service, each Customer must accept [Vendor's customer
    terms at {URL}] / [Reseller's customer agreement, which must include at
    least the terms in Schedule C].
3.2 Reseller may not promise Customers anything about the Service (features,
    uptime, security, roadmap) beyond Vendor's published documentation and
    service levels.

4. Billing and payment
   [Option A: Reseller bills the Customer]
4.1 Reseller invoices and collects from its Customers at prices it sets.
4.2 Vendor invoices Reseller {monthly in advance} for every active Customer
    subscription at the Reseller price in the Price Book. Invoices are in
    {currency} and due {30} days from the invoice date.
4.3 Reseller owes Vendor for each active subscription whether or not the
    Customer has paid Reseller.
4.4 Reseller is responsible for charging, collecting and paying any sales tax,
    VAT or GST on its sales to Customers.
4.5 If a Vendor invoice is more than {15} days overdue, Vendor may stop
    accepting new provisioning requests after {10} days' written notice.
    Vendor will not suspend a Customer's access over a payment dispute with
    Reseller without first giving that Customer {30} days' notice.
   [Option B: Vendor bills the Customer and pays the Reseller a margin]
4.1 Vendor invoices and collects from Customers at the list prices in the
    Price Book, less any discount approved under 6.4.
4.2 Vendor pays Reseller {margin}% of the net amount collected from each
    Customer for [the life of the subscription] / [the first {24} months],
    monthly, within {30} days after the end of the month in which Vendor
    received the payment.
4.3 "Net amount collected" excludes taxes, refunds, credits, chargebacks and
    payment processing fees.
4.4 If Vendor refunds a Customer, the margin paid on the refunded amount comes
    off Reseller's next payment.

5. Provisioning and account changes
5.1 Reseller creates Customer accounts and changes plans, seats and add-ons
    through [the partner portal] / [Vendor's provisioning API] / [an email to
    {provisioning address}, which Vendor actions within {1} business day].
5.2 Billing for an account starts on [the day it is provisioned] / [the day
    its trial ends]. Trials last up to {14} days.
5.3 Seat and plan increases take effect immediately and are charged pro rata
    for the rest of the billing period. Decreases take effect at the next
    renewal date.
5.4 Every Customer account has at least one admin user employed by the
    Customer, not by Reseller.
5.5 Vendor's provisioning records are the basis for billing. Reseller may
    dispute an invoice line within {30} days of the invoice date.

6. Price book and price changes
6.1 Reseller prices are set in the Price Book as [a discount of {discount}%
    off list] / [fixed wholesale prices per plan] / [the margin in 4.2].
6.2 Vendor may change list prices or Reseller prices with {90} days' written
    notice to Reseller.
6.3 A price change never applies to a Customer's current subscription term.
    It applies from that Customer's first renewal after the notice ends.
6.4 Reseller may ask Vendor to approve a deeper discount for a specific deal.
    An approval covers only that deal and must be in writing.
6.5 The Price Book is Vendor's confidential information.

7. Brand and white-label
   [Option A: Vendor-branded resale]
7.1 Reseller sells the Service under Vendor's name. It may use the logos and
    materials at {brand kit URL} only to promote the Service, and must follow
    Vendor's brand guidelines.
   [Option B: White-label]
7.1 Reseller may sell the Service as {Reseller product name}. Vendor applies
    Reseller's name, logo and colours to {the login page, app, transactional
    emails and help centre} and serves the Service at {app.resellerdomain.com}.
7.2 Reseller sets up the DNS records Vendor specifies for the custom domain
    and email sending, and keeps them in place during the term.
7.3 A "Powered by {Vendor}" mark [stays in the app footer] / [is removed].
   [Both options]
7.4 Vendor keeps all rights in the Service. White-labelling gives Reseller a
    licence to present the Service under Reseller's brand and nothing more.
7.5 Reseller may not bid on {Vendor} trademarks in paid search, or register
    domains or social handles containing them, without Vendor's written
    approval.

8. Deal registration and channel conflict
8.1 Reseller may register an opportunity through {portal or form} with the
    prospect's legal name, a named contact, the plan, estimated seats or
    value, and the expected close date.
8.2 Vendor approves or rejects a registration within {2} business days and
    gives a reason for any rejection. Vendor may reject a prospect that is
    already a Vendor customer, has an open opportunity in Vendor's CRM with
    activity in the last {90} days, or is registered to another reseller.
8.3 An approved registration protects Reseller for {90} days from approval.
    Reseller may ask once for a further {90} days if the deal is progressing.
8.4 While a registration is protected, Vendor's sales team and other resellers
    will not quote the prospect. If Vendor closes a Registered Deal directly,
    Vendor pays Reseller [the margin it would have earned for the first {12}
    months] / [{fee}% of the first year's net revenue].
8.5 Renewals, upgrades and added seats for a Customer belong to Reseller for
    as long as that Customer stays with Reseller.

9. Support and service levels
9.1 First-line support: [Reseller answers Customer questions about accounts,
    billing, setup and how-to, {hours and time zone}, and escalates what it
    can't solve] / [Vendor supports Customers directly].
9.2 Second-line support: Vendor handles bugs, outages, data issues and
    escalations from Reseller through {channel}, with the response times in
    Schedule B.
9.3 Vendor tells Reseller about any incident affecting Reseller's Customers
    within {1} hour of confirming it, and posts updates at {status page URL}.
9.4 Vendor's service levels at {SLA URL} apply to every Customer. Service
    credits are [paid to Reseller, which passes them on to the Customer] /
    [credited to the Customer directly].
9.5 Reseller staff who sell or support the Service complete {training or
    certification} within {60} days of starting.

10. Minimums
10.1 [No minimum applies.] / [Reseller will have at least {number} active
     Customers, or {amount} in annual purchases, by {date} and on each
     anniversary of it.]
10.2 If Reseller misses a minimum, Vendor's only remedy is to [move Reseller
     to the standard discount in the Price Book] / [end exclusivity under
     2.1] / [end this agreement on {60} days' notice].

11. Customer data and the customer relationship
11.1 Customer Data belongs to the Customer. Vendor and Reseller use it only to
     provide, support and bill for the Service.
11.2 Data processing: [Vendor signs its data processing agreement directly
     with each Customer] / [Reseller signs a data processing agreement with
     each Customer, and Vendor signs a matching one with Reseller as
     Reseller's sub-processor].
11.3 Reseller is the reseller of record for its Customers. During the term,
     Vendor will not invite them to move to direct billing unless the Customer
     asks or section 13 applies.
11.4 Vendor may contact any Customer's admin users about security, incidents,
     legal changes and the operation of the Service. Vendor will not send
     Reseller's Customers marketing without Reseller's consent.
11.5 Customers may export their Customer Data at any time through {export
     feature or process}.

12. Term and termination
12.1 This agreement starts on the agreement date and lasts {12} months. It
     renews for further {12}-month terms unless either party gives {60} days'
     written notice before a renewal date.
12.2 Either party may end this agreement by written notice if the other
     commits a material breach and doesn't fix it within {30} days of being
     told, or becomes insolvent.

13. When this agreement ends
13.1 Ending this agreement doesn't end any Customer's subscription. Each one
     continues to the end of its current term.
13.2 For each Customer, [Reseller may keep billing until the end of the
     current term, after which the Customer moves to Vendor or to another
     reseller of the Customer's choice] / [the Customer moves to Vendor's
     direct billing from its next billing date].
13.3 Vendor offers each Customer that moves its current price for at least
     {12} months after the move.
13.4 If Reseller leaves in good standing, Vendor pays [the margin on its
     former Customers' payments for {12} months] / [no further margin]. If
     Vendor ends this agreement for Reseller's breach, no further margin is
     due.
13.5 Within {30} days, Reseller gives Vendor a list of its Customers with
     their admin contacts and any open support issues, and stops using
     Vendor's marks.
13.6 For white-label accounts, Vendor keeps the Service running at Reseller's
     domain for {60} days after the end date, tells each Customer the new
     address at least {30} days before switching, and then serves it at
     {Vendor domain}.
13.7 Sections 4 (for amounts owed), 6.5, 11, 13 and 14 survive the end of
     this agreement.

14. Liability and general
14.1 Neither party is liable for indirect or consequential loss, or for lost
     profits.
14.2 Each party's total liability under this agreement is limited to the
     amounts paid or payable under it in the {12} months before the claim.
     This limit doesn't apply to amounts owed, breach of confidentiality, or
     the indemnity in 14.3.
14.3 Vendor will defend Reseller against any third-party claim that the
     Service infringes intellectual property rights, and pay any damages
     awarded, as long as Reseller tells Vendor promptly and lets Vendor run
     the defence.
14.4 Each party keeps the other's confidential information confidential
     during the term and for {3} years after.
14.5 Notices go by email to {Vendor notice email} and {Reseller notice email}.
14.6 Changes to this agreement must be in writing and signed by both parties,
     except Price Book updates made under section 6.
14.7 This agreement is governed by the laws of {jurisdiction}, and the courts
     of {venue} have exclusive jurisdiction.

Schedule A: Price Book (plans, list prices, Reseller prices, effective date)
Schedule B: Support contacts, severity levels and response times
Schedule C: Minimum customer terms (only if Reseller uses its own agreement)

Signed for Vendor: {name, title, date}
Signed for Reseller: {name, title, date}

How to fill in each part

Billing model (section 4)

Decide this first, because it changes sections 5, 6, 11 and 13. Option A is classic wholesale: the reseller buys at a discount, sets its own price, and carries the risk of customers who pay late or never. Option B keeps billing with you. You collect at list price and pay the reseller a share, so it earns less but carries no collection risk. Both models show up in our directory. accessiBe says its resellers own the billing relationship and keep the margin, while LucroVox runs billing itself and pays partners a share of collected monthly revenue.

Here's how the two compare on one hypothetical account. Say a Customer takes 20 seats at $30 a seat, so $600 a month at list. Under Option A with a 25% discount, the reseller pays you $450 and keeps $150, but only once the Customer pays. If the Customer is two months behind, the reseller has still paid you $900 from its own cash, which is what clause 4.3 says. Under Option B with a 20% margin, you collect the $600 and pay the reseller $120 (600 × 0.20). A late payer is your problem, not theirs.

We'd start a first reseller on Option B unless they already bill their clients for other software and want one invoice. It's less admin on both sides, and you can see every Customer's payment status, which you'll need if the reseller ever leaves. If you choose Option A, keep 4.3 even when the reseller pushes back on it. Without it, you're financing their bad debt.

Provisioning and seat changes (section 5)

Write down exactly how an account gets created, because it's the step that breaks first. If every new Customer means an email to your support inbox, a reseller with 40 Customers sends you a ticket every time one of them adds a seat. Some vendors give resellers their own tooling for this: Plesk offers licence management through an API or its Partner Central portal. If you don't have a portal or API yet, keep the email option in 5.1 and commit to a response time you can actually meet.

Clause 5.3 charges upgrades straight away and holds downgrades to the renewal date. Using the account above, if the Customer adds 5 seats halfway through a monthly period, the reseller is charged 5 × $22.50 × 0.5 = $56.25 for the rest of that month ($22.50 is the $30 list price less 25%). If your billing system treats downgrades differently, change the clause to match what it does. When the contract and the billing system disagree, invoices turn into disputes under 5.5.

Clause 5.4 looks minor. It means that if the reseller disappears, someone at the Customer can still log in, and you still have a person to send security notices to.

Price book and price changes (section 6)

Put prices in Schedule A with an effective date, not in an email thread. Since only six of the 87 reseller programs we checked publish a number, the price book a reseller receives after acceptance is the commercial deal, and it deserves the same version control as the contract.

Clause 6.3 is the one resellers care about most. Say a reseller signs a Customer to an annual contract at $600 a month and you raise the reseller price from $450 to $500 in month four. Without 6.3, the reseller's margin drops from $150 to $100 for the remaining eight months, $400 in total, on a contract it can't reprice. We'd give 90 days' notice for resellers who sell annual contracts, which leaves them a quarter to warn customers and requote renewals. If your resellers only sell monthly plans, 30 or 60 days is workable.

Brand and white-label (section 7)

Option B of 7.1 lists the surfaces that carry the reseller's brand. Be exact, and check the ones that are easy to forget: password-reset and notification emails, help articles that mention your name, mobile apps, and the favicon in the browser tab. If a surface isn't white-labelled today, leave it out of the list rather than promising it. A custom domain needs DNS records on the reseller's side and a TLS certificate on yours, which is why 7.2 puts the DNS work on the reseller.

The three reseller listings that mention white-label each mean something different by it. ActiveCampaign lists white-label options alongside direct client billing, WestFax offers a white-label portal option, and SocialBee lets agencies resell its white-label ConciergeBee services. Clause 7.5 is a short version of the promotion rules in our affiliate terms template; copy more of that template's section 5 if your resellers run paid ads.

Deal registration and channel conflict (section 8)

This section is what keeps resellers bringing you deals. The important part is 8.4: a registered deal is protected from your own sales team as well as from other resellers, and if your team closes it anyway, you pay. LucroVox, for example, gives partners 90 days of deal protection on registered leads. Our deal registration guide covers the approval flow, the conflict cases that come up, and how long published protection windows run.

Clause 8.5 matters more for software than for goods. With a subscription, the first sale is one term and everything after it is renewals and added seats. A reseller that only owns the first sale has little reason to keep the account healthy.

Support (section 9)

Pick 9.1 by asking who the Customer will call. Under white-label it has to be the reseller, because the Customer can't see your name. Billing and support don't have to sit with the same party. accessiBe's resellers own the billing relationship, but accessiBe says it handles onboarding and support itself, while LucroVox runs both billing and support. Whichever you choose, 9.3 matters. A reseller that learns about your outage from its own Customers looks bad in front of them, and it'll remember that when its agreement comes up for renewal.

On 9.4, service credits should follow the money. If the reseller bills (Option A), pay the credit to the reseller and let it credit the Customer. If you bill, credit the Customer directly.

Minimums and exclusivity (sections 2 and 10)

Don't grant exclusivity without a minimum, and don't impose a minimum on a first reseller you haven't watched sell. Jibble, for one, says its program has no minimum sales. And because none of the 87 reseller listings we checked records anything about territories or exclusivity, you won't find a published norm to copy here. Set the minimum from your own numbers: what would a reseller in that territory need to sell to be worth more than a direct sales hire there?

We left out a shortfall payment (the reseller paying for customers it didn't sign) on purpose. Losing a better discount or exclusivity gives a reseller a reason to sell more. A bill for customers it never signed gives it a reason to leave.

Customer data and the customer relationship (section 11)

Usually the Customer decides what goes into the product and why. That fits the GDPR's definition of a controller in Article 4(7): the party that determines the purposes and means of processing. If the GDPR applies to your Customers' data, Article 28(3) says processing by a processor must be governed by a contract (or other legal act) that covers, among other things, processing only on documented instructions, confidentiality, security measures, rules for using sub-processors, help with data subject requests, and deleting or returning the data when the service ends. The text of the regulation on EUR-Lex lists every required point.

Clause 11.2 offers the two common setups. In the first, you sign your data processing agreement directly with each Customer, which is simpler and keeps your terms consistent. In the second, the reseller signs with the Customer and you sign a matching agreement with the reseller as its sub-processor. Article 28(2) then requires the controller's prior written authorisation for that sub-processor, and Article 28(4) says the same data protection obligations have to be passed down to it, with the reseller staying fully liable to the Customer for how you meet them.

Clauses 11.3 and 11.4 are a trade. The reseller gets a promise that you won't poach its Customers, and you keep a direct line to the people using your product for anything that isn't marketing.

When the reseller leaves (section 13)

This is the clause that decides whether a reseller leaving costs you customers. Without it, a reseller that quits, gets acquired or goes out of business can leave Customers on accounts nobody is billing or supporting. Clauses 13.1 to 13.3 keep every subscription running and give each Customer a clear next step, with a price guarantee so the move doesn't feel like a bait and switch.

Clause 13.4 is the reseller's version of the post-exit commission question in affiliate terms. Paying margin for 12 months after a good-standing exit is generous, and it gives the reseller less reason to move its Customers to a competitor on the way out. Paying nothing is simpler and cheaper. Either way, write it down. If you used the second option in 11.2, the reseller's data processing agreement with each Customer ends too, and Article 28(3)(g) has a processor delete or return personal data at the end of the service, at the controller's choice. Get each Customer onto your own data processing agreement before the reseller's one ends.

Mistakes to avoid

  • Starting from a reseller agreement written for physical goods. Clauses on title, delivery, stock and returns mean nothing for a subscription, and those templates usually say nothing about provisioning, customer data or service levels.
  • Leaving both billing options in section 4. A contract that never says who invoices the customer turns the first late payment into an argument about who was owed it.
  • Letting a price change hit a contract the reseller has already signed with its customer. Clause 6.3 costs you a few months of the higher price and saves the relationship.
  • Promising exclusivity in a sales call before section 10 is agreed. Exclusivity without a minimum lets a reseller sit on a territory it isn't working.
  • Making the reseller the only admin on customer accounts, so a reseller that goes quiet locks its customers out of their own data.
  • Letting resellers promise uptime or features your own SLA doesn't. Clause 3.2 exists because the customer may hold you to whatever the reseller said.
  • Paying a referral partner and a reseller for the same deal without deciding the split in advance. The deal registration guide covers how to settle it before it happens.

If you run the channel on PartnersWatch (our product), the records this agreement depends on can sit in one place. Price books are set per partner or per tier with effective dates, partners provision customers into your product through signed requests that your product receives (see vendor integration and provisioning), and your product can fetch each partner's approved brand for white-label accounts. White-label portals and custom domains are on the Enterprise plan; the white-label page has the detail.

To set up the program around this agreement, read how to start a SaaS reseller program. If your partners implement more than they resell, how to build an agency partner program covers the other model, and agency partner programs shows what agency tracks publish today.

Sources

  1. eur-lex.europa.eu/eli/reg/2016/679/oj

Spotted an error or an out-of-date term? Read our editorial standards and corrections policy.

For partners

One profile, every open program

Browse the Network and apply in minutes. We forward applications to brands that aren't here yet.

For brands

Recruiting partners?

List your program in front of partners who are already looking, and run it end to end on PartnersWatch.