Reseller Agreements

How to redline terms against a negotiation playbook for Reseller Agreements

Redline reseller agreements against your negotiation playbook using a copyable decision table, transaction tests, and checks for margin and exit risk.

October 17, 2026  ·  9 min read
Book a Demo →

Redlining a reseller agreement against a negotiation playbook means translating the reseller’s commercial requirements into coordinated edits across the master agreement, product schedules, discount tables, and incorporated policies. Establish which documents control, compare material provisions with preferred positions and authorized fallbacks, and test proposed wording against sales, support, and termination scenarios. The deliverable is a tracked-changes draft supported by a clause-level decision record identifying the evidence, commercial consequences, dependencies, unresolved questions, and approvals needed to send the counterproposal.

When to use this workflow

Use this workflow when reseller-side counsel receives a supplier’s first draft, revised channel terms at renewal, or a counterproposal changing margins or customer access. It also applies to a new product attachment under an existing framework.

Focus on authority to sell, compensation, supply continuity, customer relationships, support allocation, risk transfer, and exit arrangements. An inventory-holding distributor needs different protections from a subscription reseller or a reseller combining supplier products with its own services.

This is a US-oriented transactional workflow, not advice for a particular agreement. Rights depend on the language, governing law, facts, and deal context. State franchise/dealer and restrictive-covenant issues require matter-specific review; federal competition guidance does not resolve them.

What you need

Collect the proposed master, amendments, product and territory schedules, pricing and rebate tables, order forms, support terms, end-user terms, and incorporated policies. Preserve negotiation versions and dated copies of online terms where available.

Obtain business assumptions covering existing accounts, direct-sales exposure, inventory, payment cycles, renewals, and support capacity. Confirm who invoices customers, carries credit risk, and fulfills orders.

Your playbook is the team’s own checklist and instructions. Identify its date and applicable business model. For each topic, specify a preferred position, authorized fallback, escalation threshold, and approval owner. Do not apply hardware-distribution instructions automatically to subscription sales.

Use the template

Use Reseller Agreements — Redlining playbook as the companion decision record. You can copy this table into your working document or spreadsheet. Create one row per independently negotiable issue.

ID / topic Source / version Evidence / gap Preferred position Fallback / limit Edit / reason / priority Dependencies / test Owner / status

Assign document IDs, such as M1 for the master and D1 for the discount schedule, and cite sections or pages. Distinguish express exclusions, ambiguous wording, language not present in the reviewed set, and missing documents.

Record both the permitted fallback and the approval boundary. Include severity and reviewer confidence in the edit field. Use dependencies for definitions, schedule conflicts, and financial tests, referencing spreadsheet cells where useful. Status should distinguish proposed, accepted, rejected, and awaiting decision.

Step by step

1. Establish the document hierarchy and review boundary

Read precedence, incorporation, amendment, and policy-change provisions together. Determine whether a product schedule overrides the master or an online policy can change negotiated economics.

The filed Avaya agreement generally prioritizes Product Appendices over Product Group Attachments and those attachments over the agreement, subject to express overrides. It also specifies signed written amendments. This illustrates why hierarchy matters; it is not a rule for other contracts (Avaya, §§20.4–20.5).

Record the controlling source, conflicting provisions, and missing materials. If an incorporated pricing policy is unavailable, keep its effect unresolved rather than assuming the master protects the discount.

2. Convert commercial instructions into negotiable positions

Confirm instructions with sales, finance, and support leads. Translate “protect our accounts” into positions on registered opportunities, supplier-direct sales, renewals, affiliates, and post-termination transactions.

For each topic, specify an actionable fallback. If the supplier rejects compensation on all direct sales, a fallback might cover only accepted registered opportunities for a defined period. Identify who may approve that narrower protection.

Prioritize exposure, likelihood, operational burden, and mitigation. Uncapped indemnities, warranty gaps, discretionary suspension, intrusive audits, and unilateral policy changes require decisions, not stylistic cleanup. Record the position, priority, commercial reason, and approval threshold.

3. Extract operative wording and dependencies

Capture the language creating the right or obligation, including definitions, exceptions, and cross-references. Identify the actor, action, trigger, deadline, and conditions before drafting a replacement.

Keep economic rights separate. One filed reseller agreement excludes compensation for direct end-user purchases and separately conditions certain add-on or upgrade discounts on the original sale and continuing support. These are examples of wording, not customary entitlements (Agilent–O.I., §§3(c)–(d)).

Record exact references and confidence. “Not present in reviewed documents” differs from “expressly excluded.” A missing attachment is an evidence gap, not proof that a right does not exist. Keep reporting duties separate from payment obligations even when adjacent.

4. Draft economic edits and test transactions

Redline discounts, rebates, and commissions separately. Check eligible revenue, tier thresholds, marginal versus retroactive calculations, refunds, clawbacks, taxes, currency, payment triggers, direct sales, and renewals. Define registration acceptance and disputed attribution.

Test a normal sale, return, supplier-direct sale, and renewal crossing termination. Record finance-approved assumptions and calculation references. Check whether price increases, freight, or policy changes undermine the nominal discount.

Unequal discounts alone do not establish an antitrust violation. FTC guidance identifies requirements including commodity purchases, like-grade-and-quality goods, and possible competitive injury; software and mixed offerings require classification analysis. Promotional allowances require separate treatment (FTC price-discrimination guidance). Record legal questions separately from commercial edits.

5. Redline channel restrictions without assuming enforceability

Map restrictions by product, territory, customer category, conduct, and duration. Distinguish reserved accounts, customer nonsolicitation, noncompetition, exclusive sourcing, suggested prices, advertised-price conditions, and binding resale-price restrictions.

FTC guidance describes federal rule-of-reason analysis for manufacturer-imposed vertical minimum-price arrangements, while noting different state and international treatment. It also distinguishes manufacturer-imposed customer or territory restrictions from restraints coordinated among competitors (FTC manufacturer-imposed requirements). That guidance does not decide a customer nonsolicitation covenant’s enforceability.

Where appropriate, propose carve-outs for existing relationships, unsolicited approaches, and general advertising. Record the facts and jurisdictions requiring further review, assign counsel, and keep that issue open independently of commercial approval.

6. Align performance, remedies, and termination

Compare customer promises with supplier warranties, support, license rights, and supply commitments. Review indemnities and liability limitations together, including exclusions that remove principal exposures from the cap. Allocate responsibility for the reseller’s own services separately.

For suspension and termination, address triggers, notices, cure, accepted orders, inventory disposition, prepaid support, accrued compensation, and transition assistance. Specify duration, responsibility, and payment rather than requesting undefined “continuity.”

Continuing licenses are not continuing support. The Avaya example preserves properly granted existing end-user licenses after termination of the reseller’s license and accelerates outstanding invoices at termination; those provisions do not establish renewal compensation or ongoing support (Avaya, §§7.7 and 17.4). Record each proposed protection and any customer promise requiring revision if rejected.

7. Reconcile the redline and obtain approvals

Read the revised agreement as a whole. Reconcile definitions, precedence, notices, survival, and schedules. Remove conflicting text rather than explaining it away in comments.

Prepare an internal cover note organized by unresolved decision: proposed position, fallback, consequence of rejection, and approver. Keep internal limits out of the counterparty draft.

Update every template row with its disposition and current draft reference. Confirm substantive edits appear as tracked changes and resolved comments have become operative language. The output is a negotiable draft and decision record, not an unfiltered suggestion list.

Worked example

Fictional scenario. Cedar Harbor Systems proposes to resell Northstar Relay equipment and annual support subscriptions. All parties, documents, amounts, and terms below are fictional. Master M1 excludes direct-sale compensation. Schedule D1 specifies an 18% equipment discount from list price, but incorporated channel policy CP1 is missing. M1 permits termination on 30 days’ notice without addressing accepted orders or support continuity.

Assume equipment list price and customer resale price are both $100,000. D1 produces an $82,000 supplier cost before freight, taxes, or adjustments. Cedar Harbor separately seeks a 6% fee on eligible supplier receipts from direct sales of accepted registered opportunities. These are negotiation assumptions, not market benchmarks.

ID / topic Source / version Evidence / gap Preferred position Fallback / limit Edit / reason / priority Dependencies / test Owner / status
R1 Direct sales M1 v1 §4.2 Compensation expressly excluded 6% registered-opportunity fee Narrow coverage; finance approval Add attribution and payment terms; high priority $100,000 eligible receipts × 6% = $6,000; define deductions Sales + finance / proposed
R2 Discount changes D1 v1 §2; M1 v1 §3.4 18% discount; CP1 missing Protect accepted-order pricing Prospective changes with agreed notice Limit policy override; high priority Obtain CP1; $100,000 list × 82% = $82,000 Procurement / unresolved
R3 Exit continuity M1 v1 §12 30-day termination; continuity absent Fulfill accepted orders and prepaid support Funded transition; operations approval Add express obligations; high priority Obtain customer terms; verify supplier support capacity Operations + counsel / proposed

For R1, a drafting starting point is: “Supplier shall pay Reseller 6% of Net Receipts from a direct sale arising from an Accepted Registered Opportunity.” It is incomplete until the parties define eligibility, deductions, attribution, returns, reporting, and payment timing.

The discount and direct-sale fee concern alternative transaction paths; they should not be added together as earnings on one sale. CP1 remains missing evidence, not proof of adverse terms. R3 requires customer terms before counsel can identify the actual support mismatch. These gaps make pricing and continuity approval conditional rather than complete.

Common mistakes

  • Editing only the master. A controlling schedule may defeat the change. Amend that schedule or establish an express override.
  • Conflating margin and commission. A purchase discount does not itself create direct-sale compensation. Draft separate eligibility and payment mechanisms.
  • Treating restrictions as boilerplate. Map affected customers and conduct, then assign jurisdiction-specific legal review.
  • Negotiating cure in isolation. Check suspension rights, notice delivery, and service exposure during the cure period.
  • Leaving agreement in comments. Convert resolved points into operative text and verify dependent definitions before closing the row.

Final quality check

  • Findings match the correct source version and clause or page.
  • Missing documents, absent language, and express exclusions are distinguished.
  • Positions and fallbacks fit the reseller’s operating model.
  • Transaction tests cover direct sales, returns, renewals, and exit effects.
  • Definitions, schedules, precedence, and survival support the edits.
  • Legal questions have assigned reviewers and remain separate from commercial concessions.
  • Open issues have owners and next actions; the outgoing draft excludes internal limits and comments.

Complete the workflow with DecoverAI

DecoverAI contract review supports this workflow in Word: choose the represented party and provide reseller-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. The lawyer edits or inserts suggestions as ordinary tracked changes in the signed-in Word user’s name and can dismiss findings with reasons. Tabular review supports work across documents; the playbook and approval record remain your work products. Retain legal judgment and source verification. To evaluate the workflow on reseller drafts, book a demo.

Frequently asked questions

Should every playbook deviation become a redline?

No. Separate material exposure from acceptable variation. Record the acceptance rationale and required approval so unnecessary edits do not obscure essential asks.

What if incorporated policies are unavailable?

Keep affected rows unresolved. Request applicable versions and propose limits on their ability to override negotiated terms. Any decision to proceed with unknown obligations requires explicit escalation.

Can another reseller agreement supply fallback wording?

Yes, as a drafting reference, not proof of market practice. Compare products, channel, hierarchy, customer model, and risk allocation before adapting it.

What if the supplier rejects renewal compensation?

Identify affected accounts and revenue assumptions. Consider narrower registered-account coverage, a defined compensation tail, or revised customer commitments. Document the approved trade-off and related survival language.

Sources

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo