Software Reseller Agreement Checklist For UK Partners

Yes, if you're selling or appointing someone to sell software in the UK, you should have a written software reseller agreement. It doesn't need to be overly complicated, but it does need to be specific to software.

That's because software resale isn't just about buying stock and reselling it. You're dealing with licence rights, customer data, support promises, updates, pricing rules, renewals and sometimes territory restrictions.

A good agreement helps both sides know exactly what they're allowed to sell, who owns the customer relationship, who handles problems and how money flows. This can save a lot of awkward conversations later, especially once customers start renewing or asking for support.

What Is A Software Reseller Agreement?

A software reseller agreement is a contract between a software supplier and a reseller that sets out how the reseller can market, sell or distribute the software to customers.

For software businesses, the agreement usually sits alongside customer-facing documents such as your software licence terms, SaaS terms, privacy notice and acceptable use policy. The reseller agreement deals with the channel relationship, while your customer terms deal with what end users can and can't do with the product.

There are a few common models:

• Resale model: the reseller buys licences from you at a discount and sells them to customers at its own price.
• Referral model: the partner introduces customers to you and receives a commission if the customer signs up.
• Agency model: the reseller sells on your behalf, usually under tighter control and with less freedom over pricing.
• White label model: the reseller sells your software under its own brand, which needs extra care around branding, support and customer ownership.

The right structure depends on how much control you want, who contracts with the customer and who carries the customer support risk. If you're not clear on this at the start, you can end up with two businesses promising different things to the same customer.

Do You Need A SaaS Reseller Agreement In The UK?

Yes, you generally need a tailored SaaS reseller agreement in the UK if a partner is selling subscriptions, licences or access to your software platform.

SaaS resale has a few extra moving parts compared with one-off software sales. Customers might pay monthly or annually, licences may scale up and down, and support obligations can continue for years. You also need to decide what happens if the reseller stops trading, fails to pay you or gives the customer information that doesn't match your platform.

Say CloudDesk Ltd develops project management software and appoints NorthPoint IT as a reseller in England. NorthPoint sells a 12-month subscription to a customer for 100 users at £100 per user per month. CloudDesk gives NorthPoint a 30% reseller discount.

That means the customer pays NorthPoint £10,000 per month, and NorthPoint pays CloudDesk £7,000 per month. If the agreement doesn't say when payment is due, what happens if the customer doesn't pay, and whether CloudDesk can suspend access for non-payment, both sides are exposed.

Your agreement should also line up with your SaaS product setup. For example, if customers accept your online terms when they log in, the reseller agreement should say the reseller must not promise rights that conflict with those terms. If the reseller signs customer contracts in its own name, you'll need a clear process for passing through your software licence terms to end users.

What Should A Software Reseller Agreement Include?

A software reseller agreement should clearly cover the licence scope, sales rights, pricing, customer responsibilities, support, data protection, intellectual property and exit process.

Here is a practical outline you can use when planning the agreement. This isn't a finished legal document, and a lawyer should tailor it before you use it, but it's a useful starting point for the main clauses.

1. Parties And Background: name the software supplier, the reseller and the purpose of the channel arrangement.
2. Appointment: state whether the reseller is exclusive, non-exclusive, authorised or limited to certain products or customers.
3. Territory And Market: set out where the reseller can sell and whether any industries or customer types are off-limits.
4. Licence Scope: explain what the reseller can do with the software, such as demonstrate it, market it, resell subscriptions or provide limited admin access.
5. Customer Terms: say which end user licence agreement, SaaS terms or customer contract applies to customers.
6. Pricing And Payment: cover reseller discounts, invoicing, VAT treatment, renewal pricing, late payment and currency.
7. Targets And Reporting: include any sales targets, pipeline reporting, forecasts or audit rights.
8. Support And Service Levels: divide first-line support, technical support, onboarding and escalation responsibilities.
9. Data Protection: allocate controller and processor roles under UK GDPR and the Data Protection Act 2018.
10. Intellectual Property: protect copyright, trade marks, product names, documentation, APIs and confidential information.
11. Marketing Rules: say how the reseller can use your logo, case studies, screenshots and sales materials.
12. Confidentiality And Security: cover access credentials, customer information, security standards and breach reporting.
13. Term And Termination: set the initial term, renewal process, termination rights and what happens to live customers.
14. Post-Termination: deal with customer handover, unpaid invoices, licence continuation and removal of branding.
15. Liability And Indemnities: allocate risk for mis-selling, IP claims, data issues, unpaid fees and support failures.

The most useful reseller contracts are specific. If the agreement simply says the reseller can sell your software, but doesn't explain what that means in practice, you'll still be relying on assumptions.

How Should Licence Scope Work In A Reseller Contract For Software?

The licence scope should say exactly what the reseller can do with the software and what the end customer is allowed to do with it.

This matters because software is usually protected by copyright under the Copyright, Designs and Patents Act 1988. The reseller doesn't own your code just because it has permission to sell access to it. Your agreement should make that clear.

For a typical SaaS reseller arrangement, you might give the reseller permission to:

• market the software to approved customers
• demonstrate the software using demo accounts
• resell subscriptions or user seats
• help customers with onboarding and basic configuration
• use approved product names, screenshots and logos

You may want to stop the reseller from:

• copying, modifying or reverse engineering the software
• creating competing products using your confidential information
• making promises about uptime, security or features that you haven't approved
• registering your brand name, domain names or confusingly similar trade marks
• granting customers rights that go beyond your standard licence terms

If your brand is trade marked through the UK Intellectual Property Office, the agreement should also control how the reseller uses it. You can allow use for marketing while keeping ownership and requiring brand guidelines to be followed.

One practical tip is to attach the current software licence terms, EULA or SaaS terms to the reseller agreement. That way, everyone can see what end users must accept, and the reseller is less likely to overpromise.

Who Handles Customer Support, Refunds And Renewals?

The agreement should say who handles each customer touchpoint, because support and renewals are where many reseller disputes start.

Software customers usually don't care whether the issue sits with the supplier or the reseller. They just want the platform working. Your reseller agreement should give both sides a clear playbook.

Customer Support

Decide who provides first-line support, such as password resets, basic training and account setup. Then decide when issues get escalated to the software supplier, such as bugs, outages, security incidents or feature failures.

You can also include service levels. For example, you might say priority 1 outages must be acknowledged within 2 business hours, while lower priority issues are handled within 2 business days. If you include service levels, make sure your team can actually meet them.

Refunds And Credits

If the reseller contracts directly with the customer, it may be the first business asked for a refund. If the software supplier controls access and billing, the supplier may receive that request instead.

For business-to-business sales, your contract terms will usually drive the position. If you sell to consumers, the Consumer Rights Act 2015 and digital content rules may be relevant. For business customers, your B2B terms will usually drive the position, although other rules such as unfair contract terms and misrepresentation may still need to be considered. Your customer terms should match the way you actually sell.

Renewals And Customer Ownership

Renewals should be spelt out. For example, does the reseller receive commission on every renewal, only the first 12 months, or only while it's actively supporting the account?

You should also decide who owns the customer relationship if the reseller arrangement ends. Without a written agreement, you may struggle to stop a reseller from claiming ongoing commission for customers it introduced years ago.

How Do Data Protection And Security Rules Apply?

Data protection rules apply if the reseller or supplier handles personal data, such as customer contacts, user accounts, support tickets, usage logs or billing details.

Under UK GDPR and the Data Protection Act 2018, you need to work out whether each party is a controller, processor or joint controller for each activity. The labels matter because they decide what contract terms and compliance steps are needed.

For example:

• If the software supplier hosts the platform and decides how user data is processed, it may be a controller or processor depending on the product and customer relationship.
• If the reseller collects leads and decides how to market to them, the reseller is likely to be a controller for that marketing data.
• If the reseller provides support using the supplier's ticketing system, the parties need to map who controls the data and who acts on whose instructions.

If one party processes personal data for the other, you'll usually need data processing terms that include the mandatory UK GDPR Article 28 requirements. These cover things like confidentiality, security, sub-processors, assistance with data subject requests and what happens to data at the end of the arrangement.

You should also check whether your business needs to pay the ICO data protection fee. Current ICO fee tiers start at £52 for many small organisations, but the right tier depends on your size and processing activities.

Security clauses should be practical, not decorative. Cover admin access, multi-factor authentication, incident notice timing, audit rights, approved sub-processors and what happens if the reseller loses a laptop or accidentally shares customer data with the wrong client.

Can You Restrict Territory, Customers Or Pricing?

Yes, you can often restrict territory, customer types or sales channels, but pricing controls and exclusivity need care because UK competition law may apply.

Territory restrictions are common in reseller arrangements. You might appoint one reseller for the UK, another for the EU, and another for a particular sector such as healthcare or education. The agreement should say whether the reseller can actively market outside its territory, respond to inbound enquiries from outside its territory, or sell through online marketplaces.

Exclusivity can work well if the reseller is investing time and money into your product. In return, you may want minimum sales targets, quarterly reviews and a right to remove exclusivity if targets aren't met.

Pricing is where you need to be more careful. Under the Competition Act 1998, resale price maintenance can be unlawful. In plain English, you generally shouldn't force a reseller to sell at a fixed or minimum resale price. Recommended resale prices and maximum prices may be possible, but they must be handled properly and not operate like a hidden fixed price.

A safer approach is often to control your wholesale pricing, discount structure and brand positioning, while allowing the reseller to set its own customer price. You can also require the reseller not to make misleading claims or bundle your software in a way that damages your brand.

If your reseller network is growing across the UK and overseas, get tailored advice before locking in exclusivity, pricing controls or territory rules. Small drafting choices can make a big difference.

Should You Use A Software Reseller Agreement Template?

A template can help you plan the structure, but it shouldn't be used as-is for a serious software channel arrangement.

Many templates are written for general product resale. They often miss the issues that matter most for software, such as licence scope, user limits, SaaS renewals, API access terms, data processing, uptime commitments, support and maintenance obligations and IP protection.

Your main options are usually:

• Free template: useful for seeing common headings, but risky if it doesn't match your product, sales model or UK legal position.
• Online fixed-fee legal service: usually a good middle ground if you want a tailored document and price certainty.
• Traditional hourly firm: may suit complex enterprise channels, multi-country distribution or heavily negotiated deals.

The cost of getting a software reseller agreement prepared usually depends on factors such as the complexity of the product, whether the reseller is exclusive, whether the arrangement is UK-only or international, how data protection is handled, and whether customer terms also need updating.

What should be included? At a minimum, you want a document that reflects your actual sales flow, protects your intellectual property, manages data protection properly, and explains what happens to customers if the reseller relationship ends.

If you're appointing a reseller for a low-risk side project, a lighter document may be enough. If the reseller will be a major revenue channel, will access customer data or will sell into regulated sectors, it's worth getting the drafting right from day one.

Key Takeaways

• A software reseller agreement in the UK should deal with licence rights, customer terms, support, pricing, data protection and exit rights.
• SaaS resale needs extra detail around subscriptions, renewals, customer ownership and suspension for non-payment.
• Your reseller shouldn't be able to promise customers more than your software licence or SaaS terms allow.
• UK GDPR and the Data Protection Act 2018 may require data processing terms, security obligations and clear controller or processor roles.
• Territory and exclusivity clauses can be useful, but resale pricing controls need careful handling under UK competition law.
• Templates can help with structure, but software reseller contracts work best when they're tailored to your product and sales model.

If you'd like help with your software reseller agreement, SaaS customer terms, data protection clauses or IP and branding rules, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.