Comment 18 for bug 519220

Jay,
I agree that automatic computation is better than button-pushing. I don't mind that being changed on the trunk.
5.0 is changed already, so if we're the only ones impacted then keep the changes - we'll patch our server.

Now for the trunk: from our experience, we know that a computed weight can be an estimate at best, but there are lots of reasons for overriding it: some products have variable weight (tulip bulbs for example), or sometimes 1Kg more or less can change the carrier's shipping rate and we have a tolerance.

I think we could introduce a new field "weight_override": when it's null, weight = current function ; when it's not null, weight=weight_override.
You could either show both fields side-by-side, or show only weight_override and add a button "Change weight" with a wizard to change weight_override.

If you're willing to do this in the delivery module, that's fine and I'll gladly test and validate, and probably backport/patch to our 5.0 server.
Otherwise I'll do the necessary changes in delivery_weight.

Can you please tell me what you think about this?
And would you like me to file another bug report about this improvement?
Lionel