Catch-Weight Purchasing: Why 'Price Per Kilo' Breaks in Most Back-Office Systems
Catch-weight items like whole fish, primals, and fresh produce are invoiced by actual weight, not a fixed unit — and most back-office systems simply cannot handle that gap cleanly. Here is why it matters and what a purpose-built food operations layer does differently.
The Problem Nobody Talks About at the Purchasing Meeting
A whole salmon arrives. The order said 4 kg. The actual fish weighs 4.3 kg. The invoice reflects 4.3 kg at the agreed price per kilo. Simple enough in the real world — but watch what happens inside a typical back-office system.
Most ERP and inventory tools are built around a fixed unit logic: you order one item, you receive one item, you pay one price. Catch-weight purchasing breaks every one of those assumptions. The quantity received, the quantity invoiced, and the quantity that hits your stock ledger are three different numbers, and most systems have no native way to reconcile them without manual workarounds.
What “Catch-Weight” Actually Means in a Kitchen Context
Catch-weight applies to any product invoiced by actual weight rather than a nominal unit — whole fish, bone-in primals, fresh cheeses sold by the wheel, bulk produce bought by the crate and billed per kilo. The nominal order quantity is a planning estimate. The invoiced quantity is whatever landed on the dock that morning.
The gap between those two numbers is not an error — it is the normal operating condition. Yet most purchasing modules treat any deviation as a discrepancy to be cleared manually, which means someone on the team is spending time each week reconciling lines that should have reconciled themselves.
Where Standard Systems Fail
Stock valuation goes stale. If the system posts the ordered weight to inventory rather than the received weight, your cost-per-portion figures are wrong before the fish even hits the prep table.
Recipe costing drifts silently. Linked recipe tools pull a unit cost from the purchasing record. When that record does not reflect actual received weight, every dish containing that ingredient carries a cost assumption that is quietly incorrect.
Lot traceability becomes guesswork. Catch-weight items often arrive as single lots with a single label but variable individual weights. Systems that track by nominal unit cannot correctly associate the right weight to the right lot — which matters enormously the moment you need to run a recall or respond to a supplier audit.
FEFO rotation breaks down. First-Expired-First-Out logic depends on accurate lot quantities. Inflated or deflated stock figures corrupt the rotation sequence, leading to waste you cannot see and compliance exposure you cannot document.
What a Purpose-Built Food Operations Layer Does Instead
A system designed for professional kitchens and food production treats actual received weight as the primary fact, not a footnote. Every downstream record — stock valuation, recipe ingredient cost, lot quantity, FEFO queue — is updated from that single confirmed number at goods receipt.
The purchase order becomes a planning tool, not a contract carved in stone. The invoice match is made against actual weight. The stock ledger reflects what is physically in the location. Recipe costing stays in sync without manual intervention. And when a lot needs to be traced — whether for a supplier dispute or a regulatory inspection — the weight attached to that lot is the real one.
This is not a nice-to-have for high-volume operations. It is the difference between food cost data you can act on and food cost data you can only approximate.
Closing the Loop with FoodOps
FoodOps is the Odoo-based back-office layer built specifically for food and beverage operations, synced directly to CalcMenu. It handles real-time stock and inventory by location, catch-weight purchasing, lot traceability, FEFO rotation, and HACCP compliance — without requiring an existing ERP. Catch-weight items are received at actual weight, and that number flows automatically into costing, stock, and traceability records, removing the manual reconciliation step that quietly consumes time and introduces error in most conventional setups.
Find out more at FoodOps, or Schedule a call to walk through how it handles your specific purchasing workflow.
Explore CalcMenu's recipe management software for restaurants, hotels & catering to see how it applies to your kitchen.
Related sectors
Comments
Comments coming soon.