The American Law Institute’s approval of the Principles of the Law of Software Contracts in 2009 marked a milestone for software law in the United States. The drafting project began in 2004 in response to the failure of the Uniform Computer Information Transactions Act and the long-standing perception that the doctrinal landscape governing software licensing was, in the words of one prominent commentator, “undeveloped, confused, and conflicting.” This Article argues that, while the Principles bring welcome coherence to domestic software contracting, they are not exportable to the European Union in their current form.
Software’s Long Legal Lag
Every transformative technology produces what sociologist William Ogburn called a “cultural lag” — a delay between the arrival of the technology and the institutional response to it. In 1936, a young Richard Nixon observed that thirty years after the automobile entered American life the case law had grown from a four-page article into something requiring an encyclopedia, much of it produced by judges who were creatively stretching horse-and-buggy doctrine to fit the new machine. Software has experienced its own legal lag. For nearly four decades U.S. courts have applied UCC Article 2, drafted for the national distribution of durable goods, to the licensing of intangible code. The Principles project was an effort to end that improvisation and give software contracting law its own statutory infrastructure.
The American Approach
The Principles adopt a default-rule architecture: the rules apply unless the parties agree otherwise. This is consistent with the broader U.S. preference for treating commercial parties as capable of bargaining for the protections they want. The drafters made limited concessions to mass-market consumers — for example, by recognizing implied warranties of fitness for ordinary purposes — but the structure remains optional in ways that European regulators would find unfamiliar. As we explain in our companion analysis of corporate IP enforcement strategies, the willingness to leave so much to private ordering is a defining feature of the American approach to technology law.
The European Conflict
The European Union has taken a different path. The Unfair Contract Terms Directive (93/13/EEC), the Consumer Rights Directive (2011/83/EU), and the body of case law surrounding them establish mandatory consumer protections that cannot be displaced by contract. A licensor that drafts a click-wrap agreement under the ALI Principles will, the moment that agreement is offered to a French or German consumer, find that the most fundamental terms have been overwritten by mandatory European law. The conflict is not merely textual. It reflects a deeper disagreement about whether consumer protection in software transactions should be a matter of negotiated bargaining or of regulatory floor.
Procedural Friction
The exportability problem is sharpest in the procedural rules governing jurisdiction, choice of law, and choice of forum. The Principles permit licensors to designate U.S. forums for dispute resolution and to select U.S. law as the governing regime. The Brussels I Regulation and the Rome I Regulation severely restrict the enforceability of such clauses against EU consumers, and the European Court of Justice has reinforced these restrictions in a line of decisions running from Pannon through Banco Español de Crédito. A U.S. software vendor that imports the Principles wholesale into a European-facing contract will find its dispute-resolution architecture unenforceable.
Substantive Friction
Substantive doctrines fare no better. The Principles permit broad disclaimers of consequential damages and tightly limited remedies for defective code. EU consumer law treats such terms as presumptively unfair and, in many cases, void. The Digital Content Directive (2019/770/EU), adopted after this Article’s original publication, has only sharpened the divergence by establishing mandatory remedies for non-conforming digital content delivered to consumers.
Toward Transnational Principles
We do not argue that the Principles are a failure. They are a serious and useful synthesis of U.S. software contracting practice. We argue instead that they are domestic. A genuinely exportable framework would have to begin from the premise that consumer software is now a globally distributed product and that any rule set intended to govern it must accommodate the mandatory protections of the world’s largest single marketplace. That work is for another project. The questions raised by cross-border digital goods continue to evolve in directions our analysis of EU data protection regulation and the broader treatment of digital sovereignty in the journal’s archive only begins to address.
Why It Matters
The Principles will shape U.S. software contracting practice for years to come. They will not, in their current form, govern the cross-border transactions that constitute an increasing share of the industry’s output. Practitioners advising vendors that sell into Europe should treat the Principles as a useful baseline for U.S. operations and as an incomplete starting point for any contract that will be enforced abroad. The European market is too large, and its mandatory consumer rules too settled, for the gap to be ignored.
Frequently Asked Questions
What are the ALI Principles of the Law of Software Contracts?
The Principles of the Law of Software Contracts are a 2009 American Law Institute project that codifies best practices for software licensing under U.S. law. They were drafted to address the perceived inadequacy of UCC Article 2 for transactions involving intangible code rather than tangible goods.
Why are the Principles not exportable to the European Union?
The Principles assume an opt-in U.S. consumer protection model based on private contract. The EU instead applies mandatory consumer rules that cannot be displaced by agreement, particularly under the Unfair Contract Terms Directive and the Consumer Rights Directive. A licensor that adopts the Principles for cross-border use will collide with these mandatory protections.
What is the legal lag in software contract law?
The legal lag refers to the four-decade gap between the rise of the software industry and the development of doctrinal rules tailored to it. Courts extended the law of sales of tangible goods to intangible software, much as they once extended horse-and-buggy law to the automobile, producing strained outcomes that the Principles project sought to repair.
Related articles: EU Data Protection Regulation · IP Privateering · Software Patents and ยง 271(f) · The Patent Prosecution Highway · E-Discovery in the Cloud