Purchasing in 2026: Four decisive factors for success
When I talk to purchasing managers today, I hear the same buzzwords in almost every company: Shortage of skilled workers, cost pressure, transparency, compliance, digitalization. The problems are well known. What is new is something else: Patience has run out.
While requirements are increasing, purchasing departments in many places are still operating within structures that were designed for a different era. This is particularly evident when dealing with large purchasing suites and SAP-centered transformation approaches.
At the same time, the next trend is taking shape: AI in purchasing. But what exactly is AI supposed to accelerate if processes are not fully digitized and the fundamentals are lacking? In 2026, the dividing line does not run between “digital” and “non-digital.” It runs between solutions that make purchasing more flexible – and those that continue to tie it down. This is precisely the core of purchasing's future viability. Here are our four theses on this topic.
Content
- Thesis 1: In 2026, purchasing will not fail because of targets – but because of the logic behind decision-making
- Thesis 2: Large purchasing suites do not solve the purchasing problem – they perpetuate it.
- “Yes, but Ariba...” – why these arguments will no longer hold water in 2026
- Thesis 3: Without consistent processes, AI in purchasing is purely symbolic politics.
- Thesis 4: Future purchasing will not be a system user, but rather an orchestrator
- Conclusion: Digitalization must not be a waiting room.
Thesis 1: In 2026, purchasing will not fail because of targets – but because of the logic behind decision-making
Most purchasing departments know their objectives: Reduce costs, manage risks, create transparency, and deliver value. What is lacking is not the will to change, but the operational decision-making power.
All too often, system decisions are made based on IT, architecture, or standardization logic. The purchasing department is allowed to formulate requirements – but does not make the final decision. As a result, solutions are implemented that are technologically sound but slow down the purchasing process from an organizational perspective.
An example: An energy supplier wants to standardize purchasing and improve it digitally. The goals are clear: More transparency, less manual effort, faster processes. The purchasing department formulates its technical requirements. However, the decision is made by the IT and architecture team: "Ariba fits well with the SAP landscape and the one-platform strategy."
The implementation shows that integration was significantly more complex than expected and is falling short of the hoped-for effects. Additional process steps, limited flexibility, and a high level of coordination with IT and platform operations became necessary in day-to-day purchasing.
The project is considered successful in terms of SAP compliance. The purchasing department is working more slowly than before.
The goal itself was not wrong.
What was wrong was the assumption that proximity to SAP automatically meant easy integration and immediate effectiveness in purchasing.
👉2026 clearly shows that purchasing will only be effective if it shapes its own processes – rather than adopting external objectives.
Thesis 2: Large purchasing suites do not solve the purchasing problem – they perpetuate it.
The aspiration is well known: An integrated suite should reduce complexity, standardize processes, and take purchasing “to a new level.” End-to-end, consistent, standardized – at least that's the promise.
The reality in many organizations is more sobering. After twelve to eighteen months of implementation, purchasing departments often work with new interfaces but old processes – and with added value that is difficult to grasp in everyday life.
I encounter this repeatedly in conversations: Large purchasing suites are introduced with comprehensive functionality, often accompanied by specialized service providers, long project durations, and high coordination costs. The introduction is considered successful, and the system is productive.
However, after implementation, many organizations only use some of the available functions. The complexity of the suite remain – the benefits do not scale accordingly.
The problem is not a lack of functionality.
The problem is that complexity is growing faster than usability.
Operational expenses are rising, dependence on the system is growing, and flexibility is declining. Large suites are not drivers of innovation, but rather reinforcers of structure. They perpetuate existing ways of working instead of challenging them.
👉In 2026, it is no longer the completeness of a system that counts, but the adaptability of purchasing.
“Yes, but Ariba...” – why these arguments will no longer hold water in 2026
I regularly encounter these objections in discussions about the digitalization of purchasing. They are understandable, but they lead in the wrong direction.
☝️"Ariba is the SAP standard, after all."
Yes. But a common manufacturer is no substitute for ease of use.
In practice, this results in additional coordination, lengthy integrations, and responsibilities—exactly what purchasing wants to avoid: organizational friction.
▶️ The decisive factor is not the product name, but how easy it is to use in everyday SAP purchasing.
☝️"With a suite like Ariba, we cover everything end-to-end."
On paper. In reality, large functionalities are rarely used to their full extent. Introduction, training, and acceptance limit the effect—many processes revert to exceptions.
▶️ The relevant question is not what a system can do, but what is actually used in day-to-day business.
☝️"Without the right suite, we lose governance."
Governance does not arise from a wealth of functions, but rather from clear processes, clean ERP integration, and transparent decisions. Complex suites often shift governance to projects, special rules, and escalations.
▶️ More systems do not automatically mean more control—often just more effort.
Recommended reading for further information:
Those who are wondering why many purchasing organizations are increasingly struggling with SAP Ariba – and what realistic options are available today – will find two in-depth assessments on this topic:
In a 👉 reality check on SAP Ariba Sourcing , wehighlight where expectations and everyday operational reality diverge. In a second article, we show how, using the example of 👉 FUTURA as an SAP-compatible alternative , we highlight effectiveness, integration, and organizational relief.
Thesis 3: Without consistent processes, AI in purchasing is purely symbolic politics.
Few topics are currently debated as intensely in purchasing as artificial intelligence. Forecasts, chatbots, automated analyses –many things seem possible, and many sound like the next big leap in efficiency.
But the crucial question is rarely asked: What should AI actually be based on?
In our projects, we encounter purchasing processes that are not fully digitized. Data flows inconsistently, and media breaks are commonplace. AI cannot fix this – it only amplifies it.
Here is another example from our experience: A company in the chemical industry uses AI in purchasing to identify potential savings and recognize risks at an early stage. Economic pressure is high, and quick results are expected. AI provides valid information and clear recommendations for action.
However, the findings continue to be processed by means of Excel lists, e-mails, and meetings. Decisions must be prepared manually, and measures must be tracked laboriously.
The AI knew more than the organization could process. The purchasing department recognized what needed to be done – but couldn't implement it systematically.
👉In 2026, AI will only create real added value in purchasing where processes are consistent, data is clean, and responsibilities are clear. Wherever these fundamentals are lacking, AI is not a lever and remains a reporting upgrade labeled “innovation.”
The change of perspective behind our FUTURA solution
We have summarized here why we consistently approach digitalization in purchasing with FUTURA from the perspective of the working reality of SAP purchasing
Thesis 4: Future purchasing will not be a system user, but rather an orchestrator
Purchasing in 2026 will draw its strength not from a central monolith, but from the ability to intelligently network processes. It is not a matter of squeezing all processes into a single system, but of connecting specialized solutions in such a way that they work together seamlessly in daily operations.
This fundamentally shifts the focus.
The focus is no longer on systems, but on effect:
- Systems must follow purchasing – not the other way around.
- Digitization should reduce the workload, not increase it.
- Technology must expedite decisions, not delay them.
Behind this change lies a clear organizational principle that will prevail: Orchestrating rather than centralizing. The purchasing department of the future will not manage individual tools, but end-to-end processes. It will combine specialized components where they make sense, retain decision-making authority, and ensure flow, prioritization, and impact in everyday business.
Technological development also follows this principle. Concepts such as Agentic AI do not aim for complete autonomy or another centralized system, but rather the coordinated execution of tasks along clearly defined processes. Agents take on subtasks, work with guidelines and escalations – responsibility remains with humans and the organization.
In purchasing, on the other hand, attempts are often made to establish control via a central suite. Out of concern for losing control, complexity is bundled – and this is precisely what causes a loss of flexibility.
👉Therefore, in 2026, it does not matter how many tools a purchasing department has introduced. What matters is whether it is able to orchestrate processes – and thus remain agile.
Conclusion: Digitalization must not be a waiting room.
Purchasing departments in 2026 do not have a problem with insight. They know what is expected of them – and they also know what is holding them back today. What is missing are decisions that are consistently oriented toward effect rather than historical system logic or manufacturer narratives.
This is particularly evident in the use of SAP Ariba. Ariba is a product from a different era: Developed for a highly centralized, suite-oriented approach long before modularity and rapid iteration became the norm. Many organizations still work with it today – not out of conviction, but due to structural dependence.
The announcement of Ariba Next-Gen further exacerbates this situation, as neither its design nor market readiness are clearly foreseeable. For many purchasing organizations, this creates a strategically delicate interim phase: The existing Ariba increasingly appears to be a discontinued model, while the new Ariba does not yet offer a solid foundation for today's decisions. I recently addressed this uncertainty on LinkedIn (posts on Ariba,NextGen, or SAP strategy).
Purchasing in 2026 cannot afford to wait for unclear product promises or invest further years in transitional solutions that tie up operations instead of relieving them.
The change in perspective is clear:
What matters is not which system has been announced or when the next generation will arrive, but rather what ensures purchasing's ability to act today – and which solutions make it more flexible and integrable in everyday SAP use.
The future of purchasing will not be decided by roadmaps or announcements. Rather, it will depend on whether purchasing has the courage to break free from old dependencies – and once again view technology as a means to an end.
Feel free to discuss these ideas with me on LinkedIn!
How purchasing processes become effective in everyday SAP use
An overview of our solutions and how FUTURA supports purchasing with S/4HANA.