Skip to content
← Resources
Invoice workflows

Normalize pack sizes so your numbers tell the truth

Convert cases, formats and units to a common basis before comparing prices or costs.

Two invoices list mozzarella at €89 per case and €94 per case. The first looks cheaper until you notice it holds 6Γ—2 kg blocks while the second holds 10Γ—1 kg. Per kilo, the 'expensive' one costs €9.40 against €7.42 β€” a 27% gap hiding inside identical-looking paperwork. This is why pack normalization precedes every serious analysis: price variance detection, supplier comparison, recipe costing. Skip it and you are not measuring your kitchen; you are measuring formatting differences between vendors' order systems.

Choosing the right reference unit

  • Cookable unit beats purchase unit. Price per kilo of usable product, per litre, or per portion β€” whatever survives into the pan.
  • One unit per family. All cheeses in €/kg, all oils in €/L. Mixed units inside a family make comparisons impossible.
  • Record the conversion chain. Case β†’ packs β†’ net weight, each step written down. Mental math is where errors breed.
  • Yield belongs in the number. If product A needs trimming and product B doesn't, their per-kilo prices are lying until yield adjusts them.

A worked example

Same oil, three pack formats

You receive olive oil in three formats across two months: 12Γ—1L cases at €54.00, 6Γ—3L tins at €76.50, and a 5L bag-in-box at €39.90. The case prices differ wildly; the litres tell one story.

12Γ—1L @ €54.00€4.50 / Lreference format
6Γ—3L @ €76.50€4.25 / L5.6% cheaper per litre
5L BIB @ €39.90€7.98 / Lpremium format β€” check spec!

The bag-in-box looks cheapest as a package but costs nearly double per litre β€” usually a different product grade. Normalization surfaces exactly these traps.

Interactive example Β· price spread

Spread between your highest and lowest quoted unit price: €6.30 (€39.90 β†’ €46.20). Compare the quoted prices with each supplier. This is a price difference, not a savings projection.

Building the habit

  1. 1Define units for your top 30 lines. Cover 80%+ of spend first: assign each recurring product a reference unit and write down its current conversion.
  2. 2Convert at entry, not at analysis. The moment an invoice line enters your tracking, reduce it to per-unit price. Analysis-time conversion guarantees inconsistency.
  3. 3Flag pack changes immediately. When a supplier switches from 12Γ—1kg to 6Γ—2kg at the same case price, the unit price just moved 0% β€” but most systems record nothing. Make pack changes visible events.
  4. 4Recheck conversions quarterly. Suppliers change pack sizes without announcements. A quarterly audit of conversion factors catches silent drift before it corrupts months of data.

FAQ

Do I need software for this?
No. A spreadsheet with columns for case price, pack config, net units, and computed unit price covers most kitchens. Software earns its keep by automating conversion at invoice entry and flagging pack changes for you.
What about items sold per piece, like steaks?
Count pieces per case and use price per piece, adjusting for trim if you buy unportioned cuts. The principle is identical: express everything in the unit your kitchen actually consumes.
How does this interact with price variance checks?
Variance detection compares unit price over time for the same product. Without normalization, a pack change masquerades as a price jump (or hides a real one). Normalized units are what makes variance signals trustworthy.
Who should maintain the conversion table?
One named person β€” usually the chef or purchaser β€” with changes announced to everyone who reads the numbers. Unowned tables rot; owned ones get corrected.

Keep reading

Want to review your purchasing?

Submit the details and we will confirm which invoices are useful.

Review 3 invoices free