eProcurement Toolkit

You are here: referencing, stop 3/6

The lineSupplier management

What is the vendor procurement process, step by step?

Short answer

The vendor procurement process is how an organisation finds, compares, checks and contracts a vendor it has not used before, then sets it up so the first order can go out.

Cite this answereProcurement Toolkit, “What is the vendor procurement process, step by step?”, updated 14 Nov 2026, eprocurementtoolkit.org/supplier-management/vendor-procurement-process

Key takeaways

  • Vendor procurement is the part of procurement that brings in a new vendor: confirm the need, look at the market, compare offers, check the vendor, sign, set it up, then review the first months.
  • Check first whether an existing contract or vendor already covers the need. Adding a vendor costs time and creates one more record to keep correct.
  • Fix the criteria and their weights before any offer arrives, and always include price. US federal rules require price in every source selection and the relative importance of each factor in the request; private buyers gain the same protection against a choice made first and justified later.
  • Scale the checks to the risk: a vendor that holds your data or keeps a production line running needs far more checking than a one-off supplier of office chairs.
  • Most problems come from skipped steps, not wrong choices: work starting before the contract, bank details taken from an email, a contract that renews by itself because nobody noted the date.

What is the vendor procurement process?

The vendor procurement process is the set of steps an organisation follows to buy from a vendor it has not used before: confirm the need, look at the market, compare offers on criteria fixed in advance, check the chosen vendor, sign a contract, and set the vendor up for ordering and payment.

Take a common case. The facilities team wants a new company to maintain the lifts in three buildings, because the current contract ends in six months. Nobody in the organisation has bought lift maintenance before. Someone has to find possible companies, decide what matters most, get comparable offers, check that the winner is insured and solvent, agree a contract, and make sure accounts payable can pay it. Done in that order, with a record at each step, that is the vendor procurement process.

This page follows one purchase from a new vendor. The procurement process guide covers every purchase, including orders against existing contracts. The supplier management process is the routine run across all suppliers over their whole life with the organisation. The forms and checks used to register a vendor are detailed in supplier onboarding. “Vendor” and “supplier” mean the same thing here; finance and IT teams tend to say vendor.

What are the steps of the vendor procurement process?

The process has nine steps. Small purchases merge some of them; large or risky ones take each step in full.

  1. Confirm the need and check what exists. The requester describes what is needed, by when and within which budget. Procurement checks whether a current contract, framework agreement or approved vendor already covers it. If one does, the process stops here and an order is placed against it.
  2. Write the requirement. Describe the result needed, the volumes, the service levels and any rule the vendor must meet, such as a certificate or a data location. A clear requirement is what makes offers comparable later.
  3. Look at the market. List possible vendors from trade directories, other buyers, existing vendors in nearby categories and, for larger needs, a request for information. The result is a long list, often five to ten names.
  4. Shortlist. Ask a few qualifying questions: can the vendor serve your locations, does it hold the required certificates, has it done similar work? Drop those that cannot meet a must-have condition.
  5. Ask for offers. Send the shortlisted vendors the same request for quotation or request for proposal, with the evaluation criteria, their weights and the deadline. Answer every question in writing to all of them.
  6. Evaluate and choose. Score each offer against the criteria, check references, and, where your rules allow it, negotiate with the best two or three. Record why the winner was chosen.
  7. Check the chosen vendor. Run the checks the risk calls for: legal entity, sanctions, finances, insurance, security or quality, and bank details. A vendor that fails a check does not get the contract.
  8. Contract and approve. Sign a contract that fixes scope, price, service levels, exit terms and renewal dates, signed by someone with the authority for that amount.
  9. Set up, order and review. Create the vendor record, verify the bank details, send the first purchase order, and review the vendor after the first months against what the contract promised.

The order is what protects the organisation. Criteria written after the offers arrive can be bent to fit a favourite. A vendor that starts work before the contract is signed has little reason to accept your terms. A vendor paid before its bank details are verified is a fraud risk.

How many vendors should you ask?

The value and the risk of the purchase decide how many vendors to ask. Most organisations set this in their procurement policy: one quote below a low threshold, often three written quotes above it, and a formal request for proposal or tender for large or complex needs. Public buyers follow thresholds set by law. In US federal buying, for example, purchases up to the micro-purchase threshold of $15,000 may be awarded without competitive quotations if the price is reasonable.

Sometimes only one vendor can do the work, for example the maker of a machine that alone can service it under warranty. A single-source purchase is allowed in most policies, but it needs a written reason approved by someone other than the requester. Without that record, “only one vendor can do it” becomes the easy answer every time. The routes by value, from an order against a contract to a full tender, are compared in does every purchase go through every step.

How do you compare vendors fairly?

Compare vendors on criteria and weights written down before any offer is opened, and send them to every vendor with the request. Include price in every comparison, and score each criterion on the same scale for all vendors.

Public rules make this a duty. Under US federal rules (FAR 15.304), price or cost must be evaluated in every source selection, with narrow exceptions. The solicitation must state every factor that will affect the award and its relative importance, and whether the non-price factors together are significantly more important than, about equal to, or significantly less important than price. In the EU, public contracts go to the most economically advantageous tender, judged on price or cost and, where the buyer chooses, on quality as well (Article 67 of Directive 2014/24/EU). A private company is not bound by these rules, but the reason behind them holds: weights fixed first stop a choice being made first and explained later.

Worked example: three vendors for a three-year managed print service, scored out of 100 (all figures fictional)
CriterionWeight (points)Vendor AVendor BVendor C
Annual price (€)—48,00054,00062,000
Price score: lowest price ÷ this price × 404040.035.631.0
Service levels and support (score 0–5)253 → 15.04 → 20.05 → 25.0
Security and data protection (score 0–5)153 → 9.05 → 15.04 → 12.0
Implementation plan (score 0–5)104 → 8.04 → 8.03 → 6.0
References from similar customers (score 0–5)103 → 6.04 → 8.05 → 10.0
Total (out of 100)10078.086.684.0

Vendor B wins although it is not the cheapest: its price is 12.5% above Vendor A’s, but it scores higher on service, security and references, which together weigh 50 points.

Each criterion score is the panel’s score out of 5, divided by 5 and multiplied by the weight: Vendor B’s 4 out of 5 on service gives 4 ÷ 5 × 25 = 20 points. Price uses a formula, so the cheapest offer gets the full 40 points and the others get less in proportion. If the weights had been 70 for price and 30 for the rest, Vendor A would have won. That is why the weights must be agreed with the requester and the budget holder before the offers arrive, not after. More on scoring methods is in the RFP process guide.

Which checks does a new vendor need before the contract?

A new vendor needs the checks that match the risk it brings. US banking regulators put the rule plainly: the scope and degree of due diligence should be commensurate with the level of risk and complexity of the relationship. A vendor that holds customer data or supplies a critical part gets every check; a one-off purchase of furniture gets a few.

Checks before the contract, scaled to the vendor’s risk (illustration; each organisation sets its own list)
CheckWhy it mattersLow-risk vendor (one-off goods)High-risk vendor (data, critical supply)
Legal entity and tax registrationYou contract with the right company and can pay it legallyYesYes
Sanctions and exclusion listsPaying a sanctioned party can break the lawYes, automated screeningYes, plus owners and parent company
Bank detailsPayment fraud often starts with false bank detailsVerified by a call to a known contactSame, with a second person approving the record
Financial standingA vendor that fails mid-contract leaves you without supplyNot usuallyAccounts or a credit report; a second source if it is weak
InsuranceCovers damage the vendor causes on your site or to third partiesIf it works on your premisesYes, with amounts set in the contract
Information security and data protectionA breach at the vendor is your breach tooNo, unless it touches your systemsQuestionnaire, certificates, data location
Quality, safety or sustainabilityDefects, accidents and supply chain abuses reach your nameOnly where a rule requires itCertificates, audit or site visit
ReferencesShows whether the vendor has done similar workOptionalTwo or three customers of similar size

Set the risk level first, from what the vendor will touch and what happens if it fails; the level then decides the list of checks.

Public rules list similar tests. A US federal contracting officer must find a prospective contractor responsible before award, which includes adequate financial resources, a satisfactory performance record and a satisfactory record of integrity and business ethics. The US Treasury’s sanctions office (OFAC) recommends a risk assessment that can cover the supply chain and that sets how much due diligence is done at onboarding. Bank details deserve special care: business email compromise, a scam aimed at companies that pay suppliers by wire transfer, caused reported losses of about $3.0 billion in 2025 in complaints to the FBI’s Internet Crime Complaint Center alone. How these checks fit a wider risk programme is explained in vendor risk management.

What should the contract and the set-up cover?

The contract turns the chosen offer into obligations. For a new vendor, check that it fixes at least these points before signature:

  • The scope and the deliverables, taken from the requirement and the offer, so the vendor cannot later say a task was not included.
  • The prices, how they may change, and the payment terms.
  • Service levels and how they are measured, with what happens when they are missed.
  • The start date, the end date, any automatic renewal and the notice period to stop it.
  • Exit terms: how the work, the data or the equipment come back if the contract ends early.
  • For a vendor that handles your data, where the data is held and what happens after a breach.

Then comes the set-up. The supplier data team creates the vendor record with the legal and tax details, the verified bank details and the payment terms, and enables the vendor in the ordering system. Only then does the first purchase order go out. The contract itself is filed with its owner and its key dates, so that the renewal is a decision and not an accident; contract management covers what happens next.

Is the process different for a software vendor?

The steps are the same, but three of them weigh more when the vendor sells software as a subscription. The requirement must state who will use the software and how many users, because the licence model decides the price. The checks before contract centre on security and data protection: where the data is stored, who at the vendor can see it, and how it is returned at the end. The contract needs a clear renewal date and notice period, because many subscriptions renew automatically and at a new price unless someone gives notice in time.

IT and procurement also need to agree who runs the purchase. When a department signs up for a tool with a company card, the vendor never goes through these steps at all. The full software case, from business case to renewal, is covered in the software procurement process.

Where does vendor procurement go wrong?

  • A new vendor for a need already covered. A team adds its own cleaning company while a group contract with better prices exists. Step 1 was skipped.
  • The requester chose before procurement was asked. Three quotes are collected to support a choice already made; the two other vendors never had a real chance.
  • Weights decided after the offers. The panel finds that its favourite is expensive and gives price less weight. Losing vendors and auditors can see it.
  • Work before contract. The vendor starts because the project is late, and the contract is negotiated afterwards with no leverage left.
  • Bank details from an email. The vendor record is created from an invoice or an email, and the first payment goes to a fraudster.
  • No review after the start. Nobody compares the first months with what the vendor promised, so problems wait until renewal.

Each of these is a missing check rather than a missing skill. A one-page request form, a scoring sheet fixed before the offers and a call-back rule for bank details prevent most of them. The vendor management best practices guide covers what to do once the vendor is in place.

Questions

What is the difference between vendor procurement and vendor management?

Vendor procurement brings a new vendor in: it ends when the contract is signed and the vendor can receive orders. Vendor management is the ongoing work with vendors already in place: performance reviews, risk checks, renewals and exits. The first decides who you buy from; the second makes sure you get what the contract promised.

How long does the vendor procurement process take?

It depends on value, risk and the rules that apply. A low-value purchase from a vendor that passes automated checks can take a few days. A request for proposal for a critical service, with security reviews and contract negotiation, often takes several months. Public tenders also have legal minimum periods for vendors to answer.

How many quotes do you need from vendors?

Your procurement policy sets the number by value. A common pattern is one quote for small amounts, three written quotes above a threshold and a formal request for proposal or tender for large purchases. Public buyers follow the thresholds and procedures set by their law.

What is vendor due diligence?

Vendor due diligence is the set of checks made on a vendor before the contract: who owns it, whether it is on a sanctions list, whether it is financially sound, insured and secure, and whether its bank details are real. The depth of the checks follows the risk the vendor brings.

Can you buy from a vendor without competition?

Yes, in defined cases: very small amounts, a purchase under an existing contract, an emergency, or a need only one vendor can meet. Most policies require a written reason approved by someone other than the requester, so that single-source buying stays the exception.

New guides on the supplier management line

One short email when a guide on this line is added or revised. Nothing else.

Coming soon: sign-up opens with the first email.

Seb Troz

Source-to-pay consultant · written and maintained this guide

Seb Troz is a source-to-pay consultant who implements Ivalua for buying organisations. He writes the guides on eProcurement Toolkit from that hands-on work.

Disclosure: the author works as an Ivalua consultant. Pages that compare software say so next to the comparison.