The real reason quotes aren’t comparable: you didn’t give suppliers the same worksheet
Most “messy RFQ” problems aren’t supplier problems. They’re document design problems. If one supplier prices per unit, another per pack, and a third bundles freight into the line price, you can’t compare without re-keying and guessing. The single highest-value move is blunt: force every bidder to price the same numbered rows, in the same units, with the same columns. Make it impossible to answer in free text.
Step 1 — Lock the scope so suppliers don’t quote different problems
Before you write anything, decide what you are actually buying and what you are not. If you leave “installation as required” hanging, some suppliers will include it, others will exclude it, and you’ll spend your evaluation calls reconstructing what each quote meant. Write scope as a boundary, not a brochure.
State the outcome in one sentence (e.g., “Supply of 316 stainless pipe and fittings delivered to Site A”).
List explicit inclusions (e.g., packaging suitable for outdoor storage, certificates of conformity, delivery to dock).
List explicit exclusions (e.g., installation, commissioning, disposal of old equipment).
Clarify who provides what inputs (drawings, part numbers, site access windows).
Name the commercial model you expect (one-off purchase, blanket order, call-off schedule).
Step 2 — Write specs that can be priced, not interpreted
Vague specs don’t create competition; they create assumptions. Assumptions create change orders and “that’s not included” arguments. Your goal is not maximum detail—it’s removing the decisions you don’t want suppliers to make for you. If you’re okay with equivalents, say what “equivalent” means in measurable terms.
A practical spec-writing method: “Must / Must not / Evidence”
Must: measurable requirements (material grade, dimensions, tolerance, standards, operating range).
Must not: disallowed substitutions (no refurbished parts, no mixed lots, no certain coatings).
Evidence: what proves compliance (datasheet, test report, certification, sample, drawing approval).
Common mistake: burying key requirements in email threads or attachments. Put the pricing-critical items in the RFQ itself (and reference attachments by name and version). If a supplier needs three documents to know the unit of measure, you’ll get three different units of measure back.
Step 3 — Define quantities so suppliers don’t price different volumes
Quantity ambiguity is one of the fastest ways to get unusable quotes. Suppliers price risk: uncertain volume leads to higher unit prices, minimum order quantities, or “valid only for 50 units” caveats. If you genuinely don’t know the quantity, don’t pretend you do—ask for tiered pricing and make the tiers identical for all bidders.
Use a single unit of measure per line (EA, kg, m, box of 100) and define pack size if relevant.
If demand is variable, request price breaks at your tiers (e.g., 1–99, 100–499, 500+).
Specify expected order pattern (one shipment vs multiple releases) because it changes logistics cost.
Call out minimum shelf life, lot/batch rules, or partial shipment rules if they affect supply planning.
Step 4 — Stop asking for impossible deadlines (and then paying for them)
Unrealistic timelines don’t speed anything up; they just change the quote you receive. Suppliers either ignore the date, pad pricing for overtime/air freight, or decline. If you need urgency, be explicit about what kind: fast quote turnaround, fast manufacturing, or fast delivery. Those are different constraints.
RFQ issue date and question deadline (and where questions must be sent).
Quote due date and time zone (yes, time zone).
Decision date and expected award date (so suppliers hold capacity and pricing).
Required delivery date(s) and delivery location(s) with Incoterms or delivery terms.
Validity period required for pricing (e.g., 30/60/90 days).
Trade-off to accept: longer quote windows often produce better pricing and fewer clarifications, but you may lose momentum internally. If the business insists on speed, narrow the scope (fewer lines, fewer options) rather than compressing everything.
Step 5 — Force a single pricing format: numbered rows, fixed columns, no creativity
If you do only one thing differently, do this. Create a bid sheet where each line item is a numbered row and every supplier must fill the same columns. Tell suppliers that non-conforming quotes may be rejected. This sounds harsh, but it saves everyone time and reduces “misunderstandings” that show up after award.
Bid sheet columns that make comparison instant
Row # (locked): 001, 002, 003…
Buyer item description (locked) + buyer part number (if any)
Supplier part number (required)
Compliance (Yes/No) + deviation reference (required if No)
UOM (locked) and quantity (locked)
Unit price (required) and extended line total (auto or required)
Currency (locked) and decimal rules (e.g., 2 decimals)
Lead time (days/weeks) and ship-from location
Freight term (locked choice) and freight cost (separate line or separate column—pick one)
Taxes/duties (state included/excluded; if excluded, provide estimate column)
Warranty/returns terms (short text or reference to attachment)
Pick one rule for freight and stick to it: either (a) require freight to be a separate line item, or (b) require freight to be included in unit price under a specified delivery term. Mixing approaches across suppliers is what creates the “Supplier A is cheaper… unless you add shipping” mess.
Make deviations easy to spot, not easy to hide
Suppliers will deviate. That’s normal. The failure is when deviations are buried in an email paragraph. Require a numbered “Deviations & Assumptions” table that references your row numbers. If a supplier won’t commit to your spec, you want that visible next to the price, not discovered after the PO.
Deviation ID (D1, D2…) with impacted RFQ row #
What they propose instead (exact model/spec)
Impact on price, lead time, warranty, or performance
What decision you need from the buyer (approve/reject/clarify)
Step 6 — Control questions so you don’t answer three versions of the RFQ
One supplier asks a good question, you answer them privately, and now you have multiple RFQ versions in the market. That’s how you end up awarding based on unequal information. Use a single Q&A log and issue addenda with version control.
Set one channel for questions (single email alias or portal message thread).
Publish answers to all bidders (anonymized) on a schedule.
When an answer changes pricing inputs, issue an addendum and update the bid sheet version number.
Require suppliers to acknowledge addenda in their submission.
Step 7 — Submission rules that prevent spreadsheet chaos
If you allow PDFs, screenshots, and “see attached,” you’ll spend your evaluation rebuilding a quote database by hand. Set submission rules that protect your time. You’re not being picky; you’re removing rework.
Require the completed bid sheet in editable format (XLSX/CSV), not just PDF.
Require a signed RFQ response form (or email confirmation) accepting your commercial terms or listing exceptions.
State the naming convention for files (SupplierName_RFX123_BidSheet_v2.xlsx).
State that pricing must be provided per row; “bundled” or “as per quote” entries are non-compliant.
State what happens if they miss the deadline (late bids not accepted, or accepted at buyer discretion—choose one).
Downloadable-feeling RFQ checklist (copy into your template)
RFQ header: RFQ ID, issue date, buyer contact, submission email/portal, confidentiality note.
Scope boundary: inclusions, exclusions, delivery locations, required standards, required evidence.
Spec clarity: Must/Must not/Evidence written for each critical item or group.
Quantities: fixed quantities or defined tier breaks; UOM locked; pack sizes defined.
Timeline: Q&A deadline, quote due date (time zone), validity period, delivery date(s).
Pricing format: numbered rows; fixed columns; currency; decimal rules; freight/tax treatment defined.
Deviations: mandatory deviations table referencing row numbers.
Commercials: payment terms requested, warranty expectation, return policy, incoterms/delivery terms.
Submission: editable bid sheet required; file naming; addenda acknowledgment required.
Evaluation note: state that award may be by line, by lot, or whole-of-bid (whichever is true).
Short annotated example: a bid sheet that forces comparability
Below is a compact example you can mimic. The point is not the category; it’s the structure. Every supplier prices the same rows, same UOM, same columns. Deviations are forced into a separate, referenced table.
RFQ pricing rules (paste above the table): “Complete all rows. Do not change row numbers, descriptions, UOM, or quantities. Provide unit price and lead time per row. Freight must be quoted as a separate line (Row 900). Taxes excluded; state tax rate separately. Non-conforming quotes may be rejected.”
Row 001 | Item: Nitrile gloves, powder-free, blue | Spec: EN 455 compliant | UOM: Box (100) | Qty: 200 | Supplier PN | Compliance (Y/N) | Unit price (USD) | Line total | Lead time (days) | Notes (no marketing text; deviations only)
Row 002 | Item: Safety glasses, anti-fog | Spec: ANSI Z87.1 | UOM: EA | Qty: 300 | Supplier PN | Compliance (Y/N) | Unit price (USD) | Line total | Lead time (days) | Notes
Row 003 | Item: Earplugs, disposable | Spec: SNR ≥ 33 dB | UOM: Box (200 pairs) | Qty: 50 | Supplier PN | Compliance (Y/N) | Unit price (USD) | Line total | Lead time (days) | Notes
Row 900 | Item: Freight to Buyer Dock, Site A (address in RFQ) | UOM: Lot | Qty: 1 | Unit price (USD) | Lead time (days) | Notes: “State carrier/service level”
Deviations table example: D1 impacts Row 002 — Proposed model has ANSI Z87.1 but no anti-fog coating; price -$0.40/EA; lead time unchanged; buyer decision required: accept/reject substitution.