Vendor, Supplier, and SaaS Agreements in Tennessee: What the Buyer Should Read Before Signing

Most vendor contracts arrive as the vendor's form: a quote with terms on the back, a master services agreement, or a click-through subscription. How much room the buyer has depends on which Tennessee rules apply and what the paper says. Here are the provisions that tend to matter most, and the Tennessee law behind them.

Goods, services, or software: which rules apply

Tennessee's version of UCC Article 2 applies to transactions in goods (Tenn. Code Ann. § 47-2-102). "Goods" means things that are movable at the time they are identified to the contract (§ 47-2-105(1)). Equipment, inventory, and supplies are goods. Cleaning, IT support, marketing, and consulting are services, governed by general contract law rather than Article 2.

Many deals mix the two. For contracts made before July 1, 2026, Tennessee courts look at the transaction as a whole and ask which predominates, rather than splitting it into a goods part and a non-goods part (Hudson v. Town & Country True Value Hardware, Inc., Tenn. 1984, involving the sale of a business together with its real estate). For goods and services, the Court of Appeals weighs the contract's language, the supplier's business, why the parties contracted, and how the price splits between goods and services. Applying that test, it treated a home automation system with equipment, installation, and programming as predominantly a sale of goods, and found persuasive an earlier Court of Appeals decision treating the sale of an integrated computer system, with training, as a sale of goods (Audio Visual Artistry v. Tanzer, Tenn. Ct. App. 2012). For contracts made on or after July 1, 2026, the statute addresses these hybrid transactions directly: a single transaction that combines a sale of goods with services, a lease of other goods, or a sale, lease, or license of property other than goods. Which part predominates still matters, but the answer is no longer all or nothing. If the sale-of-goods aspects predominate, Article 2 applies to the transaction, though other law can still apply to the parts that do not involve the sale of goods. If they do not predominate, only the Article 2 provisions that relate primarily to the goods apply (Tenn. Code Ann. §§ 47-2-102(2), 47-2-106(5), as amended by 2026 Tenn. Pub. Acts ch. 704).

Hosted software is a harder fit, because the customer may never receive anything movable. I am not aware of a Tennessee appellate decision deciding whether a SaaS subscription is a transaction in goods under Article 2, so the practical approach is to read a SaaS agreement as if its own terms will decide most disputes.

When the purchase order and the vendor's terms do not match

A purchase order goes out with the buyer's terms, the vendor's acknowledgment comes back with different ones, and the goods ship. Under § 47-2-207(1), a definite and seasonable acceptance, or a written confirmation sent within a reasonable time, operates as an acceptance even though it states additional or different terms, unless acceptance is expressly made conditional on assent to them. The additional terms are proposals, and between merchants they become part of the contract unless (§ 47-2-207(2)):

• the offer expressly limits acceptance to its own terms;
• they materially alter the contract; or
• notice of objection has already been given, or is given within a reasonable time after notice of them is received.

"Between merchants" means both parties are chargeable with the knowledge or skill of merchants (§ 47-2-104(3)). If the writings do not form a contract but both sides act as though one exists, the terms are those on which the writings agree plus the UCC's gap-fillers (§ 47-2-207(3)).

The practical issue is that paperwork exchanged at the ordering stage can decide which warranty, remedy, and forum terms apply later. A purchase order that limits acceptance to its own terms, and a prompt written objection to new terms, are the tools the statute recognizes. For services and SaaS, the question is simply which document was signed or accepted.

Warranties and the disclaimers that remove them

For goods, Tennessee law implies a warranty of merchantability when the seller is a merchant with respect to goods of that kind (§ 47-2-314(1)), and a warranty of fitness for a particular purpose when the seller has reason to know the buyer's purpose and that the buyer is relying on the seller's skill or judgment (§ 47-2-315). Vendor forms usually disclaim both, and the statute sets the rules (§ 47-2-316):

• To exclude or modify merchantability, the language must mention merchantability and, in a writing, must be conspicuous.
• To exclude or modify fitness, the exclusion must be in a writing and conspicuous.
• Unless the circumstances indicate otherwise, expressions like "as is" or "with all faults" exclude all implied warranties.

What is left is usually the vendor's express limited warranty: what it covers, for how long, and what the vendor must do when something fails.

Limited remedies and consequential damages

Article 2 lets the contract substitute its own remedies, such as repair or replacement, or a refund. A stated remedy is optional unless expressly made exclusive (§ 47-2-719(1)). Two limits apply:

• If an exclusive or limited remedy fails of its essential purpose, the buyer may pursue the UCC's other remedies (§ 47-2-719(2)).
• Consequential damages may be limited or excluded unless the limitation is unconscionable, and limiting damages where the loss is commercial is not prima facie unconscionable (§ 47-2-719(3)).

For a business buyer, consequential damages are often most of the loss: lost profits, downtime, and the cost of replacing the vendor. Because a commercial waiver of those damages is not presumptively unconscionable, the time to deal with it is before signing. A court may refuse to enforce an unconscionable clause (§ 47-2-302), but that is an argument, not a plan.

Liability caps and exculpatory clauses

In Copeland v. HealthSouth/Methodist Rehabilitation Hospital, LP (Tenn. 2018), the Tennessee Supreme Court held that whether an exculpatory clause is enforceable depends on the totality of the circumstances, weighing the parties' relative bargaining power, the clarity of the language (which should be clear, unambiguous, and unmistakable about what the signer gives up), and public policy. The Court also said a party may not, for public policy reasons, exempt itself from liability for gross negligence, reckless conduct, or intentional wrongdoing.

Copeland's facts matter: a patient signed a release before a medical transport company drove him to an appointment, and the release was held unenforceable. That was not a negotiated contract between two businesses, and it was a full release, not a cap. In reviewing earlier cases, Copeland treated clauses limiting liability to a sum certain as distinguishable from a full release. One of them, Houghland v. Security Alarms & Services, Inc. (Tenn. 1988), upheld an alarm company's clause fixing its liability at a stated amount, where the homeowners could have paid higher rates for greater liability. Houghland said limitations against liability for negligence or breach of contract have generally been upheld in Tennessee in the absence of fraud or overreaching. I am not aware of a Tennessee Supreme Court decision applying Copeland to a negotiated liability cap between two businesses, so whether its factors govern a cap at all, and how they play out when a small business buys from a much larger vendor, is not settled.

A later case shows why the contract carries so much weight. In Milan Supply Chain Solutions, Inc. v. Navistar, Inc. (Tenn. 2021), the Court held that when a fraud claim seeks only economic losses and rests solely on misrepresentations or nondisclosures about the quality of goods sold under a contract between sophisticated commercial parties, the economic loss doctrine bars the claim. If the warranty, remedy, and cap are thin, a tort claim may not fill the gap.

Indemnity: who pays when someone else sues

Vendor forms often require the customer to indemnify the vendor, sometimes more broadly than the reverse. As a general rule, Tennessee does not treat an agreement to indemnify a party against its own negligence as contrary to public policy, but the Tennessee Supreme Court has required that intent to be expressed in clear and unequivocal terms (Kroger Co. v. Giem, Tenn. 1964; Kellogg Co. v. Sanitors, Inc., Tenn. 1973). In Kroger, a contractor's general promise to hold the owner harmless did not cover a loss the owner's own negligence helped cause. In Kellogg, a janitorial contractor's promise to hold the plant owner harmless from "any and all" claims by the contractor's employees did cover the owner's negligence, because a narrower reading would have left that paragraph meaningless. Wording and structure decide these disputes.

There is a statutory exception. In a contract for the construction, alteration, repair, or maintenance of a building or structure, a promise to indemnify the other party against bodily injury or property damage caused by that party's sole negligence is void (Tenn. Code Ann. § 62-6-123). Kellogg was decided before that statute was enacted in 1976, so for repair and maintenance vendors on a property, the statute has to be read alongside the cases.

Auto-renewal: Tennessee's statute protects consumers, not businesses

Tennessee's automatic renewal statute requires clear disclosure, affirmative consent, an acknowledgment with cancellation information, and online cancellation for offers accepted online (Tenn. Code Ann. § 47-18-133). But it applies to offers made to a consumer, and it defines "consumer" as an individual who acquires goods or services for personal, family, or household purposes (§ 47-18-133(f)(2)). A business buying software or services for the business falls outside that definition, and I am not aware of a Tennessee statute giving business buyers the same protection.

The broader Consumer Protection Act can have a similar limit: in Milan, trucks a company bought for commercial purposes were not "goods" as defined in the part of the Act the buyer relied on. For a business, the renewal term, the notice window, and how notice must be given all come from the contract.

SaaS and your data

Tennessee's breach notice statute applies to an "information holder," a person or business conducting business in Tennessee that owns or licenses computerized personal information of Tennessee residents (Tenn. Code Ann. § 47-18-2107(a)(3)). "Personal information" is narrow: a name plus a Social Security number, a driver license number, or a financial account or card number with any required code or password (§ 47-18-2107(a)(4)).

• An information holder must notify affected Tennessee residents no later than 45 days after discovery or notification of a breach, unless law enforcement needs justify a delay (§ 47-18-2107(b), (d)).
• An information holder that maintains personal information it does not own must notify the owner or licensee within the same 45-day period (§ 47-18-2107(c)).
• The section does not apply to an information holder subject to Title V of the Gramm-Leach-Bliley Act or to HIPAA (§ 47-18-2107(i)).

Forty-five days is the outer limit, and the duty to notify customers may still fall on the business that owns the data. The statute also lets a customer of an information holder, including a business, who is injured by a violation sue for damages and an injunction (§ 47-18-2107(h)), but I have not found a Tennessee appellate decision applying that to a vendor's late notice to a business customer. That is why the agreement's own notice deadline, cooperation duties, and allocation of breach costs matter.

Tennessee's privacy statute, the Tennessee Information Protection Act, does require a controller's contract with its processor to provide for deleting or returning personal information when services end (Tenn. Code Ann. § 47-18-3306(b)(2)). Most small businesses are outside it. It applies only to businesses that target Tennessee residents, have more than $25 million in revenue, and handle the personal information of at least 175,000 Tennessee consumers in a year (or 25,000, if more than half their revenue comes from selling it), and it does not count people acting in a commercial or employment context as consumers (§§ 47-18-3302(7), -3303). For a business below those lines, I am not aware of a Tennessee statute requiring a SaaS vendor to return its data when the relationship ends. Exit rights come from the contract.

Deadlines, governing law, and where you would sue

• Sale of goods: suit must be filed within four years after the claim accrues, and the original agreement may shorten that to not less than one year but may not extend it. A claim accrues when the breach occurs, even if the buyer does not know, and a warranty breach occurs on tender of delivery unless the warranty explicitly extends to future performance and discovery of the breach must await the time of that performance (§ 47-2-725(1), (2)).
• Services and other contracts: actions on contracts not otherwise expressly provided for must be brought within six years (Tenn. Code Ann. § 28-3-109(a)(3)). Vendor forms sometimes shorten that too.
• Governing law: for transactions under the UCC, the parties may choose Tennessee law or another state's law when the transaction bears a reasonable relation to both (Tenn. Code Ann. § 47-1-301(a)). For other contracts, the Court of Appeals honors the parties' choice if the provision was executed in good faith, the chosen state bears a material connection to the transaction, the choice is reasonable and not a sham, and it is not contrary to a fundamental policy of a state with a materially greater interest (Vantage Technology, LLC v. Cross, Tenn. Ct. App. 1999, applying Goodwin Bros. Leasing, Inc. v. H & B Inc., Tenn. 1980).
• Forum: Tennessee courts enforce a forum selection clause unless the party opposing it shows enforcement would be unfair and inequitable, considering factors such as whether the chosen forum can give effective relief, whether it is substantially less convenient, and whether the clause was obtained by abuse of economic power or other unconscionable means (Dyersburg Machine Works, Inc. v. Rentenbach Engineering Co., Tenn. 1983).

If you are reviewing a supplier, service, or software agreement for a Tennessee business, my office can review the agreement and the points worth negotiating. If the vendor is an individual doing the work, independent contractor agreements raise their own classification and ownership questions.

Educational disclaimer: This article provides general Tennessee educational information only and is not legal advice for any specific agreement or business.