Buying teams can put a structured vendor inquiry on a project page. The form captures company, inquiry type, and a capability message so first replies are comparable before you open a real RFP in your sourcing tool.
Do not reuse the generic supplier Form ID if you need a clean export.
Edit the select to match the need statement.
The form will not auto-close unless you remove it.
CSV into your scoring sheet, then issue the real RFP.
A vendor inquiry is a first-pass RFI: you asked the market a question, or vendors are answering a published need. US sourcing teams and UK procurement both use a light form before Ariba. Compared with supplier contact, this page assumes there is a live question—a category you are exploring, a replacement you might buy.
It is not an RFP, not a reverse auction, and not a contract. Scoring happens in your process after export.
If every vendor writes a novel, you cannot shortlist. Prompt the same three facts in the placeholder.
Pricing on a public HTML form will be gamed. Ask for ballparks only, or wait for the RFP.
e-Sourcing suites, email to a long CC list, and a PDF questionnaire. HTML is the lightweight published RFI.
Need statement above, form below, closing date in the copy.
Use when you need sealed bids and audit. This form is the pre-market.
Version chaos. You will score the wrong PDF.
Use when there is no live question—just ‘we sell X’. Use this page when there is a question.
A temporary page for a category review can host this form for four weeks, then come down.
Keep the need statement on the page so the form submissions make sense six months later.
No. Say that. Binding offers live in the RFP/ITN.
Follow your standing orders. A website form may be allowed for pre-market engagement only.
Send after this form if the next pack is confidential.
They can use inquiry type Support or a labelled option so you can compare fairly.