...
If a code exists without a translation being done (for example, L064), that code will be brought into Rx-Universe and saved as an addon, which will cause it to print on work tickets, etc., to ensure a service isn’t missed. If the code is a billing code only and doesn’t need to exist as an addon, setting the “Code” field above to “ZZZZZZ” will cause the code to be omitted from the addon list on the order.
A note is required concerning tints. Eyefinity uses two billing codes to indicate tints - MN (solid tint) and MP (gradient tint). With the billing code, they can specify the colour of the tint in two ways,
If they send the tint in the ortc tag, Rx-Universe looks for a translation in the table of MN (or MP) plus the tint as specified in ortc. For example, a Brown 2 tint might be sent as a solid tint, in which case Rx-Universe would look for a translation for “MN BROWN 2”, as follows:
...
The other way the tint can be specified is with a combination of ortc=other, and then the tint description placed into ortnt as a free-text description. In this latter case, Rx-Universe will look for the addon to use for the MN or MP code by itself, and then place the tint description into the addon remarks on the order itself:
...
And on the order itself:
...
2.6 Frame Information
Translation of frame information is a particular challenge with Eyefinity jobs, because Eyefinity allows free-format descriptions of frame information to be made on the website. Thus, a manufacturer such as Safilo may come up by default as “Safilo” when entering the order on Eyefinity, but the user has the ability to change that. If Rx-Universe is set up to recognize “SAFILO”, but the order comes over with “SAF”, “SAFILLO”, “SAFL”, or some other spelling, Rx-Universe will be unable to match the code and properly translate it.
...