All field notes
Field notes·28 Sept 2026·6 min

RFQ vs RFP vs RFI: what each one means for an industrial supplier

An RFI asks what you can do, an RFP asks how you'd do it, and an RFQ asks what it costs. Here's what each one tells you about the buyer, and what they need to find on your site.

KA
Kai Andersen
Head of Operations, Incify

An RFQ (request for quotation) asks for a price on something the buyer has already specified. An RFP (request for proposal) asks how you'd solve a problem, and an RFI (request for information) asks what you can do at all.

For a supplier, the difference that matters is how far along the buyer is: an RFI is early research, and an RFQ means they're ready to buy.

If you run a distributor or a dealership, most of what reaches your inbox is RFQs, even when the buyer doesn't call it that.

The ones you never see are the RFIs, because most of them happen on your website before anyone writes to you.

What's the difference between an RFQ and an RFP?

An RFQ is about price. The buyer knows the part, the quantity and the delivery date, and wants the best terms from suppliers who can meet the spec.

An RFP is about the answer. The buyer knows the problem but not the solution, and wants you to propose one: the design, the method, the timeline and the price together.

In industrial buying, an RFP usually means a project, such as a new line, a plant upgrade or a system integration.

An RFQ is more often replacement stock, a repeat order or a component for a design someone has already signed off.

Buyers don't always label their messages correctly, so read the content, not the subject line. If the message names a part number, a quantity and a delivery date, it's an RFQ and it wants a price.

If it describes a problem and asks what you'd recommend, it's an RFP in all but name, and a bare price list will lose it.

If it asks which brands you carry or whether you're certified, it's an RFI, and a quick, specific answer puts you on the shortlist.

Comparison of RFI, RFP and RFQ. RFI: the buyer knows the problem area and asks what you can do, and checks your range, certifications and markets on your site. RFP: the buyer knows the problem and asks how you would solve it, and checks project references and engineering support. RFQ: the buyer knows the exact item and asks what it costs, and checks product specs, stock and a quote button.
Three requests, three different buyers. Your website has to serve all of them.

What comes first, RFI, RFP or RFQ?

When a buyer uses all three, the order is RFI, then RFP, then RFQ.

The US General Services Administration's guide for suppliers puts it plainly: an RFI is research, an RFP asks for a full plan and why you're the best choice, and an RFQ is for when the buyer knows what it needs and wants to know the cost.

Most private buyers skip steps. A maintenance manager replacing a pump sends an RFQ straight away. A procurement team building a new facility may run all three over several months.

Why don't you see most RFIs?

A formal RFI is a document sent to a shortlist of suppliers, asking about capabilities, certifications and capacity before a project is defined. Large companies and government agencies use them. Smaller buyers mostly don't bother.

The research an RFI stands for happens on every purchase, though. Before a buyer sends anyone an RFQ, they've already decided who is worth asking, and for most industrial buyers that decision is made on supplier websites, in silence.

If your site doesn't answer their questions, you don't get the RFQ, and you never learn it existed.

We've written separately about what buyers check before they enquire.

What should your website show at each stage?

Your site should answer the RFI before anyone asks it, give an RFP team enough to put you on the list, and make the RFQ easy to send.

  • For the research stage: the brands and ranges you carry, the certifications you hold, the industries you serve and the countries you deliver to. A buyer checking capability wants all of it in one scan.
  • For RFPs: project references, even anonymised ones, your engineering or application support, and who to call about a bigger job. Buyers building a shortlist look for proof you've done something similar.
  • For RFQs: a product page per range with specs, stock and lead times where you can share them, and a quote button with the product already filled in.

In August 2026 we walked 20 distributor and manufacturer sites selling into Malaysia, Singapore, Thailand and the Philippines. 16 of them had no quote path of their own.

A buyer ready to send an RFQ had to find the general contact form and start from a blank message.

That's the stage where the buyer is closest to ordering, and it's the one most sites make hardest. A good request for quote form asks for very little, and most of what sits on today's forms can go.

How should you answer an RFQ?

Fast, and with a question if you genuinely need one. The first sensible reply often sets the terms of the conversation.

  • Reply the same day, even if the full quote takes longer. Confirm you've received it and say when the price will follow.
  • Quote exactly what was asked. If you have a better alternative, offer it separately.
  • State lead time, delivery terms and how long the price is valid. Buyers compare these as closely as the price.
  • Log every RFQ with its source, so you can see which products and pages bring the enquiries that become orders.

The last one is where most distributors lose track. When RFQs arrive by email, WhatsApp and the website, and nobody records where each came from, you can't tell which part of your marketing is working.

The RFQs you get are the easy part. Worry about the ones your website never let happen.

Questions we get asked

Are an RFP and an RFQ the same?
No. An RFQ asks for a price on something the buyer has already specified. An RFP asks you to propose a solution, with method and price, for a problem the buyer has defined.
What comes first, RFI, RFP or RFQ?
The RFI comes first, then the RFP, then the RFQ. Many buyers go straight to an RFQ when they already know exactly what they need.
What is the difference between an RFQ and an RFT?
An RFT, or request for tender, is a formal invitation to bid, common in government and large infrastructure work and often public. An RFQ is usually less formal and sent to a smaller group of suppliers.
What are common RFQ mistakes suppliers make?
Replying late, quoting something slightly different from what was asked without saying so, and leaving out lead time or validity. Each one makes your quote harder to compare, and buyers tend to drop the hard ones.
SEND AN ENQUIRY

Find out where your RFQs get stuck.

Send a short note about what you're working on. We reply with how we'd approach it, or tell you if we're not the right fit.

A reply from our team within one business day.
Or email [email protected]