A useful direct-materials RFQ tells suppliers exactly what to quote, what to return for each line, and how to identify any exception. It separates firm quantities from forecasts, requested receipt dates from lead times, and the requested specification from proposed alternatives.
The downloadable direct-materials RFQ template (Excel) contains a supplier-facing response form and a short buyer preflight checklist. Adapt it to your material and approved purchasing terms before sending it.
Start with the buying decision
State whether the request supports an immediate order, a scheduled release, or evaluation of a future source. Suppliers need to know which quantities are firm requirements and which are planning assumptions. A forecast is not a purchase commitment merely because it appears in an RFQ.
Give the request an identifier and revision. Name the buyer, response channel, question deadline, quote deadline, and time zone. Ask for an explicit no-bid response when the supplier cannot participate, with a reason if they can provide one.
Set a deadline that leaves time to review technical questions and obtain internal approval before the material is needed. A quote due on the intended award day leaves no room to repair an incomplete response.
Make every line unambiguous
For each line, specify the item identifier, description, manufacturer part number where relevant, drawing or specification revision, quantity, and unit. Add the required destination and receipt schedule. Link only the technical documents approved for that supplier and confirm they can access them.
Include material-specific requirements that affect the offer: packaging, shelf life on receipt, certificates, testing, or traceability, as applicable. Have the appropriate technical or quality owner define these requirements. Avoid a generic list of certifications that neither the material nor the team requires.
Oracle’s sourcing documentation treats negotiation lines as the place for items, quantity details, attributes, and additional cost factors. That is a useful discipline for a simple RFQ document as well. Oracle sourcing documentation.
Ask for the fields you will compare
Give suppliers a repeatable response block for each line:
RFQ line:
Quoted item and specification revision:
Complies with requested specification: yes / exception attached
Quoted quantity and unit:
Unit price, currency and price basis:
Minimum order and order multiple:
Additional charges and what the price includes:
Earliest ship date and origin:
Expected receipt date at requested destination:
Lead time and event that starts the clock:
Quote valid until:
Exceptions, dependencies and proposed alternatives:
Require an explicit answer for each line: quoted, no-bid, or clarification needed. Permit partial quantities or alternatives only where your sourcing process allows them, and ask suppliers to label them separately. Oracle documents configurable partial quantities and alternate responses; they are choices to make when setting up the request. Oracle response controls.
Define the commercial basis
State the requested currency, delivery scope, approved terms reference, and how one-time costs should be presented. Ask suppliers to separate tooling, packaging, freight, and other charges, and identify anything excluded from the quoted total.
If quantity tiers matter, request specific quantities rather than asking vaguely for “best volume pricing.” Separate an initial purchase from expected annual demand. Ask whether quoted tiers depend on one release, a cumulative purchase, or a longer commitment.
Make quote validity an actual date. Ask what happens if approval arrives after that date: re-quotation, price refresh, or availability reconfirmation. Keep proposed commercial exceptions visible for the buyer’s review.
An RFQ template should reference your approved terms; it should not invent new warranty, liability, or cancellation language. Use the established review process for terms that need negotiation.
Worked example: repair a vague requirement
“Please quote 5,000 labels, annual demand 60,000, needed next month” leaves the supplier guessing about size, material, print revision, release quantity, and whether a full year is being ordered.
In this illustrative replacement, the buyer requests 5,000 labels to drawing L-24 revision D, in rolls of 500, for receipt at Plant A on October 20. Forecast annual demand is 60,000 labels, explicitly for planning only. The supplier is asked to quote the initial 5,000 and a separate 10,000-unit tier, state setup charges, and confirm the lead-time trigger.
The supplier returns a lower price at 10,000 units with one setup charge. The comparison now shows a real decision about purchase quantity and inventory, rather than confusing annual forecast pricing with the immediate order. The buyer can use the quote comparison guide to assess it.
Build a schedule suppliers can respond to
A header quantity is insufficient when a purchase will arrive in several lots. Give each required delivery a schedule reference, quantity, destination, and requested receipt date. The schedule quantities should reconcile with the total firm requirement. Show optional or forecast quantities separately so nobody includes them in a binding-looking total by accident.
For an illustrative 1,200-part requirement, the buyer needs 300 at Plant A on November 3, 400 on November 10, and 500 on November 24. These schedules sum to 1,200. Ask suppliers to price that exact release pattern and state whether the price assumes one production batch or three. A price for one shipment of 1,200 does not answer the scheduled-delivery request.
If a supplier can provide only 200 for the first date, the response should identify the short 100 and propose its earliest receipt. Do not reject the entire quote automatically or treat the total 1,200 as fully covered. The buyer and planner need the time-specific gap to decide whether the offer is usable.
Specify whether a quoted lead time ends at dispatch or receipt and what starts it. For custom parts, drawing approval, tooling approval, or an advance payment might start the clock. An RFQ should expose those dependencies before the team compares a four-week offer with one based on a different starting event.
Design technical questions so someone can answer them
Assign a technical owner before sending the RFQ, especially where suppliers are likely to challenge a tolerance, drawing note, or test requirement. The buyer coordinates the answer; the technical owner decides whether the requirement is correct or can change.
Ask suppliers to give the RFQ line, document revision, feature or clause, the precise question, and the effect on quoting. “Please clarify the drawing” is hard to route. “Line 30, drawing D revision F, dimension 12: does the stated tolerance apply after coating?” identifies a decision.
Keep clarifications distinct from proposed alternatives. Explaining an existing requirement may let all suppliers quote the same scope. Accepting a different material or test method changes what you are buying. That needs the appropriate review and potentially a revised request. The technical clarification guide covers that handoff through a revised supplier response.
Run an RFQ preflight with a recipient view
Before release, have a colleague use only the material the supplier will receive. Can they identify the current revision, total firm quantity, requested schedule, quote deadline, and required response fields? Can they open every linked attachment with the intended access?
Reconcile the line list against the attachments. A drawing for item 40 attached to line 30 can produce an internally consistent but unusable quote. Check file names, document titles, and revisions, not only that an attachment exists. Remove obsolete versions from the sending package while preserving them internally as history.
Confirm the response route and an alternate contact if the buyer is away. Record which suppliers received which version and when. If transmission fails, the supplier is not a late respondent; the request has not successfully reached them. Fix access or delivery first, then reassess their preparation time.
Judge the request by the answers it produces
After the event, count the responses that arrived with all mandatory fields complete on first submission. Divide by the responses received, and report non-responses separately. Otherwise an RFQ with one excellent reply and nine silent suppliers can look perfectly designed.
Review clarification causes: missing buyer information, supplier-specific questions, access failures, and genuine technical uncertainty. Use recurring omissions to improve the template, but do not keep adding fields nobody uses. A short, relevant response form is easier to complete than an exhaustive questionnaire with no connection to the purchase.
The RFQ release task closes when the approved package has reached the intended suppliers and the response process has owners. Quote collection and supplier selection remain separate work. Preserve that distinction when measuring turnaround: issuing ten RFQs says little about how many buying decisions became possible.
Keep revisions and clarifications fair and traceable
If a specification, quantity, or material requirement changes, issue a new revision and tell affected suppliers what changed. Apply substantive clarifications consistently across the suppliers involved, according to your sourcing process, without disclosing another supplier’s confidential offer.
Keep an amendment log, ask suppliers to identify the revision they quoted, and retire obsolete attachments. Where the change materially affects preparation time, have the buyer decide whether the response deadline should move.
Before release, open the attachments as the recipient would see them. Check units, dates, access, and references. Once responses arrive, track missing fields with the supplier quote follow-up guide.
The RFQ is ready when suppliers can prepare an offer without guessing the requirement and buyers can compare answers without reconstructing them. Mandel’s sourcing and quoting work carries the request and follow-up through to that usable set of offers, with the buyer retaining the award decision.