A price is comparable only after the requirement is comparable

Two quotations can use the same product name and still describe different outcomes. Fix the specification, tolerance, unit, packaging, documentation, delivery place and required date before comparing prices. If compatibility is uncertain, record the test that will resolve it. A low number beside an unclear requirement is not a saving; it is an unanswered question.

The comparison should name the result the operation needs: for example, 10,000 accepted components ready for use at one location by an agreed date. This prevents a larger order, a different pack size or an unverified substitute from looking cheaper merely because the quoted line is smaller.

Compare cost per accepted unit

In the fictional table, Offer A quotes 0.92 per unit and Offer B quotes 1.02. After applying transparent scenario assumptions for quantity, freight, inspection, unusable units and handling, A models at 1.1394 per accepted unit and B at 1.1254. The point is not that the second offer must win. The point is that the quoted unit price did not answer the purchasing question.

Keep the arithmetic inspectable. Do not mix a total with its components, subtract rejects twice or treat an unverified estimate as observed performance. Replace assumptions with pilot, receiving and quality data when those observations become available.

Keep important differences visible

Lead time, compatibility, traceability, response time, replacement process and return handling may affect the decision without supporting a credible monetary value. Keep them as separate fields with an owner, evidence and confidence level. A single weighted score can help discussion, but it should not conceal which facts are known and which judgments remain.

Missing information has operational value too. A supplier that cannot confirm a tolerance, delivery window or rejection process has not supplied a comparable offer. Mark the gap and set a deadline to resolve it instead of filling the cell with optimism.

Use a small acceptance gate

Before scaling a new source, agree on the sample or pilot, inspection method, acceptance threshold, documentation, disposition of rejected material and replacement path. Record who may release the order and what evidence is required. The purchasing decision then becomes a controlled transition rather than a debate over one price column.

A practical checklist is short: same specification, same delivery basis, same accepted quantity, explicit scenario assumptions, visible exceptions and a defined acceptance process. Buy the result the operation can verify, not the cheapest line it cannot explain.

See you in the next note.

← Back to articles