Requirements Contract
A requirements contract is a foundry supply agreement in which the customer commits to buy all of its actual needs for a covered part or process from a single foundry, rather than committing to a specific volume number the way a take-or-pay agreement does.
The two contract types solve different forecasting problems. A take-or-pay agreement is useful when the parties can reasonably estimate volume in advance and want to lock in a number; a requirements contract is useful when volume is genuinely hard to predict but the foundry still wants assurance that it will capture all of a customer's real demand rather than losing share to a competitor as that demand fluctuates.
Exclusivity, not volume, is the thing both sides are actually negotiating. Because the buyer promises not to source covered demand elsewhere, the contract has to define precisely what counts as a "requirement" — which parts, which process generations, which end products — since an imprecise definition leaves room for the buyer to route demand around the agreement by reclassifying what it needs.
| Feature | Take-or-pay | Requirements contract |
|---|---|---|
| What is fixed | a minimum volume number | exclusivity for covered demand |
| Buyer can source elsewhere | yes, above the floor | no, for anything the contract covers |
| Main risk to buyer | paying for unused committed volume | being locked in if the foundry underperforms |
| Main risk to foundry | none below the floor | demand could be far lower than expected |
| Typical use | leading-edge capacity reservation | ongoing mature-node supply relationships |
Requirements contracts carry legal exposure that take-or-pay deals mostly avoid. Because the buyer is giving up the right to source elsewhere, courts and antitrust regulators scrutinize requirements contracts for whether the exclusivity could foreclose competitors from a meaningful share of the market, a concern that essentially does not apply to a take-or-pay agreement where the buyer always remains free to purchase additional volume from anyone else.
Mature-node and specialty supply relationships lean toward requirements contracts more than leading-edge ones do. A leading-edge customer chasing a scarce new node usually wants a guaranteed volume floor through take-or-pay because capacity, not loyalty, is the binding constraint; a mature-node customer with a long-running, stable part is more likely to sign a requirements contract, trading future flexibility for a foundry's commitment to keep that older line running and prioritized.
Read a requirements contract through a *loyalty-for-priority* lens rather than a *volume-commitment* lens: the buyer is not promising how many wafers it will order, it is promising who gets to supply them, and that distinction is exactly why the contract's definition of covered "requirements" ends up mattering more than any number either party could have written down at signing.