Skip to the main content.

9 min read

Group Purchasing Organizations: Why Leverage Is Only Half the Value

Group Purchasing Organizations: Why Leverage Is Only Half the Value

A group purchasing organization gives procurement access to supplier contracts that someone else has already sourced, benchmarked, and maintained on behalf of a large pool of member companies. Teams activate the agreements they want, at pricing and terms they would struggle to secure alone, and bring indirect and tail spend categories under management in weeks rather than months.

Most procurement leaders meet the model believing it exists for companies too small to negotiate well on their own.

This article covers how GPOs work and make money, which categories suit them, who they actually serve, and what to ask before you sign.

Key takeaways:

  • A GPO aggregates member spend to negotiate supplier contracts centrally. Members opt into the agreements they want rather than committing their whole spend.
  • Most GPOs earn revenue through administrative fees paid by suppliers, usually a small percentage of member spend flowing through the contract.
  • Size is not the qualifier. Large organizations with stretched teams often gain more from a GPO than small ones with mature category management.
  • Price parity between the major GPO programs is closer than most buyers assume, so the real differences show up in data visibility, compliance support, and account management.

What is a group purchasing organization?

A group purchasing organization, or GPO, is a company that aggregates the purchasing volume of many member organizations to negotiate contracts with suppliers on their behalf. Members buy through those pre-negotiated agreements at pricing and terms they would find difficult to secure independently, without surrendering control over what they purchase.

The model started in healthcare, where large provider networks began outsourcing significant parts of their purchasing to shared organizations several decades ago. It has since spread across commercial and public sectors. If you search the abbreviation on its own, you will find a Group Policy Object in IT and the Government Publishing Office in Washington. In procurement, GPO means one thing: group purchasing.

The important nuance is that a GPO extends procurement's reach rather than replacing it. Teams keep their category strategy, their stakeholder relationships, and their supplier decisions. What they gain is a set of agreements someone else already negotiated, benchmarked, and maintains.

 

How does a group purchasing organization work?

The mechanics are straightforward. A GPO runs sourcing events across a defined set of categories, awards contracts to one or more suppliers, and makes those agreements available to its members. A member joins, reviews the contract portfolio, activates the agreements that fit, and begins buying. Activation typically takes weeks rather than the months a full sourcing cycle would consume.

Two details tend to surprise first-time buyers. The first is that membership is rarely all-or-nothing. Most commercial GPOs let procurement adopt contracts selectively, category by category, which is what makes group purchasing workable alongside an existing sourcing program. The second is that the GPO usually stays involved after activation, handling business reviews, tracking compliance, and holding suppliers to the pricing they committed to.

How GPOs make money

Most GPOs are funded by the supply side rather than by their buy-side members. Suppliers pay the GPO a contract administrative fee, almost always calculated as a percentage of what members buy through the agreement, in exchange for access to an aggregated customer base and a lower cost of sale. The U.S. Government Accountability Office, reviewing the healthcare GPO market, described these fees as "GPOs' main source of operating revenue," and found that among the six largest GPOs the volume-weighted average ran between 1.22 and 2.25 percent of purchases.

What happens to that fee next varies more than most buyers expect. In healthcare, where many GPOs are owned by their member hospitals, a large share flows back to members: the GAO found that five GPOs collected roughly 2.3 billion dollars in fees in 2012 and passed nearly 70 percent of it on to customers and owners. Commercial GPOs more often keep the fee and make membership free instead, with no dues and no minimum purchase commitment. Some charge a subscription. There is no single convention, which is exactly why the question is worth asking.

Healthcare GPOs also work under a legal framework that does not extend to the commercial market. A federal safe harbor exempts their administrative fees from anti-kickback rules, provided the GPO discloses the fees to each customer in writing every year and either holds them at 3 percent of the purchase price or states the maximum in the agreement. Commercial GPOs carry no equivalent obligation, so fee transparency is a matter of the provider's practice rather than the law.

Vertical and horizontal GPOs

GPOs fall into two broad models. Vertical GPOs serve a single industry, such as healthcare, dental, hospitality, or education, and tend to go deep on the direct and specialized goods that industry buys. Horizontal GPOs serve members across many industries and aggregate the indirect categories almost every organization has in common, including office supplies, small parcel shipping, facilities services, foodservice, and travel.

Depth or breadth is the real trade-off. A vertical GPO knows your industry's specifications; a horizontal GPO gives you more categories under one relationship.

What a GPO delivers beyond price

Savings are the obvious draw, and they are real. Jay Black, who leads the group purchasing practice at Insight Sourcing Group, put a number on what a well-run program returns year after year when he joined the podcast in Episode 232: an active program drives somewhere between two and four percent savings annually, sustained through category management rather than a single negotiation.

The more interesting benefits sit alongside the pricing. Paul Dhaliwal, who leads procurement and supply chain for the U.S. Capstone team at KKR, works across more than 230 portfolio companies with a small central team, and he described the second-order value in a way that stuck with me:

 

"GPOs actually provide a very effective and efficient way to drive change and value across our portfolio companies. Besides commercial benefits, we think that if we have a good GPO relationship, that also helps our portfolio companies get a much higher level of account management. That comes in very handy, especially in times of disruptions."

 

Paul Dhaliwal, U.S. Capstone Team, KKR (Art of Procurement, GPOs as Value Drivers within Private Equity Procurement)

That point deserves attention because it reframes what you are buying. Account management sounds like a soft benefit right up until a category goes short and you need a supplier to answer the phone. Buying through an aggregated relationship changes where you sit in the queue, and the companies that came through recent supply disruptions best were often the ones with a senior relationship already in place.

The third benefit is visibility. Because every transaction runs through a known contract, spend that used to be invisible becomes reportable, which is why larger organizations frequently value a GPO's compliance and category management support more than the headline discount.

 

Which categories work best in a GPO?

Not every category belongs in a group purchasing program, and the fit follows a recognizable pattern. Jay described the profile plainly on the podcast: high-velocity categories with a large number of SKUs, frequent price movement at the item level, and purchasing fragmented across many buyers in the enterprise. Office supplies, small parcel, MRO, facilities services, and corporate travel all sit squarely in that description.

The common thread is that these categories punish inattention. They generate thousands of small transactions, they rarely justify a dedicated category manager, and they leak value quietly. That makes them the natural first stop for a GPO, and it explains why group purchasing and tail spend management programs so often arrive together.

Strategic, high-value direct categories usually stay in-house. That is not a limitation of the model so much as a division of labor: your team holds the categories where deep specification knowledge and supplier development create advantage, and the GPO covers the ones where scale and administration create it. Most mature programs end up running both, which our guide to indirect procurement strategies explores in more depth.

Paul Dhaliwal added a useful test from the buy side. Before anything else, he asks whether the GPO can find a supplier willing to treat a wide group of prospective clients as one large, diversified, growing customer base. If no supplier in the category will make that leap, the aggregation has nothing to stand on, regardless of how much volume sits behind it.

Are GPOs only for smaller companies?

No, and this is the misconception worth retiring first. Company size is a poor predictor of GPO fit; the maturity and capacity of the procurement team is a much better one.

I held the small-company view myself for a long time. In an earlier role I even looked at building a GPO inside my own procurement organization, but strictly as a service we could offer our small business customers, never as something we would buy through ourselves. Jay Black reframed it for me:

 

"You've got large organizations with very immature or understaffed procurement functions, and then you might also have smaller companies that actually have surprisingly mature procurement functions, and they actively and effectively manage the categories within their domain. I think it's a disservice to dismiss one side or the other."

 

Jay Black, Vice President, Insight Sourcing Group (Art of Procurement, Episode 232)

What he is describing is a capability gap, not a revenue band, and that is a much more useful thing to assess in your own organization.

There is also a mathematical argument, which Brian Halpin, Vice President and General Manager at Procure Analytics, made at AOP’s Categorypalooza virtual event: no matter how large your spend is, you will never have the purchasing power of a thousand companies. Group purchasing pricing reflects the collective volume of the membership rather than the volume of its biggest member, so scale alone does not put you past the point of benefit. We covered that argument and four others in 5 Common Myths About GPOs.

GPOs and strategic sourcing are not competing choices

Buyers often frame this as a decision: run a sourcing event, or join a GPO. In practice the two work best together, and the hybrid model has become the norm among the teams I speak with.

Strategic sourcing earns its cost where category knowledge, specification design, and supplier development move the number. A GPO earns its place where the category is fragmented, the SKUs are many, and the marginal return on running your own event is low. Deciding which categories belong on which side is the actual strategy question, and it is a far more productive one than treating group purchasing as an admission that your team could not do the work itself.

Jay Black made a related point about the first year that I think every buyer should internalize. Any GPO can deliver a one-time reduction when you move onto a better contract. What separates programs is what happens in years two, three, and four, once that initial gain is banked and the value has to come from compliance, category management, and continued benchmarking instead.

What to ask before you choose a GPO

Because pricing between the major commercial programs sits closer together than most buyers expect, the differences that matter are usually operational. Jay put the buyer's problem well:

 

"If you assume for a moment that most GPOs are relatively similar from a pricing perspective on things like office supplies, rental cars, and multifunction machines, and you also assume those programs would drive some savings for your organization, you start to have to think about what the real decision criteria are. Pricing is only a portion of the story."

 

Jay Black, Vice President, Insight Sourcing Group (Art of Procurement, Episode 232)

If price is roughly a constant, the variables are everything else. A few questions separate the programs quickly.

How did you choose the suppliers in this category? The answer tells you whether the GPO ran a real sourcing process or simply assembled a portfolio. Ask what methodology sits behind the award and what data informed it.

How will you track and report the savings you promise? This is a genuine gap in the market. Some programs offer full category management and analytics; others provide no savings tracking at all. Neither is automatically wrong, but you should know which you are buying before the first invoice, not after.

How is the supplier relationship governed? Governance models differ meaningfully. Clarify who runs business reviews, who holds the supplier to committed pricing, and how much of the relationship you continue to own.

What does your own data look like? Black's advice to buyers was to take inventory of their spend visibility before the conversation starts, because the quality of a savings analysis depends on the quality of the baseline. A year of average pricing can quietly understate savings in a category that has taken consecutive price increases, and you want to catch that in diligence rather than in a business review.

One thing not to do: bidding GPOs against one another rarely produces a better outcome, because the pricing gap between major providers is small and the exercise tells you nothing about the operating model you will actually live with.

The bottom line on group purchasing organizations

Group purchasing works when procurement treats it as a capacity decision rather than a pricing one. The question is not whether a GPO can beat your current rate on office supplies. It is which categories deserve your team's attention, which ones will never get it, and what the best available answer is for that second group.

Get that division right and the GPO stops looking like an outsourcing decision and starts looking like what it is: a way to extend your team's reach without extending your headcount.

If you are evaluating group purchasing seriously, our GPO Buyer's Guide, created with Una, goes further than we can here. It sets out a four-step framework for evaluating and integrating a GPO, the selection criteria that separate strong partners from adequate ones, the mistakes buyers most often make, and the trends reshaping the market. It's a free download, and it is the most practical resource we have published on the subject.

Group Purchasing Organization FAQs

Here are some common questions concisely answered.

What does GPO stand for in procurement?

GPO stands for group purchasing organization. In procurement, it refers to a company that aggregates the buying volume of multiple member organizations to negotiate supplier contracts on their behalf. The abbreviation has unrelated meanings elsewhere, including Group Policy Object in IT administration and the U.S. Government Publishing Office, so context matters when searching.

How much can a GPO save?

Savings vary by category, baseline, and how actively the program is managed. According to Jay Black, then Vice President at Insight Sourcing Group, speaking on the Art of Procurement podcast, an active program returns two to four percent annually, sustained through ongoing category management rather than a single negotiation. First-year savings are often higher when a member moves from an unmanaged category onto a benchmarked contract.

Do you have to move all your spend to a GPO?

Almost never. Most commercial GPOs let members adopt contracts selectively, category by category, which is what makes group purchasing compatible with an existing sourcing program. Some agreements do include minimum volume commitments or exclusivity clauses, so confirm the terms of each individual contract before you activate it.

What is the difference between a vertical and a horizontal GPO?

A vertical GPO serves one industry, such as healthcare, dental, or hospitality, and tends to specialize in the direct and technical goods that industry buys. A horizontal GPO serves members across many industries and aggregates common indirect categories such as office supplies, shipping, facilities, and travel. Vertical offers depth; horizontal offers breadth.

Can a GPO replace a procurement team?

No. A GPO supplies pre-negotiated contracts and category support, but it does not set strategy, manage stakeholders, or own supplier decisions. The teams that get the most from group purchasing treat it as added capacity for categories they cannot resource internally, while keeping ownership of the categories where their own expertise creates advantage.