Processing Small Orders Under €500 Correctly
Orders under €500 often cost more to process than the goods themselves. Which approaches actually work in practice — and where each one reaches its limit.
Process costs are incurred per order, not per euro of goods value — for orders under €500 they often reach the value of the goods itself.- De minimis thresholds, batch orders, and framework agreements each solve only one part of the process, not the recurring supplier onboarding.
- Under the Single Creditor Model, a single service provider is enough as the creditor.
Orders under €500 often cost more to process than the goods themselves. The reason isn't the price. It's the process, which stays equally involved for every order — regardless of order value.
Procurement sets up a new supplier, approves the order, and receives the goods before the invoice is reviewed. Four steps, always the same effort: this applies to an €80 order just as much as an €8,000 order.
This weighs especially heavily on small amounts, because whether the order turns out to be a pencil or a spare part changes nothing about the effort involved.
Why Small Orders Under €500 Are So Expensive
Process costs are incurred per order. Not per euro of goods value, but per pass-through: procurement checks the master data before setting up the supplier in the system.
Setup is followed by approval, often through multiple levels depending on procurement policy, before accounting checks the invoice against the order and goods receipt after delivery and pays it.
According to Pedlar, small one-off requirements incur ≈€500 in process costs per order at companies. A small order therefore often costs as much to process as the goods themselves.
The effect grows larger because small orders rarely recur. A supplier gets set up for a single spare-part order. After that, the record often sits unused, and the work of setting it up never pays off a second time.
Common Approaches and Their Limits
Four approaches come up again and again in practice, and each works at a different point in the process. Three of them hit their own limit with one-off requirements.
De minimis thresholds simplify approval below a set value. Instead of multiple levels, a single approval is then enough, which saves time. The supplier still has to be set up from scratch. The invoice still has to be reviewed — the most expensive steps in the process remain.
Batch orders bundle several requirements into a fixed date, for example once a week. This reduces the number of order transactions. But it only works if the requirement can wait. With a broken spare part or a short-notice trade-show requirement, that isn't possible, and here batching gets in the way of the order's purpose.
Framework agreements fix terms with one set supplier — this works for requirements that recur, but a one-off requirement has no fixed supplier. The right provider is different every time. This is exactly where a framework agreement doesn't apply.
No one-time creditors: one creditor for all one-off requirements, no more supplier onboarding. This works regardless of how many providers the order actually goes to. Of the four approaches, this is the only one that also holds up with changing suppliers.
The Structural Limit: Where Process Optimization Ends
De minimis thresholds, batch orders, and framework agreements optimize the process around a single order. But every small order still brings its own supplier, its own creditor setup, and its own invoice, so a baseline of process costs remains. None of these measures removes it. At most, they shift it from one department to the next.
The lever isn't fewer orders. A solution only becomes effective once it addresses the most expensive point: the ever-recurring setup of new suppliers for requirements that never repeat.
Which Solution Actually Simplifies Processing One-Off Purchases Under €500?
Under the Single Creditor Model, a single service provider is enough as the creditor. It gets set up once in the ERP system.
Every further one-off order under €500 then goes to this one creditor as a familiar order. Which provider actually fulfills it doesn't matter.
Pedlar operates this model as a managed service. This is how such an order works with Pedlar:
- You determine the requirement yourself and send Pedlar the order with a product link or an attached quote.
- From there, Pedlar handles the processing, from ordering with the provider through payment and delivery coordination to returns.
- Each order comes with one invoice from Pedlar.
The order reaches Pedlar by email or through the Pedlar Punchout in SAP Ariba and Coupa, that is, directly from the procurement system your departments already order in.
Procurement saves itself the supplier onboarding. Accounts payable saves itself the individual review of changing invoice issuers for every small order. As a result, Pedlar customers achieve up to 85% lower process costs.
The Witzenmann example shows what this looks like in practice.
How this connects to C-parts consolidation is covered in the article on bundling one-off requirements and C-parts; the practical guide to administrative costs for occasional purchases provides an overview of all the levers.
Find out how the Single Creditor Model simplifies your small orders under €500: Schedule a call →
