Versioned CMDS engine
The platform includes versioned Consignment Movement Data Set handling, lifecycle states and applicable data-subset modelling.
The platform is designed for TMS providers, transport operators and connected systems that need to create, manage and exchange structured eFTI datasets through a controlled integration layer.

The current foundation models the operational parts of an eFTI platform separately from the shared Adminyra portal, so the product can evolve independently while still being accessible through the wider Adminyra ecosystem.
The platform includes versioned Consignment Movement Data Set handling, lifecycle states and applicable data-subset modelling.
Integrations and tributary systems are modelled explicitly so external transport software can connect without becoming part of the platform core.
Authority access, responses, follow-up communication and Gate connectivity are represented as first-class platform capabilities.
The platform foundation already separates sandbox and production environments and models authorisation, temporary access, data-element audit events, notifications and certification metadata.
The eFTI codebase already exposes its initial CMDS API and defines dedicated main, API, sandbox, documentation, Gate and status surfaces. Certification and external interoperability still require the applicable formal processes and connected infrastructure.
Open efti.adminyra.com→Adminyra eFTI keeps the regulated freight-data layer separate from the customer's TMS. That allows an existing transport product to integrate through a stable boundary instead of rebuilding the complete eFTI platform stack internally.
Connect an existing transport management system to the Adminyra eFTI integration boundary.
Explore solution →Read the practical architecture and implementation material being published alongside the platform build.
View insights →Tell us what you want to improve. We will define a practical first version, a clear scope and a transparent price.