Account for the work before comparison.

Supplier offers and customer requests often arrive through separate emails and attachments. Repeatedly copying product references, prices and quantities creates another file to maintain before a buyer can assess the offer.

The method below describes what a reliable comparison should preserve. In Pycache, connected inbox and file workflows can capture and structure supported material automatically. Representative Excel and CSV files and supported email layouts establish the intake scope. Additional formats, including PDFs, are assessed separately; source issues remain visible for review.

1. Keep the original and identify each row.

Retain the supplier workbook unchanged. Record the filename, sheet, row, supplier, received date and offer validity beside your comparison. A later correction should lead back to the value you actually received, rather than a price copied into an untraceable summary.

Import EAN as text to preserve leading zeros. Check size, variant and pack details too. Flag uncertain matches for review; do not force every row into a match. A missing product identifier needs investigation before the price becomes comparable.

2. Put prices on a common basis.

Record whether the quoted price is for one unit, a pack or a carton. Divide a confirmed pack price by the units in that pack. Preserve the original amount and pack quantity alongside the calculated unit price, so another buyer can check the calculation.

Separate currencies and tax bases. If you convert currencies, retain the original currency, rate, rate source and date. A blank freight or duty field means unknown, not free. Keep unallocated charges separate until you have an agreed basis for comparing the total cost.

Worked example: fictional offers for the same confirmed product
TermSupplier ASupplier B
Pack size12 units24 units
Pack price, excluding VAT£72£132
Calculated unit price£72 ÷ 12 = £6£132 ÷ 24 = £5.50
Minimum order for this product4 packs = 48 units5 packs = 120 units
Goods total at that minimum£288£660
Stated availabilityStock; delivery to confirmPreorder in 30 days
Freight and supplier-wide minimumNot suppliedNot supplied

3. Compare the order you would actually place.

Assume the requirement is 48 units within ten days, both prices are GBP excluding VAT, and no discounts apply. Supplier B has the lower unit price, but requires 120 units and later availability. Supplier A's minimum matches the requested quantity; its delivery date, freight and any supplier-wide minimum still need checking.

The £288 and £660 figures buy different quantities. Their difference is not a like-for-like saving. Review excess quantity, expiry where relevant, stock versus preorder timing and order increments. A supplier-wide minimum order value is distinct from the minimum quantity for a particular product.

4. Add history, demand and the decision.

Compare with the previous purchase only after checking its date, currency, quantity and terms. Add known customer requests, keeping enquiries separate from confirmed orders. Do not count one request repeatedly because several suppliers can fulfil it.

Record the next action and its reason: investigate availability, clarify a pack, negotiate, review for approval or leave the offer. Keep unknowns visible. Review the whole scope being approved before Sales prepares a customer offer; no formula replaces that approval.

Use the example as a starting point.

Download the example comparison CSV

The CSV contains the two fictional rows above, source references and columns for unresolved terms. EAN is intentionally blank: add a verified identifier, imported as text, for your own comparison. A separate example product key links the sample rows.

It is a plain CSV, with no macros or formulas. Calculated values are static examples: recalculate them when changing prices, packs or minimums. Blank freight, validity and supplier-wide minimum fields are not zero. Keep your original files and extend the sheet for your actual commercial terms.

When repeated file comparison needs a shared workflow, see how Pycache supports supplier review. An ERP connection can be scoped around the records your team already maintains.