Stolen Orbit
ENIT
Let’s talk
FREE TEMPLATE · FILL IN, DOWNLOAD, REUSE

Procurement quotation comparison

Make quotations equivalent before comparing them. AI can help organise information, but missing specifications and ambiguous terms must remain visible until clarified.

By Stolen OrbitRevision

When to use it and what to produce

When suppliers offer different formats, units and conditions for the same purchase and you need a reasoned decision.

A line-by-line and condition-by-condition comparison with source references, missing information and an approved decision.

Fill in the fields below and download your document. The website does not send or save answers: closing the page may lose them. Examples are illustrative and should be replaced with your process data.

Download the complete blank template (.md)

1. Establish common requirements

Agree what you are buying before reading prices. Keep alternatives separate until the person using the product confirms they are equivalent.

See a worked example

Illustrative example: purchase 100 units of a specified component. An offer in packs of 10 needs normalisation; a technical variant remains a separate proposal.

Describe required characteristics, quantity, units, destination and operating conditions to satisfy.

Distinguish conditions that disqualify a proposal from preferences that can be negotiated.

Record required delivery date, who clarifies specifications and who may approve the choice.

2. Normalise and cite

Keep original values beside comparable ones. Do not infer additional costs, availability or equivalence that the quotation does not state.

See a worked example

Illustrative example: one supplier includes shipping and another does not mention it. The second entry remains “clarification needed”; it is not automatically counted as zero.

Record currency, quantity, unit price, shipping and other stated items; separate missing amounts and tax treatment requiring confirmation.

Record stated lead times, offer validity, availability and relevant operating conditions without unsupported interpretation.

Link document, version and line; record clarification requests and received answers.

3. Record the decision

Apply agreed criteria and verify differences that could change the choice. Generated summaries should refer back to the approved original terms.

See a worked example

Illustrative example: faster delivery may justify a higher cost only when the date is confirmed and the owner accepts the operational trade-off.

Describe comparable cost, requirements met, timing and uncertainties that could alter the ranking.

List required answers and who checks specifications, conditions and the final quotation version.

Record selected proposal, rationale, approver and exact references to use in the purchase order.

Pitfalls to avoid

  • Comparing per-pack prices with per-unit prices.
  • Treating an unstated condition as favourable or free.
  • Creating an order from a summary without checking the final quotation version.

Take the next step together.

Use this document to start a discussion about scope, evaluation and project ownership.

Review the text before sending. Only your email is needed alongside the message; other details are optional.