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.

Two Ways to Commit to a Foundry one fixes a volume floor, the other fixes who the buyer is loyal to Take-or-pay fixes a volume number Pay for X wafers minimum Free to also buy elsewhere risk: demand falls short of X Requirements contract fixes exclusivity, not a number Buy all actual needs from us Not allowed to buy elsewhere risk: actual demand is unknowable upfront Take-or-pay bets on a number; a requirements contract bets on exclusivity. Volume is whatever the buyer actually needs, so the risk shifts to defining "needs" precisely.

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.

Buyer needs an ongoing wafer supply
volume is hard to forecast precisely
Buyer commits to exclusivity instead of a numberthe foundry gets certainty on share, not on volume
All qualifying demand routed to this foundry
no parallel sourcing for covered parts
Foundry supplies whatever that demand turns out to be
within capacity limits negotiated separately
Actual volume floats with real demand
neither side locked a number, only a relationship

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.

FeatureTake-or-payRequirements contract
What is fixeda minimum volume numberexclusivity for covered demand
Buyer can source elsewhereyes, above the floorno, for anything the contract covers
Main risk to buyerpaying for unused committed volumebeing locked in if the foundry underperforms
Main risk to foundrynone below the floordemand could be far lower than expected
Typical useleading-edge capacity reservationongoing 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.

Take requirements contract further

Ask the copilot about this term, or have our engineers assess it against your process.