Procurement price comparison, without the spreadsheet rebuild

What procurement price comparison actually involves

Standardizing bid formats

Each supplier's bid arrives as its own file, with its own column names and layout. A real comparison needs them matched to one structure before any price is evaluated — not re-typed by hand into a shared sheet.

Evaluating price on its own first

Price is one input to a sourcing decision, not the whole decision. Comparing it cleanly first — before lead time, minimum order quantity, or payment terms enter the conversation — keeps the price comparison itself honest.

Recording other criteria without letting them skew the price result

Lead time and MOQ matter, but if they're mixed into the same number as price, the comparison stops being a price comparison. Record them alongside the price, visibly, without them changing which bid shows as cheapest.

Keeping a record of the decision

A procurement decision is usually worth being able to show later — which bids were compared, what each quoted, and which was selected. That's a different need from just finding today's cheapest price.

What a price comparison does and doesn't tell you

A clean price comparison tells you, item by item, which bid is cheapest given what's actually comparable between them — same identifier, same currency, same unit of measure. It doesn't tell you whether a supplier will deliver on time, whether their quality is consistent, or whether the relationship is worth the switch. Treat the price result as one input to the decision, not the whole decision — and record the other inputs next to it rather than folding them into a single blended score that hides what actually drove the choice.

Step by step

1. Add each supplier's bid — CSV or XLSX — exactly as received, one per supplier.
2. Map the item identifier and unit cost column for each bid independently; the files don't need to share a layout.
3. Items are matched across bids by identifier, and the lowest usable price per item is marked.
4. Add custom fields for lead time, minimum order quantity, or notes on any bid — informational only, never part of the price comparison itself.
5. Review coverage per supplier and the price-based winner per item, then save the comparison to history if you want a record of it.

Keeping a record of the decision

A sourcing decision is often worth being able to show later — which bids came in, what each quoted, and which was selected. When you're signed in, saving a comparison's structured rows to history keeps exactly that record: not the original files, but the matched items, prices, and the comparison result itself, available to look back on by supplier.

Frequently asked questions

Related comparisons

For the item-by-item mechanics of comparing bids — cheapest price, coverage, basket savings — see comparing supplier quotes. To build the same comparison by hand first, comparing supplier quotes in Excel walks through the formulas. For a shared workspace where your whole purchasing team sees the same comparisons and saved suppliers, see CostRift for purchasing teams.