The Quote Sheet Looks Complete, So Why Can Nobody Choose a Supplier?
A method to normalize hidden variables—currencies, validity windows, and exclusions—across supplier quotes so strategic procurement leads can compare options with confidence.
Benchmark methodology · Representative workflowThis page documents a representative operating model for this type of team. It does not describe a named customer, testimonial, contract, revenue result, or verified conversion.
Signals to watch
- quote comparison
- hidden variables
- normalization sheet
The Hour of Maximum Information, Minimum Clarity
You have just closed a three-round RFQ. Seven suppliers responded. The spreadsheet looks clean: column A has the part number, column B has the unit price. You sort ascending, highlight the bottom three, and book a review meeting.
Then the emails start. “That price excludes DDP.” “The lead time was quoted in working days, not calendar.” “The validity window expired last Tuesday.”
The lowest number is not executable. The second-lowest carries a currency mismatch that the procurement system flags two days before the PO deadline. You are not deciding between suppliers. You are decoding what each supplier actually offered—a task that should have been done before the quotes landed in your inbox.
This is the hidden-variable trap of cross-border sourcing. And the usual responses make it worse.
Why “Just Ask for Clarification” Fails at Scale
The natural reflex is to write individual emails: Can you confirm this is FOB Shanghai? What exchange rate are you using? Does that include the packaging surcharge?
Three problems appear immediately.
First, suppliers interpret the same question differently. One answers in good faith with their spot rate. Another revises their price upward because they sense the buyer is shopping around. A third delegates the reply to a junior who omits half the details.
Second, the answers arrive in a thread, a PDF attachment, and a WhatsApp voice note. Now the evidence lives in three channels. Nobody has time to consolidate it before the Wednesday review.
Third, the cycle repeats on the next RFQ. No single question gets retired because no structure captured the answers.
The underlying mistake is treating clarification as a one-off conversation rather than a repeatable data-normalization step.
The Quote-Evidence Normalization Sheet
The fix is a lightweight structure that sits between the raw quote and the comparison table. Call it a quote-evidence normalization sheet. It is not a new software tool. It is a column rubric that forces every hidden variable to be stated, estimated, or flagged before a price comparison happens.
| Field | What to capture |
|---|---|
| Currency basis | Spot date or forward rate reference |
| Incoterm version | e.g. FOB Incoterms 2020 |
| Lead-time unit | Working days / calendar days |
| Validity window | Expiry date of the quoted price |
| Inclusions | What is priced in (packaging, insurance, duties) |
| Exclusions | What is priced out (surcharges, testing, late delivery penalty) |
| Quote medium | Email attachment, portal, voice note transcript |
Fill this for every line item before any price column is sorted. If a value is unknown, mark it UNKNOWN in bold red. The goal is not perfect data. The goal is visible data. An unknown that is flagged is safer than a number that implies precision.
Building the Normalization Protocol in Six Steps
Step 1 — Standardise the currency reference. Pick one base currency for the RFQ and state the conversion date. If a supplier quotes in a different currency, convert at the published central bank rate for that date, not a spot rate from a screen grab. Attach the rate source to the cell as a comment.
Step 2 — Unpack the Incoterm. Two suppliers may both write “FOB” but reference different Incoterm editions. FOB Incoterms 2010 differs from FOB Incoterms 2020 on risk transfer for goods loaded by the seller. Record the edition. If none is given, flag it.
Step 3 — Normalise lead time to calendar days. A supplier who quotes 15 working days is actually offering 21 calendar days at a five-day workweek. Recalculate and note the working-day assumption so the buyer and seller share the same delivery expectation.
Step 4 — Tag the validity window. Stamp each quote line with an expiry date. A quote that expires before the sourcing committee meets should be highlighted, not averaged into the comparison.
Step 5 — Log inclusions and exclusions as separate columns. Many quote sheets collapse these into fine print. Pull them into their own cells. If supplier A includes packaging and supplier B charges it as a line item, the unit prices are not comparable until both are on the same basis.
Step 6 — Assign a confidence score per line. Use three levels: Confirmed (written evidence matches the normalization criteria), Assumed (extrapolated from a partial statement), or Unknown (no evidence). Unknown lines are excluded from price ranking until clarified.
What the Normalised Output Looks Like
After the protocol runs, the comparison table changes shape. Instead of one price column, you have:
- Adjusted comparable price — converted and normalised to the same Incoterm and inclusion basis.
- Validity flag — green (valid >30 days), amber (7–30 days), red (<7 days).
- Confidence — Confirmed, Assumed, or Unknown.
The lowest adjusted comparable price may or may not be supplier C. But you now know that supplier D’s price was marked Unknown on currency reference and cannot be ranked until clarified. You also know that supplier A’s lead time was calculated from a working-day assumption that you can verify in one phone call.
This is the outcome that matters: comparable and traceable supplier options with unknowns clearly marked. You can now present a sourcing recommendation where every number has a parent, and every gap has a next action.
The Role of a Structured Signal Layer
Once the normalization sheet becomes routine, a pattern emerges: the same variables cause friction across every RFQ—currency volatility, validity drift, and definition gaps in lead time. These are not one-off problems. They are structural signals that repeat across suppliers and categories.
A team that has been running normalization sheets for a few quarters can begin to recognize these signals before quotes arrive. They build a small playbook of clarification questions that get sent with the RFQ, not after it. They also start to notice which suppliers consistently submit quotes that pass normalization with zero UNKNOWN flags—those suppliers have internal processes that align with the buyer’s operating rhythm.
For teams ready to move beyond spreadsheets, a dedicated signal layer can surface these patterns across dozens of active sourcing events without rebuilding the same columns each time. Telegram business signal intelligence tools help procurement teams centralize quote evidence from multiple channels—email, messaging, portals—into a single normalized view. Source governance workflows then lock the normalization criteria so every buyer in the organisation applies the same rubric. And a signal framework for supplier communication ensures that clarification requests become structured data points instead of inbox clutter.
The method works on a spreadsheet first. The tool only accelerates what the process already does.
FAQ
Should we normalize freight terms retroactively if old quotes lack them?
Mark them as “missing” on the normalization sheet rather than inserting estimates. Guessing a freight cost introduces noise that warps the price ranking. Treat a missing field as a mandatory question for the next RFQ round so the data improves over time.
How granular should the normalization sheet be for a seven-figure capital equipment buy?
Create a separate sheet per lot, but keep the column schema identical across lots so you can roll up insights. Capital buys usually need two extra columns: installation scope (what the supplier includes) and payment milestone structure.
Can we automate the sheet without buying software?
Yes. A shared spreadsheet with data-validation dropdowns, conditional formatting for expiry warnings, and a locked template is enough for teams sourcing up to a few hundred RFQ lines per quarter. The method scales on process discipline before it needs a tool.
Key Takeaways
- A quote is not comparable until hidden variables—currency, Incoterm, lead-time unit, validity window, inclusions, exclusions—are normalised into the same basis.
- The quote-evidence normalization sheet is a column rubric, not a software purchase. It works in any spreadsheet and costs nothing to start.
- Mark unknowns in bold red. A flagged gap is safer than a number that looks precise.
- Run the protocol before any price sort. The ranking changes once every line sits on the same footing.
- Over time, normalization reveals structural supplier signals that can improve RFQ design and supplier selection criteria.
Sources
Frequently Asked Questions
Should we normalize freight terms retroactively if old quotes lack them?
Mark them as “missing” on the normalization sheet rather than inserting estimates. Guessing a freight cost introduces noise that warps the price ranking. Treat a missing field as a mandatory question for the next RFQ round so the data improves over time.
How granular should the normalization sheet be for a seven-figure capital equipment buy?
Create a separate sheet per lot, but keep the column schema identical across lots so you can roll up insights. Capital buys usually need two extra columns: installation scope (what the supplier includes) and payment milestone structure.
Can we automate the sheet without buying software?
Yes. A shared spreadsheet with data-validation dropdowns, conditional formatting for expiry warnings, and a locked template is enough for teams sourcing up to a few hundred RFQ lines per quarter. The method scales on process discipline before it needs a tool.
Frequently asked questions
Should we normalize freight terms retroactively if old quotes lack them?
Mark them as "missing" on the normalization sheet rather than inserting estimates. Guessing a freight cost introduces noise that warps the price ranking. Treat a missing field as a mandatory question for the next RFQ round so the data improves over time.
How granular should the normalization sheet be for a seven-figure capital equipment buy?
Create a separate sheet per lot, but keep the column schema identical across lots so you can roll up insights. Capital buys usually need two extra columns: installation scope (what the supplier includes) and payment milestone structure.
Can we automate the sheet without buying software?
Yes. A shared spreadsheet with data-validation dropdowns, conditional formatting for expiry warnings, and a locked template is enough for teams sourcing up to a few hundred RFQ lines per quarter. The method scales on process discipline before it needs a tool.