I have an issue where the prices are inconsistent because of formatting.
Example
Currency format: C0 Product Price: 199,10 ;-
Product page: 199 ;- Order in BO: 199 ;-
Order row in DB: 199,10 Payment in DB: 199,10
Implications
The customer see one price on the site, but then when paying for the product they will see a different price.
If there are integrations to other systems we will show inconsistent data. But in fact the DB is storing the data with the decimals, so the data is in reality correct.
Question
Why do we have the formatting if it’s not applying it everywhere?
Or is that not the correct use case?
If you want the same prices in database as see you use more decimals in your format string.
Format string is only for presentation (to make the site nicer to view) it doesnt change the price. if you have integrations with other systems you should use the database value and not formatted value.
You could make sure you have pricelist in you solution without decimal prices but if you have campaign or discounts with % then the possibility of decimals are back again.
But this isn’t a problem just for the litium or the web. Even when you go to the grocerystore at least in Sweden they will round the prices the say to you but if you pay with you card the exact amount will be debited.
Currency format is only to format the value in presentation, have nothing to do with how the actual value is stored.
For storing, we using the minor currency unit for the currency to ensure that we haven’t more decimals then allowed. The rounding to the minor currency unit is used to avoid problems when communicating with example the payment providers.
But then I would think that BO should show the Litium user the actual stored information, and not the rounded numbers. Or what’s your thoughts on that?
