Hello,
on the TakePOS touch module, when we select a product and that we change the quantity, the price change to a wrong rounding
Example : 1 coffee = 25’000 vnd (no problem)
Example : 2 coffees = 49’999.99 vnd (instead of 50’000 vnd)
I tried to change limit in the configuration pane but nothing change
Someone already had the same problem ?
Which version of dolibarr do you use ?
Can you also put a screenshot of the definition or price of the product card (tab Selling price)
Confirmed here when printing invoice on 10.0.2 but not on every product . I can’t get if there is something wrong in the product card, it’s seems to be OK…
I can’t reproduce. Can you try to upgrade to 10.0.3 ?
What’s the difference between café and muscat ? It’s seems that the muscat product has something wrong in the product card
The problem is still here on 10.0.3.
A way to reproduce it on every product in my set up is to use decimal number for the quantity (3 digits can be useful for weight selling for example).
Then the rounding issue appears in the invoice printing window.
For me no need to use a decimal number for the quantity, the problem still appear with normal number. I tried to change the currency and modify the price to a smaller but still the same problem… I don’t know from where come the problem
In addition, the new product creation on 10.0.3 doesn’t solve the problem.
rounding rate seems to be quantity dependent, this is the only thing that we can note.
@Mathrix22
We need to figure out the steps to reproduce this issue otherwise it will be quite difficult for the dev to fix something.
On more thing in the new product window:
ProductTest was created with a TTC Price (10.5 TTC)
ProductTest2 was created with a HT Price (8.75 HT)
VAT: 20%
Here is the result, we can note differences in unit price rounding issue behaviour:
@Aurel-GDN : I already tried everything that you post and explain that in my other post. If the dev need something they will ask me and I will give print-screen and more informations.
That’s a little bit weird because this workaround doesn’t affect this unexpected behaviour in my setup…
