The eFTI framework requires a unique electronic identifying link between the transport operation and the relevant regulatory information held on the platform.
The identifying link lets the right regulatory information be located without embedding the complete dataset in a QR code or other carrier.
An authorised operator can make the machine-readable reference available as part of the inspection workflow.
Transport software should decide where the identifying reference appears in the driver's workflow, document pack or mobile interface.
That experience can be tested before live Gate connectivity is enabled.
No. Its purpose is to identify and locate the relevant regulatory information, not to duplicate the entire dataset.
No. Adminyra eFTI is under active development. Production authority exchange stays disabled until the required interoperability, conformity-assessment and certification steps are complete.
Yes. Data mapping, sandbox API work, CMDS lifecycle design and application integration can be prepared before production Gate trust is enabled.
Start with a real freight-data mapping in the sandbox. Production Gate exchange remains locked until the certification and interoperability path is complete.