Blog · Procurement and supply chain · Procurement
Normalize comparable supplier purchases to an approved reference unit before interpreting case-price changes or estimating a fixed-quantity scenario.
Compare supplier prices in a reviewed reference unit before describing a pack-price change as a saving. A $22 case can be more expensive than a $24 case if it contains fewer comparable items. The key is to establish what the quantities mean, not merely divide amounts by whichever quantity column is available.
Microsoft's unit-of-measure documentation distinguishes standard conversions from product-specific conversions. That is a useful source-system example: a generic relationship between unit labels may be insufficient for a particular product or pack version.
Use one purchase or invoice line, with a reviewed product-equivalence key and effective unit conversion. Inputs include product and supplier keys, raw description, pack identifier, pack version, invoiced quantity and unit, reference unit, conversion factor, net amount basis, currency, date and conversion evidence.
Record the cutoff and period being compared. A conversion from cases to individual items may change when the pack changes. Do not apply today's factor to last year's purchases unless the evidence supports it.
The contracted-price comparison guide owns the broader question of entitled prices. This method makes quantity and price bases comparable; it does not establish contractual entitlement or recommend a substitute product.
Reference quantity equals purchased quantity multiplied by the approved reference units per purchased unit. Comparable price per reference unit equals the selected line amount divided by reference quantity. Report a missing or zero quantity as unavailable rather than forcing a zero price.
Use the same treatment of discounts, freight, taxes and credits in both periods. If a broader landed-cost comparison is needed, show those components separately and state the allocation policy. An invoice price excluding freight is not directly comparable with an all-in quote including freight.
Follow the credit, tax and FX method for the approved monetary basis. Keep source currencies visible; the synthetic example below uses USD throughout.
The following is a synthetic comparison reviewed on October 6, 2026. The items are confirmed equivalent for the demonstration, amounts exclude taxes and freight consistently, and each item is the reference unit.
| DEMO pack | Items per case | Case price | Price per item |
|---|---|---|---|
| Earlier pack | 12 | $24.00 | $2.00 |
| Current pack | 10 | $22.00 | $2.20 |
The case price falls by $2, or 8.33% rounded: ($22 − $24) ÷ $24. The item price rises by $0.20, or 10%: ($2.20 − $2.00) ÷ $2.00. Both statements are correct because they measure different quantities.
For a fixed requirement of 120 items and whole-case purchases, the earlier pack requires 10 cases costing $240. The current pack requires 12 cases costing $264. The scenario increases purchase cost by $24 under these exact assumptions. It is not an achieved saving, a recommendation to buy the earlier pack or proof that the current product is inferior.
The decision is to review the unit-price movement with the buyer and confirm whether any specification, discount or freight change explains it before labeling the difference a price issue.
Weight, concentration, usable yield and item count are not interchangeable measures. A kilogram-to-liter conversion may require product-specific density evidence. A concentrated product may need a reviewed usage basis rather than a nominal volume comparison.
Whole-pack rounding, minimum orders and shelf-life constraints can change a fixed-demand scenario. Display the rounding rule and excess quantity. Do not assume the buyer can purchase fractional cases or consume every purchased unit.
If product equivalence is disputed, preserve the candidate pair with an unknown comparison status. Excluding it from the comparable-price calculation should not erase its amount from the total source reconciliation.
Report how much purchase value and quantity has reviewed conversions, how much has unknown conversions and how much is outside the selected product scope. Inspect abrupt conversion-factor changes and duplicated unit mappings before interpreting price movement.
Use three-way match exception analysis when invoice and order units create document discrepancies. A correctly normalized price comparison and a matching-policy result remain distinct outputs.
Start with one product family and one dated pack change. Ask whether the result explains a purchasing decision under the available evidence. Keep product-quality and specification judgments with the responsible buyer.
The procurement review example shows a bounded evidence pack. Contact Covirage with the raw unit fields and reviewed conversion evidence to discuss a scoped comparison.
Not necessarily. A smaller case can cost less while its price per comparable item rises. Compare the approved reference-unit price as well as the case price.
No. Product specifications, packaging and usable quantity need review. Unknown equivalence or conversion should remain an exception, not become an assumed match.