الإجابة المختصرة
Ham is bought, stocked and picked by the case, but sold and paid for by the kilo, and no two cases weigh the same. Catch weight keeps both numbers: the nominal weight you plan with and the actual weight on the scale.
Two weights for one case
A case of cured ham is listed at a nominal 10 kg. The scale says otherwise. One case is 10.4 kg, the next is 9.7 kg and the third is 10.2 kg. The same is true of cheese wheels, whole fish, melons by the crate and a rack of lamb. The unit is fixed; the weight is not.
In a conventional item set-up a case converts to kilograms at a fixed ratio. That is fine when every case holds the same amount, and misleading when it does not. The supplier invoices the real weight. The customer is quoted a price per kilo. The warehouse counts cases. Somebody has to carry the difference.
Illustrative figures chosen to show the arithmetic; they are not customer data and not from our test runs.
| Nominal | Actual | |
|---|---|---|
| Three cases | 30.0 kg (3 x 10.0) | 30.3 kg (10.4 + 9.7 + 10.2) |
| At 12.00 per kg | 360.00 | 363.60 |
The gap on this order is 0.3 kg, or 1%, worth 3.60. On one order that is a rounding error. Across a week of orders it is a number someone has to explain.
Where the gap hurts
Nominal weight is a planning number. Actual weight is a money number. When the system knows only the first, the difference leaks out in places that are hard to trace:
- A customer is invoiced on one weight and the delivery note shows another.
- A supplier invoice, based on the weighed quantity, does not match the receipt in cases.
- Stock in kilograms drifts away from what is physically on the shelf.
- Margin per kilo looks wrong, and nobody can say why.
- Trim and shrink, which are real, get blamed on the weighing rather than measured.
None of this is exotic. Meat, cheese and produce businesses live with it every day, usually with a spreadsheet next to the system, and usually with one person who knows how the spreadsheet works.
What catch weight changes
Catch weight records the actual weight of each unit alongside its nominal weight. In ManufacturingFlow 365 that pair of numbers is carried on journals and documents, so the weighed figure does not stop at the scale or the clipboard.
That is the whole idea, and it is deliberately modest. It gives you the information to price, invoice and value on the real weight. How your business uses it is a matter of set-up and policy, and you should test that with your own items rather than assume it.
A practical way to start is to pick one fast-moving catch-weight item, one supplier receipt, one production output and one customer order, and follow the weight from the first to the last. If the number on the scale survives that journey on paper and on screen, you have a set-up worth extending. If it changes somewhere along the way, you have found the step to fix first.
Questions to bring to any demo
Whatever product you evaluate, ask to see these with your own item and a short order:
- Where is the actual weight captured: at receipt, at production output, at picking?
- Which weight does the sales price use, and which does the invoice print?
- Which weight does the stock value use, and what happens to the difference?
- Does a returned case keep its weight, or revert to nominal?
- Is the weight visible on the document the customer actually receives?
- Can you count stock by cases and by kilograms and see both?
A vendor who answers all six from a working screen has done the work. One who answers in slides has not.
Who this matters to most
Meat and poultry processors, cheese makers and maturers, produce packers and any distributor of random-weight goods. It also matters when the same plant makes the product: a ham produced in a batch is weighed on the way out, and that weight is the one that matters to the next stage and to the customer. If you cut carcasses, the disassembly of a carcass into cuts has the same weight question at every grade, and a receiving weighbridge adds another weighing before any of it starts.
In Business Central
- Catch weight in ManufacturingFlow 365: the actual weight of each unit is carried next to its nominal weight on journals and documents.
- A catch-weight ham scenario in the demo data, created by one action in a sandbox along with dairy, tablet formula, crude oil, planning and lot scenarios.
- Lots and traceability, so a weighed unit keeps its history.
Limits
We claim only what is above: the app carries actual weight next to nominal weight on journals and documents. We do not claim how a sales line calculates its price from the actual weight, or how inventory valuation postings treat the difference between actual and nominal. Test both against your own items in the scenario before you rely on them. ManufacturingFlow 365 is designed from 63 identified gaps, of which 27 are implemented and 36 partly; exports and some planning pages have not been run. The apps have been run in a UAT sandbox with demo data and no live customer is recorded.
See it on your process
Bring an item you sell by the kilo and stock by the case. We will weigh it in the sandbox and follow the weight through: book the catch-weight ham scenario.
Keep reading: a mock recall in 15 minutes and the weighbridge as your first quality gate.