RFQ is one of those acronyms that arrives in a business inbox with no explanation attached, as though the meaning were obvious. It rarely is. This guide explains what an RFQ means in ordinary commercial life rather than in the language of a procurement department: what it is, what it looks like from both sides of the transaction, how it sits alongside a quotation and an invoice, when a plain email does the job better, and the unwritten etiquette that decides whether people enjoy dealing with you.
Key takeaways
- An RFQ, or request for quotation, is simply a business asking a supplier to price something specific.
- Most companies sit on both sides of it: sending RFQs to buy, receiving them to sell.
- The RFQ, the quotation and the invoice form one chain, each with a different job.
- Formality should match the value of the purchase; a short email is often the better tool.
What an RFQ means in everyday business
An RFQ is a request for quotation. Strip away the abbreviation and it is nothing more exotic than a business saying: here is exactly what we want, please tell us what it would cost. The defining feature is that the what has already been decided. The buyer is not asking the supplier to design a solution or recommend an approach. They are asking for a number, and for the terms attached to that number.
That distinction matters because it sets expectations on both sides. When a builder's merchant receives an RFQ for four hundred metres of a named cable at a stated specification, the answer is arithmetic and stock availability. When a marketing agency receives an enquiry asking how they would grow a client's audience, that is a different animal altogether and should not be called an RFQ. Using the term loosely is one of the quiet causes of friction between buyers and sellers, because each side ends up preparing for a different conversation.
You will meet the term in three common situations. A small business owner sends one when they want to test whether their current supplier is still competitive. A sales team receives one when a prospect has moved from browsing to buying. A finance team sees the trail of one months later, when they are matching what was ordered against what was invoiced. Same document, three very different vantage points.
The two sides of the same document
Almost every trading company plays both roles. You buy stock, services, software and equipment, so you send RFQs. You also sell, so RFQs land in your inbox. Understanding both sides makes you better at each, because the frustrations you feel as a recipient are usually the ones you are creating as a sender.
As the buyer, your job is to make quoting easy. Every ambiguity you leave in the request comes back as a question, a delay or a caveat in the price. Suppliers pad quotes when they are uncertain, and that padding is invisible to you but very real in what you pay. A precise request is not bureaucracy; it is the cheapest negotiating tool available.
As the seller, your job is to answer the question that was actually asked. Sales teams have a habit of treating an RFQ as an opening for a pitch, replying with a brochure, a discovery call request and three alternative options. Sometimes that is right. More often the buyer has already made the decision and simply needs a comparable number by Friday. Answer first, then add value.
What goes into a usable RFQ
You do not need a template with a company crest on it. You need the handful of facts a supplier cannot quote without, set out in an order they can read quickly.
- What you want. The item or service described precisely enough that two different suppliers would price the same thing, including part numbers, grades or standards where they exist.
- How much of it. Quantity, and whether that is a one-off, a call-off against a larger volume or a recurring requirement.
- Where and when. Delivery address, delivery date and any access or timing constraints that could affect cost.
- How you want the price broken down. Unit price, carriage, tax and any minimum order value, stated separately so quotes can be compared line by line.
- Your deadline. The date by which quotes must arrive, and how you want them sent.
- Any commercial terms. Payment terms, warranty expectations, or a note that these are open to discussion.
Six items. Most poor RFQs fail on the first or the last, either describing the requirement so loosely that every quote answers a different question, or hiding payment terms until after a price has been agreed, which sours an otherwise good start.
A few terms travel with the RFQ wherever it appears, and knowing them saves a lot of guesswork when the documents start arriving.
Quotation
The seller's written price and the conditions attached to it. The direct answer to an RFQ, and usually valid only for a stated number of days.
Purchase order
The buyer's acceptance of a quote, carrying its own reference number. This is the document that turns talk into a commitment.
Specification
The written description of what is being bought. Everything an RFQ achieves depends on how carefully this is written.
Lead time
How long the supplier needs between the order and delivery. Often more decisive than price when a deadline is fixed.
Payment terms
When the invoice falls due, commonly thirty days from receipt. A real part of the cost, and worth stating in the request.
Incumbent
The supplier you currently use. Worth naming to yourself before you start, because the comparison is rarely neutral.
Notice how the vocabulary joins up. The specification drives the quotation, the quotation carries the lead time and payment terms, and the purchase order fixes all of it in place. Get the language right and the process tends to follow.
RFQ, quotation and invoice: how the paperwork joins up
Finance teams see these three documents constantly and are often the only people in the business who understand how they relate. The chain is simple once it is laid out, and knowing it stops a great deal of confusion about which number is binding.
| Document | Who sends it | What it says | Commercial weight |
|---|---|---|---|
| RFQ | Buyer | Here is what we need, please price it | An invitation, not an order |
| Quotation | Seller | Here is our price and the terms attached | An offer, valid for a stated period |
| Purchase order | Buyer | We accept, please supply | The point of commitment |
| Invoice | Seller | Goods supplied, payment now due | A demand for payment |
Read across the rows and the logic falls out. Nothing is owed at the RFQ stage. The quotation creates an offer that the buyer can accept or let lapse. Acceptance, usually in the form of a purchase order, is where obligation begins. The invoice comes last and should never contain a surprise, because every figure on it was settled earlier in the chain. When an invoice does surprise someone, the fault is nearly always an RFQ that left something unsaid. Our guide to quotations in business covers the middle link in more detail.
When a simple email beats a formal RFQ
There is a persistent belief that formality signals professionalism. In buying, it often signals only that someone has a template. Matching the weight of the process to the weight of the purchase is a skill worth developing, particularly in smaller businesses where the person sending the request is also the person running the company.
A practical test. If the value of the purchase is lower than the cost of the time everyone will spend on the paperwork, send an email. If several suppliers are competing, the spend is material, or you may need to explain the decision to a board, an auditor or a funder months later, use a structured RFQ.
A short email still benefits from the six facts listed earlier; it simply carries them in two paragraphs rather than a form. What you lose is the audit trail and the like-for-like comparison, and for a small repeat order neither is worth much. What you should not do is send an email with none of the detail, then complain that the quotes are not comparable. Informal is fine. Vague is not.
Responding well when an RFQ lands on you
For a sales team, an inbound RFQ is a strong buying signal and is treated with surprising carelessness in many firms. The buyer has done work to specify a requirement and has almost certainly sent the same request to your competitors. Speed and clarity now count for more than polish.
Acknowledge receipt quickly and confirm the closing date you are working to. If something in the specification is genuinely unclear, ask one consolidated question rather than three separate ones over two days. Quote exactly what was requested, then, if you believe there is a better option, offer it as a clearly labelled alternative beneath the compliant quote rather than instead of it. Buyers running a comparison cannot use a quote that answers a different question, however good the idea behind it.
State validity plainly. A price that holds for thirty days, with any assumptions written down, protects both sides when raw material costs or exchange rates move. And if you cannot quote, say so early. Declining politely and promptly leaves the relationship intact; silence does not.
The commercial etiquette nobody writes down
Requesting quotes is a relationship activity as much as a commercial one, and the conventions around it are real even though they are rarely stated. Ignoring them costs you goodwill that is hard to buy back.
Do not use suppliers as free price-checking services. Asking three firms to quote when you have already decided to renew with the incumbent wastes their time and, once noticed, guarantees a slower and less generous response next time. Give a realistic deadline; a request that arrives on Thursday afternoon demanding a price by Friday morning tells suppliers what kind of customer you will be. Tell the unsuccessful bidders they were unsuccessful, briefly and without theatre. Two sentences are enough, and the supplier who is thanked for losing is the supplier who quotes keenly next time.
On the selling side, the etiquette is equally simple: honour the closing date, do not attempt to bypass the stated contact, and do not lead with a lowball price you intend to revise. In practical procurement terms, trust built across a handful of small requests is what gets you invited to the large ones.
Making the whole thing lighter work
Once a business is issuing more than a few requests a month, the administration starts to bite. Quotes arrive as attachments in different formats, get copied into a spreadsheet, and the comparison drifts out of date before the decision is made. Finance then spends its month-end reconciling numbers that nobody wrote down in one place. This is the point at which most owners look for a system rather than a folder.
ProcureWave was built around exactly this chain. Requests go out from one template, supplier responses come back into a single comparison view, and the accepted quote flows straight through to an order without anyone retyping a figure. The audit trail assembles itself, which matters as much for the small business proving its spending to a lender as for the large one satisfying an auditor. If you want the specialist view of the same document, our complete RFQ guide and our RFQ meaning guide go deeper into procurement practice.
Whichever side of the transaction you sit on, the principle holds: an RFQ is a clear question that deserves a clear answer, and the businesses that handle it well are the ones people want to trade with. If you would like to see how the process looks when it runs in one place, take a look at what ProcureWave does or have a quick word with our team about how your own requests are handled today.
Frequently asked questions
What does RFQ mean in business?
In business, RFQ means request for quotation. It is the message or document one company sends another to ask for a price on something it has already described in detail. Any business can send one and any business can receive one, which is why the term turns up in sales inboxes as often as in purchasing folders. For the term itself in more depth, see our RFQ meaning guide.
Is an RFQ the same as a quotation?
No. They are the two halves of one conversation. The RFQ is the buyer asking, and the quotation is the seller answering. The RFQ carries the specification, quantity and deadline; the quotation carries the price, the validity period and the terms attached to it.
Does a small business need to send formal RFQs?
Not for everything. For low-value or one-off purchases a short email naming the item, the quantity and the date you need it is usually faster and perfectly professional. Formal RFQs earn their place when the spend is significant, when several suppliers are competing, or when you will need to show later how the decision was made.
Am I obliged to buy after sending an RFQ?
Generally no. Sending an RFQ is an invitation for suppliers to quote, not a promise to place an order. The commitment usually forms when you accept a quote, most often by issuing a purchase order. It is good practice to say clearly in the RFQ that no order is guaranteed.
How quickly should a seller respond to an RFQ?
Acknowledge it the same day, even if the full price will take longer. Buyers frequently work to a stated closing date, and a quick acknowledgement with a realistic promise of when the quote will land is often the difference between staying on the list and being quietly dropped from it.
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