Why ERP Systems Fail to Map Indirect Procurement Efficiently

Why classic ERP logic fails against the reality of indirect procurement — and how the 1-creditor model reduces complexity rather than perpetuating it

TL;DR
  • ERP systems are designed for standardised, plannable processes and reach structural limits when handling spontaneous, decentralised indirect procurement needs
  • High effort for master data, vendor onboarding and approvals makes small purchases disproportionately complex, causing departments to bypass defined processes
  • Consolidating through a 1-creditor model like Pedlar's significantly reduces system complexity, interfaces and operational effort
read this if
... your ERP system has become too complex and time-consuming for indirect procurement

When indirect procurement reaches its limits in the ERP system, the next step often seems obvious. An additional tool is supposed to close the gap. E-procurement, catalog systems or specialised platforms promise exactly what is missing in daily operations: simpler processes and less effort.

In practice, however, something else frequently happens. The complexity does not disappear — it merely spreads across more systems.

From a system problem to a system mix

Instead of one clear process logic, a grown landscape of different solutions emerges over time. The ERP remains in place, joined by purchasing tools, approval platforms and external systems for individual categories.

This development rarely happens strategically; it happens step by step. One problem is solved without rethinking the overall picture.

Daily work does not get simpler — it gets more fragmented

For users, this means one thing above all: more switching between systems. Different logics depending on the tool. And the recurring question of where which process actually takes place.

Especially in indirect procurement, where many small and spontaneous requirements arise, this creates additional friction in day-to-day business.

Integration becomes the new burden

With every additional system, the effort for coordination and integration grows. Data must be kept in sync, processes must be aligned and responsibilities clearly defined.

What was meant as relief quickly develops into additional organisational overhead in the background.

The actual problem remains unchanged

The central challenge in indirect procurement is not a lack of software, but the way procurement is structured. Many individual requirements are handled, managed and processed one by one.

As long as this underlying logic remains, every new tool will only open another window onto the same complexity.

Departments lose their bearings

The more systems are in use, the harder it becomes for departments to know the right path. Different tools mean different processes and rules. That creates uncertainty rather than clarity.

The consequence is often that procurement happens directly again, outside the intended structures.

Simplification does not come from more systems

Real efficiency does not come from the number of tools in use, but from reducing the complexity behind them. When fewer individual steps are necessary, the need for systems automatically decreases.

A different approach through consolidation

Instead of adding ever more tools, the focus can be placed on the structure itself. Pedlar's 1-creditor model starts exactly here. Indirect procurement is consolidated and handled through one central process instead of being spread across many systems and suppliers.

This reduces interfaces, simplifies workflows and creates clarity for everyone involved.

Conclusion

A growing tool stack in procurement is often a sign that the actual problem has not been solved, only relocated. More systems rarely lead to more simplicity.

What matters is not the next piece of software, but the question of how much complexity in the process is really necessary.

Learn how the 1-creditor model reduces ERP complexity: Get in touch →

Worth reading

Resources
Subscribe to our newsletter
Stay up to date on news and trends in indirect procurement and receive practical insights directly in your inbox every month.
This link will take you to LinkedIn, where you can subscribe to our German-language newsletter.
Pedlar-Logo mit Überschrift: Wie Witzenmann ihr Tailspend-Management vereinfachte, mit einem abstrakten, geschwungenen 3D-Design darunter.
Case Study
Reducing complexity in indirect procurement
Pedlar Logo