Opinion ID: 765542
Heading Depth: 2
Heading Rank: 1

Heading: Whether the Contract Was an Exclusive Requirements Contract

Text: 7 The district court concluded that, as a matter of law, this contract is not a requirements contract. A requirements contract is one in which the purchaser agrees to buy all of its needs of a specified material exclusively from a particular supplier, and the supplier agrees, in turn, to fill all of the purchaser's needs during the period of the contract. Indiana-American Water Co. v. Seelyville, 698 N.E.2d 1255, 1259 (Ind. Ct. App. 1998). This definition, which reflects not only Indiana law but the law of other American jurisdictions, establishes that a requirements contract exists only when the contract (1) obligates the buyer to buy goods, (2) obligates the buyer to buy goods exclusively from the seller, and (3) obligates the buyer to buy all of its requirements for goods of a particular kind from the seller. See James J. White & Robert S. Summers, Uniform Commercial Code sec. 3-9, at 154-55 (1995); see also E. Allan Farnsworth, Farnsworth on Contracts sec. 2- 15, at 135-37 (1990). 8 We first turn to the language of the contract. The district court took the view that the language of the contract made clear that this contract is not, as a matter of law, a requirements contract. The court stressed that the language of what it considered the most important paragraphs is permissive: Navistar is required to purchase such quantities of the items listed herein as [it] might order or schedule. By the express language of the contract, Navistar could choose the quantities that it wished to order. Paragraphs 2 and 4 state, in part: 9 2. Unless otherwise specified, deliveries are to be made in quantities and at times specified in shipping schedules furnished to the Seller and from time to time by the Buyer, and the Buyer shall not be obligated to take any goods, the delivery of which has not been specified in such shipping schedules. . . . 10 4. Buyer shall have the right at any time and from time to time to cancel, in whole or in part, the deliveries specified and the authorizations contained in any shipping schedule given to the Seller. 11 R.1, Ex.A. 12 This language, standing alone, certainly does not establish the existence of a requirements contract. Nevertheless, we cannot say that it establishes, as a matter of law, that the contract is not such a contract. Rather, this language, upon which the district court and Navistar so heavily rely, is susceptible to several interpretations. As Navistar suggests, it may be construed as giving Navistar complete authority to decide how many parts to order from Zemco. On the other hand, the language may be read simply as an articulation of the manner in which Navistar should place its orders as it has need for the parts. 13 Other considerations, based on the language of the contract, make it even more clear that the contract is ambiguous as to whether it is a requirements contract. As Zemco notes, the contract provides that, in the event that Zemco cannot fill all the orders placed with it, it will give priority to the orders of Navistar as permitted by Indiana Code sec. 26-1-2-615. This contractual provision, standing alone, does not establish that the contract is a requirements contract. As the statutory language and its commentary suggest, the parties are entitled to great flexibility in agreeing how to allocate sales in the event all demands cannot be met. See Ind. Code sec. 26-1-2-615 & UCC cmt. 8. 2 It is quite possible, therefore, for parties to contract under this section of the Code for an arrangement other than a requirements contract. In this case, the contract contains a priority clause, and it also lacks a specific reference to quantity anywhere in the contract. As the Fifth Circuit has noted, in the absence of any explicit agreement as to quantity, the section of the Code authorizing requirements contracts is the primary 'gap filler' in the Code for quantity terms. Reigel Fiber Corp. v. Anderson Gin Co., 512 F.2d 784, 789 (5th Cir. 1975); see also Gestetner Corp. v. Case Equip. Co., 815 F.2d 806, 811 (7th Cir. 1987). 14 When we evaluate all of these textual considerations, we must conclude that the contract, taken as a whole, is ambiguous and that further investigation as to whether the parties intended a requirements contract is required. Resort to extrinsic evidence is appropriate in such a situation. Indeed, the Indiana Commercial Code makes clear that the provisions ought to be harmonized with the parties' course of dealing and the usage of trade. Indiana Code sec. 26-1-2-208(2) states: 15 The express terms of the agreement and any such course of performance, as well as any course of dealing and usage of trade, shall be construed whenever reasonable as consistent with each other; but when such construction is unreasonable, express terms shall control course of performance and course of performance shall control both course of dealing and usage of trade. 16 Ind. Code sec. 26-1-2-208(2). Here, the text of the contract, in what it affirmatively says and in what it omits, renders the intent of the parties ambiguous. It is therefore necessary to construe these terms in conformity with the parties' course of dealing and the usage of trade. See Universal Power Systems, Inc. v. Godfather's Pizza, Inc., 818 F.2d 667, 671 (8th Cir. 1987). Examination of the course of dealing, to the extent that it is developed in this record, supports the conclusion that there exists a genuine issue of triable fact with respect to the parties' intent. For 12 years--every year in which the contract was in effect--Navistar purchased all of its requirements from Zemco. We therefore cannot affirm the district court's grant of summary judgment to Navistar on this ground. 3 17