What is Customized / Hybrid Optical Transceiver Coding?

QSFP Memory map
Source: SFF-8636 Specification for Management Interface for Cabled Environments

When it comes to optical transceiver coding (EEPROM memory tables 00h, 01h, etc), many equipment vendors follow optical transceiver industry specifications, however, some vendors have chosen the path where if optical transceivers do not have specific vendor set criteria in the EEPROM tables, ports will be blocked and traffic will not flow.
Customized (hybrid) coding refers to situations when vendors originally did not have a specific optical transceiver hardware type in the supported transceiver list, and we make a hybrid solution of hardware and code, where we use preferred hardware (not in the supported transceiver list), but in the code, we write the closest optical transceiver from the supported transceiver table.
Below example explains the situation more in-depth:

We recently had successful 100G-QSFP28-80 (ZR4) tests in Nokia routers (7210 SAS-Sx, 7750 SR1, and 7250 IXR). Originally, these Nokia routers did not support a 100G ZR4 module, but we made a hybrid solution, where hardware remains 100G-QSFP28-80 (ZR4) and code is 100GBASE-ER4 (40km). With such a hybrid solution, we can have ZR4 80km link performance, but the optical transceiver is recognized as ER4 40km and is accepted by the networking gear. A similar hybrid approach is used to make CWDM/DWDM/BIDI or long-distance optical transceivers work in platforms where they are not among the supported transceivers.