Thanks for the suggestion, @mazen-hajjar. I’ve split it from the other feature request to its own thread so it doesn’t get lost in the discussion of a different request. Please can you give this thread a vote? Thank you.
What I mean for clarity, is we pack various numbers of units into a case and get charged per case or per keg by our 3PL and differently. We would like to charge per case and per keg differently.
Ahh, that doesn’t do the full n things is m units, so it doesn’t seem to be as useful as the container based version. There’s no way I can see of setting this to be something fractional?
See also:
That’s right, the override is an integer for now. Allowing decimals adds extra complication, so we’ll leave that to that dedicated feature request for now.
Thanks
That’s not quite what I meant. The “decimal” FR is one thing, but the container “units” definition allows a fractional expression, albeit sort of upside down
n containers = m units.
The per product setting doesn’t allow this.
Just saying.
The product override feature was intended for use in more specific scenarios—for example, if cases of up to 12 cans count as 1 unit, while cases with any more than 12 cans count as 2 units. Alternatively, it can be used if you want all cases, regardless of the number of cans, to count as 1 unit, so defining units by the number of products is intentionally “non-fractional”, and related to just that product which can only be added to an order as an integer. If your unit definitions need to be even more complicated than fractional via container types and specific (albeit, integer) values set on individual products, then we’d need to expand this even further, as you say. Is this something you’re currently needing or were you simply pointing it out?