TL;DR: A SaaS reseller agreement governs a fundamentally different relationship from your standard subscription terms. Instead of a direct end-user paying you, a third party resells, rebrands, or bundles your software under its own commercial relationship with the end customer, which changes who owns the customer data, who collects and remits sales tax, who’s liable if something breaks, who controls pricing, and what happens when the relationship ends. Getting this agreement wrong is one of the more common, expensive mistakes growing SaaS companies make once they start building a channel or partner program, and the mistakes usually aren’t in the obvious clauses, they’re in the ones nobody thought to include at all.
Quick overview: This guide covers what a SaaS reseller agreement actually needs to contain, the different reseller models and why the structure you choose changes the contract, the tax and compliance provisions most templates skip entirely, and what to watch for around data, liability, and exit. For the full set of legal documents a SaaS company needs beyond this one relationship, our complete guide to legal documents every SaaS startup needs covers the broader picture this agreement sits inside.
Why a reseller agreement isn’t just your subscription agreement with a new name
The instinct many SaaS founders have is to hand a reseller a version of their standard customer terms with the company name swapped out. This is a genuine mistake, and it usually surfaces at the worst possible time, during a dispute, a tax audit, or when the reseller relationship ends and nobody’s clear on what happens to the customers in between.
A standard SaaS subscription agreement governs a direct relationship: you and the end user, one party responsible for the software, one party paying for and using it. A reseller agreement introduces a third party standing between you and the end customer, one who may be rebranding your product, setting their own pricing, collecting sales tax in jurisdictions you’ve never had to think about, providing their own first-line support, and holding a direct commercial relationship with a customer you may never interact with directly. Every one of those differences needs its own contractual answer, and a relabelled subscription agreement doesn’t provide any of them.
Reseller agreements versus the adjacent structures they get confused with
| Structure | Who bills the end customer | Who owns the customer relationship | Typical use case |
|---|---|---|---|
| Reseller of record | Reseller | Reseller | Reseller wants full commercial control, including pricing and billing |
| Referral/affiliate | Provider | Provider | Reseller only introduces leads, earns a commission |
| Distribution agreement | Distributor | Distributor | Physical goods, not typically appropriate for SaaS delivery mechanics |
| API/technical partnership | Varies | Partner builds on top of the platform | Partner integrates your platform into their own product, not simple resale |
| White-label reseller | Reseller | Reseller, invisibly | Reseller wants the product to appear entirely as its own |
Getting the category wrong at the outset is a common, expensive mistake. A referral partner given reseller-of-record terms ends up with tax and liability obligations it never expected. A true reseller of record given only referral-style terms has no clear authority to actually bill and support its own customers. Confirm which category you’re actually building before drafting anything.
The different reseller models, and why the model changes the contract
White-label reselling. The reseller sells your software entirely under its own brand, with no visible connection to your company. This requires the most detailed branding, IP licensing, and quality control provisions, since your product’s reputation is now entirely in someone else’s hands, invisibly to the end customer.
Co-branded reselling. Both your brand and the reseller’s brand appear to the end customer. This needs clearer allocation of which party handles which support and liability functions, since the customer may reasonably expect either party to answer for problems.
Referral or affiliate arrangements. The reseller introduces customers but you maintain the direct billing and support relationship. This is a lighter-weight structure, closer to a commission arrangement than a true reseller relationship, and the contract should reflect that lighter obligation on both sides.
Full reseller of record. The reseller bills the end customer directly, sets its own retail pricing within agreed bounds, and effectively owns the commercial relationship, while you remain responsible for the underlying software and infrastructure. This is the most complex model and needs the most comprehensive agreement, and it’s also the model that carries tax and compliance consequences the other three largely avoid.
The merchant of record question, and why it changes your tax exposure
This is one of the most consequential decisions in the entire agreement, and it’s frequently never addressed at all. “Merchant of record” refers to whichever party is legally responsible for collecting and remitting sales tax, VAT, or GST on the transaction with the end customer, and for handling the associated compliance, registration, and audit obligations across every jurisdiction that transaction touches.
In a full reseller-of-record model, the reseller is typically the merchant of record, meaning the reseller, not the underlying SaaS provider, bears responsibility for correctly charging and remitting tax in every jurisdiction its end customers are located. In a referral or agency-style arrangement, the provider usually remains the merchant of record, and the reseller’s commission is a separate, internal transaction between the two businesses that doesn’t touch end-customer tax treatment at all. Getting this backwards, assuming you remain the merchant of record when your contract actually makes the reseller responsible, or vice versa, is exactly the kind of gap that surfaces as an unpleasant surprise during a tax authority audit, not during the relationship’s happy early months. State explicitly, in the agreement itself, which party is the merchant of record, and make sure your actual billing infrastructure matches what the contract says.
What the agreement actually needs to contain
Pricing and margin structure. State clearly whether the reseller pays you a wholesale rate and sets its own retail price, or whether pricing is fixed and the reseller earns a defined margin or commission. Ambiguity here is one of the most common sources of dispute, particularly once volume grows and the margin becomes commercially significant to either side.
Territory and exclusivity. Define precisely where the reseller is authorised to sell, geographically, by industry vertical, or by customer segment, and state explicitly whether that territory is exclusive or non-exclusive. An exclusive territory without clear performance minimums attached can leave you locked out of a market the reseller isn’t actually developing.
Minimum commitments and performance targets. Where exclusivity or preferential pricing is granted, tie it to a minimum sales commitment or renewal-linked performance target, so the exclusivity can be revisited if the reseller isn’t actually delivering the volume that justified it.
Most-favoured-reseller treatment. Where you’re building a multi-reseller program, decide upfront whether any reseller is entitled to pricing or terms at least as favourable as those given to any other reseller. Silence on this point is fine for a single early reseller relationship, but becomes a genuine negotiating flashpoint once you’re managing several resellers simultaneously and one discovers another got a better deal.
Branding and intellectual property. Specify exactly what the reseller can and cannot do with your trademarks, logos, and product name, particularly in a white-label arrangement, and make clear that any goodwill generated through the reseller’s use of your brand remains your property, not the reseller’s, once the relationship ends.
IP infringement indemnification. Address what happens if a third party claims your underlying software infringes their intellectual property, and that claim is brought against the reseller or one of its end customers rather than against you directly. A properly drafted agreement has the provider indemnify the reseller for genuine platform-level IP claims, while carving out claims arising from the reseller’s own modifications, branding, or misuse of the Service. Leaving this silent means the reseller is left exposed for a risk it never created and has no ability to control.
Data ownership and processing responsibilities. This is one of the most consequential and most frequently overlooked sections. Where the reseller holds the direct billing or support relationship with the end customer, work out explicitly who owns the resulting customer data, what the reseller is permitted to do with it, and what data protection obligations flow through to the reseller as a processor or sub-processor. This needs to reflect whichever data protection regime actually applies, GDPR’s controller-processor framework in the EU, or DPDP’s Data Fiduciary and Data Processor structure in India, since the underlying accountability obligations differ in real, specific ways depending on jurisdiction, not just terminology. A reseller handling end-customer data on your platform’s behalf typically needs its own Data Processing Agreement layered into or alongside the reseller agreement, our complete guide to legal documents every SaaS startup needs covers what that underlying DPA needs to contain.
Service levels and support responsibility. Clarify who handles first-line customer support, what service level commitments the reseller is allowed to make to end customers, and critically, that the reseller cannot promise service levels to customers that your underlying platform doesn’t actually guarantee to the reseller itself. A reseller over-promising uptime it can’t control is a genuine, recurring source of liability exposure.
Liability allocation. Address specifically what happens when something goes wrong, a platform outage, a data incident, a billing dispute, and whether the reseller or the underlying SaaS provider bears responsibility to the end customer, and to each other. This needs to work consistently with your underlying Terms of Service and any liability caps in your core product agreements, not sit in isolation.
Insurance requirements. For any reseller handling end-customer billing, support, or data directly, require evidence of appropriate insurance, commonly errors and omissions coverage and cyber liability coverage, sized to the scale of the reseller’s actual customer base. This protects you as much as it protects the reseller, since a reseller without adequate coverage that causes a data incident or service failure is a liability that can flow back to your own platform’s reputation even where you bear no direct legal responsibility.
Audit rights. Where compensation depends on the reseller’s self-reported sales volume, active users, or revenue, include a right to audit the reseller’s relevant records, with reasonable notice and frequency limits, to confirm what’s being reported matches what’s actually been sold. Without this, a margin or commission structure based on self-reporting has no real enforcement mechanism behind it.
Export controls and sanctions screening. For any reseller operating internationally, or reselling into multiple jurisdictions, require the reseller to screen its end customers against applicable sanctions and export control lists before onboarding them, and prohibit resale into jurisdictions or to parties your own compliance obligations restrict. This is a genuinely common gap in reseller agreements, and it becomes a serious, direct problem the moment a reseller signs up a sanctioned entity your own compliance program would never have onboarded directly.
Non-circumvention. Include a clause preventing either party from bypassing the other to deal directly with a customer the reseller introduced, in either direction, the reseller poaching a customer you introduced, or you cutting out the reseller once a customer relationship matures.
Sub-reseller restrictions. Decide explicitly whether the reseller may appoint its own sub-resellers, and if so, whether it remains fully responsible for those sub-resellers’ compliance with this Agreement’s terms, particularly around data handling and branding. Silence here can result in your platform being resold two or three layers removed from any relationship you actually agreed to.
Termination and transition. Specify what happens to existing end-customer relationships when the reseller agreement ends, whether customers transition to a direct relationship with you, migrate to another reseller, or lose access entirely, and set a clear timeline and data-return obligation for that transition. This is the section most reseller agreements handle worst, and the one that causes the most damage when a relationship ends badly.
How this relates to your other technology agreements
A SaaS reseller agreement doesn’t operate in isolation. It should be built consistently with your core SaaS subscription agreement or Terms of Service, since the reseller’s obligations to end customers ultimately need to be compatible with what your platform actually commits to. Where the reseller relationship involves technical integration rather than pure commercial resale, our API Licensing Agreement guide covers the specific terms that apply when a partner is building on top of your platform rather than simply reselling access to it, a genuinely different relationship that sometimes gets bundled incorrectly into a single reseller agreement when it should be documented separately.
Complete pre-signature checklist
| Area | Confirm before signing |
|---|---|
| Model | Which of the four reseller models actually describes this relationship, and does the contract match it |
| Merchant of record | Which party collects and remits sales tax, VAT, or GST, and does your billing infrastructure match |
| Pricing | Wholesale rate, margin, or commission clearly defined; most-favoured-reseller position decided |
| Territory | Exclusivity, if any, tied to a specific, measurable performance commitment |
| Data | Ownership and processing responsibilities defined against the actual applicable data protection regime; DPA in place |
| IP | Branding rights scoped; infringement indemnification allocated correctly between platform-level and reseller-caused claims |
| Compliance | Insurance requirements set; export control and sanctions screening obligations included |
| Accountability | Audit rights included wherever compensation depends on self-reported figures |
| Exit | Customer transition path, data return, and timeline defined explicitly, not left to be negotiated after the relationship has already ended |
Frequently asked questions
What’s the difference between a SaaS reseller agreement and a distribution agreement?
A distribution agreement traditionally governs the sale of physical goods through a distribution channel. A SaaS reseller agreement covers the same underlying commercial concept, a third party selling on your behalf, but is built around the specific realities of software delivery: recurring subscription billing, data processing responsibilities, service level commitments, and access provisioning, none of which a traditional goods-based distribution agreement addresses.
Who is responsible for collecting sales tax or VAT in a SaaS reseller relationship?
This depends entirely on which party is designated the merchant of record in the agreement. In a full reseller-of-record model, the reseller typically bears this responsibility across every jurisdiction its customers are located. In a referral or agency arrangement, the provider usually remains responsible. This should be stated explicitly in the contract, not assumed from the general structure of the relationship.
Who owns customer data when a reseller handles the billing relationship?
This needs to be explicitly stated in the agreement rather than assumed. Depending on the structure, the underlying SaaS provider, the reseller, or both parties jointly may hold data obligations, and the agreement should specify exactly what the reseller can do with the data it collects, consistent with the provider’s own privacy commitments to end users and whichever data protection law actually applies.
Should a SaaS reseller agreement include exclusivity?
Only where it’s tied to a genuine, measurable performance commitment. Granting an exclusive territory or vertical without a minimum sales target attached risks locking the provider out of a market the reseller isn’t actually developing, with no contractual mechanism to revisit the exclusivity.
Who is liable if a reseller’s software infringes a third party’s intellectual property rights?
This should be addressed through an IP infringement indemnification clause. A properly drafted agreement has the provider indemnify the reseller for claims arising from the underlying platform itself, while carving out claims caused by the reseller’s own modifications, branding, or misuse, since the reseller shouldn’t bear risk for a defect it had no ability to create or control.
What happens to customers if a reseller agreement is terminated?
This should be defined explicitly in the agreement’s termination and transition provisions, whether customers transition to a direct relationship with the provider, move to a different reseller, or lose access after a defined notice period, along with a clear data-return and transition timeline. Agreements that leave this undefined create genuine disruption and dispute risk when the relationship actually ends.
This article is general information, not legal advice. Reseller agreement terms, including tax and merchant of record structuring, should be tailored to your specific commercial structure and the jurisdictions involved. For a reseller agreement built around your actual business, speak to a qualified lawyer.
Authored and reviewed by Prakhar Rai, Advocate, founder of My Legal Pal. Connect on LinkedIn.
If you’re building a reseller or channel partner program for your SaaS product, getting the agreement right protects your platform, your tax position, your data obligations, and your customer relationships as the program scales. Our team drafts SaaS reseller agreements tailored to your specific model. Get yours drafted and reviewed by an expert contract lawyer.
