Cooperative Purchasing Under 2 CFR 200.318(e)

2 CFR §200.318(e) encourages non-federal entities — universities, hospitals, nonprofits, and other recipients of federal grant or cooperative agreement funds — to buy common or shared goods and services through state and local intergovernmental agreements or inter-entity agreements rather than running an independent solicitation every time. In practice this means a research institution can often purchase off a state master contract, a multi-state purchasing cooperative, or another public entity’s existing competitively bid contract, instead of issuing its own bid or RFP for the same item. Done correctly, it is a genuine, federally sanctioned cost- and time-saving tool. Done carelessly, it is one of the more common procurement audit findings in federally funded research administration.

This page explains what §200.318(e) actually authorizes, how cooperative/intergovernmental purchasing differs from a commercial group purchasing organization (GPO), and what a research office still has to document to use one compliantly. It is a companion to the site’s broader 2 CFR 200 Procurement Standards (§§200.317–200.327) guide, which covers the full Subpart D framework this provision sits inside.

What §200.318(e) actually says

The regulatory text is short and permissive, not mandatory. In full: “When appropriate for the procurement or use of common or shared goods and services, recipients and subrecipients are encouraged to enter into State and local intergovernmental agreements or inter-entity agreements for procurement transactions.” Three things follow directly from that wording:

It’s an encouragement, not a requirement. Nothing in §200.318(e) obligates an institution to use a cooperative agreement; it removes a barrier that might otherwise exist, and signals that federal reviewers view the practice favorably when used appropriately.
It sits alongside, not instead of, the rest of §200.318. The other paragraphs of the same section — documented procurement procedures, conflict-of-interest standards, responsible-contractor determinations, and recordkeeping — still apply in full to a purchase made through a cooperative agreement. §200.318(e) authorizes the vehicle; it doesn’t waive the surrounding standards.
“Appropriate” is doing real work in that sentence. The provision only applies when the cooperative vehicle is genuinely suited to the purchase — a common or shared good or service, not a specialized item that happens to be on a convenient contract.

What counts as a cooperative or intergovernmental purchasing agreement

In federal grants administration, this category covers several related but distinct mechanisms:

State master contracts / statewide term contracts — a state government competitively solicits and awards a contract (e.g., for lab supplies, computers, or furniture), and other public entities within the state, including public universities, are permitted to purchase off that same contract.
Interlocal or joint powers agreements — formal agreements between two or more governmental entities (a public university and a city, county, or another state agency, for example) authorizing them to jointly use or extend each other’s competitively bid contracts.
Multi-state and national public-sector purchasing cooperatives — organizations that run a competitive solicitation once on behalf of many public agencies nationwide, so any member agency can then purchase off the resulting contract without a separate bid. Well-established examples in U.S. public procurement include NASPO ValuePoint (run by the National Association of State Procurement Officials), Sourcewell, and OMNIA Partners’ public-sector program.
Piggyback clauses — a contract clause, written into the original competitively bid contract by the lead agency, that expressly permits other public entities to purchase under the same terms and pricing.

Cooperative purchasing vs. group purchasing organizations (GPOs)

Cooperative/intergovernmental agreements under §200.318(e) are often confused with commercial group purchasing organizations (GPOs) such as E&I Cooperative Services or Vizient — and the confusion is understandable, because both let an institution buy at pre-negotiated, aggregated pricing without running its own solicitation, and both are recognized as consistent with §200.318(e) when used appropriately. The distinction that matters for compliance is who ran the underlying competition and under what authority:

A GPO is typically a member-owned, nonprofit or for-profit organization that negotiates supplier contracts on behalf of its member institutions (often higher-education or healthcare institutions specifically); membership is voluntary and contractual, not governmental.
A state/intergovernmental cooperative under §200.318(e) is specifically a government-to-government or government-authorized arrangement — a state contract, an interlocal agreement, or a public purchasing cooperative — grounded in public procurement law rather than a private membership agreement.

In practice the two categories overlap: some public purchasing cooperatives (NASPO ValuePoint, Sourcewell) function very similarly to a GPO in day-to-day use. The compliance question is the same either way — see the next section — but an institution’s procurement file should correctly identify which type of vehicle was used, since a grants auditor or cognizant agency reviewer may ask the question differently for each.

Using a cooperative agreement without waiving competition

The most consequential misunderstanding of §200.318(e) is treating it as a blanket exemption from competition requirements. It isn’t. The competition requirement in the underlying purchase is satisfied only if the lead agency’s original contract was itself competitively solicited in a manner that meets full-and-open-competition standards. Before an institution relies on a cooperative or piggyback contract for a federally funded purchase, its procurement office should be able to confirm:

The lead agency’s contract was competitively solicited (sealed bid or competitive proposal, consistent with §200.320), not itself a sole-source or informally negotiated award.
The cooperative contract’s scope genuinely covers the item or service being purchased — not a stretch interpretation to avoid running a separate solicitation.
Price reasonableness for the specific purchase is independently considered, not assumed automatically because the contract exists (the general §200.318 documentation standard still applies).
No organizational conflict of interest exists in choosing to use that particular cooperative vehicle.

Federal awarding agencies and cognizant audit staff have specifically flagged improper reliance on state or cooperative contracts as a recurring finding: an institution using a contract it never verified was competitively procured, or applying a cooperative contract to a purchase outside its actual scope, can be cited for a competition-standard violation even though the raw dollar amount looks reasonable.

What the procurement file should document

A defensible file for a cooperative or intergovernmental purchase generally includes:

Identification of the specific cooperative agreement, state contract number, or interlocal agreement relied on.
Evidence (even a summary reference) that the underlying contract was competitively solicited by the lead entity.
A brief rationale for why the cooperative vehicle was “appropriate” for this purchase — i.e., that the item is a common or shared good or service consistent with §200.318(e)’s own language.
Confirmation the price is reasonable for the specific transaction, not just a reference to the contract’s existence.
Sign-off consistent with the institution’s own documented, normal procurement procedures under §200.318(a).

When a cooperative agreement is the wrong fit

Cooperative purchasing isn’t a universal shortcut. It’s a weaker fit when:

The purchase is highly specialized, custom, or unique to the specific research project — not a “common or shared” good or service in the sense the provision contemplates.
The institution cannot readily verify that the lead agency’s contract was competitively solicited (an unverifiable or opaque cooperative arrangement should not be relied on for a federally funded purchase).
A specific sponsor or program has its own procurement restrictions that conflict with using a third-party cooperative vehicle.
The purchase is large enough, or specialized enough, that a project-specific competitive solicitation would likely produce meaningfully better pricing or terms — cooperative pricing is aggregated and general, not tailored to a single large purchase.

Frequently asked questions

Does 2 CFR 200.318(e) require institutions to use cooperative purchasing?

No. The provision encourages the practice where appropriate; it doesn’t mandate it, and an institution remains free to run its own competitive solicitation instead.

Is buying off a state contract the same as a sole-source purchase?

No, provided the state’s original contract was itself competitively solicited. If it wasn’t — or the institution can’t confirm that it was — relying on it can effectively function as an undocumented sole-source purchase, which is a compliance risk, not a safe harbor.

Are GPOs like E&I or Vizient covered by 200.318(e)?

Yes, in practice federal guidance and audit practice treat well-run GPO purchasing as consistent with the spirit of §200.318(e)’s encouragement of shared/cooperative procurement, alongside government-run cooperatives like NASPO ValuePoint. See the site’s dedicated GPO guide for how that specific mechanism works and what to verify before treating a GPO contract as compliant.

Does using a cooperative contract eliminate the need for a price reasonableness determination?

No. The general documentation standards in §200.318 — including maintaining records sufficient to detail the history of the procurement and its basis — still apply. An institution should be able to show it considered whether the price was reasonable for the specific purchase, not simply that a contract existed.

What’s the difference between an interlocal agreement and a purchasing cooperative?

An interlocal (or joint powers) agreement is a direct agreement between two or more specific governmental entities to share or extend each other’s contracts. A purchasing cooperative is a broader, often national or multi-state organization that runs solicitations centrally so that many member agencies can each purchase off the resulting contracts without a separate agreement for every pairing of entities.

This page explains 2 CFR §200.318(e) as codified in the current eCFR text, as one piece of the broader Subpart D procurement standards. It is a general reference, not legal advice — an institution’s own sponsored-programs or procurement office, and its cognizant federal agency, are the authoritative source for how these standards apply to a specific award.