Manufacturing
MRO (Maintenance, Repair and Operations)
MRO covers maintenance, repair, and operations spend — the parts, consumables, and services that keep facilities and equipment running without becoming part of a product. MRO is characterised by high transaction volume, low unit values, and a long tail of suppliers.
Also known as: maintenance repair and operations, MRO spend
The economics of the tail
MRO is where transaction cost overtakes unit cost. An order worth $180 can consume the same buyer attention as one worth $180,000: raise it, send it, chase acknowledgement, chase delivery, resolve the invoice mismatch.
Because the value per line is low, MRO rarely justifies the attention it consumes — so it gets triaged down, which is precisely how unplanned downtime happens when a needed part turns out not to be on site.
Why portals rarely solve MRO
The obvious fix is to move MRO suppliers onto a portal or catalogue. It works for the largest few and stalls for the rest, because onboarding cost per supplier is roughly constant while the spend per supplier is tiny.
Any approach to the MRO tail has to have near-zero marginal cost per supplier, or the arithmetic never closes.
How Evolinq handles it
Evolinq's marginal cost per supplier is effectively zero, since suppliers need no account or onboarding — which is what makes automating the MRO tail viable.
Frequently asked questions
What does MRO stand for in procurement?
MRO stands for Maintenance, Repair and Operations. It covers the parts, consumables, and services needed to keep equipment and facilities running — as distinct from direct materials, which become part of the finished product.
Why is MRO procurement hard to automate?
Because the value per transaction is low while the coordination effort per transaction is not. Portal and catalogue approaches carry a roughly fixed onboarding cost per supplier, which cannot be justified across a long tail of suppliers each holding a handful of lines.