Low-value purchases need a lighter process, not no process. Set a clear value threshold, give each kind of small purchase one fast route, and let approvals run in the system people already use. Then the quick way to buy is also the controlled way, and nobody has a reason to go around it.
Why do small purchases cause big problems?
Each one is trivial. Together they produce most of procurement's transactions and very little of its value.
- Processing cost. A request, an approval, a quote or two, a purchase order, a receipt and an invoice match cost the same whether the item is worth AED 200 or AED 200,000.
- Requisitions pile up. Small requests queue behind big ones, requesters wait, and the queue becomes the reason people stop asking.
- Split orders. When the process is slow, orders get split to stay under an approval limit.
- One-time vendors. Every small purchase from a new supplier adds a vendor record, checks and a payment run.
- No data. Card spend and free-text purchase orders cannot be analysed, so nobody can say what is being bought or at what price.
What counts as a low-value purchase?
Whatever you decide, as long as you decide it. Set a value ceiling per purchase order below which the light process applies. In the tail spend programmes we run, the ceiling is set per client, at AED 50,000 or AED 200,000 per purchase order, covering any category, indirect or direct. Above it, purchases go to normal sourcing.
Which route should each small purchase take?
- Catalogue. For recurring, standard items. Prices are agreed in advance, and ordering takes minutes.
- Quick quote or buying desk. For one-off, defined needs. The request is competed by default without a procurement officer chasing quotes.
- Corporate card with category controls. For very small, urgent, ad hoc purchases where processing anything else would cost more than the item.
- Framework call-off. For services bought repeatedly under an existing agreement.
Tail spend management platforms compared covers the strengths and blind spots of each route.
How should approvals work for small purchases?
- Tier them by value. The approval chain for a AED 300 item should not look like the one for a AED 300,000 contract.
- Approve catalogue items within budget automatically where the price and the supplier are already agreed.
- Keep approvals in your existing system. A punchout connection returns the basket to your ERP or procurement suite, where it goes through your normal approval chain before the purchase order is issued.
- Never add a step to save a step. If the new route has more approvals than the old one, people will not use it.
How do you stop requisitions piling up?
- Let people ask in plain language. "Two ergonomic chairs for the Riyadh office by next week" is a complete request; a requisition form should not need a procurement expert.
- Publish turnaround times. In one of our Gulf programmes, quick quotes run to a three working day SLA.
- Show requesters where their request is. Most chasing is uncertainty, not impatience.
What about unplanned and urgent purchases?
They need the same route, faster, rather than a different one. Our quick guide to managing unplanned purchases covers the rules that keep urgent buying controlled.
How does METIS handle low-value purchasing?
METIS takes the request in plain English, buys catalogue items directly, and sends everything else to AI agents that find suppliers, compete and negotiate the quotes, then return the result to your approval chain. Request to approved purchase order takes around 48 hours instead of two to three weeks. Watch it in 20 seconds.