@pandhm & @Tor you suggested the same thing. I use that field to pass the “Brandname”. There lurks a small danger about what you are proposing.
A localized custom field, will be future proof. But business code, I am not so sure. Let’s say that for some reason the development team, puts a limit to the length of that code (for their reasons). If you’ve putten critical information that’s required by the law in there you may face another bad deprecation. That’s the point of localizations, for every country to have exactly the critical legally binding fields ready for you
@pandhm For the Greek Localization I am writing, cooperating with @lubos, there is a field for VAT that will be used, among with other ones, for myDATA connection.
I believe it 'll be ready with the start of new year. Stay tuned, and don’t use another field, because you 'll do the same task 2 times.
I also have ideas of making a tool for mass transferring between fields when I finish, for all of those that need to transfer data to be able to work with the new localization.