Request for quote form: what an industrial RFQ form should ask
Most industrial quote forms ask the wrong questions and send the answers somewhere sales never looks. Here's what to ask, what to drop, and where it should land.
An industrial request for quote form should ask for four things: the product or part number, the quantity, where it's going and by when, and how to reach the buyer.
Everything else can wait for your first reply, and the form has to land somewhere your sales team actually looks.
That sounds obvious. On the distributor and manufacturer sites we check, it's rarely what happens.
The quote button sits under the spec table, the form wants a company registration number, and the enquiry ends up in a platform inbox that nobody opens until Thursday.
What should a request for quote form ask?
Split the fields into two groups. The first is what sales needs to price the job. Only those should be required.
- Product, part number or model. Pre-fill it when the buyer clicks the quote button on a product page.
- Quantity and unit, whether that's pieces, metres or sets. A price for 10 and a price for 10,000 are different conversations.
- Delivery country and city. In Southeast Asia this decides lead time, duties and which branch or distributor should answer.
- Required-by date, so sales can tell a project from an urgent replacement.
- Name, company and work email.
- Phone or WhatsApp number, with the country code set to where the buyer is.
The second group is useful but optional:
- A file upload for drawings, a bill of materials or tender documents.
- A free-text box for the application or anything unusual.
- The branch or distributor they already buy from, if any.
Which fields cost you enquiries?
Every extra field is a reason to stop. These are the ones we'd remove first, because they ask the buyer to do your qualification for you.
- Budget. A buyer asking for a quote doesn't know yet. That's why they're asking.
- Company registration or tax number. Collect it when you open the account, not before the first price.
- Forced account creation. A login wall before a quote sends people to the next supplier on their list.
- A dropdown with 400 products. If they came from a product page, you already know which one.
- Job title and company size. Your salesperson will learn both in the first call.
Our view is simple. The form's only job is to start the conversation with enough detail to answer well. Qualifying the buyer is sales' job, and it's quicker on the phone.
Where should the quote button go?
Next to the part number and the specs that affect price, and visible without scrolling on a phone.
On most industrial product pages we review, it sits at the bottom under downloads and related products, or it doesn't exist and the buyer has to find a generic contact page.
Two more things matter in this region. Many buyers we deal with in Malaysia, Indonesia and Thailand would rather message than fill in a form, so offer WhatsApp next to the button, with the product name already in the message.
And if you sell through distributors, say who will reply. Buyers want to know whether they're talking to the manufacturer or a local dealer.
Where do your RFQs go after someone presses submit?
This is where most quote forms fail, and you can't see it from the outside.
On a locked platform (SAP Commerce, an enterprise CMS, a portal IT owns), the form often posts straight into the platform's own database. Someone in sales or customer service sees it eventually. Your marketing never does.
That causes four problems at once.
- Nobody can tell which campaign, keyword or page produced the enquiry.
- The lead isn't in your CRM, so it never enters a real sales process.
- No one gets an alert, and the reply goes out days later.
- If the buyer doesn't order, nothing follows up.
You don't need to rebuild the form to fix this. At the moment the buyer clicks submit, the form data and the traffic source are both sitting on the page.
You can capture them in the browser and send them to your CRM alongside the platform's own submission. The buyer sees nothing different, and IT doesn't touch the template.
We did exactly this for a regional cable and connector manufacturer running a locked SAP eShop. The enquiries had been arriving all along. Marketing just couldn't see them.
How fast should you reply to an RFQ?
Within the hour if you can. The study most people quote on this, published in Harvard Business Review in 2011, audited 2,241 US companies.
Firms that contacted a lead within an hour were nearly seven times as likely to qualify it as firms that waited even one more hour, and more than 60 times as likely as firms that waited a day or longer.
Industrial deals move slower than most of the leads in that study, so don't expect the same multiples. The direction holds, though. The first supplier to reply with one sensible question usually sets the terms of the conversation.
Test your own form this week
The steps before the form, from search to product page, are what our free RFQ readiness score measures. For the form itself, send a realistic enquiry through your own site from your phone. Then check:
- Did the form take under a minute to fill in?
- Did the enquiry reach your CRM within five minutes, with its source attached?
- Did someone get an alert, and did a person reply the same day?
- When you didn't buy, did anything follow up a week later?
Every no is an enquiry you paid for and lost.

The RFQ-Leak Audit
Submit a test enquiry on your own site, then walk it through five checks. Any leaking answer is an enquiry you paid for and can't see.
The RFQ-Leak Audit
Submit a test enquiry on your own site and walk it through five checks: speed, attribution, alert, nurture, coverage. Each leaking answer is an enquiry your locked platform is swallowing. No IT needed.
Get the auditQuestions we get asked
- What should an RFQ include?
- An RFQ should name the product or part number, the quantity and unit, the delivery location and required date, and any drawings or specifications the supplier needs to price it. Payment terms and delivery terms can follow in the supplier's reply.
- What's the difference between an RFQ and an RFP?
- An RFQ asks suppliers for a price on something already specified. An RFP asks them to propose how they'd solve a problem, so buyers use it when they haven't settled on the exact product or approach.
- How do I write a good request for quotation?
- Say exactly what you need, how many, where it's going and by when, and attach drawings or datasheets. The more precise the request, the easier the quotes you get back are to compare.
- How quickly should a supplier respond to an RFQ?
- Acknowledge it the same day, ideally within the hour, and send the price as soon as you can quote accurately. A fast first reply with one good question beats a slow perfect quote.
See where your RFQ flow leaks.
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.