Yeah, a whole lot of things would be great, but that’s available for you already. You have some custom key pairs (value/text) and I offered you the possibility to load these key pairs into an empty select field that is recognized by WooCommerce. I’m not responsible for the value/text combination: this is your data! The value can represent something meaningful to a human or it can represent a number, a code that is meaningful only to an interpreter and it can be a mix of both, like I indicated to you. To automate external data handling that is different from data provider to data provider is not the goal of my plugin. It’s up to you to assure that your data complies with your expectations.
To put it clearer. Exactly for this reason you can hide some data from display and it’s your decision to add a custom field and to display the selected value. If you want the value to be comprehensible to humans you have to provide such a value. WooCommerce itself does not display for instance the country selection value as the value would show up as es_ES for example.
For sure, it’s possible to remap a value to a corresponding text but once again, that’s far behind of the scope of the plugin at this moment and if I implement something like this it will be a feature of the Rich Guys Swiss Knife.
If you’d like to fix this, adapt your javascript code. I tested your code both in wcpgsk_user.js and inside of the storage field for script snippets in the checkout section and it’s possible to get this solved. If you want to reconfigure the value you only have to change one line in your javascript code that configures the value/text pairs of the select.
uh