Three quotes, one table: a comparison template that states its basis before it ranks anything

A quote comparison is not a spreadsheet of prices. It is an argument, made in a table, that one supplier should be chosen on a stated basis — and the table either shows the basis or it hides it. Three quotations stapled together in price order are not a comparison; they are three offers placed next to each other, and the decision that follows them is a preference with a number attached. The template in this piece exists to make the basis explicit before anything is ranked, because a ranking produced before the basis is stated is a ranking someone will have to defend later, in a room, without the documents.

The artefact is the point. A purchase manager produces one comparison per cycle, and it is the document an approver signs, an auditor reads and a successor inherits. Everything else in the cycle — the request, the order, the match — is downstream of it. Get the comparison right and the rest of the file is bookkeeping. Get it wrong, and the error is not corrected later: it is reproduced in the order, matched against the invoice and settled in the bank.

This piece gives the columns, the basis statement that has to sit above them, a worked example of three quotes for the same part in which the last conversion reverses the ranking, the cost of running the template in calls, the first policy question a buyer has to answer — how many quotes to collect — and the one limit no template removes.

The template

Seven columns. They are the minimum for a table that can be signed and later re-read by someone who was not in the room, and each of them exists because its absence produces a specific failure. Table 1 sets them out with the failure each one prevents.

Table 1. The seven columns of a quote comparison, what each holds, and the failure its absence produces. Source: the studio’s purchase manager specification, whose comparison is documents/data_table output against one named basis.

The fourth and fifth columns are where the work sits. A quoted price is a statement about a point in a chain: it holds at a named place, at a named time, on named conditions, and the cheaper of two figures is frequently the one that stops earliest. A supplier quoting ex-works has priced the goods and not the journey; a supplier quoting delivered has priced both and buried the freight in a line the buyer never sees. Both figures are honest. They are not comparable.

The seventh column is the one most often left out, and its absence is the clearest evidence that the table was built to justify a decision rather than to inform one. A basis statement is five parameters and a sentence: currency and rate, unit and quantity basis, delivery point and tax treatment, payment days, warranty period. Every cell above it is converted to those five. Where a conversion cannot be made — where a supplier will not state its warranty exclusions, or a quote’s validity expires before the order can issue — the correct entry is not an assumption. It is a gap, marked, with the question that will close it.

Three is a policy, not a rule

Nothing in accounting, in procurement practice or in any standard requires three quotations. Three is a convention that organisations adopt because it produces a visible spread without turning a purchase into a project, and it is a policy choice that each organisation makes for itself, in writing, with a value band attached. Say so in the template’s header, or the next reader will treat the number as a requirement and defend it as one.

The choice has a price, and it is paid in days rather than in money. Each additional quotation is a request, a chase, an extraction and a row; the last of those is cheap and the first three are not, because they wait on another organisation’s calendar. In the worked example below, two of the three quotes arrived within two working days of the request and the third arrived nine days later. The decision moved with it — and against the organisation’s stated 15-working-day delivery window, nine days of waiting is three fifths of the window spent before a supplier has been chosen. Nothing in the comparison table records that cost, which is why the table should not be the only document in the cycle: the request date and each quote’s arrival date belong in the supplier file, where the pattern is visible over twelve months.

The policy that survives contact with a real month is banded rather than fixed. A small organisation that states, as its own policy, two quotes below a desk-level value, three between desk level and the functional head’s limit, and a competitive tender above that, has made a decision it can explain. An organisation that says “three quotes” and then waives the requirement whenever it is inconvenient has made a decision it will have to explain, badly, to somebody who notices the waivers.

The basis statement

Five parameters, written once at the top of the table, and every cell converted to them.

Currency and rate. One currency, one rate, one date, stated. Where a quote arrives in another currency the converted figure is shown beside the original, and the rate is the one the organisation’s own treasury would have used on the day the comparison was built — not a rate recalled later. A comparison that mixes currencies without a stated rate cannot be rechecked.

Unit and quantity basis. The same unit, and the same quantity. Quantity is the parameter buyers forget, and it is not cosmetic: a supplier’s price for 400 units and another’s price for 500 are two different offers, and putting them in one table as though they were one is the single most common arithmetic fraud in the work — usually committed by accident, which does not make the resulting decision any better.

Delivery point and tax treatment. Delivered to a named address, with duty and non-recoverable tax inside the figure and recoverable value-added tax outside it. A VAT-registered buyer that compares gross invoice values is comparing a tax it will reclaim against a tax it will reclaim, which cancels — and then choosing on the residue, which does not. The recoverable element belongs on the invoice, not in the comparison.

Payment days. Converted to one number at the organisation’s own stated cost of funds, because 60 days from one supplier and 30 from another are not the same offer at the same price. Thirty days of working capital has a price, and it is small, and it is knowable.

Warranty period and exclusions. The period that is actually covered, and what is excluded, since a 24-month warranty that excludes the part that fails is a 12-month warranty with better lettering. Where one quote is short of the organisation’s stated standard, the cost of closing the gap — bought cover, or an accepted risk — is a line in the table.

Worked example: 400 brackets, three quotes

The organisation in this example is illustrative and its policies are stated rather than assumed: 60-day payment terms, a cost of funds of 8 per cent a year, a 24-month warranty as the standard for this class of part, and a delivery window of 15 working days. The quotes are constructed for this piece; no supplier, price or engagement is described. Table 2 sets the three quotations out as they arrived, each on its own terms; Table 3 carries all three to the one basis and adds the arithmetic.

Table 2. Three quotations as they arrived, on their own terms. Constructed for this piece; not a real supplier file.

Four conversions follow, and each one is arithmetic a reader can check.

Alto. Goods $4,960.00, delivered, nothing to add. Payment at 30 days against the 60-day standard means 30 days of cash paid early: $4,960.00 × 8 per cent × 30 ÷ 365 = $32.61. Warranty at 12 months against a 24-month standard leaves a year uncovered, and the organisation’s stated replacement price for cover on this part is $0.35 a unit a year: 400 × $0.35 = $140.00. Normalised total: $5,132.61.

Brenner. Goods $4,340.00, freight $420.00, duty at 4.5 per cent of $4,340.00 = $195.30. Landed: $4,955.30. The recoverable VAT that the invoice will carry — 20 per cent, $991.06 — is excluded, because it is reclaimed. Payment at 30 days: $4,955.30 × 8 per cent × 30 ÷ 365 = $32.58. Warranty meets the standard, so nothing is added. The lead time is the problem: 25 working days against a 15-day window, and the supplier’s own expedite option is $260.00 to bring it to 12. Normalised total, with the expedite bought: $5,247.88. Without it, the order arrives ten working days late and the table says so instead.

Cortez. Goods $5,560.00, delivered. Payment at 60 days matches the standard, so no adjustment. Warranty at 18 months is six short, and six months of cover on 400 units is 400 × $0.35 × 0.5 = $70.00. Normalised total: $5,630.00.

Table 3. The same three quotes normalised to one basis: delivered, net of recoverable VAT, 60-day payment, 24-month warranty, inside a 15-working-day window.

The ranking collapses, and then reverses. On quoted unit price the order is Brenner at $10.85, Alto at $12.40, Cortez at $13.90 — a 28 per cent spread between the cheapest and the dearest. On landed cost the order is Brenner at $4,955.30 and Alto at $4,960.00, with $4.70 between them and Cortez $604.70 behind: the 28 per cent spread has become nine-tenths of one per cent at the top. On the full basis Alto wins at $5,132.61, $115.27 clear of Brenner, which is 2.2 per cent; Cortez is 9.7 per cent behind the winner. The supplier that looked 12.5 per cent cheaper than Alto on the unit price is 2.2 per cent more expensive once the freight, the duty, the expedite and a year of warranty cover are in the same column.

What the table does not settle is the remaining $115.27. That gap sits inside the uncertainty of two of its own inputs — the expedite price, which assumes the supplier holds a slot, and the warranty replacement rate, which is the organisation’s own stated price rather than a market one. A comparison that produces a winner by two per cent has produced a tie with a preference, and the honest way to record it is the term that is not monetised: Brenner’s 24 months against Alto’s 12 is an unquantified advantage, and Alto’s 10-day lead time against a 25-day one is a quantified one that the expedite has already paid for. The decision follows from which of those the buyer actually cares about, and the table’s job is to put the question in front of the person who does.

Two smaller points sit in the same documents. Cortez’s quantity break is not a term in this comparison at all: 500 units at $12.95 is $6,475.00 against 400 units at $13.90, which is $5,560.00, so the break buys 100 extra units for $915.00 — $9.15 each — and it is only cheaper if those 100 units are used before they obsolesce. A break that changes the quantity changes the basis, and a table that admits the break without pricing it has let a second offer into a comparison of a single quantity. Brenner’s 14-day validity is the other: the comparison was built on day 12, and a quote that expires before the order issues is not a price, it is a deadline.

The cost of the comparison

The template is a document, and documents carry no per-call price. What is priced is the reading and the arithmetic: three quote documents extracted, one call to build the comparison as a data table, and one read-back before it goes to the approver. Five calls at the measured rate of $0.00700 is $0.03500 a cycle. At the metered ceiling of $0.00955 a call it is $0.04775; at Qwen flash’s exact rate of $0.00875, which is the figure that circulates for this call and belongs to a different service, it would have been $0.04375 for work that costs $0.03500.

Twenty cycles in a month is 100 calls and $0.70000. Sixty cycles — the volume the purchase manager’s own page assumes — is the 300 calls and $2.10000 that page states, five a cycle, which is the same count reached from the other end.

That figure is small enough that the interesting cost is elsewhere. Five calls does not include the days spent waiting for the third quote, the two rounds of correspondence spent closing a gap the template marked, or the hour a person spends deciding what the 2.2 per cent is worth. Those are the costs the policy on quote count is actually trading against, and none of them appears in any table on this page, because none of them has been measured.

What the template cannot do

A template fixes the shape of a comparison and cannot fix its inputs. Where a supplier won’t state its warranty exclusions, the row is a gap; where a quote’s validity has lapsed, the row is out of date; where two quotes answer different scopes, the table will happily place them side by side and produce a number that means nothing. The columns make those failures visible. They do not prevent them, and a well-shaped table is more dangerous than a messy one for exactly that reason: it looks like a decision.

The second limit is that the comparison cannot choose the basis for the organisation. Delivered cost, landed cost, total cost of ownership over the life of the part, and lead time are four defensible bases, and they produce four different winners from the same three quotes. The table can state which one was used; it cannot say which one is right, because that is a judgement about what the item is for. A part that stops a production line and a part that sits in a stores bin should not be bought on the same basis, and no template knows which is which.

The third is arithmetic’s own limit. A comparison built on a stated cost of funds, a stated warranty replacement price and a stated expedite charge is a model, and its output is as good as those three assumptions. The organisation’s 8 per cent is a policy figure, not an observed cost of capital; the $0.35 a unit a year is a price for cover, not a measure of what a failure costs. When the gap between first and second place is 2.2 per cent, the assumptions are larger than the result, and the table should say so in the row rather than in a footnote.

The fourth is the one that matters most, and it is structural rather than technical. The comparison is evidence of a decision taken on documents. It is not evidence that the documents were true. A quote can be padded, a specification can be written around one supplier’s product, and a third quote can be obtained from a supplier who was told what to bid. None of that is visible in a table whose columns are correct, and a buyer who wants the control has to look at how the requirement was written and who chose the three suppliers — which is a different document, in a different part of the file.

The decision

Write the basis before the quotes are read, and put the five parameters in the header of the table where the approver has to see them. A comparison whose basis was chosen after the quotes arrived has been chosen to produce a result, and the difference between the two is invisible in the finished file.

Then fix the basis in policy, by band, in writing — two quotes or three, and at what value — and record the arrival date of every quote in the supplier file, because the days a third quote costs are the price of the policy and the only way to know whether it is worth paying is to count them over a year.

Then read the ranking twice. Once as quoted, to see what the suppliers think they are offering. Once on the basis, to see what the organisation would actually pay. Where the two rankings differ, the difference is the negotiation, not the decision: a supplier whose price wins on its own terms and loses on the organisation’s has been asked the wrong question, and the answer is a conversation about freight, terms or lead time rather than a note in the file.

Where this goes

• The pillar: x402.review/2026/10/31/commercial-operations/ — the job, the record and the approvals between the two ends
• The role that builds it: studio.x402.press/roles/purchase_manager — the comparison, the approval record, the order and the match
• The other side of the table: studio.x402.press/roles/sales — the proposal that becomes the quotation being compared
• The service it buys: x402.press/services/deepseek/ — the canonical price, seven chains
• The review: x402.review/2026/10/31/deepseek-review/ — the measured handshake and what it does not promise

Method note

The price was read from the live 402 challenge on Base on 31 October 2026, outside DeepSeek’s weekday peak windows of 01:00–04:00 and 06:00–10:00 UTC: 7000 atomic units for deepseek-v4-flash under exact, which is $0.00700, and 9550 under upto at the max_tokens tested, which is the ceiling. Qwen flash answers 8750 on the same chain, $0.00875, and that figure appears here only where it is named as the rate belonging to a different service. Call counts are planning assumptions, stated in the cost section and repeated in the arithmetic; the five calls a cycle reconcile with the purchase manager’s own page at three hundred calls for sixty cycles.

The three quotes, the supplier names and the organisation’s stated policies are constructed for this piece and labelled as such. No real supplier was asked to quote, no purchase was made, and no figure for the time a real comparison takes has been measured here: the nine-day wait for the third quote is this example’s, not an observation. The cost of funds, the warranty replacement price and the expedite charge are the illustrative organisation’s stated figures, not market norms, and a reader who substitutes their own will get a different winner from the same table — which is the point of stating them.

x402.review is written and edited by N.P. Vincent. The publication is connected to x402.press, which sells the services reviewed here; that interest is disclosed on every piece that touches a service, and it is stated here rather than left to inference.

Filed under Jobs · Tags: procurement, quotes, comparison, template