RFQ, RFP and RFI: the sourcing requests explained
RFQ, RFP and RFI — collectively the 'RFx' family — are the formal requests procurement teams send to suppliers during sourcing. They look similar but do different jobs: one gathers information, one compares prices, and one evaluates full proposals. Choosing the right request for the situation is what makes a sourcing event fair, comparable and efficient. This guide defines each, explains how they differ, and shows when to use which.
10 min read · Last updated 11 July 2026 · By Lapasar Procurement Technology
In short
An RFI (request for information) gathers general information about suppliers and their capabilities. An RFQ (request for quotation) asks shortlisted suppliers for firm prices on clearly defined items. An RFP (request for proposal) invites suppliers to propose a solution and is evaluated on more than price. Use an RFI to explore, an RFQ when the requirement is well-defined, and an RFP when the solution matters as much as the cost.
What are RFQ, RFP and RFI?
RFI, RFQ and RFP are three types of formal request procurement uses to engage suppliers during sourcing. They are often grouped as 'RFx' because they share a structure — a written request, a defined response format and a deadline — but each is designed for a different stage and purpose.
A request for information (RFI) is exploratory. It gathers general information about the market and potential suppliers — their capabilities, experience and offerings — usually early on, when you are still shaping the requirement and want to understand who and what is available.
A request for quotation (RFQ) is about price. When the requirement is clear and well-specified, an RFQ asks a shortlist of suppliers to quote firm prices on exactly those items, so responses are directly comparable. A request for proposal (RFP), by contrast, is about the solution: it invites suppliers to propose how they would meet a more complex or open requirement, and is evaluated on quality, approach and value — not price alone.
How to choose and run the right request
The three requests often work in sequence — explore, then shortlist, then decide — but each can also be used on its own depending on how well-defined the requirement is.
- Use an RFI when you are still exploring the market and need to understand who and what is available.
- Use an RFQ when the requirement is clearly specified and price is the main variable to compare.
- Use an RFP when the solution matters as much as the cost and you want suppliers to propose an approach.
- Define the requirement precisely: the clearer the specification, the more comparable the responses.
- Set consistent response formats and deadlines so submissions can be evaluated fairly side by side.
- Evaluate against agreed criteria: price for an RFQ, weighted quality-and-value criteria for an RFP.
Why the right request matters
Using the wrong request wastes everyone's time and produces answers you cannot compare. Sending a full RFP for a simple, well-defined commodity buy burdens suppliers and your team with unnecessary work; sending an RFQ for a complex service reduces a nuanced decision to a price line and hides the differences that actually matter. Matching the request to the situation is what keeps sourcing proportionate and the results decision-ready.
A well-run RFx process also protects fairness and value. Clear specifications and consistent response formats make submissions genuinely comparable, support a defensible decision, and strengthen your negotiating position. For routine, well-defined categories, though, the fastest 'sourcing' is often no event at all: buying from a managed catalogue at pre-negotiated contract prices removes the need to run an RFQ for every purchase. Knowing when to run a formal request and when to buy from a catalogue is a core procurement judgement.
Benefits
Comparable responses
A well-structured request produces submissions you can evaluate fairly side by side.
Better decisions
Matching the request type to the need surfaces the information that actually drives the choice.
Stronger negotiating position
Competitive quotes and proposals give you leverage and a market benchmark on price and terms.
A defensible, auditable process
Documented criteria and consistent formats make the award transparent and easy to justify.
Right-sized effort
Choosing RFI, RFQ or RFP proportionately avoids over-burdening suppliers and your own team.
Common challenges
Vague requirements
Poorly specified requests produce inconsistent responses that cannot be compared cleanly.
Using the wrong request
An RFP for a simple buy, or an RFQ for a complex service, wastes effort and hides what matters.
Inconsistent evaluation
Without agreed criteria and weightings, scoring becomes subjective and hard to defend.
Over-sourcing routine spend
Running a formal event for every small, well-defined purchase adds cost the savings rarely justify.
RFQ, RFP and RFI in practice
A team setting up a new facility might start with an RFI to understand which suppliers can serve the region and what they offer. For the fit-out consumables, where the specification is exact, they run an RFQ and pick on price. For a managed cleaning-and-maintenance service, where approach, staffing and service levels matter, they run an RFP and evaluate weighted criteria, not just cost.
For everything that recurs — the day-to-day office, pantry, safety and facilities items — running an RFQ every time would be wasteful. Instead, procurement negotiates contract pricing once and moves ongoing buying onto a managed catalogue, so staff simply order at agreed prices. Malaysian organisations often combine both: formal RFx events for new or complex categories, and catalogue buying at contract prices for the routine tail. The RFQ template linked below standardises your quotation requests, and the RFQ-vs-catalogue comparison explores exactly where each fits.
Best practices
Match the request to the need
RFI to explore, RFQ for well-defined price comparisons, RFP when the solution matters as much as cost.
Specify precisely
The clearer and more complete the requirement, the more comparable and useful the responses.
Standardise response formats
Ask for answers in a consistent structure so evaluation is fair and fast.
Agree criteria upfront
Define and weight evaluation criteria before responses arrive to keep scoring objective and defensible.
Don't over-source the routine
For recurring, well-defined categories, negotiate contract pricing once and buy from a catalogue instead.
Summary
RFQ, RFP and RFI are the formal sourcing requests procurement uses to engage suppliers: an RFI to explore the market, an RFQ to compare firm prices on well-defined requirements, and an RFP to evaluate proposed solutions on quality and value. Matching the request to the situation keeps sourcing proportionate and the results comparable.
A well-run RFx process produces comparable, decision-ready responses and a defensible award — but for recurring, well-defined categories, the most efficient path is often to negotiate contract pricing once and buy from a managed catalogue rather than run an event every time.
Key takeaways
- RFI gathers information; RFQ compares prices; RFP evaluates solutions.
- Use the request that matches how well-defined the requirement is.
- Precise specifications make responses genuinely comparable.
- Agree and weight evaluation criteria before responses arrive.
- For routine categories, catalogue buying beats repeated RFQs.
Frequently asked questions
- What is the difference between an RFQ, RFP and RFI?
- An RFI (request for information) gathers general information about suppliers and the market, usually early in sourcing. An RFQ (request for quotation) asks shortlisted suppliers for firm prices on a clearly defined requirement, so price can be compared directly. An RFP (request for proposal) invites suppliers to propose a solution and is evaluated on quality, approach and value as well as price.
- When should I use an RFQ instead of an RFP?
- Use an RFQ when the requirement is well-defined and standardised, so price is the main thing you need to compare — for example, a specified quantity of a known product. Use an RFP when the requirement is complex or open, and how a supplier proposes to meet it matters as much as the cost — for example, a managed service.
- Do the three requests have to be used in sequence?
- No. They often flow in sequence — an RFI to explore, then an RFQ or RFP to decide — but each can be used alone. If you already understand the market and have a clear specification, you can go straight to an RFQ. If the requirement is complex from the outset, you might begin with an RFP.
- When is a formal RFx not worth running?
- For recurring, well-defined, lower-value categories, running a formal request for every purchase costs more effort than it saves. The better approach is to source those categories once, negotiate contract pricing, and move ongoing buying onto a managed catalogue so staff simply order at agreed prices.
- How does Lapasar fit with the RFx process?
- Lapasar complements formal sourcing by handling the recurring, well-defined categories through a managed marketplace with pre-negotiated contract pricing — so you reserve RFQs and RFPs for new or complex needs and buy the routine tail from a catalogue at agreed prices across Peninsular Malaysia. See the RFQ template and the RFQ-vs-catalogue comparison linked below.
Take it further with Lapasar
Put it into practice
Templates & frameworks
Go deeper
Explore related across the knowledge graph
Put these ideas to work
Talk to our team about consolidating spend, wholesale pricing, credit terms and delivery across Peninsular Malaysia — or request a walkthrough of the marketplace.
Prefer to talk to a real person?
Our team replies fast on WhatsApp and email — no forms, no waiting.

