Limitation of Liability in Commercial Contracts: How Liability Caps and Consequential Damages Waivers Allocate Risk

By Hank FasthoffJuly 6, 2026

Every commercial contract allocates risk between the parties, and the limitation of liability clause is where the most significant risk decisions are made. It determines how much money one party can recover from the other when something goes wrong. Without it, a minor service failure or a product defect could expose a vendor to damages worth many times the contract's value. With a poorly drafted one, a customer could waive the right to recover meaningful compensation for losses the vendor caused.

Limitation of liability is the most negotiated term in commercial contracts globally and has held that position for over two decades according to World Commerce and Contracting's annual surveys. It's also the provision most likely to be drafted from boilerplate without being tailored to the transaction, which is how parties end up with caps that are too low to provide meaningful protection, waivers that exclude damages they didn't intend to give up, and carve-outs that swallow the limitation entirely.

The Two Components

A limitation of liability clause has two distinct mechanisms that work together.

First, a liability cap sets a maximum dollar amount that one party can recover from the other for all claims arising under the agreement. Common cap formulas include the total fees paid under the agreement, fees paid in the preceding 12 months (standard in subscription and SaaS contracts), a fixed dollar amount negotiated at signing, or a multiple of the contract value (2x or 3x for higher-risk engagements). Whatever formula is used, the cap represents the ceiling on the paying party's aggregate exposure for direct damages.

Second, an exclusion of certain types of damages removes entire categories of loss from recovery regardless of the cap amount. Most commercial contracts exclude consequential, indirect, incidental, special, and punitive damages. Even if the liability cap is $5 million, excluded categories of damages can't be recovered at all.

These two mechanisms are independent. A party can recover direct damages up to the cap, but can't recover consequential damages even if the cap hasn't been reached. A contract that caps liability at 12 months of fees and excludes consequential damages has two separate limitations operating simultaneously, and both must be evaluated to understand the actual risk allocation.

Direct Versus Consequential Damages

The distinction between direct and consequential damages determines what falls inside the exclusion. Direct damages are losses that arise naturally and necessarily from the breach. If a vendor delivers defective software that requires $50,000 to fix, the repair cost is a direct damage. If a supplier delivers non-conforming materials that must be replaced, the replacement cost is a direct damage. Direct damages are the immediate, foreseeable cost of the breach itself.

Consequential damages (also called indirect or special damages) are losses that result from the breach but aren't the immediate cost of the breach itself. They're the downstream business impact. If the defective software causes the customer's e-commerce platform to go offline for 24 hours and the customer loses $200,000 in sales, the lost sales are consequential damages. If non-conforming materials delay a construction project and the owner incurs $100,000 in liquidated damages from the project owner, those delay damages are consequential.

In practice, the line between direct and consequential damages is less precise than the definitions suggest. Texas courts and courts in other jurisdictions don't always agree on which side of the line a particular category of loss falls. Lost profits, for example, are treated as consequential damages in most contexts but can be classified as direct damages in some circumstances (such as when the entire purpose of the contract was to generate profits). If your consequential damages waiver doesn't define the term, you're leaving it to a court to decide what you waived, which is a dispute you didn't need to have.

Carve-Outs and Super-Caps

A liability cap isn't absolute. Most commercial contracts carve out specific categories of claims that fall outside the general cap, either subject to a higher "super-cap" or with no cap at all. Carve-outs exist because certain risks are too significant to limit to the general cap amount.

Common carve-outs include IP indemnification (the provider's obligation to defend and indemnify the customer against third-party intellectual property infringement claims), confidentiality breaches (particularly where the breaching party had access to trade secrets, customer data, or other sensitive information), data security incidents (breach notification costs, regulatory fines, credit monitoring for affected individuals), willful misconduct and fraud (courts in Texas won't enforce liability limitations for gross negligence, intentional misconduct, or fraud as a matter of public policy), bodily injury and property damage (most jurisdictions prohibit limiting liability for physical harm), and payment obligations (amounts owed under the contract shouldn't be subject to the liability cap).

A super-cap sets an elevated ceiling for carve-out claims rather than leaving them entirely uncapped. If the general liability cap is 12 months of fees, the super-cap for data security and confidentiality breaches might be 3x to 5x the annual fees. Super-caps are more commercially reasonable than unlimited liability for the provider, while still giving the customer meaningful recourse for high-risk events.

Every carve-out weakens the cap. A provider who agrees to carve out IP indemnity, confidentiality, data security, willful misconduct, bodily injury, and payment obligations has a liability cap that applies to almost nothing except ordinary breach of contract claims. Negotiate carve-outs deliberately and understand what remains inside the cap after the carve-outs are taken out.

Interaction with Indemnification

Limitation of liability and indemnification serve different purposes but interact in ways that create ambiguity if the contract doesn't address the relationship between them.

Limitation of liability caps what one contracting party can recover from the other. Indemnification requires one party to compensate the other for losses caused by third-party claims (a customer who gets sued because the vendor's product infringed someone's patent, for example). Limitation of liability protects you from your counterparty. Indemnification protects you from third parties through your counterparty's obligation to defend and pay.

If the contract doesn't specify whether indemnification obligations are inside or outside the liability cap, you have one of the most heavily negotiated sub-issues in commercial contracting. Customers argue that indemnification should fall outside the cap because third-party claims can produce judgments far exceeding the contract value. Vendors argue that indemnification should be inside the cap because the cap is supposed to define total exposure. The answer should be stated in the contract, not left to a court.

Best practice is to address the interaction in one of three ways. Indemnification obligations are inside the general cap (vendor-favorable). Indemnification obligations are outside the general cap but subject to a separate super-cap (balanced). Indemnification obligations are entirely uncapped (customer-favorable). Whichever approach you choose, state it in the limitation of liability clause so there's no ambiguity.

Texas Enforceability

Texas courts generally enforce limitation of liability clauses in commercial contracts between sophisticated parties, consistent with the state's strong public policy favoring freedom of contract. But enforceability depends on drafting and presentation.

Under the fair notice doctrine, a limitation of liability clause must satisfy two requirements. First, the clause must express the intent to limit liability with sufficient specificity that the other party understands what's being limited. Second, the clause must be conspicuous, meaning it must be presented in a way that a reasonable person would notice it. Texas courts have adopted the UCC § 1.201 standard for conspicuousness, which requires that the language be displayed so that a reasonable person against whom it's to operate ought to notice it. Capitalization, bold text, larger font, separate headings, and other visual distinctions all contribute to conspicuousness.

Texas courts won't enforce limitation of liability clauses that attempt to limit liability for gross negligence, intentional misconduct, or fraud. These limitations violate public policy. If your contract includes a limitation clause, make sure it includes an exception for these categories, because a court will invalidate a limitation that purports to cover them, and the invalidation could affect the entire clause depending on how it's drafted.

For contracts involving the sale of goods, Texas Business and Commerce Code § 2.719(3) (the Texas UCC) allows parties to limit or exclude consequential damages unless the limitation is unconscionable. In a commercial context (as opposed to a consumer context), consequential damage exclusions carry a presumption of conscionability. Under § 2.302, a court may refuse to enforce a contract or clause that was unconscionable at the time it was made, but the bar for unconscionability in Texas is high. Courts focus on whether the clause is so one-sided that it shocks the conscience, considering the parties' commercial sophistication and bargaining power.

Alignment with Insurance

A liability cap that isn't coordinated with insurance coverage creates an exposure that nobody is paying for. If the contract caps liability at $5 million but the vendor's errors and omissions policy covers only $1 million, there's a $4 million difference between what the vendor has agreed to pay and what the vendor's insurance will cover. That difference comes out of the vendor's operating funds, which may or may not be sufficient.

When setting liability caps, both parties should consider whether the cap is commercially rational relative to the vendor's (or the customer's) insurance program, whether the carve-out categories (particularly data security and IP indemnity) are insurable under the vendor's cyber liability or professional liability policies, and whether the contract requires the vendor to maintain insurance coverage at specified minimums. Aligning liability caps with insurance limits ensures that the risk allocation in the contract is backed by a realistic source of funds.

Practical Recommendations

Don't accept boilerplate limitation of liability language without evaluating it against the specific transaction. A cap of 12 months of fees may be reasonable for a $10,000 monthly engagement but inadequate for a $500,000 monthly engagement where a failure could cause millions in downstream losses.

Define "consequential damages" in the contract if your governing jurisdiction has inconsistent case law on what the term includes. An enumerated list (lost profits, lost revenue, loss of data, loss of business opportunity, cost of substitute services) eliminates ambiguity and prevents disputes about classification.

Address the indemnification interaction in the limitation clause itself. State whether indemnification obligations are inside the general cap, subject to a separate super-cap, or uncapped.

Include carve-outs for the risks that justify them and resist carve-outs for risks that don't. Every carve-out is a negotiation point, and agreeing to too many turns the liability cap into a formality.

Make the clause conspicuous. In Texas, a limitation of liability clause that's buried in dense text without visual distinction may not satisfy the fair notice doctrine, and an unenforceable limitation is worse than no limitation, because you drafted one, relied on it, and discovered in litigation that it didn't protect you.

Don't attempt to limit liability for gross negligence, willful misconduct, or fraud. Texas courts won't enforce those limitations, and including them in the clause may call the entire provision into question.