What it means
Procurement teams often spend their time on the largest contracts, while smaller orders across many suppliers form a long tail that is harder to see and manage. Each purchase may be modest, but the combined processing time and uncontrolled supplier exposure can matter, and that is tail spend.
CIPS discusses technology for handling fragmented purchasing and Roland Berger examines opportunities in tail spend, but these are strategy references, not proof that every company has the same 80:20 split. Define the tail using actual transactions, suppliers and management effort, and state the rule before measuring or comparing periods.
One company might classify suppliers below a yearly threshold as tail spend, another may use the bottom portion of total spend after ranking categories, and a third may focus on purchases without a contract. These definitions identify different problems.
Start by bringing purchasing data together from cards, expense claims, local branches and accounts payable, then clean duplicate supplier names and group items into categories. A report of "small suppliers" may miss a large vendor receiving hundreds of tiny off-contract transactions, and processing a $100 purchase order may consume nearly as much administrative effort as a $10,000 order.
If ten offices each buy the same consumable from different vendors, a catalogue or framework agreement could reduce effort and improve terms, although one national contract may not serve remote sites well. Guided buying can make the approved route easier, since staff should be able to find common items, see prices and use an appropriate payment method.
If a required procurement process takes longer than the operational need, buyers will seek workarounds, so tail-spend control should remove friction rather than merely impose forms. A procurement card may suit low-risk, low-value purchases with limits, allowed categories, approval thresholds and reconciliation evidence, but it is not permission to buy sensitive software or bypass supplier checks.
A marketplace or aggregator can consolidate many small suppliers through one interface, which improves visibility but may add fees or hide the underlying seller. Check product quality, data access and contract terms, because a single platform is not the same as one low-risk supplier.
Measure process cost as well as purchase value, since if staff spend hours finding quotes and approving a $50 item, the internal effort can exceed the invoice. For illustration, suppose total addressable purchases are $10 million and transactions classified as tail spend total $1.8 million, so the tail share is 18%.
That number does not tell you how many suppliers or invoices are involved, and a small contract can still give a vendor access to customer data or a production system, so segment by risk and not just spend. Track realised outcomes against the pre-change baseline, including adoption, total landed cost, exception rate and user feedback, because a catalogue discount is not a benefit if staff keep using old vendors.
In practice
Real-world examples.
Example
Ten offices buy the same consumable from ten different small suppliers at ten different prices. Procurement spots the pattern after merging card, expense and invoice data. A single catalogue with local delivery cuts both the price and the number of approvals needed.
Example
A low-value software subscription receives extra review because it can access customer data. The annual fee is small, but a breach could be costly and hard to reverse. The supplier goes through the same onboarding as a major vendor, whatever its invoice value.
Example
An approved catalogue reduces processing time for routine purchases such as stationery and cleaning supplies. Staff see prices and delivery times before ordering, and managers approve only exceptions. After six months, procurement compares adoption and process time with the pre-change baseline.
Formula
Calculation
Tail share = Spend in the defined tail / Total addressable spend x 100.
Worked example: tail spend of $1,800,000 divided by total addressable spend of $10,000,000 gives 0.18, and 0.18 x 100 = 18%. Also report supplier and transaction counts, because the boundary is company-specific and the percentage alone says nothing about administrative burden.Case study
Seen in the real world.
This illustrative and entirely fictional case follows Desert Workspace, an invented firm with many small stationery purchases. It finds repeated orders across sites and offers an approved catalogue with local delivery options. Staff keep a documented emergency route, and procurement tracks actual adoption.
The finance team also reports the number of invoices per supplier, so that the administrative burden is visible alongside the spend. Suppliers with access to systems or customer data are reviewed separately, whatever their annual value. The case does not assume every small vendor should be removed.
Watch out
Common mistakes.
- Claiming tail spend is always exactly 20% of purchases.
- Using invoice value alone to dismiss a small but sensitive supplier risk.
- Announcing savings from a catalogue before staff actually use it.
Questions
People also ask.
What is tail spend?
Fragmented small purchases or suppliers that receive less attention than major contracts.
Why does it matter?
Many small transactions can add process cost and hide supplier or compliance risks.
How is it managed?
Define and analyse it, simplify routine buying, and apply risk-based controls.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%