Understanding Which Law Actually Applies to Your Contract

Most people don't think about this until they're already in a dispute. You sign something, a problem shows up six months later, and suddenly you need to know whether common law or the UCC is going to determine what happens next. The difference isn't academic. It changes how offer and acceptance work, how warranties are implied, how damages are calculated, and whether a modification even needs new consideration.

When The Common Law Governs Contracts For Services, Real Estate, and Employment

Common law governs contracts for things that aren't the sale of goods. That means services, real estate transactions, employment agreements, insurance policies, lease agreements (yes, even though leases feel like a sale of temporary use), and almost anything involving intangible rights or professional obligations. The UCC Article 2 applies only to transactions in goods. Goods are tangible, movable things. A computer is goods. A consulting arrangement where someone provides expertise is not. A software license is sometimes goods, sometimes not — and that boundary is where people get tripped up. Here's the practical test: if the predominant purpose of the contract is the transfer of a physical item, you're likely in UCC territory. If it's the provision of skill, labor, or a result, common law applies. The line between the two is fuzzier than textbooks suggest. I handled a case last year where a client hired a systems integrator to build a custom inventory management platform. The contract included hardware — servers, scanners, cabling — but also hundreds of hours of configuration, database design, and staff training. The counterparty delivered a product that barely functioned and refused to come back. When we went to court on the breach claim, the central issue was whether this was a sale of goods or a services contract. Under the predominant purpose test, the court looked at the contract price breakdown: roughly 60 percent was services, 40 percent was hardware. Common law applied. That mattered because under common law, the statute of frauds requires a writing for contracts that can't be performed within one year, and it also governs how modifications work. Under the UCC, a contract for $500 or more needs a writing, but modifications don't require new consideration — which is a meaningful difference when the original deal went sideways and both parties verbally agreed to change scope.

How to Tell What Law Applies

It's not always obvious from the face of the contract. The document might say "this is a services agreement" and still involve a significant goods component. Courts look at the predominant purpose, not the label. Here's what I've learned from actually litigating and drafting these distinctions: The mixed contract test. When a single contract blends goods and services, you apply the predominant purpose test. Look at the nature of the supplier's business — is this company fundamentally a seller of products or a provider of services? Look at the relative cost allocation. Look at how the contract is structured in terms of delivery terms versus performance milestones. If a HVAC company installs a heating system, the equipment is goods but the installation is services. Courts typically treat that as a services contract because the installation complexity and labor usually outweigh the equipment value. But if the same company sells you a furnace and installs it as an afterthought, it's goods. The software question. This is the most unpredictable area. Off-the-shelf software sold on a disk or download is generally goods. Custom-developed software is generally services. But hybrid situations are a nightmare. A SaaS subscription where you never take possession of any tangible medium is services under common law. A licensed software package with a maintenance agreement — depends on how the agreement is structured. I learned this the hard way when a client's EULA claimed UCC govern but the actual engagement included extensive custom integration work. The other side moved to dismiss our breach claim, arguing the written contract incorporated the UCC through the EULA. The motion failed because the custom work was the substantive part of the deal, but it delayed resolution by four months and cost roughly $18,000 in motion practice we could have avoided with a clearer engagement letter. Real estate is almost always common law. Not UCC Article 2. A contract to sell land, a lease of real property, an option on real estate — these are common law contracts. The statute of frauds in every jurisdiction requires a writing for real estate transfers. The rules about title, risk of loss, and remedies come from common law principles and state-specific real estate statutes, not from the UCC.

What Changes When Common Law Applies Instead of the UCC

There are several operational differences that affect your rights and your strategy: Consideration for modifications. Under common law, a contract modification requires new consideration to be enforceable. If you agree to pay an extra $10,000 for accelerated delivery and the other side later refuses to speed up, you might not have a claim for the extra money if the original contract didn't include an option or waiver provision. Under the UCC, modifications don't need consideration — just good faith. This is a critical distinction that comes up constantly in construction and consulting disputes. Merchant status matters under the UCC but not under common law. The UCC creates special rules for merchants — stricter firm offer rules, different warranty standards, different formation rules. Under common law, everyone is treated essentially the same regardless of whether they're in business for themselves or not. Implied warranties. The UCC has well-developed implied warranty of merchantability and fitness for a particular purpose doctrines. Common law doesn't recognize these same implied warranties. In common law, you get what you bargain for, not what a court might think a reasonable merchant would imply. This is why service contracts need very careful express warranty language — the default protections are weaker. The battle of the forms. The UCC has Section 2-207, which means additional or different terms in an acceptance might still form a contract. Under common law, a response with different terms is a counteroffer, not an acceptance. The entire formation analysis shifts. Statute of frauds thresholds. The UCC requires a writing for goods priced at $500 or more. Common law thresholds vary by jurisdiction and by contract type — real estate, contracts that can't perform within a year, promises to answer for the debt of another. The writing requirements are different.

Practical Steps to Determine and Draft Around the Rule

If you're drafting a contract and you're unsure whether common law or the UCC governs, here's the process I use: First, identify whether the contract's primary purpose involves goods or services. Break down every deliverable. List each material element. Categorize it. Second, calculate the predominant purpose by dollar value and by functional importance. A $5,000 laptop that sits on a desk is goods. A $5,000 consulting engagement that produces a strategic plan is services. A $50,000 IT project that includes a $15,000 server and $35,000 in implementation work is services, even though the hardware is expensive. Third, check the jurisdiction. Some states have adopted modified versions of the predominant purpose test. A few apply a "gravamen of the action" approach instead. New York, for example, has its own nuances around mixed contracts that differ from the Restatement approach used in most other states. Fourth, include a governing law clause that addresses the distinction. Most standard clauses just say "the laws of the State of X shall govern." That's insufficient when the contract has both goods and services components. Specify whether you intend the UCC to apply in full, whether you intend common law to govern, and how mixed elements should be treated. Better yet, structure the contract so the classification is clear from the document itself. Fifth, if you're negotiating a contract where the other party is pushing for UCC treatment and you want common law (or vice versa), understand what you're actually gaining or losing. UCC treatment gives you more flexibility on modifications but imposes stricter warranty obligations. Common law treatment gives you stronger consideration requirements for changes but fewer implied warranty claims.

When the Law Doesn't Apply the Way You Expect

There are scenarios where neither the UCC nor common law neatly covers the situation. Arbitration agreements, non-compete clauses, intellectual property licensing arrangements, and regulatory compliance contracts often fall into gray areas that courts decide case by case. I dealt with a contract last year for a marketing automation platform that included both software licensing and ongoing campaign management services. The provider argued UCC governed the licensing portion and common law governed the services portion — a partial applicability argument. The client's counsel argued the whole thing was a services contract. The court agreed with the client but only after examining four years of similar cases in that district. The outcome wasn't clear from any single precedent. This is why jurisdiction matters so much. The same contract structure could go either way depending on which court hears it. The best workaround is to explicitly allocate which law governs which provisions in the contract itself. Split governance clauses — UCC for the license, common law for the services, specific arbitration rules for disputes — are increasingly common in technology contracts and they prevent this exact uncertainty from becoming a litigation battle. Common law governs contracts for services, employment, real estate, insurance, and anything that isn't primarily a sale of goods. The distinction determines how your contract forms, how it modifies, what warranties apply, and what remedies are available. Don't assume it one way or the other based on the document title. Look at the actual substance of what you're buying and selling.