If we do price override after set quantity of weighted products, the override price is considered for quantity before set quantity and is then recaculated accordingly for the units in the basket. The right behaviour should be to override price based on the quantity in basket.

The above applies to some low value low weighted products like Ginger, are purchased in Kilo(Kgs) and sold in Grams (g) in the stores on POS.

But as these products are so low value low weight, we cannot keep the sales unit as grams as it's diffcult to define price per gram.

So the sell trade agreement is defined in KGs and hence,the product is added to POS in KGs...1KG = £9.95

Then we set quantity to the req quantity customer has purchased like 0.3Kg (300 grams) .. 0.3 KG = £2.99

Sometimes these products are on one off markdown to clear stock towards their best before date and we sell these for a giveaway price like £1.

When user overrides the price after setting quantity, the overriden price is considered for the 1Kg instead of 0.3 KG and instead of 0.3 KG being £1, it calculates 1kg = £1 and hence 0.3 KG = £0.3, which is incorrect, we wanted to override 0.3 KG = £1.

It's difficult to calculate how much percentage it is during peak hours to be able to use line discount % function as is prone to manual error.

We did raise this as a bug with Microsoft (2404150050004828), but we were told to raise an IDEA instead.