Practical perspectives
How to Compare Supplier Quotes When RFQ Scope Changes
A buyer worksheet for keeping supplier quotes comparable when specifications, quantities or delivery terms change during an RFQ.
On this page
A sourcing event can produce several apparently comparable prices that answer different questions. One supplier priced the original quantity, another included expedited freight, and a third answered a revised specification. Ranking the totals before normalizing scope can reward the wrong response.
This worksheet follows one controlled RFQ amendment. It complements our AI bid-evaluation software guide, which maps software approaches. Here the buyer records the facts, questions and approvals that make a comparison defensible.
1. Freeze the common requirement and its version
Before opening bids, record the version of the specification, unit of measure, quantity, delivery location and date, required service level, tax and freight treatment, and response deadline. Keep the original request and each amendment; do not silently replace a prior version. A line-item comparison should show which version each supplier answered.
The Market Dojo supplier event guide ↗ describes structured RFQ responses and auctions. The buyer’s fairness rule still matters: if a material requirement changes, tell every invited supplier what changed and give them the same opportunity to respond.
2. Separate quoted facts from buyer adjustments
Create two columns for each bid: the supplier’s stated offer and the buyer’s normalized comparison. Never overwrite the offer. If the supplier excludes a service, mark the gap as unresolved until it gives a priced clarification or the buyer applies a documented, consistently sourced adjustment.
| Change | What to compare | What needs clarification |
|---|---|---|
| Quantity rises from 1,000 to 1,400 units | Unit price, volume break, setup and capacity at the revised volume. | Can every bidder supply the same revised quantity and date? |
| Delivery moves to a second site | Freight, duties, packaging and service coverage for both sites. | Is the new location included in the submitted price? |
| Specification adds testing | Testing cost, lead time and acceptance evidence. | Which test standard and failure remedy did each bidder price? |
| Supplier offers an alternate design | The base compliant offer and alternate offer as separate scenarios. | Who can approve a technical deviation? |
An AI tool can help identify mismatched fields or suggest a normalization. Ask it to show the exact response line and assumption behind each adjustment. A missing answer is not a zero cost or proof that a supplier cannot deliver.
3. Reopen the right part of the event
Decide whether the change is a clarification, a priced amendment, or a new event. A spelling correction may need only a common notice. A new testing requirement can change every supplier’s offer and may require revised bids and a new deadline. Keep the response history attached to the original event.
- Common notice: send the same revised requirement and response window to all eligible bidders.
- Bid identity: preserve the supplier’s original quote and the revised quote; identify which one is valid for award.
- Technical approval: obtain the correct engineering or business sign-off for any alternative specification.
- Commercial approval: do not announce a preferred supplier until the revised award scenario is authorized.
4. Test whether the preferred award survives the change
Run the original scope, the revised scope, and an alternative allocation. Compare total landed cost alongside lead time, capacity, quality and concentration risk. Keelvar’s sourcing optimization description ↗ illustrates how a product may model such constraints. That published capability is a reason to test the scenario, not evidence that a particular buyer will save money.
If the winning supplier changes when one assumption moves slightly, show that sensitivity to the decision owner. If an AI recommendation does not change, ask whether it actually ingested the amendment. The buyer should be able to reconstruct both the recommendation and the reason for overriding it.
5. Close the decision and the handoff
The final award record should name the governing requirement version, all eligible revised bids, approved exclusions, the selected scenario, decision owner and supplier communication. Check that the resulting contract or purchase order carries the same quantity, location and specification. A clean comparison table does not help if the old scope is sent downstream.
For a software demonstration, use the same fictional RFQ amendment in each product. Score version control, quote traceability, fair supplier communication, scenario explainability and the purchase-order handoff. Our direct-materials RFQ-to-PO pilot covers the longer downstream test.