Kuehne+Nagel requires support for handling and validating two distinct EORI numbers for the same customer in the post-BREXIT environment:
One EU EORI
One UK EORI
From the KN CIP data-model perspective, both identifiers must be stored and validated independently. Since a single identifier/technical key cannot reliably hold multiple EORI values, KN requires two separate technical keys to ensure clear and unambiguous processing.
KN would like CDQ to support two distinct technical keys for EORI validation, for example:
EU.EORI mapped to CIP identifier EORI
UK.EORI mapped to CIP identifier UK_EORI
In ticket CDLS-4798, CDQ confirmed that currently only a single identifier/technical key is supported for EORI validation.
However, KN has a business requirement to maintain and validate both EU and UK EORI numbers independently for the same customer record. The current limitation creates a risk of ambiguous validation behaviour and potential false negatives when both identifiers exist simultaneously.
KN requests CDQ to evaluate and provide:
Support for two separate technical keys for EORI validation, or
An alternative solution that guarantees independent and unambiguous validation of both EU and UK EORI numbers for the same customer.
Please also advise whether this capability can be supported within the current CDQ framework or requires product enhancement/roadmap consideration.