eFTI in 2027: what transport software vendors should prepare now

The important date is 9 July 2027

The European Commission states that the eFTI Regulation will apply in full from 9 July 2027. From that point, Member State authorities must accept regulatory freight information made available electronically by operators through certified eFTI platforms.

For software vendors, the useful question is therefore not whether every final implementation detail is available today. It is which parts of the product can already be prepared without locking the architecture to unfinished specifications.

Keep eFTI behind an integration boundary

A TMS or logistics platform should not scatter eFTI-specific fields, validation and authority-facing logic throughout the core product. A separate integration layer makes it easier to adapt as implementing specifications and certification requirements mature.

That layer can translate internal shipment and consignment data into the structures required by the eFTI ecosystem while keeping the operational TMS model stable.

• Inventory the regulatory freight data already available in the product.
• Map ownership and source-of-truth for each field.
• Separate transport-domain data from eFTI transport-envelope logic.
• Design asynchronous status and error handling from the start.
• Keep authority access, audit events and certification-sensitive functions isolated.

Certification changes the build-vs-connect decision

The eFTI model is built around certified platforms and service providers. That creates a strategic choice for a software company: become part of the certified platform layer, or integrate with one through a stable API.

For many TMS vendors, keeping their own product focused on customer workflow while consuming a specialised eFTI service can reduce the amount of regulatory infrastructure they need to maintain themselves.

Prepare the product even while specifications continue to mature

The Commission's implementation timeline indicates that remaining detailed specifications are expected during 2026. That means interface details can still move, but core engineering work does not have to wait.

Data mapping, tenant separation, event logging, permissions, error states and an adapter-based integration architecture are useful regardless of the final wire format.

Adminyra's integration direction

Adminyra is researching an API-first eFTI integration layer intended to sit between transport software and the eFTI ecosystem. The design principle is the same as with other European infrastructure: keep regulatory integration in one controlled module instead of spreading it through the customer's application.

Public product claims will follow the specifications and implementation status as they become final.