There was a previous question that was closed as off topic that I wanted to re-iterate:
https://community.clover.com/questions/16094/incorrect-locale-on-eu-devices.html
We recently had a customer contact us because they recieved a new device. The new (mini) device is displaying all currencies in USD$ rather than EUR€, but their other device (older station from 2018) is displaying € correctly. Both are on the same MID with identical settings.
After looking into this further it seems that there has been a recent change in the Clover production process around language selection (Settings->Personal->Language and Inputs). Where previously you could chose your locale e.g. English (UK) or English (US), on the new devices you can only select "English". This default option sets the device locale to en_US and this cannot be changed by the user (or by the Clover support channels e.g. AIBMS). So all new devices are locked to the US if we use the standard java.util.Locale: `Locale.getDefault()` as recommended in the Clover docs (
like this one)
It is possible for us to go back an rewrite every instance of the Locale function to instead use the Merchant settings, but if this is indeed a production change I think it would be worth highlighting to the production team as it could have some pretty serious un-intended effects to any non-US merchant e.g. the way tax is handled, languages, timezones, currencies etc.
I have already spoken to First Data UK and it doesn't look like there is anything that can be done either by their support team or on our end. I suspect the only way to fix this would be to flash the merchant devices. Is there anything Clover can do to remedy this issue for individual merchants remotely?
