Vertical transport software is a strong fit for shared eFTI infrastructure because one TMS codebase can serve many independent logistics organisations.
The software vendor can own one integration while each customer keeps separate datasets, integration references, users and rights inside the eFTI platform.
Customer onboarding becomes configuration and mapping work instead of another protocol implementation.
Because eFTI remains its own product boundary, a TMS can decide which customers activate the module and how it packages the functionality.
A future Adminyra portal may handle product selection without becoming part of the eFTI data runtime.
No. Multi-tenant separation keeps organisations and their regulated datasets distinct.
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.