|
By Pam Fulmer
Our earlier piece made two points that sit in tension. First, when a software vendor’s exclusive “repair or replace” remedy collapses, Article 2 of the Uniform Commercial Code may give a buyer a statutory path around contractual remedy limitations. See Cal. Com. Code § 2719. Second—and inconveniently—that doctrine applies only if Article 2 governs the transaction. A modern cloud ERP delivered as software-as-a-service may be characterized as a service rather than a sale of goods. If a court holds that the enterprise system was a service, the UCC’s cleanest tool may disappear with it. So, the natural question is: if the UCC is off the table, is the customer defenseless against a vendor’s one-sided agreement? No. California common law and the Civil Code supply a different set of tools. A 2025 California Supreme Court decision, New Eng. Country Foods v. Vanlaw Food Prod., Inc., 567 P.3d 63, 331 Cal. Rptr. 3d 890 (Cal. 2025), has made one of them--Civil Code Section 1668—considerably sharper. First, an Honest Concession There is no freestanding California common-law doctrine called “failure of essential purpose.” That phrase belongs to UCC Section 2-719 and its California counterpart, Commercial Code Section 2719. A customer cannot simply invoke it in a services case and expect the same statutory framework to apply. What California does have is a cluster of common-law and statutory doctrines that can accomplish some of the same practical work: freeing a customer from contractual limitations when the vendor’s conduct, or the collapse of the bargain, justifies relief outside ordinary capped contract damages. The key is to understand which tool gets you past the vendor’s damages cap. Ordinary breach doctrine may establish liability, but it often leaves a negotiated limitation-of-liability clause standing. Rescission, Civil Code section 1668, fraud, and unconscionability are the doctrines that attack the limitations themselves. Tool One: Rescission for Failure of Consideration The closest functional cousin to “you are not trapped by a remedy that failed” is rescission. A contract is extinguished by rescission. Cal. Civ. Code § 1688. A party may rescind where the consideration for its obligation fails, in whole or in part, through the fault of the other party, or where the consideration fails in a material respect before it is rendered. Cal. Civ. Code § 1689(b)(2), (b)(4). For a failed ERP, the theory is intuitive. The customer bargained for an operational, integrated system that would run core business functions. If the vendor never delivers a working system—go-live never occurs, the system is rolled back, or critical functions never work—the customer may argue that the consideration failed in a material respect. The strategic payoff can be significant. Rescission seeks to unwind the agreement rather than enforce it. If successful, the customer may obtain restitutionary relief and avoid contractual limitations that presuppose an enforceable contract. See Cal. Civ. Code § 1692. California courts recognize that rescission may support broader restorative relief designed to return the parties to their pre-contract positions. See Runyan v. Pacific Air Industries, Inc., 2 Cal. 3d 304 (1970). But the tradeoffs are real. Rescission requires prompt notice after discovering the facts entitling the party to rescind and generally requires restoration, or an offer to restore, what the rescinding party received. Cal. Civ. Code § 1691. It is also a different remedial posture from expectation damages: rescission is about unwinding the deal, not keeping the contract and recovering the full benefit of the bargain. For a customer that has sunk years and millions into a system it still wants fixed, that is a meaningful choice. Pleading rescission and damages in the alternative can preserve flexibility. Tool Two: Civil Code § 1668—and the 2025 VanLaw Decision The vendor’s most powerful weapons in a failed-implementation case are often its limitation-of-liability clause and consequential-damages waiver. California Civil Code Section 1668 is the most direct statutory answer to those provisions when the claim involves fraud, willful injury, or violation of law. Section 1668 provides that contracts having as their object, directly or indirectly, exemption from responsibility for one’s own fraud, willful injury to the person or property of another, or violation of law are against public policy. Cal. Civ. Code § 1668. Two California Supreme Court decisions are especially important. First, in City of Santa Barbara v. Superior Court, 41 Cal. 4th 747 (2007), the court held that an agreement purporting to release liability for future gross negligence is generally unenforceable as a matter of public policy. That rule does not depend on the transaction-by-transaction public-interest analysis used for ordinary negligence releases. Second, in New Eng. Country Foods v. Vanlaw Food Prod., Inc., 567 P.3d 63, 331 Cal. Rptr. 3d 890 (Cal. 2025), the California Supreme Court held that Section 1668 invalidates limitations on damages for willful injury to the person or property of another. The court rejected the argument that Section 1668 reaches only complete exculpation clauses and not damages limitations. It also rejected a case-by-case exception based on the parties’ sophistication or commercial bargaining context. VanLaw matters because many vendor agreements do not say, “we are not liable for intentional wrongdoing.” They instead cap damages, exclude lost profits, and bar consequential or punitive damages. VanLaw confirms that, at least for willful injury within section 1668, a clause that substantially limits damages can be invalid even if it does not eliminate every theoretical remedy. The implications for ERP litigation are substantial. If the customer can establish a qualifying independent tort—such as intentional misrepresentation, intentional interference, or other willful injury—or a qualifying violation of law, the vendor’s damages cap and consequential-damages waiver may be unenforceable as to that claim. That result is UCC-independent: it does not matter whether the ERP is classified as a good or a service. But the limitation is equally important. Section 1668 does not turn an ordinary breach of contract into an uncapped tort case. VanLaw expressly preserved the distinction between breach of contract and violation of an independent duty. The court stated that Section 1668 does not preclude parties from limiting liability for pure breaches of contract absent violation of an independent duty within the statute’s scope. Recent California authority also continues to police that boundary through the economic loss rule. See Rattagan v. Uber Technologies, Inc., 553 P.3d 1213, 324 Cal. Rptr. 3d 433 (Cal. 2024); Robinson Helicopter Co., Inc. v. Dana Corp., 34 Cal. 4th 979 (2004). The practical upshot is that the Section 1668 route demands real tort or statutory-duty facts. A disappointing system is not enough. A concrete pre-sale misrepresentation, concealment, willful injury, gross negligence, or qualifying statutory violation may be. Tool Three: Fraudulent Inducement Fraud is both a claim in its own right and a gateway to the tools above. ERP sales cycles are full of representations: capability demos, “it does that out of the box,” implementation timelines, integration promises, industry-fit assurances, and statements about the vendor’s experience with comparable deployments. Where those representations were false, material, and relied upon, fraudulent inducement can support rescission and can also bring section 1668 into play. The fraud claim must be pleaded and proved with discipline: the specific statement, the speaker, the timing, the falsity, the customer’s reliance, and resulting harm. California law supports the general principle that limitation-of-liability clauses do not protect fraud. In Food Safety Net Servs. v. ECO Safe Sys. USA, Inc., 209 Cal. App. 4th 1118 (2012), the court stated that limitation-of-liability clauses are ineffective as to fraud and misrepresentation under section 1668. But Food Safety is also a cautionary case: the fraud claim failed because the plaintiff did not establish tortious conduct independent of the contract, and the economic loss rule barred repackaging contract nonperformance as fraud. That is the lesson for ERP disputes. Fraud framed as generalized disappointment will not survive. Fraud tied to concrete, provable, extra-contractual or pre-contractual misrepresentations may unlock rescission, section 1668, and uncapped tort remedies. Tool Four: Unconscionability Under Civil Code § 1670.5 Unconscionability is not a UCC-only concept. California’s general unconscionability statute empowers courts to refuse to enforce an unconscionable contract or clause, or to limit its application to avoid an unconscionable result. Cal. Civ. Code § 1670.5. The familiar framework has both procedural and substantive components. Procedural unconscionability focuses on oppression or surprise, often from unequal bargaining power or non-negotiable form terms. Substantive unconscionability focuses on overly harsh or one-sided terms. A limitation clause that leaves the customer with no meaningful remedy for a total implementation failure may be a candidate for substantive unconscionability. The caveat is that unconscionability is an uphill fight between sophisticated commercial parties negotiating a major enterprise deal. California courts generally enforce limitation-of-liability clauses in ordinary commercial contracts unless a doctrine such as unconscionability, section 1668, or public policy applies. Food Safety illustrates that point: the court enforced a limitation clause against contract and ordinary-negligence theories where the plaintiff did not show unconscionability or a public-interest basis to invalidate it. Unconscionability is therefore best treated as a supporting theory, especially where the vendor’s terms were genuinely non-negotiable, the cap is illusory, or the remedy structure leaves the customer with no practical recourse for catastrophic failure. Tool Five: Material Breach—and Why It Is Not Enough on Its Own Common law has its own concept of a failure so serious that it excuses further performance: material breach. In a failed ERP case, the customer may argue that the vendor’s failure to deliver a functioning system was a material breach that discharged the customer’s remaining obligations and supported damages. But this doctrine does not, by itself, defeat a limitation-of-liability clause. Limitation clauses are drafted for breaches; that is their purpose. California courts generally enforce them in ordinary commercial settings unless a separate doctrine attacks the clause itself. That is why material breach supplies the liability theory, but rescission, section 1668, fraud, and unconscionability do the cap-defeating work. A customer should not assume that proving a catastrophic breach automatically means recovering uncapped consequential damages. The Balance Sheet Compared with the UCC path, the common-law playbook has disadvantages worth stating plainly. There are no UCC implied warranties if Article 2 does not apply. The customer must rely on express contractual promises, tort duties, statutory doctrines, and equitable remedies. Section 1668 requires more than a breach; it requires fraud, willful injury, violation of law, or another qualifying independent duty. The economic loss rule limits attempts to repackage disappointed contractual expectations as tort claims. Rescission requires prompt action and may force a strategic election. Unconscionability is difficult between sophisticated parties. But the advantages are real. These doctrines do not depend on proving that a cloud ERP is a “good.” Rescission can unwind the contract. Section 1668 can invalidate damages limitations for qualifying fraud, willful injury, or statutory-duty claims. And after VanLaw, a vendor cannot save a damages cap merely by arguing that the clause leaves some theoretical remedy in place. A Practical Playbook Plead in the Alternative and Preserve Rescission Early Preserve breach-of-contract damages, but plead rescission promptly where the facts support a material failure of consideration. Delay can waive rescission, so the remedy should not be an afterthought. Build the Fraud Record From Day One Collect demos, RFP responses, implementation promises, capability matrices, sales emails, and executive assurances. The question is not just whether the project failed; it is whether the vendor made a specific false representation or concealment that induced the deal. Frame Independent Torts Carefully To survive the economic loss rule, identify duties and conduct independent of the contract. Do not rely on artful relabeling of missed milestones or defective performance. Tie tort claims to misrepresentation, concealment, willful injury, or other conduct recognized as independent under California law. Use Section 1668 Where the Claim Qualifies After VanLaw, Section 1668 should be front and center when the customer has a genuine intentional tort or willful-injury theory. It should not be overused for ordinary breach. Its power comes from matching the doctrine to the facts. Negotiate Express Warranties on the Front End Because implied UCC warranties may not apply, buyers should negotiate express warranties and objective commitments: acceptance criteria, go-live conditions, data-migration accuracy, integration requirements, uptime, response times, project staffing, and remedies that are meaningful even if Article 2 never applies. Watch the Choice-of-Law Clause California’s Civil Code Section 1668 and VanLaw are favorable to customers with qualifying tort or statutory-duty claims. A vendor’s out-of-state governing-law clause may materially change the analysis. Bottom Line The UCC gives a wronged software buyer one clean, well-worn statutory doctrine. California common law and the Civil Code give the buyer a more complex toolkit: rescission, Section 1668, fraud, unconscionability, and material breach.. For SaaS deals that dominate enterprise buying today, that distinction is no longer academic. And after VanLaw, a vendor’s limitation clause is more vulnerable when the customer can plead and prove genuine intentional wrongdoing or another independent duty within section 1668. The customer whose implementation was sold on promises the vendor could not—or never intended to—keep may have a viable path outside the UCC. But the path must be built deliberately, with facts that attack the limitation clause itself rather than merely proving that the project failed. This article is provided for general informational purposes only and does not constitute legal advice or create an attorney-client relationship. The doctrines discussed are fact-intensive and continue to develop. The availability of rescission, the reach of Civil Code section 1668 after VanLaw, and the operation of the economic loss rule all turn on the specific contract and conduct at issue. Companies facing a cloud ERP dispute should consult qualified counsel.
0 Comments
By Pam Fulmer
Is Your Cloud ERP Even Governed by the UCC? When an enterprise software implementation goes sideways, a customer’s lawyers often reach for the Uniform Commercial Code. Implied warranties of merchantability and fitness. Perfect tender. And the failed-remedy rule: when an exclusive or limited remedy fails of its essential purpose, the buyer may be able to reach the Code’s default remedies. See Cal. Com. Code § 2719; RRX Industries, Inc. v. Lab-Con, Inc., 772 F.2d 543 (9th Cir. 1985). There is a threshold problem that a surprising number of complaints skate past: those tools live in Article 2 of the UCC, and Article 2 governs transactions in goods. For delivered, licensed, on-premise software of the 1990s and 2000s, that was a fight worth having and often winnable. For the cloud ERP that dominates enterprise buying today—Oracle Fusion, Workday, SAP S/4HANA Cloud, NetSuite, Dynamics 365—the answer is far less certain and may well be no. A customer who builds its entire case on the UCC without first confirming that the UCC applies is building on sand. This piece explains why the goods-versus-services question has become central in modern ERP disputes, why software-as-a-service (SaaS) is hard to fit inside Article 2, and what sophisticated buyers should do about it. Why Classification Can Decide the Case The stakes of classification are not academic. If a transaction is governed by Article 2, the buyer may have access to the UCC’s buyer-protective architecture: implied warranties that attach unless effectively disclaimed, a demanding tender standard, and statutory remedies when an agreed remedy fails. If the transaction is governed instead by common law service-contract principles, the buyer may face a different regime: no implied warranty of merchantability, no Article 2 perfect-tender rule, and no statutory failure-of-essential-purpose provision. That does not mean common law leaves the buyer without remedies. It does mean the buyer’s path is different, and the vendor’s carefully drafted limitations may be harder to dislodge. The same failed implementation can therefore produce very different outcomes depending on a classification question the parties may never have consciously negotiated. That is why cloud vendors increasingly draft around the issue. Their forms often characterize the offering as “services,” confirm that the provider retains ownership of the software, and state that the customer receives only access rights—not delivery, title, or possession of a copy. Those labels are not automatically controlling, but they are important evidence of the transaction the parties made. The Framework: Goods, Sales, and Predominant Purpose Two threshold requirements must be satisfied before Article 2 governs, and cloud software strains both. First, the subject matter must be goods—defined in California as “all things ... which are movable at the time of identification to the contract for sale.” Cal. Com. Code § 2105. Second, there must be a sale, which the Code defines as the passing of title from seller to buyer for a price. Cal. Com. Code § 2106. A transaction that confers only a right to access or use software, without transferring title or a copy, sits uneasily inside that definition. When a contract blends goods and services—as nearly every enterprise software deal does—courts generally ask which aspect predominates. The classic formulation asks whether the contract’s predominant factor, thrust, or purpose is the rendition of services with goods incidentally involved, or a transaction of sale with labor incidentally involved. Bonebrake v. Cox, 499 F.2d 951, 960 (8th Cir. 1974). California courts apply a similar essence-of-the-transaction analysis. See Ventures v. SVC–W., L.P., 202 Cal. App. 4th 1483, 1502–03 (2012). The classification inquiry is typically contract-wide. If services predominate, common law—not Article 2—will generally govern the contract, including the software component. Why SaaS Is Different From the Software the Case Law Was Built On Much of the software-as-a-good precedent comes from a world of delivered products. Courts held that software could be treated as a good where something was delivered or transferred: a disk, a copy, a bundled hardware-and-software system, or a standardized software product. The leading example is Advent Systems Ltd. v. Unisys Corp., 925 F.2d 670 (3d Cir. 1991), which held that software was a “good” under the UCC where the contract’s main objective was the transfer of software and related products, with training and support treated as ancillary. The Ninth Circuit reached a similar result in RRX Industries, Inc. v. Lab-Con, Inc., 772 F.2d 543 (9th Cir. 1985), holding that the sales aspect of a software-system transaction predominated and that employee training, repair services, and upgrades were incidental to the sale of the software package. RRX is also important for remedies: applying California Commercial Code section 2719, the court affirmed consequential damages where the seller’s default was sufficiently total and fundamental that the limitation failed. But RRX should not be overread. It involved an installed software system in the 1980s, not a modern cloud-access subscription. SaaS changes the premise. In a true cloud ERP subscription, the customer usually receives no disk, no download, no executable, no object code, and no title to a copy. The customer receives a time-limited right to access software running on the vendor’s infrastructure, often priced by users, modules, or consumption. When the subscription ends, access ends. That structure creates problems on both Article 2 prongs. On the “goods” prong, there may be no movable thing delivered to the customer. On the “sale” prong, there may be no transfer of title. Some courts have applied Article 2 to software licenses, but the more cloud-like the transaction becomes, the harder it is to describe it as a sale of goods. Marquette University v. Kuali, Inc., 584 F. Supp. 3d 720 (E.D. Wis. 2022), is the modern SaaS decision buyers and vendors both should know. Applying Wisconsin law, the court accepted that the software underlying Kuali Research Cloud could be a good, and it accepted for purposes of analysis that the agreement included a sale. But it held that the contract was predominantly for services because Marquette paid for hosted access, maintenance, backups, updates, support, and the infrastructure needed to use the software—not primarily for a transferred software copy. Because services predominated, the UCC did not apply, and the contract’s remedy and damages limitations controlled. That reasoning maps naturally onto many cloud ERP subscriptions. The customer may care about the software functionality, but what it buys is often the vendor’s continuing operation of a hosted environment: access, uptime, maintenance, security, updates, integrations, and support. Those are service-like features, not the transfer of a movable chattel. The Law Is Unsettled—and the Facts Matter None of this means the UCC argument is dead. The authority is mixed, and the outcome depends heavily on the structure of the transaction, the governing law, and the factual record. A buyer has its best Article 2 argument when the deal involves standardized software, a meaningful delivered or downloadable component, or a contract whose economic center is the transfer of software functionality rather than ongoing vendor labor. Cases such as Advent and RRX remain useful for that proposition. The vendor has its best common-law argument when the contract is framed as a subscription service, the customer receives access rather than possession, the vendor retains title and operational control, and the customer pays materially for hosting, maintenance, configuration, support, and implementation. Kuali is the strongest modern SaaS example. California-specific authority also supports a careful, fact-based approach. In Tk Power, Inc. v. Textron, Inc., 433 F. Supp. 2d 1058 (N.D. Cal. 2006), the court applied common law rather than the UCC to a transaction involving prototype development because the essence of the agreement was development work—knowledge, skill, and ability—not the sale of finished goods. The court contrasted RRX, where the software sale predominated, with transactions centered on custom development. Other courts have drawn similar lines in technology disputes. In Conwell v. Gray Loon Outdoor Marketing, 906 N.E.2d 805 (Ind. 2009), the Indiana Supreme Court held that the UCC did not govern a website-design and hosting relationship because the arrangement involved custom design and ongoing hosting services, not a conventional transaction in tangible goods. The better formulation, then, is not that “software is a good” or “SaaS is a service.” The better formulation is: delivered, standardized software is often treated as a good; custom development, hosted access, and SaaS subscriptions often create stronger service-contract arguments. The Implementation Layer Makes the Goods Argument Harder Modern ERP deals rarely stop at a subscription. They often bundle implementation: configuration, data migration, integration, testing, change management, and training. These services may be performed by the vendor, a systems integrator, or both, and they may cost as much as—or more than—the subscription itself. Under the predominant-purpose test, that implementation layer matters. The more the buyer pays for the vendor’s labor, expertise, configuration, and project execution, the easier it is for the vendor to argue that services predominate. The irony is sharp: the more comprehensive and hands-on the vendor’s involvement—the very thing a customer wants when buying a mission-critical system—the harder it may become to characterize the transaction as the acquisition of a good. A deal in which the customer receives no delivered software copy, no title, and substantial implementation labor is difficult to shoehorn into Article 2. That does not make the UCC argument impossible. It does mean the argument must be pleaded and supported deliberately. What Sophisticated Buyers Should Do The practical response is not to abandon UCC theories. It is to stop depending on them and build a case that survives either classification. Plead in the Alternative Preserve the goods argument where the facts support it—especially for standardized suites, delivered components, downloadable modules, or arrangements where software functionality is the economic center of the deal. But assume the vendor will argue that the transaction is a service, and make sure the complaint survives if the court agrees. Build UCC-Independent Theories From Day One Fraud, negligent misrepresentation, and other pre-contractual representation theories do not depend on Article 2. ERP sales cycles often include capability representations, implementation assurances, timeline commitments, and integration promises that may support claims independent of the UCC. In California, Civil Code § 1668 provides that contracts that exempt a party from responsibility for its own fraud, willful injury, or violation of law are against public policy. That statute can be important when a vendor invokes limitation-of-liability language against fraud-based claims, regardless of whether the transaction is classified as goods or services. Negotiate Express Warranties Because Implied Ones May Never Attach If the transaction is classified as a service, implied UCC warranties may not apply. Buyers should negotiate explicit contractual warranties instead: implementation milestones, defined acceptance criteria, uptime commitments, integration obligations, performance standards, data-migration requirements, and meaningful remedies if the system does not work. Draft Remedies That Work Outside the UCC Do not rely solely on section 2719. A buyer should negotiate remedies that are enforceable as contract terms even if Article 2 never applies: refund rights, service credits that are not the exclusive remedy, termination rights, milestone holdbacks, fee clawbacks, audit rights, and carveouts from damages exclusions for mission-critical failures, data loss, security breaches, fraud, willful misconduct, and confidentiality breaches. Mind Choice-of-Law and Forum Clauses The goods-versus-services question can turn on governing law. Some jurisdictions are more receptive than others to treating software as a good; others focus more heavily on hosting, customization, and services. A vendor’s governing-law clause may therefore shape the classification fight before the dispute begins. Read the Vendor’s Characterization—and Rebut It Deliberately If the agreement says the offering is a “service,” states that the provider retains all rights in the software, disclaims delivery of any copy, and limits the customer to access rights, expect the vendor to rely on that language. If the buyer intends to invoke Article 2, it should develop a record showing why the transaction’s substance was the acquisition of software functionality rather than the purchase of labor or hosted operations. Bottom Line For a generation, “the software failed, so the UCC lets us past the vendor’s limitations” was a powerful opening move. In the cloud era, that move depends on a threshold question with an increasingly uncomfortable answer: a pure SaaS ERP subscription, especially one bundled with substantial vendor-led implementation, may fall outside Article 2 entirely. The sophisticated posture is not to assume the UCC applies, nor to concede that it does not. It is to recognize that the question is unsettled, litigate it deliberately where the facts support it, and—above all—build a case that does not collapse if the court decides the enterprise system was a service all along. This article is provided for general informational purposes only and does not constitute legal advice or create an attorney-client relationship. The classification of cloud and SaaS transactions under the UCC remains fact- and jurisdiction-specific. Companies facing a cloud software dispute should consult qualified counsel about their particular contract and circumstances. Breaking the Cap: Fraud in the Inducement in Failed Oracle Fusion and other ERP Implementations7/11/2026 By Pam Fulmer When a nine-figure ERP transformation collapses, the vendor’s limitation-of-liability clause is usually the whole ballgame. Here is how a well-pleaded fraud claim can get you past it — under California law, and in the two other jurisdictions where these disputes often land. Every large enterprise software dispute eventually comes down to the same question, and it is rarely the one the client expects. The client wants to talk about whether Oracle Fusion Cloud actually delivered the manufacturing or payroll functionality that was promised, or whether SAP’s S/4HANA rollout ever came close to going live. Those are the merits. But the number that decides whether the case is worth bringing — and whether it settles for real money — is buried in a boilerplate paragraph near the back of the Master Agreement: the limitation of liability. In a failed $30 million transformation, the cap is the ballgame. If the vendor’s limitation clause holds, the customer’s recovery is contractually squeezed down to the fees paid under the order form, with all consequential and “indirect” damages waived. The wasted internal labor, the second implementation, the lost efficiencies, the emergency consultants brought in to keep the lights on — none of it counts. A customer that spent $18 million and got nothing may find its recovery capped at a few million, minus what it still “owes.” The single most effective way past that cap is a properly pleaded, well-supported claim for fraud in the inducement, if the customer believes the vendor made misrepresentations to induce the contract and has the evidence to support it. Fraud is not just another count to pile onto the complaint. In the right posture it does two things at once: it opens the door to tort and out-of-pocket damages that the contract tried to foreclose, and — critically — it can render the limitation-of-liability clause itself unenforceable as to the fraudulent conduct. This article explains the mechanics, with California as the primary focus and New York and Massachusetts as the two other jurisdictions where enterprise software disputes frequently end up. Why the cap is the battlefield Oracle’s and SAP’s enterprise agreements are drafted by very good lawyers to do one thing above all: convert a potentially catastrophic delivery failure into a bounded, budgetable liability. The tools are familiar. Oracle’s cloud contracts — the Oracle Master Agreement and the Fusion Cloud Service order documents — pair a damages cap, typically pegged to fees paid over some trailing period, with a sweeping waiver of indirect, special, incidental, and consequential damages, and a disclaimer of lost profits. They are frequently accompanied by an integration or merger clause and, in financed deals, a payment agreement assigned to a third-party lender through Oracle Credit Corporation. SAP’s agreements follow a similar architecture around its software license and cloud/RISE subscription terms. The result is a structural mismatch. A customer’s real-world loss from a failed enterprise implementation is dominated by exactly the categories the contract waives — consequential damages, lost productivity, and the cost of a replacement system. The cap is engineered so that the customer’s provable “direct” damages are a fraction of its true loss. Litigating the breach alone, in other words, is often a losing economic proposition even when liability is clear. That is precisely why the analysis has to start with the cap, not the breach — and why fraud is the lever, provided the customer has real facts to support the claim. The fraud lever: an independent wrong the contract did not price The intuition behind every fraud-based attack on a liability cap is the same across jurisdictions: parties are presumed to have allocated the ordinary risks of performance in their contract, but no one bargains for the right to be lied to. A limitation clause allocates the risk that the software underperforms. It does not, as a matter of public policy in many commercial jurisdictions, allocate the risk that the vendor knowingly misrepresented the software’s capabilities to win the deal in the first place. The evidentiary heart of these cases is almost always the pre-contract sales cycle: the demos, the “solution overviews,” the RFP responses, the emails assuring the customer that the platform will handle its industry “out of the box,” that go-live will happen on a fixed timeline for a fixed price, that little or no customization is required, and that third-party add-ons will not be needed. When the executed order form then describes only components — and omits the capability that was the whole reason for the purchase — the gap between what was sold and what was signed is where the fraud claim lives. California: the primary jurisdiction California is where a large share of these disputes are filed, as many companies including Oracle are present here, and California law is comparatively favorable to defrauded customers. Three doctrinal pillars matter. 1. The economic loss rule does not bar fraud independent of the breach California’s economic loss rule generally bars tort recovery for purely economic losses between contracting parties. But it does not bar an intentional fraud claim based on conduct independent of the breach. In Robinson Helicopter Co. v. Dana Corp., 34 Cal. 4th 979, (2004), the California Supreme Court allowed fraud-based tort remedies where the defendant’s affirmative misrepresentations were independent of the mere failure to deliver conforming goods. The Court reasoned that no rational party enters a contract expecting to be defrauded, and that allowing the economic loss rule to swallow intentional fraud would reward dishonesty. For years, defendants argued that Robinson Helicopter was narrow and confined to affirmative misrepresentations that exposed the plaintiff to personal-injury-type liability. The Supreme Court closed much of that gap in Rattagan v. Uber Technologies, Inc., 17 Cal. 5th 1, (2024). Rattagan confirms that fraudulent concealment arising from or related to contract performance may also sound in tort where the concealment can be established independently of the parties’ contractual obligations and exposes the plaintiff to a risk beyond what the parties reasonably contemplated at contracting. Read together with Lazar v. Superior Court, 12 Cal. 4th 631, (1996), which recognizes tort remedies for fraudulent inducement, and consistent with Erlich v. Menezes, 21 Cal. 4th 543, 981 P.2d 978, 87 Cal. Rptr. 2d 886 (1999), which insists on an independent tort duty before contract claims become tort claims, Rattagan confirms that both affirmative misrepresentations and knowing concealment in the ERP sales cycle can sound in tort. That matters because tort framing is what unlocks out-of-pocket damages and, in egregious cases, punitive exposure that the contract’s damages waiver may not reach. The important limit, reaffirmed in Sheen v. Wells Fargo Bank, N.A., 12 Cal. 5th 905, (2022), is that the tort must be genuinely independent of the broken promise. A repackaged breach — “they promised the software would work and it didn’t” — will not clear the bar. The claim has to rest on a knowing misrepresentation of then-existing fact or a concealed material fact, pleaded with the specificity California fraud pleading demands. 2. Civil Code section 1668 can void the cap itself — even for sophisticated parties This is the development that has changed the leverage in these cases. Cal. Civ. Code § 1668 provides that all contracts that have as their object, “directly or indirectly,” the exemption of anyone from responsibility for their own fraud or willful injury are against the policy of the law. For decades, courts disagreed about whether section 1668 voided only total releases or also reached clauses that merely limited liability. In New England Country Foods, LLC v. Vanlaw Food Products, Inc., 17 Cal. 5th 618, (2025), answering a question certified by the Ninth Circuit, the California Supreme Court resolved the split: Section 1668 invalidates contractual provisions that substantially limit damages for willful injury to person or property, even where the clause is framed as a limitation of liability rather than a complete release. The Court rejected a broad sophisticated-party exception, while preserving ordinary contractual limitations for non-willful breach-of-contract claims. Earlier authority, including Food Safety Net Services v. Eco Safe Systems USA, Inc., 209 Cal. App. 4th 1118, (2012), points in the same direction for fraud-based claims. The practical significance is hard to overstate, but it should be stated precisely. Where the customer can plead and ultimately prove intentional fraud or willful injury within section 1668’s scope — as opposed to a garden-variety breach — the vendor’s fees-paid cap and consequential-damages waiver cannot be used to substantially exempt the vendor from responsibility for that conduct. New England Country Foods was careful to preserve the enforceability of caps for ordinary breach of contract; the statute reaches intentional wrongs within its ambit, not ordinary contract disappointment. So the fraud claim is not just a route to bigger damages. It is the mechanism that can dissolve the cap as to the fraudulent or willful conduct. 3. The integration clause is not the wall the vendor thinks it is Vendors routinely argue that the contract’s merger or integration clause bars any reliance on pre-contract sales representations. In California, the fraud exception to the parol evidence rule answers that argument. Riverisland Cold Storage, Inc. v. Fresno-Madera Production Credit Ass’n, 55 Cal. 4th (2013), overruled the old Pendergrass limitation and confirmed that a party may introduce extrinsic evidence of fraudulent representations to establish fraud in the inducement, even where those representations contradict the written agreement. An integration clause does not immunize a vendor from proof of the promises its salesforce actually made. How this looks in real Oracle litigationThese are not abstractions. A wave of California suits and filings has tested variations of this theory against Oracle’s ERP, HCM, and cloud products. The recurring allegations are familiar: the customer contends that Oracle or its implementation partner misrepresented product capabilities, downplayed the customization required, overstated the partner’s expertise, or promised functionality that did not appear in the executed order documents. In that posture, the breach claim may be vulnerable if the final contract does not actually require the configured, workable solution the customer thought it was buying. The fraud claim, by contrast, may remain viable if the customer can identify specific pre-contract misrepresentations of then-existing fact, the speakers, the timing, reliance, and resulting damage. Recent Oracle and NetSuite disputes illustrate the pattern at the pleading level. Customers have alleged that sales representatives made specific pre-contract promises that a system was tailored to the customer’s industry, would require little or no third-party functionality, or would support critical business requirements. Those allegations are typically paired with breach, fraudulent misrepresentation, negligent misrepresentation, and, in California cases, claims under California’s Unfair Competition Law, Cal. Bus. & Prof. Code § 17200. The lesson is not that every failed implementation becomes fraud. It is that the decisive facts often live in the sales record, not the project plan. The exposure is not limited to NetSuite. Public reporting around failed large-scale Oracle Fusion and SAP programs shows how an enterprise implementation can fail at scale, leaving the customer with impaired operations, a costly remediation project, and losses that ordinary contract caps are designed to exclude. Those examples are useful business context, but they should be distinguished from legal authority. The legal question remains whether the customer can plead and prove fraud or willful misconduct independent of the contract breach. One California-specific trap should be flagged at the outset. Many Oracle deals are financed through Oracle Credit Corporation, with the payment agreement then assigned to a third-party bank. Those financing agreements may contain waiver-of-defenses language governed by UCC Article 9, including Cal. Com. Code § 9403, which can materially affect the customer’s ability to assert software-related defenses against an assignee. The fraud strategy therefore has to account for the financing structure from day one, not after the bank seeks payment. New York: the sophisticated-party jurisdiction New York is the other dominant forum for enterprise software disputes, and its law is meaningfully less forgiving than California’s. The starting presumption favors enforcement. In Metropolitan Life Insurance Co. v. Noble Lowndes International, Inc., 84 N.Y.2d 430, 643 N.E.2d 504, 618 N.Y.S.2d 882 (1994) — itself a software development and installation dispute — the Court of Appeals enforced a negotiated limitation of liability where the vendor’s deliberate, economically motivated refusal to perform was not enough to defeat the cap absent proof of fraud, malice, or other truly willful tortious conduct. New York courts generally hold sophisticated parties to their negotiated risk allocation. The public-policy exception is real but demanding. Under Kalisch-Jarcho, Inc. v. City of New York, 58 N.Y.2d 377, 461 N.Y.S.2d 746 (1983), and related authorities including Sommer v. Federal Signal Corp., 79 N.Y.2d 540, 593 N.E.2d 1365, 583 N.Y.S.2d 957 (1992), a limitation or exculpatory clause generally will not shield conduct that is grossly negligent, willful, or in bad faith. But Colnaghi, U.S.A., Ltd. v. Jewelers Protection Services, Ltd., 81 N.Y.2d 821, 611 N.E.2d 282, 595 N.Y.S.2d 381 (1993), illustrates how high that bar is: gross negligence requires conduct that evinces reckless disregard for the rights of others or smacks of intentional wrongdoing. Fraud in the inducement, well pleaded, is the archetypal conduct that may clear this bar. Ordinary breach, and even deliberate nonperformance for economic reasons, usually does not. The distinctive New York battleground is the anti-reliance clause. Under Danann Realty Corp. v. Harris, 5 N.Y.2d 317, 157 N.E.2d 597, 184 N.Y.S.2d 599 (1959), a specific disclaimer of reliance — a provision in which the buyer represents that it did not rely on any representations outside the four corners of the agreement as to the very matter later alleged to be misrepresented — can defeat a fraudulent inducement claim. A general merger clause, by contrast, does not. The line between the two frequently decides these cases at the motion-to-dismiss stage, which is why the precise wording of the vendor’s “no reliance” language must be scrutinized before filing. There is a crucial but fact-specific escape hatch. Even a specific disclaimer may not bar a fraud claim where the misrepresented facts were peculiarly within the defendant’s knowledge and not discoverable through ordinary diligence. Basis Yield Alpha Fund (Master) v. Goldman Sachs Group, Inc., 115 A.D.3d 128, 980 N.Y.S.2d 21 (1st Dep’t 2014), is useful on that point. In the ERP context, internal defect logs, failed reference implementations, and internal engineering assessments may be candidates for peculiar-knowledge treatment, but the issue will turn on the precise disclaimer language and what diligence was realistically available to the customer. And throughout, New York’s heightened pleading standard, N.Y. C.P.L.R. 3016(b), means the fraud must be alleged with particularity: the specific statements, speakers, and circumstances, not conclusory labels. Massachusetts: Chapter 93A as a damages multiplier Massachusetts deserves its own analysis because it offers a statutory route that can be even more powerful than common-law fraud. Mass. Gen. Laws ch. 93A, § 11 prohibits unfair or deceptive acts in trade or commerce between businesses and authorizes recovery of double or treble damages plus attorneys’ fees for willful or knowing violations. Deceptive pre-contract representations of the kind at issue in ERP disputes are classic Chapter 93A conduct. Decisively, in H1 Lincoln, Inc. v. South Washington Street, LLC, 489 Mass. 1, 179 N.E.3d 545 (2022), the Supreme Judicial Court held that a contractual limitation-of-liability provision will not be enforced to protect a defendant who willfully or knowingly engages in unfair or deceptive conduct prohibited by Chapter 93A. The Court reasoned that the statute’s punitive and deterrent purposes cannot be overridden by private risk allocation, even among sophisticated parties, and even where the clause purports to waive consequential damages — the very category into which Chapter 93A multiple damages fall. The Court declined to let the older, more permissive analysis of Canal Electric Co. v. Westinghouse Electric Corp., 406 Mass. 369, 548 N.E.2d 182 (1990), shield willful violators, and distinguished the tort/contract analysis in Standard Register Co. v. Bolton-Emerson, Inc., 38 Mass. App. Ct. 545, 649 N.E.2d 791 (1995). Massachusetts also has directly relevant software authority. In VMark Software, Inc. v. EMC Corp., 37 Mass. App. Ct. 610, 642 N.E.2d 587 (1994), the Appeals Court affirmed misrepresentation-based relief arising from assurances about software functionality, while declining multiple damages on the facts. The lesson is familiar: the quality of the misconduct — merely misleading versus willful or knowing — drives both whether contractual limitations yield and whether damages multiply. Two practical cautions. First, a section 11 claim requires that the unfair or deceptive conduct occurred “primarily and substantially” within Massachusetts; courts examine the center of gravity of the misconduct, and an out-of-state vendor will press this hard. Second, a defendant can blunt the multiplier by making a reasonable single-damages settlement offer with its answer, so the timing and content of pre-suit Chapter 93A demand letters and early settlement posture genuinely affect the exposure. Practical takeaways for enterprise customers and their counsel The through-line across all three jurisdictions is that the fraud claim, not the breach claim, is what can make a failed enterprise implementation economically worth litigating. To preserve it:
|
By Tactical Law Attorneys and From Time to Time Their Guests
|
RSS Feed
tactical law group llp |
COPYRIGHT TACTICAL LAW GROUP LLP 2016-2026. ALL RIGHTS RESERVED
|
Legal Disclaimer: Contents may contain attorney advertising under the laws of some states. Prior results do not guarantee a similar outcome.