Target versus actual
Store a target and captured actual weight on the same order line, with variance available for operational review.
Catch-weight software
Larder models variable-weight food sales from target weight and lot allocation through weighing, tolerance review and per-kilogram calculation. The physical weighing and downstream lifecycle are validated before live use.
Variable weight, one transaction
Catch-weight work is not just a number from a scale. Larder keeps the commercial order, chosen stock, weighing evidence and resulting value connected.
Create the order line with catch-weight enabled, a target weight and the applicable customer or per-kilogram rate.
Allocate the relevant lot so the weight recorded for fulfilment remains connected to batch traceability.
A configured workflow can record the measured weight with a scale reference or a controlled manual-entry path and reason. The weighing and printing process must be validated at your site before live use.
Compare actual against target, minimum, maximum and tolerance rules before the line moves on.
Keep actual weight and the applicable per-kilogram rate available for a configured downstream commercial calculation; do not assume automatic dispatch or invoicing.
Workflow diagram based on current Larder product capabilities. The exact configuration is agreed during implementation.
The current product model supports the data needed to explain what was ordered, what was weighed, how far it varied and how the final value was derived.
Store a target and captured actual weight on the same order line, with variance available for operational review.
Minimum, maximum and percentage tolerance fields support an explicit in- or out-of-tolerance status.
Keep the applicable rate and calculated price beside the actual weight so a configured finance hand-off can use the same commercial context.
Production weigh events can record the user, time, scale device, receipt reference and idempotent event identity.
Where a manual weight is permitted, the product model supports a required reason and provenance rather than an unexplained override.
The data model can retain the chosen lot and actual weight with the order item; downstream dispatch evidence depends on the validated rollout stage.
The precise screen and device flow depends on the operation, but the underlying record can hold the commercial and operational detail needed for review.
The order model keeps actual weight, price per kilogram and calculated price together. The exact capture and approval flow is configured and tested before the fulfilled value is used downstream.
Yes. Minimum, maximum and percentage-tolerance fields support variance and tolerance status. The exact thresholds and handling process are configured around the operation.
That needs a hardware and workflow check. We verify the scale model, connection method, required accuracy and fallback process before promising integration.
Keep the weighed item connected to its received or produced lot.
Read moreSee how actual-weight context can support configured delivery and finance hand-offs.
Read moreSee catch weight alongside yield, species, origin and existing ABP records.
Read moreWe will walk it from order entry to final value, including stock allocation, tolerances, scale constraints and what happens when the weight is outside the expected range.
Request a catch-weight demo