Robin

no that wasn't mentioned in that topic

After some digging in the forums for other options to get around this I found the following snippet of code: if you read the sources if(sVariableTypePrefix.equals("20")) { dPriceSell = Double.parseDouble(sVariableNum) / 100; // price with two decimals } else if (sVariableTypePrefix.equals("21")) { dPriceSell = Double.parseDouble(sVariableNum) / 10; //price with one decimal } else if (sVariableTypePrefix.equals("22")) { dPriceSell = Double.parseDouble(sVariableNum); //price with no decimals } else...

Thanks for the reply, good to know. I this case this barcode is on a paint bottle so no idea why the manufacturer uses barcodes beginning with 25. Is there any way around this so I can get unicenta to process this as a regular EAN13 barcode?

I have a strange problem with a few barcodes. Specifically the following barcode put to EAN13 like all products I have: 2561125111111 If I scan this product in Unicenta in the sales screen it gives me the product and puts the amount immediately to 111,1 pieces. Which is of course not desirable. Anyone has run into this problem and know how to solve it?

you are right when talking about a single receipt. I'm talking about the close cash...

The last month I have had 3 occurences where my close cash Total Sales and Totals...

Ah wonderful! Thank you so much!

As a shop owner and a happy user of Unicenta I do have a few issues with the new...