I am currently reviewing opentaps for several customers of mine in the meat producing industry. Actually they are producing kebap.
These are produced in pieces of various sizes. So you can assume that the product_A is available in 5 kg, 7.5kg, 10kg and so on.
The customers order e.g. 2 pieces of product_a in 10kg size. The price caculation is based on the unit (kg).
So one order line looks like: "2 pcs; 10 kg; product_a; price_per_kg; price_of_line=2*10*price_per_kg".
just using a single line for each piece is not a good option as QOH etc. will not reflect the size of the ordered product, just the count*size.
Unfortunately they have to be able to track the pieces with a lot_id because of law_regulations.
I would like to implement this feature with minimal penetration and impact.
I thought about using variants on the size, but the price for the different variant must be kept in sync (price_per_kg*size).
Maybe a good option would be to use configurations and add a new type of "size" to inputed as decimal.
Any hints for other ways to solve this or pointers to code to help me estimate the effort welcome.
it can be handled with the "require amount" setting at the products page, but it can not be added to an order from the opentaps crm module (any configurable product fails) but only from the web shop. unfortunately the entered amount is not handed through to the manufacturing/packing stages. prices are calced correctly but it is impossible to see from the packing order how big the entered amount is.