The Sourcing Process in Procurement: Stages & Guide

Every supplier your organisation relies on was chosen through a process, whether that process was deliberate or accidental. Sourcing is where that choice is made well or badly, and it shapes cost, quality and risk long after the paperwork is filed. This guide maps the sourcing process in procurement one stage at a time, from the first sign of a need to a supplier live and delivering, with a described flowchart, a stage-by-stage table, the metrics that matter, the bottlenecks that slow teams down, and how automation compresses the whole cycle.

What is the sourcing process in procurement?

The sourcing process is the structured sequence an organisation follows to find, assess and secure the suppliers behind a given need. It is the part of procurement concerned with choice: which market to buy from, which suppliers to approach, how to compare them fairly and how to reach terms that hold up over the life of the contract. Where day-to-day purchasing repeats the same transactions against suppliers already in place, sourcing is the periodic, more strategic work that decides who those suppliers should be in the first place.

It helps to place sourcing inside the wider flow. The full procurement process runs from need to payment and record; sourcing is the front half of that journey, ending at a signed contract and a supplier ready to deliver. Done as a repeatable discipline rather than a scramble each time something is needed, it becomes strategic sourcing, where every cycle draws on the data and relationships built by the last. That shift, from reactive buying to deliberate supplier selection, is where most of the value in procurement is actually created.

The sourcing process flowchart at a glance

Before we examine each stage in detail, it helps to see the whole route. Picture it as a text flowchart, reading left to right, with each box passing its output to the next:

Identify need -> Analyse the market -> Discover suppliers -> Issue RFx (RFI, RFQ or RFP) -> Evaluate responses -> Negotiate terms -> Award and contract -> Onboard the supplier.

Two features stand out when the flow is laid out this way. The first is that the early stages narrow while the later ones deepen: market analysis and discovery widen the field to make sure nothing good is missed, then RFx, evaluation and negotiation progressively narrow it to a single award. The second is that the process is a loop, not a straight line. The performance data gathered once a supplier is onboarded feeds the market analysis for the next cycle, so a well-run sourcing function gets sharper each time round. Where the boxes are joined by a system rather than by email and spreadsheets, the output of one stage becomes the input of the next automatically, which is where cycle time collapses.

The eight stages, from need to onboarding

Here is the full sequence in one place, with the purpose of each stage and the artefact it produces. Use it as a reference map for the sections that follow.

Smaller, lower-risk buys often collapse several of these stages: a repeat purchase from a known market may skip discovery and run a quick RFQ against a handful of familiar names. Larger or riskier categories run the full sequence, sometimes twice, as an early RFI narrows the field before a formal RFP. The art is matching the depth of the process to the value and risk of the need, rather than forcing every requirement down the same long road.

Inside each stage of the process

With the map in view, it is worth walking the route once more, this time focusing on what actually happens at each step and why it matters.

Need identification starts the cycle. A team recognises a gap and defines the requirement in terms of the outcome it needs, not a brand it happens to remember, which keeps the later sourcing genuinely competitive. Market analysis then studies the supply landscape: who the credible suppliers are, how pricing behaves, where the supply risks sit and whether the market favours the buyer or the seller. This is the homework that stops a team walking into a negotiation blind. Supplier discovery turns that view into names, building a longlist of candidates and pre-qualifying them on capability, financial health and compliance before anyone is invited to bid.

RFx is where the field is formally engaged. Depending on the need, that means a request for information to learn, a request for quotation to price a defined item, or a request for proposal to compare solutions to a more open problem. Evaluation scores the responses against criteria agreed in advance, keeping the decision objective. Negotiation settles price, payment terms, warranties and service levels, ideally on total value rather than headline price alone. Award and contract confirms the winner and captures the deal in a signed agreement, often the point where a purchase order framework is set up so day-to-day buying can begin. Finally, onboarding sets the supplier up in your systems, verifies their details and connects them to your ordering flow, at which point the relationship moves into the domain of supplier relationship management.

The metrics that tell you it is working

A process you cannot measure is one you cannot improve. Sourcing has a handful of KPIs that, watched together, tell you whether the discipline is healthy or quietly slipping.

• Sourcing cycle time. The elapsed time from documented need to signed contract; the single clearest measure of how responsive your function is.
• Cost savings realised. Not just the savings negotiated on paper, but the portion that actually reaches the budget once contracts are used as intended.
• Supplier response rate. The share of invited suppliers who return a usable RFx response, a signal of how attractive and how clear your requests are.
• Spend under contract. The proportion of category spend covered by a sourced, negotiated agreement rather than leaking to ad hoc purchases.
• Time to onboard. How long it takes an awarded supplier to become active and ready to deliver, which often hides more delay than teams expect.

None of these numbers means much in isolation. Read together and tracked over time, they show whether the process is getting faster, cheaper and more controlled, or whether effort in one stage is simply pushing delay into the next. That trend line, more than any single figure, is what turns sourcing from a series of tasks into a measurable discipline.

Common bottlenecks, and how to clear them

Even a well-designed sourcing process develops predictable weak points. Knowing where they appear makes them far easier to prevent. The most common is the approval gate: an RFx that cannot go out, or a contract that cannot be signed, because it is waiting in one person's inbox. The fix is clear routing rules and delegated approvers, so nothing waits on a single individual being at their desk. The next is fragmented supplier information, where the same vendor is scattered across spreadsheets, emails and someone's memory, so discovery and pre-qualification start from scratch every time.

Two quieter bottlenecks round out the list. Inconsistent evaluation, where criteria are argued after the bids arrive rather than agreed before, makes decisions slow and contestable. And weak handoff to onboarding, where an awarded supplier sits idle because no one owns setting them up, wastes the savings the deal was meant to deliver. All four share a root cause: stages that are disconnected and unmonitored, so work stalls in the gaps between people and systems.

How automation compresses the cycle

The single biggest determinant of how quickly a sourcing process runs is whether its stages are connected. In a manual setup each stage lives in its own tool: needs in email, market notes in documents, supplier lists in spreadsheets, RFx responses in an inbox and contracts in a filing system. Information is re-keyed at every boundary, which is slow and error-prone, and no one can see the whole cycle at once or tell where a given event is stuck.

A sourcing platform closes those gaps by making each stage feed the next. A documented need becomes a structured RFx with the specification already populated. Supplier responses arrive in a comparable format and flow straight into a scoring grid. An awarded bid becomes a draft contract with the negotiated terms in place, and a signed contract triggers onboarding automatically. Because everything lives in one connected record, the audit trail builds itself as work happens rather than being reconstructed afterwards. This is the practical difference a system such as ProcureWave makes: not a new process, but the same process with the waiting and the re-keying removed, so a cycle that took weeks can run in days.

Connection also changes what the process can tell you. When every stage writes to one place, you can see where events are stalled, how long each stage takes and how much spend is actually under contract, in real time rather than in a quarterly report assembled by hand. That visibility is what lets a sourcing function improve rather than merely repeat, turning a sequence of tasks into a source of insight and drawing on decades of thinking about procurement practice to do it.

Getting your sourcing process working

A good sourcing process does not have to be elaborate to be effective. It needs to be clear, consistent and connected, with each stage owned by someone, each handoff explicit and each decision measurable. Start by mapping your current cycle against the eight stages above and marking where events genuinely stall or where savings leak away. Fix the worst bottleneck first, prove the improvement on one high-value category, then extend the same discipline outward. Most organisations find that connecting the stages, so information flows once and stays visible, delivers more than any single hard-won negotiation.

If your sourcing today runs on email threads and spreadsheets, the fastest gain is usually to bring the stages onto one platform so they hand off cleanly and the cycle stops leaking time. See how ProcureWave connects the whole flow from need to onboarding, or talk to our team to walk through your own process and find where the friction is hiding. The organisations that treat sourcing as a discipline, mapping it, connecting it and measuring it, are the ones whose every cycle makes the next one faster.

Frequently asked questions

What is the sourcing process in procurement?

Sourcing is the front half of procurement: the structured work of finding, evaluating and securing the right suppliers for a defined need. It runs from identifying the requirement and studying the market through supplier discovery, RFx, evaluation and negotiation to a signed contract and onboarding. Where the wider procurement process covers buying end to end, sourcing is specifically about choosing who you buy from and on what terms.

What is the difference between sourcing and purchasing?

Sourcing decides who supplies you and negotiates the deal; purchasing executes individual buys against that decision. Sourcing is strategic and periodic, run when a need is new, a contract expires or the market shifts. Purchasing is transactional and continuous, raising orders against the suppliers and prices that sourcing has already established.

How long does a sourcing cycle usually take?

It depends on value and risk. A routine buy from a known market can close in days, while a complex, high-value category with a formal RFP, multiple rounds and legal review can run for several months. The biggest variable is rarely the work itself but the waiting between stages, which is exactly where automation compresses the cycle.

When should a business use single sourcing instead of competitive sourcing?

Single or sole sourcing suits cases where only one supplier can meet the need, where switching cost is prohibitive, or where a strategic partnership outweighs price competition. It trades leverage for speed and continuity, so it should be a deliberate choice with clear justification rather than a default. Our sole sourcing guide covers when it is the right call.