In the procurement cycle, the request for quotation is the step where a defined need becomes a set of comparable prices. It sits in the sourcing stage, after someone has specified exactly what is required and before any order is raised. This guide follows the RFQ through the process: when procurement teams issue one, how to build it from line items and terms, how to run the evaluation and award, and how e-sourcing software turns the whole exercise from a spreadsheet chore into an auditable flow.
Key takeaways
- The RFQ lives in the sourcing stage of the procurement cycle, between specification and purchase order.
- Procurement teams issue an RFQ when the requirement is fixed and only price and terms vary.
- A good RFQ is built from precise line items, quantities and commercial terms suppliers answer in one shape.
- E-sourcing software issues, collects, evaluates and awards RFQs without re-keying a single quote.
Where the RFQ sits in the procurement cycle
Procurement is a cycle, not a single act. It runs from identifying a need, through sourcing a supplier, to raising an order, receiving the goods and settling the invoice. The request for quotation belongs firmly to the sourcing stage. By the time an RFQ is issued, someone has already established that a purchase is needed and has written down exactly what it is. The RFQ is the mechanism that turns that fixed specification into a shortlist of prices you can compare and act on.
Understanding that position matters, because it tells you what the RFQ is and is not responsible for. It is not where you decide what to buy, and it is not where you scope the market. Those happen earlier. The RFQ has one job: to get competitive, comparable prices on something already defined. Everything about how you build and run it should serve that single purpose. For the wider picture, our complete RFQ guide covers the document itself in depth, while this article follows it through the procurement process.
Seeing the RFQ as a stage rather than a form also changes how you measure it. A well-run RFQ is not just a document that went out and came back; it is a clean handover from the people who defined the need to the people who will place and receive the order. If the specification is solid and the response format is consistent, that handover is smooth and the downstream steps inherit clean data. If the RFQ is rushed, every later stage pays for it, from a muddled purchase order to a disputed invoice. Good procurement teams treat the RFQ as the point where quality is either locked in or lost.
When procurement teams issue an RFQ
A procurement team reaches for an RFQ at a specific moment: when the requirement is fully understood and the only remaining variable is commercial. If a colleague can hand you a specification that leaves nothing to interpretation, and the market has several suppliers who can meet it, the conditions for an RFQ are in place. The typical triggers look like this:
- Standard goods. Components, hardware or consumables with a clear specification or part number.
- Repeat purchases. Items bought regularly, where the need is well understood and pricing simply needs refreshing.
- Scoped services. Well-defined work such as a fixed number of licences or a set maintenance package.
- Price-driven decisions. Categories where quality is a given and cost and terms are what separate suppliers.
The unifying thread is certainty about the what. When the what is still open, the RFQ is premature. Teams that issue one too early end up with quotes built on different assumptions, which defeats the whole point of the exercise.
Timing within the calendar matters too. For repeat categories, many procurement teams schedule RFQs to refresh pricing at sensible intervals rather than assuming last year's rate still holds. Markets move, input costs shift, and a supplier who was keenest twelve months ago may no longer be. Re-issuing an RFQ periodically keeps your pricing honest and gives you a documented reason for staying with a supplier or switching. The trigger to issue, then, is not only a new need but also the moment an existing arrangement is worth testing against the market again.
Building the RFQ: line items, quantities and terms
A strong RFQ is a structured document, not a loose email. Its value comes entirely from precision, because precision is what makes the quotes comparable. Build it from a predictable set of components, and make sure every one is unambiguous before it goes out:
Line items
Each item described precisely, with a part number or bill-of-materials reference where one exists.
Quantities
Exact volumes per line, plus any minimum order quantity or phased schedule that affects price.
Delivery
Where the goods go, the date they are needed, and who bears the freight.
Commercial terms
Requested payment terms, currency, and how long the quote must remain valid.
The single most useful discipline when building an RFQ is to supply the response table yourself. When every supplier fills in the same columns, unit price, total price, lead time and minimum order, you avoid the tedious job of re-typing a dozen different quote formats into one comparison. Our guide to writing an RFQ request works through the wording of each section in more detail.
Issuing the RFQ to suppliers
With the document built, the next step in the process is issuing it to a chosen set of suppliers. This is a deliberately small number. Three to five pre-qualified vendors creates real competitive tension while keeping every respondent a genuine candidate. Blasting an RFQ to twenty suppliers wastes their time and yours, and it signals that you have not thought about who can actually meet the requirement.
Invite only suppliers you would happily award. Because an RFQ is decided largely on price, every supplier you include must be one whose lowest bid you would accept. Screen for capability, reliability and compliance before the RFQ goes out, not after the quotes come back.
Issuing also means setting the rules of engagement clearly: the submission deadline, the format, where to send the response, and a single point of contact for questions. Clarity here keeps the responses clean and the comparison honest.
Evaluating quotes and awarding
When the quotes arrive, the evaluation stage begins, and this is where the discipline of a fixed specification pays off. Because every supplier quoted on the same requirement, you can line the responses up and compare them directly. The one rule to hold is to compare total cost of ownership, not sticker price. A low unit price with slow delivery, weak payment terms or hidden freight can easily cost more than a slightly higher quote that arrives on time.
Reject any quote that quietly changes the specification, because it breaks comparability. Normalise everything that remains into the same shape, then weigh price against lead time, terms, warranty and the supplier's track record. Once the winner is clear, the award converts the quote into a purchase order, and the cycle moves from sourcing into transacting. Keep the quotes, the scoring and the decision together, because that record is what makes the award auditable later.
It is worth communicating the outcome to the suppliers who did not win, briefly and professionally. The RFQ is rarely a one-off; for repeat categories you will be back in a few months, and the suppliers who feel they were treated fairly are the ones who quote sharply next time. A quiet no-response teaches capable vendors to deprioritise your requests, which slowly hollows out the competitive field the RFQ depends on. Closing the loop costs a minute and protects the very competition that makes the tool work.
RFQ vs RFP vs tender in procurement
The RFQ is one of several sourcing instruments, and choosing the right one is a core procurement judgement. Each answers a different question and belongs at a different point in the process:
| Instrument | Asks suppliers for | Best when |
|---|---|---|
| RFI | Background and capability | You are still scoping the market |
| RFQ | A price on a fixed specification | You know exactly what you need |
| RFP | A proposed solution and price | The approach and method matter |
| Tender | A formal, structured bid | Value or regulation demands open competition |
In practice the RFQ and the tender overlap: a public-sector or high-value tender often contains an RFQ-style pricing schedule at its heart, wrapped in stricter procedural rules. The meaning of an RFQ within procurement is best understood by contrast. If you find yourself writing long questions about how a supplier would approach the work, you need an RFP. If you can describe the requirement on a page and simply need a number, the RFQ is right. When thresholds or regulation require open, documented competition, that RFQ pricing lives inside a formal tender.
Running RFQs in e-sourcing software
Run by email, an RFQ means chasing responses, re-typing quotes into a spreadsheet and hoping none slipped through. That is exactly the friction e-sourcing software removes, and the RFQ is the process it handles best, because a fixed specification with price as the variable is precisely what software compares well. The stages map cleanly onto the tool:
- Build. Assemble line items, quantities and terms once, in a structured form.
- Issue. Send the RFQ to your shortlist and let the system track who has responded.
- Collect. Gather quotes in one consistent format, with no re-keying.
- Evaluate. Rank suppliers automatically on total cost rather than headline unit price.
- Award. Turn the winning quote straight into a purchase order, with the full trail intact.
Handled this way, the RFQ stops being an isolated spreadsheet task and becomes a connected step in the procurement cycle. A quote flows through to an order, and the order through to payment, all on one record. That is what ProcureWave is built to do: issue the RFQ, collect structured quotes, lay them side by side and convert the winner without ever re-typing a number. If you would like to see it run against your own purchases, book a short demo and we will walk through it with your categories.
Getting the RFQ right in your process
Placed correctly in the cycle, the RFQ is one of the most efficient tools procurement has. The failures are almost always failures of placement and discipline rather than of the document itself. Watch for the common ones: issuing an RFQ before the specification is truly fixed, inviting too many or the wrong suppliers, judging on unit price alone, and letting quotes scatter across inboxes instead of keeping them together with the decision.
Get the sequence right instead. Wait until the requirement is settled, build a precise document, issue it to a focused set of capable suppliers, evaluate on total cost, and award into an order with the record intact. Do that and the RFQ does exactly what the procurement process needs of it: a fast, fair and well-documented way to turn a known need into the best available price and terms, ready for the next stage of the cycle.
Frequently asked questions
Where does an RFQ sit in the procurement process?
The RFQ belongs to the sourcing stage, after a need has been identified and specified but before a purchase order is raised. Once quotes come back and a supplier is chosen, the winning quote flows straight into a purchase order and the transactional side of the cycle takes over.
When should a procurement team issue an RFQ rather than an RFP?
Issue an RFQ when the requirement is fixed and only the price and terms vary, so quotes can be compared line by line. Use an request for proposal when the approach matters and you want suppliers to propose how they would solve the problem.
How many suppliers should receive the RFQ?
Three to five capable, pre-qualified suppliers is the usual sweet spot. That is enough to create genuine competition on price while keeping every respondent a realistic candidate worth evaluating properly.
Can an RFQ be run entirely in software?
Yes. E-sourcing tools issue the RFQ, collect structured quotes, rank them on total cost and convert the winner into an order without re-keying. See how ProcureWave handles it end to end.
Want to see this in your own numbers?
Book a tailored demo and we will show ProcureWave running on scenarios that match your business.
Get in touch
