The real problem isn’t different formats—it’s different assumptions
When five suppliers reply in five formats, the headache isn’t the PDF vs. Excel debate. It’s that each quote quietly bakes in assumptions: what’s included, what’s optional, what unit of measure they used, whether delivery is inside the price, whether warranty is standard, and whether they bundled “helpful extras” that make their total look higher (or suspiciously lower). If you compare totals at this stage, you’re not comparing vendors—you’re comparing interpretations of your requirement.
The fastest way to regain control is to force every quote into the same structure, even if the suppliers didn’t. And next time, prevent the mess by issuing that structure up front so you aren’t rebuilding it under deadline pressure.
Prevention: issue a pricing table (or BoQ) that makes comparison automatic
If you want comparable quotes, you have to give suppliers something comparable to fill in. A standardized pricing table (or Bill of Quantities for works/services) does two things: it anchors scope and it forces the same unit economics across suppliers. You can still allow alternatives, but they must sit next to the baseline rather than replacing it.
What to include in the table (minimum viable version)
Line item ID (your ID, not theirs) and description written in plain language
Unit of measure (each, hour, month, kg, site, lot) and required quantity
Unit price field and extended line total field (so you can spot math errors)
Currency and tax treatment (prices excl. tax vs incl. tax; specify one)
Incoterms / delivery terms (or at least “delivery included: yes/no”)
Lead time field and validity period
Warranty/support fields: duration, response time, what’s included
A separate section for one-time fees (setup, tooling, onboarding) and recurring fees (subscription, maintenance, call-out)
A common mistake is letting suppliers “respond in their own format” because it feels supplier-friendly. It is—until you’re reconciling five different scope definitions the night before an internal review. If you want flexibility, add an “Alternative offer (optional)” section rather than letting the alternative replace the baseline.
Rules to write into the RFQ so suppliers can’t wriggle out
“Pricing must be entered into the attached pricing table. Supplier quote may be attached, but the table is the basis of evaluation.”
“Any bundled items must be broken out to line level (materials, labor, freight, warranty, support).”
“Any deviations from specification must be listed in a deviations log.”
“If an item is included at no charge, enter 0.00 and note ‘included’—do not omit the line.”
“State assumptions explicitly (e.g., minimum order quantities, packaging, site access, working hours).”
You’ll get pushback from some suppliers (“our system can’t do that”). Let them attach their system output—but keep your table mandatory. If they can’t populate a spreadsheet, that’s a signal about how painful the relationship will be when you need billing fixes, credits, or change control.
Recovery: you already have mismatched quotes—now what?
When the quotes are already in your inbox, the goal is not to create a perfect model. The goal is to create a single comparison view that is fair, auditable, and good enough to support a decision. You’re going to build a normalized matrix and then chase only the gaps that change the outcome.
Step 1: pick a “master scope” and lock it
Choose one scope baseline to normalize against: your RFQ requirement, a BoQ, or a cleaned-up list of deliverables. Do not let the most detailed supplier quote become the scope by default—it usually includes extras that were never requested. Your master scope becomes the rows in your spreadsheet.
Step 2: build the normalization matrix (the spreadsheet you wish you had sent)
Create one sheet called “Pricing Matrix.” Each row is a line item from your master scope. Each vendor gets the same set of columns. Don’t start with totals—start with unit price and quantity so you can see where the numbers come from.
Columns A–F (common): Line ID, item description, unit of measure, quantity, spec/notes, evaluation rule (mandatory/optional)
Per vendor columns (repeat for Vendor A, B, C…): unit price, line total, included? (Y/N), quoted unit of measure, assumptions/notes, source reference (page/line from quote)
The “source reference” column sounds fussy until someone challenges the award. Being able to point to “Vendor B quote p.3, line ‘Installation & commissioning’” saves hours and keeps the conversation factual.
Step 3: unbundle what’s bundled (without guessing)
Bundling is where comparability dies. One supplier quotes “All-in project fee,” another itemizes labor, travel, materials, and testing. Don’t punish transparency. If a supplier bundles, ask them to split it into the same buckets you’re using—even if the commercial offer stays all-in.
Ask for a commercial breakdown: materials vs labor vs freight vs warranty/support vs other fees
If they refuse, treat the bundle as a single line item and mark all sub-lines as “Not itemized (bundled)”—then flag it as a comparability risk
Watch for “included” items that are actually conditional (e.g., “training included if remote,” “freight included for full truckload”)
A trap: trying to reverse-engineer a bundle by dividing totals across items. That creates fake precision and can bias the outcome. If you can’t get a breakdown, record it as a risk and escalate it as part of evaluation.
Step 4: separate unit price from total cost of ownership (TCO)
Unit price answers “how much per thing.” TCO answers “how much to run this decision for its useful life.” Many quote comparisons fail because they mix those two ideas in the same number. Keep them separate: compare like-for-like unit prices first, then layer in ownership costs in a controlled way.
One-time costs: setup, tooling, onboarding, implementation, site surveys, commissioning
Recurring costs: maintenance, subscription, support tiers, calibration, consumables, license renewals
Usage-driven costs: per-call-out fees, overtime rates, travel rates, minimum order quantities
Risk/contingency items you can price: extended warranty, spares, service credits, performance penalties (if applicable)
If you’re stuck on what time horizon to use, pick one that matches your internal decision: 12 months for a pilot, 36 months for many services, or the expected asset life for equipment if you have it. Document the horizon in the sheet so nobody later argues the math was “wrong” when it was really just a different timeframe.
Step 5: normalize the “gotchas” that make totals misleading
Two quotes can have the same total and still be miles apart. Normalize these items explicitly; don’t bury them in notes.
Tax: confirm whether prices exclude or include VAT/sales tax; don’t mix treatments
Freight/delivery: included, estimated, or billed at cost; note Incoterms if relevant
Lead time and availability: faster delivery can be worth more than a small price gap
Payment terms: differences affect cash flow; record them even if you don’t monetize them
Price validity and escalation: short validity periods can be a hidden risk
Minimum order quantities and pack sizes: can inflate real spend vs quoted unit price
One opinionated rule: if a quote is missing a required line item, don’t “assume included.” Mark it as “Not quoted” and force clarification. Assumptions are how procurement ends up owning someone else’s mistake.
A simple template you can rebuild in Excel (and reuse next RFQ)
Below is a structure that works for most indirect spend, services, and straightforward goods. It’s not fancy, but it produces a clean audit trail and makes supplier clarifications targeted instead of chaotic.
Sheet 1 — Scope & Assumptions: master scope lines, units, quantities, and any fixed assumptions you used (hours, sites, usage volumes)
Sheet 2 — Pricing Matrix: line-by-line comparison with unit price, totals, included flags, and source references
Sheet 3 — TCO Summary: one-time + recurring totals per vendor across your chosen time horizon
Sheet 4 — Clarifications Log: question, vendor response, date, and what changed in the matrix
Sheet 5 — Deviations & Risks: non-compliances, bundling, exclusions, conditional inclusions, and commercial risks
If you only build two sheets, make it the Pricing Matrix and the Clarifications Log. Those two alone stop most arguments later because they show exactly what was compared and what was confirmed.
How to ask for clarifications without restarting the whole process
Suppliers often interpret a clarification request as a negotiation or a rejection. Make it clear you’re standardizing, not haggling. Send a short, structured list and reference your line IDs so they can respond quickly.
“For Line 12 (Installation), please confirm unit of measure and whether travel time is included.”
“For Lines 18–22 (Support), please split the bundled fee into: support subscription, SLA uplift, and per-incident charges (if any).”
“Please confirm whether pricing is exclusive of tax and whether freight is included to [delivery location].”
“Please confirm warranty duration and what actions void warranty (if any).”
“Please confirm price validity period and any escalation after that date.”
If a vendor’s quote is so vague you need ten clarifications, that’s information. It may still be the right supplier, but you should treat “quote quality” as a delivery risk and reflect it in evaluation notes.
The uncomfortable truth: the cheapest quote is often the least comparable
Low totals are sometimes real efficiency. They’re also sometimes missing freight, missing commissioning, assuming unrealistic volumes, or quietly limiting warranty. A standardized table doesn’t magically make suppliers honest, but it makes omissions visible and forces the conversation onto specific lines instead of vibes.
Once you’ve normalized quotes into a matrix, awarding becomes less dramatic: you can explain the decision in rows and columns, not in gut feel. And the next time you run an RFQ, you’ll send the table first—so the “five formats” problem doesn’t get a second chance.