Compare Product Quotes with an Explicit Deviations Column
Normalize product quotes with separate scope, evidence and deviation fields. Keep unanswered requirements visible before ranking supplier prices.
Before ranking product quotes, give every supplier reply a place for deviations and unanswered requirements. A short response saying “same specification” may coexist with a different model revision, an omitted material field or an excluded accessory. A comparison that hides those differences behind one price per supplier is unfinished.
Use a requirement-by-supplier matrix to preserve the buyer’s baseline, the supplier’s exact answer, the cited evidence and the decision still needed. The purpose is to decide which offers answer the same product brief. It is not a supplier scorecard, a product certification or a comparison of service fees and freight charges.
Freeze the comparison question
Identify the issued RFQ, product references, revision, quantities and requested product boundary before entering offers. If different suppliers received different revisions, resolve that problem first. A precise matrix cannot repair an inconsistent request.
Break the brief into requirements that can be answered individually. For a passive enclosure, these might include the specified revision, material requirement, included mounting accessory and required documentation. For an energy product, preserve the exact manufacturer/model and the scope of each requested rating or document. Do not use the spreadsheet to infer technical compatibility.
Classify requirements according to decisions already authorized by the buyer: essential, negotiable within a stated boundary, or informational. If that decision has not been made, mark it open. The person entering quote data should not downgrade an essential requirement simply because an attractive offer fails to answer it.
Keep answers, evidence and decisions separate
The supplier-response field records what the supplier actually said, with a dated quote or message reference. The evidence field records the supporting document and the exact location relevant to the requirement. The decision field records what the authorized reviewer concluded.
These fields should not collapse into one green tick. A supplier can explicitly claim a requirement is included while the required supporting evidence remains absent. Conversely, a catalogue may describe a feature that the supplier has excluded from the offered configuration. Both the offered scope and the evidence matter.
Retain the original response alongside a concise normalization. For example, “Accessory not in this price; optional” can be summarized as “excluded from baseline offer.” Do not normalize it as included merely because the accessory is available elsewhere. Where translation is necessary, preserve the original model identifiers and technical references.
Use scope and evidence states independently
For each requirement, use a scope state such as included, excluded or unknown. An explicit changed proposal belongs in the deviation field. Separately use an evidence state such as supplied and matched, supplied but mismatch unresolved, or not supplied. “Supplied and matched” should describe only the comparison actually performed, not an unearned technical pass.
A blank response is unknown. It is neither proof of compliance nor proof that the supplier cannot comply. Ask a targeted question and keep the row open. “Not applicable” also needs a reason accepted by the appropriate owner; it should not serve as a convenient way to remove a difficult requirement.
The following buyer template makes those distinctions visible.
| Matrix column | Record this | Avoid this shortcut |
|---|---|---|
| Requirement ID and baseline | Exact requirement and RFQ issue | Rewriting the brief to fit an offer |
| Supplier and quote reference | Dated response and revision | A price copied without context |
| Exact response | Relevant statement or clear omission | “Probably included” |
| Scope state | Included, excluded or unknown | Treating silence as acceptance |
| Evidence reference and state | Document/model/revision and match reviewed | A generic certificate tick |
| Deviation | Difference from the baseline and proposal status | Mixing alternatives with matching offers |
| Owner and next question | Who decides, and what would resolve the row | An unexplained red or green cell |
| Disposition | Clarify, hold, reject or accept for stated purpose | Automatic cheapest-wins ranking |
If a reply concerns multiple requirements, link it to each relevant row without inventing additional content. If one document fails to resolve a model identity question, all dependent conclusions remain conditional until that identity issue is closed.
A fictional enclosure comparison
Assume an invented RFQ for 30 passive organizer enclosures against specification E-12 Revision B, material requirement M-02, and included mounting accessory AC-01. These references are fictional. No product capability, technical suitability or actual supplier offer is asserted.
| Requirement | Fictional Offer A | Fictional Offer B | Fictional Offer C |
|---|---|---|---|
| E-12 Revision B | Explicitly quoted | Offers Revision A instead | Explicitly quoted |
| Material M-02 | No answer | Explicitly quoted | Explicitly quoted |
| Accessory AC-01 | Explicitly included | Explicitly included | Explicitly excluded |
| Immediate action | Clarify material | Hold changed revision for decision | Request matching accessory scope |
Assume all remaining requirements are still subject to their normal review; the table does not imply they passed. Offer A is incomplete on material. Offer B is an alternative on revision. Offer C does not include the requested accessory. None should enter a like-for-like price ranking as a fully answered baseline offer yet.
The next questions are narrow. Ask A to state the offered material and provide the required evidence. Ask B whether Revision B can be quoted, keeping Revision A as a separate proposal if the buyer wants to consider it. Ask C to quote the requested inclusion or clearly maintain the exclusion. No invented allowance should be added to make C appear complete.
Resolve rows without losing the original offer
When clarification arrives, add the new reply reference and identify which rows it resolves. Preserve the previous response so the buyer can see why the comparison changed. If the supplier changes its offered product, ask for a consolidated revised quote rather than constructing a final offer from incompatible message fragments.
An accepted deviation needs the owner’s name or role, the exact accepted change and the scope of that decision. Approval to compare an alternative is not approval to purchase it. Acceptance of a cosmetic variation is not permission to substitute an unrelated model or remove required documentation.
Do not create a numerical penalty for every unknown. A missing accessory price can sometimes be quoted and added later, but a missing technical requirement cannot be made acceptable by an arbitrary risk surcharge. Keep the consequence in words when the evidence does not support a number.
Rank only the offers that answer the chosen basis
Once a baseline offer has explicit answers and the required evidence stage is satisfied, it can move into the commercial comparison. Keep conditional offers and alternatives visibly separate, with their unresolved decisions. A lower number is useful only after the buyer understands what that number buys.
Hold selection if the quoted identity is unclear, evidence names another configuration, required inclusions remain unanswered, or a deviation has no authorized decision. If the buyer chooses to revise the baseline, issue that revision consistently and reconfirm affected offers rather than silently changing one supplier’s column.
Send the completed matrix back as a short clarification request, with row IDs and specific questions. The result should be a reviewable product decision: matching offer, accepted alternative or unresolved offer. The matrix earns its value by showing those differences clearly, not by producing a confident-looking supplier ranking before the facts support one.
Frequently asked questions
How should an unanswered requirement be recorded?
Use an unknown scope state and a specific clarification question. Silence does not establish either acceptance or inability to comply.
Can I count a supplier declaration as verified evidence?
Record it as the supplier’s statement. Separately note whether the evidence required for the decision was supplied and matched to the offered product.
Should alternatives share the same price-ranking column?
Keep their changed requirements and approval status visible. Compare them on a revised or separately approved basis rather than presenting them as unchanged baseline offers.
What if the cheapest offer excludes an accessory?
Ask for an explicit matching-scope quotation or maintain the exclusion. Do not invent an accessory price or assume another seller’s part is suitable.
Sources
Discuss a sourcing request related to this article.Compare Product Quotes with an Explicit Deviations Column