A group purchasing organization (GPO) is an entity that aggregates the buying volume of many separate institutions and uses that combined leverage to negotiate contracts with suppliers — pricing, terms, and service levels that no single lab, department, or even university could get on its own. For research institutions, GPOs sit alongside a formal, in-house competitive bid as a second legitimate way to satisfy procurement requirements: instead of running your own solicitation for scientific equipment, lab consumables, or services, you “piggyback” on a contract someone else already competed.
They matter to research administrators and lab managers for a practical reason: most purchases a lab makes are too small individually to justify the time cost of a full RFP, but too large in aggregate — across an institution, or across a GPO’s whole membership — to ignore the savings available from real negotiated volume. Understanding how GPO contracts are built, who the major GPOs serving research institutions actually are, and where a GPO contract does and doesn’t satisfy federal procurement rules is a core piece of research-office and lab-operations competency.
What a GPO actually does
A GPO does not sell anything itself. Its function is contracting and aggregation:
- It solicits and negotiates contracts with manufacturers and distributors — lab equipment, reagents, general lab supplies, furniture, IT hardware, and services — on behalf of its member institutions.
- It aggregates volume across hundreds or thousands of members so the negotiated price reflects combined purchasing power, not any one institution’s individual spend.
- It publishes the resulting contracts for members to use directly with the awarded supplier, without each member running its own solicitation for that item or service.
- It is typically funded by supplier administrative fees (a small percentage of sales made through the contract, paid by the awarded vendor to the GPO), not by membership dues charged to the institution — most GPO membership for public and nonprofit research institutions is free or low-cost.
Members are not obligated to buy through every GPO contract; a GPO contract is one procurement option among several, and an institution’s own procurement policy determines which contracts it will accept as satisfying its purchasing rules.
GPOs commonly used by research institutions
Several GPOs are widely used across U.S. higher education and academic medical centers. Coverage below is general orientation, not an endorsement or a complete vendor comparison — verify current contract portfolios and terms directly with each organization.
- E&I Cooperative Services — a member-owned, nonprofit purchasing cooperative whose membership is limited to education and affiliated nonprofit research institutions. Because it is member-owned rather than a for-profit intermediary, its governance and contract award process are structured specifically around higher-education and research-institution purchasing categories: scientific and lab equipment, facilities, technology, and professional services.
- Vizient — originally built around healthcare group purchasing and widely used by academic medical centers and hospital-affiliated research operations; its contract portfolio is strongest in clinical, laboratory, and healthcare-adjacent categories relevant to institutions that combine research with patient care.
- OMNIA Partners — a cooperative purchasing organization serving public-sector and education members broadly, including higher education institutions, with a wide multi-category contract portfolio spanning facilities, technology, and general procurement categories beyond lab-specific goods.
Institutions frequently hold active memberships in more than one of these simultaneously, using whichever GPO has the strongest contract for a given purchase category.
When a GPO contract makes sense — and when it doesn’t
A GPO contract is generally worth using when:
- The item or service is a common, standardized purchase (general lab consumables, off-the-shelf equipment, common services) where a pre-negotiated national contract is unlikely to leave meaningful savings on the table.
- The purchase is too small to justify the administrative cost of an institution running its own competitive solicitation, but the item is still significant enough that an informal, uncompeted purchase would be a poor use of funds.
- Speed matters — a GPO contract can typically be used immediately, where an in-house RFP can take weeks or months.
A GPO contract is a weaker fit when:
- The purchase is highly specialized or custom (a one-of-a-kind instrument configuration, a niche reagent, a specific PI-preferred vendor) where no aggregated contract exists or the aggregated price isn’t actually competitive for that specific need.
- An award’s terms or a sponsor’s own procurement conditions require documentation the GPO contract doesn’t provide in the form the institution needs.
- Institutional policy caps the dollar value or category eligible for GPO-contract use without additional internal approval.
GPOs and federal grant procurement compliance
For purchases made with federal award funds, the relevant rule is the Uniform Guidance at 2 CFR §200.318, which explicitly encourages non-federal entities to enter into intergovernmental or inter-entity procurement arrangements — including cooperative purchasing through organizations like GPOs — “for procurement or use of common or shared goods and services” as a way to foster economy and efficiency.
Encouragement to use cooperative purchasing is not, however, a blanket waiver of competition requirements. Two things a research office should actually verify before treating a GPO purchase as compliant:
- That the GPO’s own underlying solicitation was competitively run in a manner consistent with the Uniform Guidance’s procurement standards. Reputable GPOs serving education (E&I, for instance, points institutions to third-party validation of its RFP process against public-procurement standards) document this; if a GPO can’t show how a given contract was competed, using it doesn’t automatically satisfy your own institution’s competition obligation.
- That your institution’s own procurement policy formally recognizes GPO contracts as a valid procurement method — this is an internal-policy question, not just a federal-rules question, and it’s where audit findings actually tend to surface: a purchase made through a GPO contract the institution’s own policy never approved as an acceptable method.
A single-source or sole-source purchase made without a GPO contract behind it is a different situation and generally needs its own documented justification — see Sole-Source Justification Letter: Format, Required Elements, and a Worked Example for what that requires. Using an already-competed GPO contract is meant to be the easier, lower-documentation path precisely because the competition already happened upstream — but only if the institution can actually show that.
Benefits and limitations
| Benefits | Limitations |
|---|---|
| Lower prices from aggregated national volume than most single institutions can negotiate alone | Contract terms are standardized across many members and can’t be customized to one lab’s specific need |
| Faster than running an in-house competitive solicitation for every purchase | Coverage gaps exist for specialized/niche categories with no strong aggregated contract |
| Membership is typically free or low-cost for public/nonprofit institutions | Institution still must confirm the GPO’s award process meets its own compliance standard, especially for federally funded purchases |
| Reduces administrative burden and audit exposure from repeated small uncompeted purchases | Requires internal procurement policy to formally recognize GPO contracts as an approved method |
Getting started with a GPO
- Confirm your institution already holds membership — most research universities and academic medical centers are already members of at least one major GPO through central procurement, even if individual labs don’t know it.
- Check with central procurement/purchasing services before assuming a category isn’t covered; contract portfolios change frequently and new categories are added regularly.
- For federally funded purchases, ask procurement to confirm in writing that the specific GPO contract you intend to use is treated as compliant under your institution’s Uniform Guidance procurement policy — don’t assume it automatically is.
- Keep the GPO contract reference number and award documentation with your purchase records; auditors reviewing a federally funded purchase will want to see that a competed contract, not an informal single-quote purchase, was the basis for the price paid.
Frequently asked questions
Do GPO contracts satisfy federal competitive-bidding requirements automatically?
Not automatically. 2 CFR §200.318(e) encourages cooperative purchasing arrangements like GPOs as a way to achieve economy and efficiency, but the purchase still has to be traceable to a genuinely competed contract, and your own institution’s procurement policy has to recognize that GPO contract as an approved method. Confirm both before relying on a GPO purchase to satisfy a federal award’s competition requirement.
How do GPOs make money if institutions don’t pay membership fees?
Most GPOs serving education and research institutions are funded through administrative fees paid by the awarded supplier — typically a small percentage of sales made through the contract — rather than dues charged to member institutions. This is why membership for a public university or nonprofit research institution is usually free or nominal.
Is a GPO contract the same thing as a cooperative purchasing agreement?
They’re related but not identical terms. A GPO is an organization that runs competed contracts on members’ behalf; “cooperative purchasing agreement” is the broader regulatory category (2 CFR §200.318(e)) that includes using a GPO contract as well as other intergovernmental or inter-entity purchasing arrangements, such as piggybacking directly on another public entity’s competed contract.
Can a single lab use a GPO contract without going through central procurement?
This depends entirely on institutional policy. Some institutions let departments and labs use published GPO contracts directly up to a dollar threshold; others require central procurement to process any purchase above a minimal amount regardless of whether a GPO contract exists. Check your institution’s own procurement policy rather than assuming.
This guide covers general GPO mechanics for research-institution audiences. It is not legal or compliance advice — consult your institution’s sponsored-programs or procurement office and, for federally funded purchases, your award terms and 2 CFR Part 200 directly.
