Skip to content

Course of Dealing

A prior pattern of transactions between the same contracting parties used, under an applicable legal rule, to interpret or supplement their current agreement.

Version
v1 · 2026-10-25 · History
Domain-specific #
14375
Domain group
Professional & Organizational Practice
Origin domain
Law & Governance
Subdomains
Contract Law, Commercial Contracts → Law & Governance

Core Idea

A course of dealing uses the contracting parties' relevant conduct in previous transactions to interpret their current agreement.[1] Under UCC §1-303(b), the earlier sequence must fairly establish a common basis of understanding for their expressions and conduct.[1] The operative relation is therefore more specific than “the past matters”: the history belongs to the same parties, concerns comparable dealings, and bears on a current question of meaning or obligation. The applicable legal rule determines what effect that history can have.

In a freight-service dispute, 47 earlier invoices carrying the same liability limit informed the parties' later oral shipping arrangement.[2] In an international equipment-sales dispute, an arbitrator treated an established between-party spare-parts practice as relevant under CISG Article 9(1) to the seller's timely supply obligation.[3] Those are different transactions and legal regimes. Their common structure is the use of the parties' own earlier dealings as evidence of an operative present understanding, not a universal UCC priority rule or a fixed number of repetitions.

Structural Signature

Sig role-phrases:

  • Same parties. The earlier conduct and disputed current relationship involve the same contracting pair.[1] If the history belongs only to other market participants, it may show trade usage but not this bilateral course.[1]
  • Relevant previous transactions. A sequence of dealings precedes the transaction now in dispute.[1] Conduct only under the present agreement lacks this temporal role; it may satisfy a separate course-of-performance rule if that rule's conditions are met.[1]
  • Common-understanding inference. The prior conduct must fairly support a shared basis under the applicable rule.[1] Mere recurrence without a fair inference is not enough under the UCC definition; receipt of identical invoices supplied notice on the particular NNR Aircargo record.[1][2]
  • Present content question. A term, agreement, or obligation now calls for interpretation, supplementation, or qualification.[1][2][3] Without that present question, the prior transactions are only historical facts.[1][2][3]
  • Applicable rule. The governing legal regime gives the prior practice its potential legal effect and its limits.[1][2][3] UCC §1-303, the freight-service opinion, and CISG Article 9 do not have identical scopes.[1][2][3]

The parties and time relationship identify the evidence; the inference tests whether it conveys a shared understanding; the current question and governing rule determine its use.

What It Is Not

  • Not course of performance under the current transaction. UCC §1-303(a) separately requires repeated occasions for performance, knowledge and opportunity to object, and acceptance or acquiescence.[1] A single current-contract act need not satisfy that rule either.[1]
  • Not usage of trade. A practice regular in a place, vocation, or trade may matter even without previous transactions between these particular parties.[1] That is a different source of interpretive evidence under UCC §1-303©.[1]
  • Not an automatic amendment by repetition. Whether a pattern establishes a common basis, and whether it can affect the current terms, depends on the evidence and governing rule.[1] The UCC first calls for reasonable consistency among express terms and these interpretive sources; it then states a conflict order where consistency is unreasonable.[1]
  • Not a universal number of transactions or a guaranteed result. The 47 invoices in NNR Aircargo were that case's facts, not a universal threshold.[2]
  • Not judicial precedent. Courts may rely on earlier opinions to decide the law, but the course being evaluated here is the contracting pair's own prior conduct.

Scope of Application

The UCC expressly distinguishes previous bilateral dealings, performance under the current transaction, and trade usage, and allows course of dealing to give meaning to, supplement, or qualify agreement terms.[1] Its ordering of conflicting sources is a UCC rule, not a definition that transfers unchanged to every contract regime.[1]

The Ninth Circuit applied course-of-dealing reasoning to a freight-forwarding service arrangement despite treating the disputed shipment as outside a UCC Article 2 goods-sale analysis.[2] In the ICC 8611 award, the arbitrator applied CISG rules to individual international equipment sales, not to the distributorship agreement as such, and used a practice established between the parties to assess spare-parts supply.[3] UNIDROIT Principles Article 1.9 also addresses established between-party practices; it is a separate instrument with its own legal setting.[4]

These settings support a domain-bound contract-interpretation entry. Their legal consequences cannot be transferred to a new jurisdiction or agreement without identifying its governing rule.

The Restatement (Second) of Contracts §223 supplies a separate formulation: unless the parties agree otherwise, their earlier course may give meaning to, supplement, or qualify their agreement.[5] UCC Article 1 was revised in 2001; the official comment to the enacted D.C. §28:1-303 identifies former §§1-205, 2-208, and 2A-207 as its sources and describes the integration of course of performance into the older course-of-dealing framework.[6][7] That model revision and a jurisdiction's adoption are different events; D.C.'s cited enactment occurred in 2013.[7]

UCC §1-303(f) expressly treats course of performance as relevant to waiver or modification, subject to §2-209.[1] The fact that this subsection names performance does not prove that prior dealings can never affect a modification question. Section 1-303(d) separately permits course of dealing to supplement or qualify agreement terms.[1]

A general integration clause did not exclude course-of-dealing evidence in the particular UCC gasoline-dealer dispute in Allapattah.[8] By contrast, the Precision Fitness court enforced an express clause barring use of past dealings to interpret that agreement's terms.[9] Neither decision supplies a universal rule for all merger clauses or jurisdictions.

The Colorado court in Pepcol required ambiguity before using the conduct at issue under its common-law analysis; that conduct occurred during a single contract and is not itself a clean previous-transaction course-of-dealing example.[10] The Tenth Circuit's Amoco discussion allowed prior dealings and trade usage to explain or supplement a UCC agreement without a preliminary ambiguity finding.[11] This is a bounded jurisdictional contrast, not a rule for all common law and all UCC applications.

CISG Article 9(1) concerns practices established between the parties, while Article 9(2) separately concerns trade usage known, or that ought to be known, in the relevant international trade.[12] The UNCITRAL Digest reports differing tribunal treatments of how repeated or long-standing a practice must be; it does not supply one universal number of dealings.[13]

Clarity

Ask whose history, when it occurred, what was repeated, what the other party could understand, and which present term or obligation it informs. The answer should identify the governing legal rule before describing the effect. “They have always done it this way” omits the relevant parties, the previous-transaction boundary, and the inference from conduct to shared meaning.

In NNR Aircargo, the opinion identifies 47 previous transactions, invoices with identical terms, and the later oral shipping agreement's silence about liability.[2] The court treated those repeated invoices as notice of the invoice liability limit.[2] The conclusion is tied to that record; it does not establish that any invoice printed after performance automatically binds a customer.

Manages Complexity

Contract interpretation can draw on express words, current performance, earlier dealings, and wider trade practice.[1] UCC §1-303 separates these evidence sources by who acted and when, and then provides rules for their possible effect and inconsistency.[1] This separation prevents a present act from being silently counted as a prior transaction, or an industry custom from being attributed to the parties' own shared history.

The sequence also narrows the factual inquiry. First establish the particular contracting pair and earlier transactions; next test whether the repeated conduct fairly conveyed a common understanding; then ask what present issue that understanding could resolve under the governing rule. A broad history narrative without those checks can obscure the actual legal question.

Abstract Reasoning

  1. Identify the current agreement and applicable regime. A freight-service dispute and a CISG individual-sale dispute can use similar historical evidence but different legal rules.[2][3]
  2. Collect the prior transactions of these same parties. Distinguish them from conduct only under the current transaction or a market-wide practice.[1]
  3. Test the inference. Determine whether the earlier acts are relevant and regular enough to fairly establish a common basis rather than assuming that repetition alone is decisive.[1]
  4. Map the history to the present question. State which term, silence, or obligation the practice might illuminate.[1][2][3]
  5. Apply the rule's limits. Under UCC §1-303(e), sources should be reconciled where reasonable, with its stated order if they cannot be. The CISG award must be read within its own individual-sales scope.[1][3]

Knowledge Transfer

The useful transferable question within contract law is whether repeat dealings of the same parties supplied a shared understanding for a later obligation. That question can be asked of shipping services, sales, and other contractual relationships, but its answer and legal effect follow the governing rule and the quality of the earlier evidence.[2][3]

This is not a general license to treat every path-dependent relationship as a contract term. The defining mechanism includes bilateral transactional history and legally relevant interpretation. Outside that setting, “course of dealing” is at most an analogy unless an applicable doctrine gives it the same roles.

Examples

Canonical: freight-service invoice limit

Dunlop used NNR Aircargo for 47 earlier import-related service transactions.[2] For each, NNR sent an invoice with identical conditions, including a limit of 50 US dollars per shipment.[2] The disputed 48th shipment was arranged orally; the invoice arrived after cargo was stolen.[2] The Ninth Circuit held that the earlier invoices provided a sufficient course of dealing for the limit to supplement the silent shipping agreement, and explicitly distinguished the matter from an Article 2 goods-sale material-alteration analysis.[2]

Mapped back: NNR and Dunlop are the same contracting pair, and the 47 earlier service transactions supply previous conduct.[2] Receipt of repeated identical invoice terms supplies the court's notice inference; liability for the later shipment is the present content question; the opinion supplies the governing analysis.[2] INA appeared as Dunlop's insurer and plaintiff, not as the historical contracting counterparty.[2]

Applied: international equipment sales and spare parts

In ICC award 8611/HV/JK, W (formerly I) and R had a distributorship arrangement and numerous individual equipment sales.[3] The arbitrator treated spare-parts supply as a practice established between the parties under CISG Article 9(1), supporting a duty to supply within a reasonable time in the sales relationship.[3] The award treated the distributorship agreement itself as outside the CISG's scope.[3]

Mapped back: W/I and R supply the continuing contracting pair; earlier sales and spare-parts dealings supply the history.[3] Their established practice supplies the operative inference under the award's CISG analysis; timely supply is the present obligation; CISG governs the individual sales.[3] The award's original German text is the direct source; an English abstract is used only as a translation aid.[3]

Structural Tensions

No general opposed-pressure pair is established by the bounded sources for both settings. The UCC's consistency and priority provisions and the ICC award's CISG scope are legal limits to apply, not interchangeable claims of a universal trade-off.[1][3]

Structural–Framed Character

The entry can be compared across unlike contract settings through its five roles: same parties, earlier transactions, a shared-understanding inference, a present content question, and a governing rule. Its vocabulary travels between freight services and equipment sales, but words such as course of dealing and agreement retain legal meanings there. Its evaluative weight depends on whether a rule gives the prior practice interpretive effect; a repeated habit is not inherently binding. Its human-practice dependence is high because the evidence is conduct and understanding between contracting people or organizations. Its institutional origin is contract doctrine, visible in the UCC and CISG treatments; the same history might matter differently under another legal regime.[1][3] On import versus recognition, calling a noncontractual pattern a course of dealing imports legal vocabulary unless the same party, transaction, inference, and rule roles can actually be shown.

Its character: framed. The reusable role comparison supports careful reasoning within contract law, while the named doctrine's operative effect depends on contract institutions and sources. The limited portable skeleton does not make the named legal entry a cross-domain Prime.

Structural Core vs. Domain Accent

The skeletal relation is earlier interaction informing later interpretation. Whether that wider relation deserves a separate Prime is an open identity question; this entry does not assign it to an existing Prime by word resemblance. The domain-bound mechanism here requires previous transactions of the same contracting parties, a shared-basis inference, a present agreement or obligation, and an applicable interpretive rule.[1] Remove those legal roles and a generic historical influence may remain, but the named course-of-dealing doctrine does not.

The UCC's exact priority order, the freight-service notice analysis, and CISG Article 9 practice are domain accents with their own sources and jurisdictional limits.[1][2][3] They should not be recast as cross-domain mechanisms or silently fused into a single universal rule.

Contract names a binding obligation relation whose terms may be interpreted through prior dealings; a contract need not have any such prior course. The UCC distinguishes an agreement's bargain-in-fact, which course of dealing may help infer, from the resulting total legal obligation called a contract.[14] Path Dependence requires a historical sequence that locks in consequences and forecloses alternatives despite present incentives. Course of dealing can affect interpretation without that lock-in. Precedent / Stare Decisis concerns earlier judicial decisions used as authority; the operative earlier items here are the parties' transactions. These neighboring ideas help identify boundaries but do not replace the same-party history and governing-rule roles of course of dealing.

Neighborhood in Abstraction Space

Course of Dealing sits in a moderately populated region (57th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Competitive Strategy & Market Entry (11 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25

Not to Be Confused With

  • Course of performance: repeated acts under the current transaction, subject to UCC §1-303(a)'s further conditions.[1]
  • Usage of trade: a regular practice of a place, vocation, or trade rather than the history of the particular contracting pair.[1]
  • Judicial precedent: prior court rulings used as legal authority, not the parties' earlier transactions.

  • Requirements contract: an agreement whose quantity depends on the buyer's actual requirements; prior dealings may be evidence within it but are not its defining quantity commitment.

  • Patent prosecution history: Judge Mayer's concurrence in the Federal Circuit's Markman decision calls the applicant's exchanges with the Patent Office a “course of dealing.”[15] In that concurrence, prosecution history may show meaning attached to a patent term or an applicant position taken to obtain issuance.[15] The majority says a patent is not a contract.[15] This sourced patent claim-construction context is adjacent to, and outside the identity of, the present bilateral contract-law entry. It does not by itself establish a separate canonical abstraction.

References

[1] American Law Institute & Uniform Law Commission. Uniform Commercial Code § 1-303. Subsections (a)–(f), course of performance, course of dealing, and usage of trade. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q ↩r ↩s ↩t ↩u ↩v ↩w ↩x ↩y ↩z ↩27 ↩28 ↩29 ↩30 ↩31 ↩32 ↩33 ↩34

[2] United States Court of Appeals for the Ninth Circuit. Insurance Company of North America v. NNR Aircargo Service (USA), Inc. (2000), 201 F.3d 1111, factual history and Discussion I–III. https://law.justia.com/cases/federal/appellate-courts/F3/201/1111/642791/ registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q ↩r ↩s ↩t ↩u

[3] ICC Court of Arbitration. Award 8611/HV/JK (1997), original German, facts and spare-parts analysis; English abstract is a translation aid. https://www.unilex.info/cisg/case/229 registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q ↩r ↩s

[4] UNIDROIT. Principles of International Commercial Contracts (2010), Article 1.9, usages and practices. https://www.unidroit.org/instruments/commercial-contracts/unidroit-principles-2010/chapter-1/ registry ↩

[5] American Law Institute. Restatement (Second) of Contracts (1981), §223; licensed reprint in Howard Law Contracts casebook §7.12. https://opencasebook.org/casebooks/11720-bruckner-howard-law-contracts-2024/as-printable-html/7/ registry ↩

[6] Uniform Law Commission. Uniform Commercial Code Article 1, General Provisions (2001), revision history. https://www.uniformlaws.org/acts/ucc registry ↩

[7] District of Columbia Council. District of Columbia Code Section 28-1-303 (2013), enactment history and Uniform Commercial Code Comment. https://code.dccouncil.gov/us/dc/council/code/sections/28:1-303 registry ↩a ↩b

[8] United States District Court for the Southern District of Florida. Allapattah Services, Inc. v. Exxon Corp. (1999), 61 F. Supp. 2d 1308, pp. 1314–1315. https://law.justia.com/cases/federal/district-courts/FSupp2/61/1308/2501008/ registry ↩

[9] United States District Court for the District of Colorado. KLM Precision Fitness Equipment of Pompano Beach, Inc. v. Nautilus, Inc. (2011), No. 08-cv-01228, Doc. 229, pp. 13–15. https://law.justia.com/cases/federal/district-courts/colorado/codce/1:2008cv01228/107953/229/ registry ↩

[10] Colorado Supreme Court. Pepcol Manufacturing Co. v. Denver Union Corp. (1984), 687 P.2d 1310, p. 1314. https://openjurist.org/687/p2d/1310/pepcol-manufacturing-co-v-denver-union-corp-5329522 registry ↩

[11] United States Court of Appeals for the Tenth Circuit. Amoco Production Co. v. Western Slope Gas Co. (1985), 754 F.2d 303, pp. 307–308. https://law.justia.com/cases/federal/appellate-courts/F2/754/303/319014/ registry ↩

[12] United Nations. Convention on Contracts for the International Sale of Goods (1980), Article 9(1)–(2). https://www.unilex.info/cisg/text registry ↩

[13] UNCITRAL. Digest of Case Law on the United Nations Convention on Contracts for the International Sale of Goods (2016), Article 9, paragraph 7. https://uncitral.un.org/sites/uncitral.un.org/files/media-documents/uncitral/en/cisg_digest_2016.pdf registry ↩

[14] American Law Institute & Uniform Law Commission. Uniform Commercial Code § 1-201. Subsections (b)(3) and (b)(12), agreement and contract. registry ↩

[15] United States Court of Appeals for the Federal Circuit. Markman v. Westview Instruments, Inc. (1995), 52 F.3d 967, majority p. 985 and Mayer concurrence p. 991. https://openjurist.org/52/f3d/967 registry ↩a ↩b ↩c