Order a carton of lamb racks, a bin of snapper fillets or a case of cheese wheels and the label might say one thing, but the scale at the other end says another. That's catch-weight — products sold in a nominal unit like a carton or a case, where the real weight varies every single time. It's completely normal in meat, seafood and some produce and dairy lines. The problem is that most ordering and invoicing software was never built to handle it, so distributors end up bolting a manual weight sheet onto a system that assumes every carton weighs the same.
Where catch-weight breaks a normal order-to-invoice flow
A standard order system multiplies quantity by unit price and calls it done — ten cartons at a fixed carton price, invoice generated. Catch-weight products don't work that way: the customer might order ten cartons, but what actually gets picked, packed and shipped is ten cartons at ten slightly different weights, and the agreed price is per kilogram, not per carton. If the system can't capture the real weight against the order, someone ends up re-keying invoices from a handwritten weight sheet, or — worse — invoicing the nominal weight and quietly under- or over-charging on every single line.
That gap shows up in three places at once: the customer's invoice doesn't match what they actually received, stock on hand drifts away from what's really in the chiller, and margin reporting is built on a weight that was never real to begin with.
What catch-weight pricing should actually look like
Fixing this isn't about a generic "catch-weight" toggle — it's about the actual weight flowing through the same system as the order, from pick to invoice:
- Customers order in whatever unit makes sense to them — carton, case, bin — without needing to know the exact weight up front
- The real weight is captured at pick or pack, against that specific order line, not estimated afterwards
- Invoicing uses the actual captured weight and the agreed price, so the invoice reflects what was really shipped
- Stock on hand is adjusted by real weight moved, not a nominal carton count
Done this way, "what do we invoice this customer" stops depending on a weight sheet someone has to chase down after the truck's already left, and margin reporting reflects what actually moved rather than a rounded-off average.
Why this compounds at volume
A handful of catch-weight cartons a week is a manageable manual correction. Hundreds of cartons a day, across dozens of customers each with their own agreed pricing, is a different problem entirely — and it's exactly where small, unnoticed gaps between nominal and actual weight add up to a real margin leak, invoice disputes, and stock counts nobody quite trusts. It's the same pattern we see across food and beverage distribution generally — the pressure points are specific to the category, but the fix is the same: real data flowing through one system instead of being reconstructed by hand afterwards.
Built into your system, not a bolt-on module
Catch-weight handling isn't something we sell as an off-the-shelf feature, because how it needs to work varies by product, supplier agreement and customer — some businesses invoice strictly on actual weight, others round to agreed bands, others handle it differently again by product line. Tell us how your catch-weight products are ordered, weighed and invoiced today, and we build that logic into your Cognit system so it works with your real pricing, stock and invoicing — the same approach we take for food distribution more broadly: tell us your problem, we build it into your system.
Getting catch-weight off the weight sheet
If your invoices for meat, seafood or other variable-weight lines still depend on a handwritten weight sheet making it back to the office, it's worth talking through how that should actually flow through your system. See pricing or get in touch to talk through your catch-weight products specifically.
Frequently asked questions
What is catch-weight, and why does it break normal ordering software?
Catch-weight is when the actual weight of a unit — a carton, a bin, a side of meat, a tray of fillets — varies from item to item, even though it's ordered and often priced by a fixed unit like a carton or a case. Most ordering and invoicing software assumes one unit always weighs the same, so it can only invoice what was ordered, not what was actually picked, packed and shipped. That forces distributors into manual weight sheets and invoice corrections after the fact.
Does Cognit have catch-weight pricing built in already?
Catch-weight is exactly the kind of requirement we build into a distributor's system rather than sell as a generic checkbox feature — because how it needs to work differs by product, supplier and customer agreement. Tell us how your catch-weight products are ordered, weighed and invoiced today, and we'll build that logic into your Cognit system so ordering, stock and invoicing all use the real weight.
Can customers still order by carton or case, even if they're invoiced on actual weight?
Yes — that's the point. A customer can order in the units that make sense to them (cartons, cases, bins), while your system captures the actual weight at pick or pack and invoices on that real figure, with the ordered quantity and the invoiced weight both visible and reconciled, not fought over after delivery.
How does catch-weight affect stock and margin reporting?
If stock is only tracked by carton or case count, your on-hand figures and your margin are both slightly wrong, and the gap grows with volume. Tracking actual weight through stock, sales and invoicing means on-hand quantities and margin reporting reflect what you really moved and were really paid for, not a nominal average.
Is this relevant outside meat and seafood?
Any product sold in variable-weight units has the same problem — cheese, produce, some bakery and butchery lines. If your business invoices customers on a weight that's rarely the same twice, catch-weight handling is worth building into your system regardless of which food category you're in.
