The case for centralized procurement is clean on paper: consolidate spend, increase leverage, negotiate better prices, capture the savings. It works in the spreadsheet every time. The problem is that spreadsheets do not buy things. People do. And people, faced with rigid centralized processes that do not match how they actually work, find ways around them.
The Hackett Group estimates that organizations lose 5–16% of negotiated savings to maverick buying — purchases made outside approved contracts and channels. For a $500 million spend organization, that is $25–80 million per year. Centralization promises savings through compliance. Then it creates the conditions that destroy compliance.
The myth, stated fairly
Centralized procurement has a valid origin. Before consolidation, most organizations had fragmented buying across divisions, regions, and business units. Multiple teams bought the same categories from different suppliers at different prices. No one had visibility into total spend. Consolidating purchasing under one team reduced supplier count, increased volume leverage, and produced immediate savings. For organizations coming from total fragmentation, centralization is an improvement. The myth is not that centralization produces savings. The myth is that it always produces the most savings — that more centralization always means more value.
Where the myth breaks down: the compliance assumption
Centralized procurement models assume that negotiated contracts get used. They assume users search the catalog, find the approved supplier, and buy at the negotiated price. Opstream data shows maverick spend accounts for 20–40% of total procurement activity and costs 5–10% more than compliant buying. The savings that centralization claims on paper are real in the contract. They are not real in the P&L.
The Hackett Group identifies process complexity as the number one cause of maverick spend. When the compliant path requires three approvals, a purchase requisition in a system the user accesses twice a year, and a catalog that does not list the specific item the site needs, the non-compliant path — a corporate card and an Amazon order — becomes the rational choice. The central team blames the user for bypassing the process. The user blames the process for being unusable. Both are right.
The responsiveness tax: when speed matters more than price
A plant maintenance team needs a replacement motor by Friday or the line stops. The central procurement team needs five business days to process the requisition, source three quotes, and issue a purchase order. The line stops. The motor costs $4,200 from the approved supplier with a two-week lead time, or $4,800 from a local distributor who can deliver tomorrow. Centralization saves $600 on paper and costs $180,000 in downtime.
Academic research confirms the pattern. A Danish field experiment on centralized procurement found that standardization of products "can hamper responsiveness and adaptation to local demand." A 2025 study of Italian local government centralization found that when required to consolidate, local authorities engaged in three types of strategic behavior to retain autonomy — including choosing the least centralized forms of compliance available. The centralization mandate was technically met. The centralization outcome was not.
The stakeholder alienation problem
Deloitte's 2025 Global CPO Survey identifies siloed ways of working as the top barrier to procurement effectiveness, cited by 57% of organizations. Centralization is supposed to break silos. In practice, it often creates a new one: the central procurement silo, disconnected from the business units it serves, making decisions that look optimal from headquarters and unworkable from the plant floor.
Art of Procurement describes the dynamic precisely: centralization's rigidity "alienates stakeholders" who perceive it as overly bureaucratic. When business units feel procurement decisions are made without their input, they disengage. Disengagement produces maverick spend. Maverick spend erodes the savings centralization was supposed to deliver. The model becomes self-defeating.
Strategy and execution centralized. Business units lose purchasing authority. Local needs filtered through headquarters. Compliance enforced through policy, not usability. Savings assumed because contracts exist. Actual savings eroded by 5–16% maverick leakage.
Strategy centralized. Execution stays with business units. Major contracts centrally negotiated. Local sourcing for categories below threshold. Compliance achieved through ease of use, not policy enforcement. Savings retention 60% higher than average (Hackett Group).
What the data actually shows: hybrid outperforms on every margin metric
KPMG's CPO survey found that no organization operates a pure centralized or decentralized model. All show characteristics of other models. The industry is not moving toward centralization as an end state. It is moving toward center-led structures — strategy and major contracts managed centrally, execution and local sourcing decisions remaining with business units.
Ardent Partners' research on sourcing success found that organizations with center-led procurement "considerably outperform" on spend under management and supply cost reductions. The Hackett Group found top-performing procurement organizations have 60% less savings lost to maverick buying and contract noncompliance compared to average performers. The performance gap is not between centralized and decentralized. It is between rigid and adaptive.
What replaces the myth
Centralization is a tool, not a destination. It produces the most value when applied to categories where leverage matters and local responsiveness does not: indirect spend with standardized specifications, high-volume direct materials with few regional variations, categories where price variance across business units is the primary cost driver.
For categories where local responsiveness, speed, or supplier relationships drive more value than 2–3% of price leverage, decentralization or hybrid models outperform. The decision is not "centralize everything" versus "decentralize everything." It is: "For this specific category, in this specific operating context, does consolidation produce net savings after accounting for the compliance leakage, responsiveness cost, and stakeholder disengagement it creates?" The spreadsheet says yes. The P&L is where you find the real answer.
What this means in practice
- Audit compliance rates on your top 10 centrally negotiated contracts. If usage is below 70%, the negotiated savings are not real — they are theoretical
- For categories below 70% compliance, interview five users who bypass the contract. The process complexity they describe is your savings leakage map
- Segment categories by the responsiveness premium: how much does a one-day delay cost vs. the price savings centralization produces? Categories where the premium exceeds the savings should stay local
- Move from pure centralization to center-led for at least three categories this quarter: keep the contract centrally managed, give business units authority to execute within guardrails
- Track compliance rate as a procurement KPI with the same weight as negotiated savings. A 12% negotiated saving with 50% compliance is a 6% realized saving
What percentage of centralized savings actually reach the P&L?
Between 84% and 95% of negotiated savings reach the P&L in organizations with strong compliance. In organizations with weak compliance, that drops to 50–70%. The gap is maverick spend — purchases that bypass the negotiated contract entirely. Top performers retain 60% more savings than average performers by making the compliant path the easiest path.
Which categories should stay centralized vs. decentralized?
Centralize: indirect spend with standardized specs, high-volume direct materials where price variance across business units is the primary cost driver, and categories where no single business unit has unique requirements. Keep local: categories where lead time is the dominant cost driver, where local supplier relationships and knowledge produce better outcomes than price leverage, and where specifications vary meaningfully by site or region.
How do you measure whether centralization is working?
Track two numbers: negotiated savings (what the contract says) and realized savings (what the P&L shows). If the gap exceeds 5%, centralization is creating leakage faster than it is capturing savings. Also track procurement cycle time — if centralization adds more than 48 hours to the average purchase-to-order cycle, the responsiveness tax is likely exceeding the leverage benefit for time-sensitive categories.
Data sources
- The Hackett Group (via Suplari) — "How to Control Maverick Spend". Accessed July 10, 2026.
- Sievo — "Maverick Spend" (citing SDC Exec and Hackett Group data). Accessed July 10, 2026.
- Varisource — "Cost Reduction Procurement Strategies" (citing Deloitte 2025 CPO Survey and Hackett Group). Accessed July 10, 2026.
- McKinsey & Company — "Contracting for performance: Unlocking additional value". Accessed July 10, 2026.
- Corcentric — "Center-Led Procurement: An Introduction" (citing KPMG and Ardent Partners). Accessed July 10, 2026.
- ScienceDirect — "Centralization responses in Italian local government" (2025). Accessed July 10, 2026.