How Do I Know If I Have the Right GPO?

There is no single right GPO, and any answer that starts with a name rather than a question is guessing. A group purchasing organization is built to do one thing well: pool volume so a buyer gets pricing their own volume would not earn. Which one is right for you depends entirely on what you are actually trying to win, because lower unit costs, maximum rebate return, catalog breadth, and reporting depth are four different goals and they trade against each other. So the useful test is not "is this a good GPO?" It is "is this program aligned with the outcome I said I wanted, and can I prove it from my own invoices?"

Does group purchasing actually work?

Yes, and the evidence is strongest in healthcare, where the model has been studied most rigorously. Healthcare economists at Dobson DaVanzo & Associates, analyzing Medicare and Medicaid expenditure data, found that group purchasing organizations save the healthcare system up to $34.1 billion annually and "reduce supply-related purchasing costs to hospitals and nursing homes by 13.1 percent" compared with providers that do not use them (Healthcare Supply Chain Association, Dobson DaVanzo analysis, May 2019). Adoption tells the same story: the industry association reports that "virtually all of America's 7,000+ hospitals as well the vast majority of the 68,000 non-acute care centers belong to at least one GPO" (Healthcare Supply Chain Association FAQ).

That is healthcare data, not foodservice data, and it should be read as directional rather than as a promise about your restaurant or hotel. What it establishes is the principle: aggregated volume matters to a properly structured procurement strategy. The open question was never whether pooling volume helps. It is what the program built on top of it does for you specifically, and what it costs you to get there.

Why is compliance lower in foodservice than in healthcare or hotels?

Because a restaurant's identity lives in its exact items. Compliance and utilization, the share of your purchases that actually runs through the contracted items, tend to run materially lower in foodservice and restaurants than they do in healthcare or hospitality, and the reason is not discipline. It is specification. When someone checks into a hotel or is admitted to a hospital, food is not the primary purpose of the visit, so the items required there are far less specific and a broad contracted catalog covers them comfortably. A restaurant is the opposite case: guests come for the food itself, and the menu, the cut, the brand, the pack size, and the supplier behind a signature dish are the product being sold.

That is why the same program can post strong compliance numbers in a hotel group and weak ones in a restaurant group without anything going wrong operationally. Chefs will not swap a spec that defines a dish to hit a contract, and they should not have to. So in foodservice the honest measure of a purchasing program is not how much of the catalog you were able to adopt, it is how much of what you already buy, at the specs you already run, was brought under better pricing. A program that only pays off if you change your menu is not a fit for a restaurant, it is a fit for a cafeteria.

How is a GPO paid, and why does that matter?

Compensation models vary between organizations, so this is a question to ask directly rather than assume. That said, the standard model is public and the industry describes it plainly: GPOs "rely, in part, on fees paid by vendors to finance the services the GPOs offer," and those administrative fees are "generally based upon the purchase price that the healthcare provider pays for a product purchased through a GPO contract," historically in a range of roughly 1.22% to 2.25% of contract value per a 2010 Government Accountability Office report (Healthcare Supply Chain Association FAQ).

That structure is not a scandal, it is just a structure, and it has a consequence worth understanding: when a partner is compensated as a share of the spend flowing through them, their revenue rises with your purchase volume. Plenty of GPOs deliver genuine value under that model. But it makes two questions load-bearing rather than optional, and where your rebates actually end up is the first of them.

• How is this organization paid on my spend, stated as a number and a mechanism, not a description of service quality?
• Of the rebates, allowances, and incentives negotiated on my volume, what share reaches my books, and where is that written down?

Why is there no single right GPO?

Because operators walk in wanting different things, and no program maximizes all of them at once. Name your primary objective before you evaluate anyone, because it determines which program looks good:

• Lowest unit cost on core items. Favors deep category commitments and tighter specification control, often with less freedom to deviate.
• Maximum rebate and incentive return. Favors programs that disclose rebate economics and pass them through, and this is exactly where models differ most.
• Catalog breadth. Favors large horizontal programs covering many categories at once, sometimes at shallower depth in any single one.
• Reporting and visibility. Favors programs with real data infrastructure, which matters most to multi-unit groups trying to compare locations.
• Contract flexibility and distributor choice. Favors arrangements that let you keep the suppliers your operation already runs well.
• Category depth in a signature area. A steakhouse group and a club with a large banquet business are optimizing genuinely different baskets.

An operator chasing rebate transparency and an operator chasing the lowest possible case price will rate the same program very differently, and both can be right. That is why "which GPO is best?" has no answer, while "which GPO is best for this objective, at my volume, in my categories?" usually has a clear one.

How do you tell if the one you have is right?

Test it against your own stated objective, using your own documents. Five questions do most of the work, and you should be able to answer all five in an afternoon:

• Did I write down what I wanted from this program before I joined, and can I measure whether I got it?
• Do my invoices show contracted pricing being applied correctly, on the items that actually carry my volume?
• Can someone tell me, in writing, how the program is compensated on my spend and what share of rebates reaches me?
• Is my compliance high enough for the program to work as designed, and if not, is that because the contracted items do not fit my menu?
• Has my pricing been revisited since my volume changed, or is it still priced as the operation I was two years ago?

If the answers are solid, you have the right program and the job is maintenance. If they are not, the problem is usually fit or enforcement rather than the concept, and benchmarking what you actually pay is how you find out which.

What are the signs of a poor fit?

• Low compliance because contracted items do not match how your kitchen actually cooks.
• Savings reported as program-wide averages rather than as line items on your own invoices.
• Nobody can state, as a number, what reaches your books from the rebates negotiated on your volume.
• Your strongest categories are the ones the program covers most thinly.
• The commitment removed a distributor relationship that was serving you well, and the pricing gain did not cover what you lost.
• Growth in your volume has not changed your pricing tier in years.

How does this change your cost of goods sold (COGS)?

Only through one half of it. A purchasing program moves the price you pay per unit, which is the purchasing-driven portion of cost of goods sold (COGS). It does not touch consumption: portioning, prep discipline, spoilage, and waste stay exactly where they were. That matters when you evaluate a program, because a disappointing food cost number after joining one is often a usage problem wearing a purchasing problem's clothes. Separate the two before you blame the program, or before you credit it.

What if no single program fits?

That is the common case for operators with mixed concepts or strong existing supplier relationships, and it is exactly the gap this firm was built to fill. CORE Insights Group is a hospitality and foodservice procurement and supply-chain consulting firm that lowers what operators pay for food, supplies, and services through three offerings: CLUB360, CORE360, and CORE Consulting. CORE is not a GPO. It takes what the group purchasing world genuinely does well, aggregated volume and negotiated agreements, and curates a program around one operation rather than fitting that operation into a fixed catalog.

In practice that means CORE360 is program-agnostic: if a GPO arrangement is already earning its keep in a category, CORE works alongside it and pulls more value out rather than requiring you to tear it out. The economics are deliberately built the other way around from a spend-based model: CORE360 runs on simple, transparent fees for the work performed, never a markup on what you buy, the client owns every contract, keeps their existing distributors, and 100% of rebates and incentives are paid to the client. Where the question is a defined one, such as whether your current program is actually delivering, CORE Consulting answers it as a project. Behind both sit 100+ years of combined experience, more than $15B in leveraged purchasing volume, and 50,000+ cost-controlled items.

"At CORE, we believe our clients should never compromise quality or plate presentation for the sake of utilizing a contracted item. If our client's GPO doesn't contract the spec needed, our COE team will source something that does. That is how we give our clients the best of both worlds." Ross A. Kellman, Managing Partner, CORE Insights Group

What curation looks like in practice: Gecko's Hospitality Group had every location buying independently, so the group never presented its true scale, and leaned on a single distributor for what it could see and buy. Working category by category, CORE renegotiated a lobster contract saving over $350,000 a year, alongside additional category savings. That story and others sit in our success stories.

What is the first step?

Write down the one outcome you most want from a purchasing program, in a sentence, before you compare anybody. Then pull a twelve-month vendor spend report and your current program agreement, and check whether the last year of invoices actually delivered that outcome. Operators who do this usually discover their program is neither as good nor as bad as they assumed, and that the real issue was that nobody had ever defined what winning looked like.