Spot Buy in Procurement: What It Is and How to Control It

A spot buy is a one-off, unplanned purchase of something no contract or catalog covers, bought quickly from whoever can deliver, at whatever the price happens to be that day. The defining features are all absences: no pre-negotiated price, no incumbent supplier, usually no sourcing event. A pump fails on a Friday, and somebody buys a replacement on Monday from a supplier nobody has used before.

Spot buys are not a failure of procurement. They are a normal part of running a business, and any plan to eliminate them will fail. The goal is to make them fast, visible, and compliant, because the ones that go dark are the ones that cost you.

Spot buy, tail spend, maverick spend: three different things

These three get used interchangeably and they are not interchangeable. They measure completely different axes, and a single purchase can be one, two, or all three at once.

The short version: a spot buy means no contract existed. Maverick spend means a contract existed and somebody ignored it. Tail spend means it is small and there are thousands of them.

The distinction that matters most in practice is the first two. A spot buy is not automatically maverick spend. If nothing in your catalog covers the item, the buyer raises a PO, and the approval is obtained, that purchase is fully compliant. It becomes maverick spend only when it bypasses a contract that already covered the item, or skips the PO and approval process entirely. Getting this wrong produces a frightening compliance number that nobody can act on, because half of it describes purchases that were fine.

The tail spend confusion runs the other way. A spot buy usually lands in the tail, but not always. An emergency turbine part bought in a hurry for six figures is a spot buy and is nowhere near the tail. And plenty of tail spend is contracted, recurring, and entirely routine. If you want the full picture of the small-supplier problem, that is tail spend management, and the compliance problem is covered in maverick spend.

Why spot buys cost more than they look like they should

The unit price is only part of it. Six mechanisms drive the real cost, and most of them never show up on the invoice.

• There is no price benchmark. Nobody knows what the item should cost, so there is no baseline to compute a variance against and no basis on which to push back. You find out you overpaid, if ever, months later.
• Urgency destroys your leverage. When the need-by date is shorter than your sourcing cycle, you are buying from a single quote, paying premium freight, and accepting expedite fees. The supplier knows this.
• A one-time supplier gives you nothing. No volume leverage, worse payment terms, onboarding cost, and a counterparty nobody has screened for risk, insurance, or sanctions exposure.
• Transaction cost swamps small orders. Raising, approving, and processing a purchase order costs roughly the same whether the order is $200 or $200,000. On a small spot buy, the cost of the process can rival the cost of the item.
• The same item gets bought five times. Five sites, five suppliers, five prices, one quarter. This is invisible unless somebody rolls the data up at item level, and almost nobody does.
• They corrupt your metrics. Spot buys inflate the emergency purchase ratio, depress spend under management and contract compliance, and are usually the single largest source of unfavorable purchase price variance.

The 40 percent statistic you keep seeing is not real

Search this topic and you will meet a claim that spot buys make up close to 40 percent of an organization's spend. It appears on vendor page after vendor page, hedged with phrases like estimates suggest. None of them cites a primary source. They do not even agree with each other on what the number refers to, with some saying direct spend and others saying indirect. It is a circular citation: everyone is quoting everyone else.

Do not build a business case on it, and be wary of any page that does. The honest position is that the share of spot buys varies enormously by industry and by how well the contract coverage is built, and the only number that matters is the one from your own data. Which brings us to the problem of getting your own data.

What is a spot buy PO, and why it is the whole game

The purchase order is the only structured record a spot buy ever leaves behind. Contracted spend already lives somewhere: in the catalog, in the contract, in the pricing agreement. A spot buy exists nowhere until a PO records it. The item, the quantity, the unit price, the unit of measure, the supplier, the need-by date, the account it is coded to. If that PO is not raised, the purchase surfaces as an invoice or a card charge, and it is unanalyzable forever.

Without a PO you get no spend visibility, no accrual at month end, no three-way match, no price baseline for the next time you buy the same thing, and by definition the purchase is maverick. With a PO, an uncontrolled event becomes a data point, and once you have enough data points you can see the item that got bought three times and turn it into a contract. A spot buy that happens three times is not a spot buy. It is a sourcing failure with a friendly name.

There is a practical wrinkle here that catches teams out. Spot buys usually arrive as a supplier quote or a pro forma, as a PDF, under time pressure, and somebody retypes it into a PO in a hurry. That is exactly where the wrong quantity, the wrong unit of measure, and the wrong unit price enter your data, which then flow into every metric downstream.

How mature teams handle spot buys

Not by banning them. Banning spot buys converts them into maverick spend and expense claims, which is strictly worse, because at least a spot buy with a PO leaves a record. What good teams do instead:

1. Give spot buys their own channel. A simple intake form, a value threshold, a light approval path, and a mandatory PO. Make the compliant route the fast route, or people will route around it.
2. Speed up quoting above a threshold. Three quotes in hours rather than a sourcing event in weeks. Above a certain value the time is worth spending, below it the process costs more than it saves.
3. Capture the lines, not just the total. A spot buy recorded as a $4,200 total from a supplier tells you nothing later. Recorded as 60 units at $70 with a part number, it is a negotiating position.
4. Run item-level rollups quarterly. Repeated spot buys of the same item across sites are the highest-return sourcing opportunity most companies never look at, because the analysis requires line-item data nobody has.
5. Measure three things: spot buys as a share of spend, the price variance on spot buys versus contracted buys, and the repeat-item rate. The third one is where the money is.

Is a spot buy a strategic activity?

Individually, no. A single spot buy is transactional by nature: reactive, time-boxed, and low leverage, and treating each one as a sourcing project would bankrupt the function in process cost. In aggregate, yes, and this is the part that gets missed. The pattern in your spot buys is strategic information. It tells you exactly where your contract coverage has holes, which categories generate emergencies, and which items you are repeatedly buying at whatever price the market offers that week. Handling one spot buy is administration. Reading a year of them is strategy.

Spot buying vs strategic sourcing

Strategic sourcing is planned, analytical, and forward-looking: you understand the category, you run a competitive event, you negotiate, you sign a contract, and the price is known before the need arises. Spot buying is the opposite on every axis: unplanned, reactive, and the price is discovered after the need arises. That last clause is the entire reason spot buys cost more. Everything else follows from it.

Both are legitimate. The mistake is not having spot buys, it is letting them stay invisible, so that the same emergency recurs every year and never becomes a contract.

Getting the data out of the documents

Every recommendation above depends on having item-level data for purchases that, by their nature, happened outside your systems. The quote came by email. The confirmation came as a PDF. The PO was raised in a hurry, if it was raised at all. Spot buys often end up paid on a card too, which is why a decent expense management system catches some of what the PO process misses, though it will only ever show you the total and not the lines.

For the documents themselves, upload the purchase order or the supplier confirmation to our AI purchase order software and it returns the PO number, supplier, dates, terms, and every line item with quantity, unit of measure, and unit price as Excel, CSV, JSON, or an API response in about ten seconds. No template per supplier, which matters here because a spot buy is by definition from a supplier you have not seen before. A quarter of accumulated documents goes through bulk purchase order upload in one batch, which is the practical way to run the item-level rollup that finds your repeat spot buys.

To be plain about the scope: it captures the data from the documents. It does not raise purchase orders, route approvals, enforce a policy, or run a three-way match.

Frequently asked questions

What is a spot buy in procurement?

A spot buy is a one-off purchase of a good or service that no existing contract or catalog covers, made quickly from whichever supplier can meet the need, at the market price on the day. It is reactive and non-recurring, and it typically skips the competitive sourcing process because there is no time for one.

What is the difference between a spot buy and maverick spend?

A spot buy means no contract existed for what you needed. Maverick spend means a contract or catalog did exist and the buyer went around it. A spot buy is compliant as long as the approved process is followed and a PO is raised. It only becomes maverick spend when it bypasses an available contract or skips the PO entirely.

Is a spot buy the same as tail spend?

No. Tail spend describes where spend sits in the distribution, the many small suppliers that add up to a modest share of value. A spot buy describes how the purchase was made. Most spot buys land in the tail, but a large emergency purchase can be a spot buy and be nowhere near it, and plenty of tail spend is contracted and routine.

Do you need a purchase order for a spot buy?

Yes, and it matters more here than anywhere else. Contracted purchases are already recorded in the contract or catalog. A spot buy exists in no system until a PO captures the item, quantity, unit price, supplier, and delivery date. Without one there is no accrual, no invoice match, no price baseline for next time, and the spend is invisible to every report you run.

How do you reduce spot buys?

Not by banning them, which just pushes the spend onto cards and expense claims. Give spot buys a fast compliant channel with a mandatory PO, then analyze them at item level every quarter. Any item that shows up repeatedly is a contract waiting to be negotiated, and converting repeat spot buys into contracted spend is where the savings actually are.

What is a spot purchase order?

It is a purchase order raised for a one-off buy with no contract or catalog behind it. Unlike a catalog release or a blanket order call-off, the price on it was discovered rather than pre-negotiated, which is why it is worth capturing accurately: it is the only price record you will have when the same need comes round again.