Most procurement disasters don’t start with a bad vendor. They start three steps earlier, with a request nobody defined clearly.
By the time the problem surfaces, the contract’s signed and the budget’s spent. Now you’re stuck managing a relationship that never should have happened.
The frustrating part? The procurement process steps are well understood. Companies still trip over the same spots, again and again. Let’s walk through where it breaks down and how to keep it from costing you.
The Steps Most Companies Actually Follow
Before we get into the mistakes, here’s the basic shape of a procurement workflow. Most organizations move through some version of these stages:
- Identify the need: Someone figures out what’s required and writes it up as a requisition.
- Get approval: The request goes through an approval process before anyone spends money.
- Source and evaluate vendors: You find suppliers, compare them, and run a vendor selection process.
- Negotiate and issue the PO: Terms get agreed and this is where contract management begins, ensuring terms are tracked long after the PO goes out.
- Receive and review: Goods or services arrive, and someone confirms they match what was ordered.
- Pay and manage the relationship: Invoices get settled, and ongoing vendor management kicks in.
Clean on paper. Messy in practice. The procurement lifecycle rarely runs as smoothly as the diagram suggests, and the gaps are where money leaks out.
Step One Is Where the Damage Usually Begins
Vague requirements sink more projects than bad vendors ever do.
When the initial need isn’t defined clearly, everything downstream wobbles. You source the wrong solution. You compare suppliers against fuzzy criteria. You end up negotiating for something that doesn’t quite fit.
Here’s the thing. A request like “we need new laptops” tells you almost nothing. How many? What specs? What budget? What timeline? Skip those answers and you’re setting up the whole chain to fail.
Spend the extra hour up front. It saves you weeks later.
Why Approvals Become a Bottleneck
Approval should protect the business. Too often it just slows everything to a crawl.
When nobody knows who signs off on what, requests sit in limbo. Teams get frustrated. And that frustration breeds the single most expensive habit in procurement: people going around the process entirely.
That’s maverick spending, and it’s a quiet budget killer. Someone needs software today, can’t wait for sign-off, and just buys it on a company card. No negotiation, no vendor vetting, no record.
A clear approval process with named owners fixes most of this. People follow the path when the path actually works.
The Vendor Evaluation Trap
Picking a vendor on price alone is the mistake almost everyone makes at least once.
The cheapest quote wins the deal, then costs you triple in downtime, missed deadlines, and support headaches. Lowest price and lowest total cost are not the same number.
A stronger vendor selection process looks at more than one column. Weigh these together:
- Reliability and track record with companies like yours
- Security and compliance posture, especially for anything touching your data
- Support quality and response times
- Total cost over the contract, not just the sticker price
- Cultural and operational fit with your team
This matters even more in technical buys. A solid IT procurement service page weighs security and integration risk, not just the invoice.
The Visibility Problem Nobody Talks About
You can’t fix what you can’t see. Most procurement bottlenecks hide in plain sight because nobody has a full view of the workflow.
Where is each request right now? Who’s it waiting on? How much have you actually committed across all your vendors this quarter? When those answers live in scattered inboxes and spreadsheets, things slip.
Lack of procurement visibility leads straight to vendor onboarding delays, duplicate purchases, and compliance gaps. Centralize the view and the process starts running itself.
If you’re still untangling the basics, this explainer on Procurement vs Purchasing clears up a distinction that trips up a lot of teams.
Who Actually Owns This Mess
Ask five people who own the procurement process and you’ll get five answers. That’s the real problem.
When ownership is fuzzy, accountability disappears. Requirements go undefined, vendors go unmanaged, and savings opportunities go unnoticed. Procurement stakeholder alignment isn’t a nice-to-have. It’s the thing that makes every other step work.
Name an owner. Define responsibilities. Then the workflow has someone steering it.
Frequently Asked Questions
What is the basic procurement process?
It’s the series of steps a business follows to buy goods or services, from identifying a need to paying the vendor. The core stages are need identification, approval, vendor sourcing, negotiation, purchase order, receipt, and payment. Each step feeds the next, so a weak link early on causes problems down the line.
What are the 4 types of procurement?
The four common types are direct procurement, indirect procurement, goods procurement, and services procurement. Direct covers materials tied to your product, indirect covers operational buys like office supplies or software, and the other two split purchases by whether you’re buying physical goods or services.
Which comes first, PO or PR?
The purchase requisition (PR) comes first. It’s the internal request to buy something, which then needs approval. Once approved, a purchase order (PO) is issued to the vendor as the official order. So the flow is requisition to purchase order, not the other way around.
What is the 80/20 rule in procurement?
It’s the idea that roughly 80% of your procurement value comes from about 20% of your suppliers or spend categories. Spotting that critical 20% lets you focus your time, negotiation effort, and risk management where it actually moves the needle.
What is a KPI in procurement?
A KPI, or key performance indicator, is a metric you track to measure how well procurement is performing. Common ones include cost savings, purchase order cycle time, supplier defect rates, and compliance with approved vendors. Good KPIs turn a vague “are we doing well” into something you can actually answer.
Procurement isn’t hard because the steps are complicated but it does require a strategic procurement mindset to avoid costly surprises. It’s hard because the small failures, a vague request here, a price-only decision there, compound quietly until they’re expensive. Tighten the weak spots, give the process an owner, and most of those costly surprises simply stop happening.