When a deal goes sideways, the limitation-of-liability clause is usually the first paragraph the lawyers read. Minnesota has no general statute setting the rules; these clauses are enforced under common-law contract-construction principles, and the enforcement turns on drafting craft. A cap that looks identical to one across the table can survive in one contract and get struck down in another, depending on how it was written, who signed it, and what the clause tried to shield. In my practice, I see the same four or five drafting errors repeat: a cap that swallows fraud, a missing consequential-damages waiver, consumer language copy-pasted into a business-to-business deal, and carve-outs that contradict the indemnification clause. For more on how these pieces fit together across a business contract, our Minnesota business contract attorney overview sets the context.
How do Minnesota courts decide whether a liability cap is enforceable?
Minnesota courts enforce limitation-of-liability clauses under common-law contract-construction principles, not a specific statute. The starting point is whether the language is clear and unambiguous. If it is, and both sides had a fair chance to read and negotiate, courts usually enforce the cap as written. If the language is ambiguous, the court reads the ambiguity against the drafter, which almost always means against the party trying to enforce the cap. That single rule is why the best limitation clauses are short, direct, and use defined terms rather than generic “any and all” language.
Beyond clarity, courts look at bargaining power, sophistication of the parties, whether the clause is conspicuous (bolded, all-caps, or set off in its own section is good; buried in paragraph 38 is bad), and whether public policy blocks enforcement for the type of harm at issue. A cap written for a software license between two companies will often be enforced; the same words pasted into a consumer-facing home-services contract may not. The legal test is not a checklist. It is a weighing exercise that turns on facts. That is why the 7 factors that affect contract enforceability apply here with particular force.
What carve-outs should survive a liability cap?
Certain categories of wrongdoing should sit outside the cap, not inside it, because courts will not enforce a contract that tries to release a party from its own worst conduct. The standard carve-out set in Minnesota business contracts: fraud, willful or intentional misconduct, and gross negligence. Some drafters also carve out breaches of confidentiality, indemnification obligations for third-party IP infringement, and any liability that cannot be limited by law. Carving these out protects the rest of the cap. Leaving them inside is the single most common way a Minnesota court strikes an entire limitation clause rather than trimming it.
The drafting pattern is straightforward. After stating the cap, add a sentence that begins, “Notwithstanding the foregoing, the cap shall not apply to…” and list the carve-outs. Order matters less than completeness. The carve-outs for fraud and intentional misconduct are the most important because they are the ones a court is most likely to read in anyway; spelling them out just confirms the parties understood the rule. For how similar carve-outs work in the indemnification context, see indemnity carve-outs for gross negligence and fraud and carve-outs to caps in liability provisions.
How does bargaining power affect enforceability?
Bargaining power is one of the first things a Minnesota court examines when a liability cap is challenged. Two sophisticated businesses negotiating a commercial contract through counsel sit at one end of the spectrum: the cap almost always sticks. A take-it-or-leave-it contract handed to a consumer with no meaningful opportunity to negotiate sits at the other end, and the cap faces real unconscionability risk. Most contracts live somewhere in between, and the analysis gets fact-intensive fast.
The factors that weigh in: whether the party being capped had counsel, whether the clause was conspicuously drawn to their attention, whether they had a meaningful alternative (another vendor, another deal structure), and whether the price paid reflects the risk allocation. A low price combined with a tight cap can be defensible when both sides understood the trade-off. The same cap paired with a premium price and no discussion of risk allocation looks different. Minnesota’s unconscionability doctrine is described in the MN legal standard for unconscionable contracts. Where the cap is in a consumer-facing form contract, also review the overlap with unconscionable contracts generally.
Are gross negligence and willful misconduct always carved out?
In Minnesota, the safer working assumption is yes, even if the contract does not say so. Courts are reluctant to enforce a contract term that would release a party from gross negligence, willful misconduct, or intentional wrongdoing, on the theory that allowing parties to contract away responsibility for their worst acts invites behavior the law should not encourage. That reluctance sits as a backstop regardless of how the clause is drafted.
The practical drafting point is different from the legal rule. Even if the court will imply the carve-out, silent-cap clauses get challenged, and challenges are expensive to defend. An express carve-out for fraud, gross negligence, and intentional misconduct resolves the argument on the page, before it ever reaches a motion. In my practice, I routinely see parties try to delete these carve-outs during negotiation to “tighten” the cap. That is almost always the wrong move: it saves nothing legally (courts read them in anyway) and creates needless litigation risk if the relationship breaks. The drafting principles here overlap with liability caps for breach of confidentiality, where the same carve-out logic applies.
How does a liability cap interact with a consequential-damages waiver?
The liability cap and the consequential-damages waiver do different work and should sit in different sentences. The cap limits the total dollar amount a party can owe. The consequential-damages waiver removes whole categories of damages (lost profits, lost business opportunities, loss of goodwill, downstream losses to the customer’s customers) from the universe of recoverable harms. A contract can have one, both, or neither. The strongest protection uses both, drafted separately, with each clause doing its own job.
Combining them in a single sentence almost always creates ambiguity. A court reading “Supplier’s total liability shall not exceed fees paid, excluding consequential damages” could read that as a cap on direct damages with consequential damages separately barred, or as a cap that somehow includes consequential damages in a way the parties cannot later recover. Minnesota’s rule against drafter-favored ambiguity means the less protective reading often wins. The safer pattern is two back-to-back clauses, each in its own numbered section, each with its own carve-outs. For the damages side of that analysis, see consequential vs. direct damages in business contracts and consequential damages in contract breaches.
How does a liability cap interact with an indemnification obligation?
The default in most business contracts is that the cap applies to indemnification too, unless the contract says otherwise. That default produces more disputes than any other cap-related issue I see. A supplier agrees to indemnify the customer for third-party IP infringement claims, then learns that its indemnity obligation is capped at the fees the customer paid, which is often far less than the cost of defending the suit. The supplier thought it was giving meaningful protection; the customer thought it was getting meaningful protection; nobody negotiated the interaction.
The fix is an express statement. The contract should say whether the cap applies to indemnified claims, and if so, whether any indemnity obligations sit outside the cap. IP indemnification is frequently carved out of the cap (or given its own separate, larger cap) because IP exposure is often uninsurable and asymmetric. General contract indemnities are more often kept inside the cap. The negotiation point is not which answer is right in the abstract; it is which answer matches the risk the parties actually want to allocate. For the companion concept, see indemnification clauses in Minnesota contracts.
Does it matter whether the other side is a consumer or another business?
Yes, meaningfully. Minnesota courts treat business-to-business caps and consumer caps under different expectations even though the underlying contract-construction rules are the same. In a business-to-business contract, sophistication and equal bargaining position are presumed unless one side shows otherwise; the cap usually survives if the language is clear. In a consumer contract, the court starts from a default that the consumer had little or no ability to negotiate, and the cap has to earn enforcement: conspicuous language, fair scope, and no statutory overlay that blocks it.
Consumer-protection statutes can also blunt caps in specific contexts that go beyond the common-law rules, and those overlays vary by industry. A cap in a home-improvement contract, a healthcare contract, or a clickwrap consumer product contract can hit statutory limits the parties did not anticipate. If your business has both B2B and consumer versions of the same product, the liability clause should almost never be identical in both. For more on consumer-facing risk, see contract clauses violate consumer protection laws and the clickwrap-specific analysis in are clickwrap agreement liability waivers enforceable.
Are there public-policy limits on limitation clauses?
Yes. Outside any specific statute, Minnesota courts recognize a general public-policy limit: parties cannot contract out of liability for their own fraud, intentional torts, or grossly negligent conduct, and they cannot use private contract language to neutralize duties the law imposes on the public interest. That rule reaches beyond the standard carve-out list. For example, certain safety-related obligations, fiduciary duties, and statutory rights cannot be waived by contract, regardless of how clearly the clause is drawn.
The practical consequence is that a liability cap is not a universal shield. It is strongest against ordinary breach and negligence claims between sophisticated parties and weakest against intentional wrongdoing, fiduciary breaches, and statutory violations. The most common pattern I see is a business owner assuming the cap closes every exposure in the contract, then discovering after a dispute that the cap did not reach the claim the other side actually brought. The best drafting response is to know which claims the cap actually limits, which it does not, and to size insurance accordingly.
What drafting patterns hold up best?
A few patterns repeatedly survive Minnesota scrutiny. First, the cap sits in its own numbered section with a clear heading (“Limitation of Liability”), not buried inside a larger clause. Second, the cap is in conspicuous type (bolded or all-caps for the key limiting language) so there is no question the other side was on notice. Third, the carve-outs are express: fraud, intentional misconduct, gross negligence, indemnification obligations (if appropriate), and any liability that cannot be limited by law. Fourth, the consequential-damages waiver sits in its own sentence, not folded into the cap. Fifth, the cap amount is tied to something specific and measurable (fees paid in the prior 12 months, insurance proceeds, a stated dollar figure), not zero and not an arbitrary nominal amount.
The structural point is that limitation-of-liability clauses fail more often from sloppy drafting than from hostile law. Minnesota’s common-law rules are predictable. A careful clause with clear language, conspicuous presentation, and proper carve-outs enforces cleanly most of the time. A clause that tries to do too much, hide the ball, or paper over unequal bargaining power invites the challenge and often loses it. For additional drafting context on related clauses, see 5 contract clauses every growing business should understand.
Can I cap my liability at the fees the customer paid?
Yes, a fee-based cap is common and usually enforceable between businesses in Minnesota if the language is clear. The cap works best when the contract defines what counts (fees paid in the prior 12 months is a common formulation) and lists the carve-outs that sit outside the cap. A cap equal to zero or a purely nominal number invites unconscionability challenges, so most drafters scale the cap to something the parties actually bargained for.
Do liability caps cover fraud claims in Minnesota?
No, not reliably. Minnesota courts generally refuse to enforce contract language that purports to release a party from its own fraud, intentional misconduct, or gross negligence. A well-drafted cap says so expressly, carving fraud and intentional wrongs out of the cap so the clause does not get struck down wholesale. Leaving fraud inside the cap is a common drafting error that puts the whole provision at risk.
Is a liability cap enforceable against a consumer?
Sometimes, but the bar is much higher than in a business-to-business contract. Minnesota courts look harder at bargaining power, conspicuousness, and whether the consumer had any real ability to negotiate. Caps buried in fine print, in adhesion contracts, or in clickwrap agreements face meaningful unconscionability risk. Statutory consumer-protection overlays can also blunt the cap in specific contexts.
Should the cap include the consequential-damages waiver or be separate?
Separate, almost always. A liability cap limits total dollar exposure. A consequential-damages waiver removes an entire category of damages (lost profits, lost business, downstream losses) regardless of the cap. Collapsing them into one sentence usually creates ambiguity, and ambiguity in Minnesota liability clauses is resolved against the drafter. Two clauses, two purposes, two separate sentences.
What if the liability cap conflicts with the indemnification clause?
Minnesota courts try to read the clauses together before picking a winner. If the indemnification clause is silent on the cap, the default assumption in most business contracts is that the cap applies to indemnity too, unless the contract says otherwise. To avoid the fight, well-drafted contracts say expressly whether the cap applies to indemnified claims, and the answer is usually different for third-party IP indemnities than for ordinary contract indemnities.
Does signing the contract mean the cap is automatically enforceable?
No. A signature is necessary but not sufficient. Minnesota courts still examine whether the language is clear and unambiguous, whether the carve-outs (fraud, intentional misconduct, gross negligence) are preserved, whether the clause is conspicuous, and whether the bargaining positions were comparable. A signed contract with a buried, broad-form cap still fails more often than business owners expect.
Closing thought
A limitation-of-liability clause is not a fire-and-forget paragraph. It has to match the contract it lives in, the parties who signed it, and the risks the business actually faces. Minnesota’s common-law approach gives drafters real room to allocate risk, but only if the clause is written with care: clear language, express carve-outs, conspicuous presentation, and a cap tied to something the parties actually bargained for. For a practical read on the specific clause you are about to sign or send, our Minnesota business contract practice handles this work regularly; email aaron@aaronhall.com with the contract and a short description of the deal and I can give you a candid read on where the clause is strong and where it is exposed.
