eFTI API integration architecture for logistics software

eFTI becomes fully applicable on 9 July 2027

From 9 July 2027 Member State authorities must accept regulatory freight information shared electronically by operators through certified eFTI platforms. The Commission plans to complete the remaining implementation specifications by December 2026.

Software vendors do not need to wait until the final month to prepare their architecture. Data ownership, mapping, permissions, status handling and an integration boundary can be designed now.

Keep the regulated layer modular

The TMS, ERP or freight platform should remain the source of operational shipment data. An eFTI adapter can translate the subset required for the regulatory exchange while preserving a clear boundary around certification-sensitive behaviour.

That makes later changes to schemas, gate communication or platform requirements much easier to contain.

• Map internal shipment fields to eFTI data elements.
• Track which system owns every regulatory data element.
• Separate data preparation from eFTI transport and authority-access logic.
• Record request, disclosure and status events.
• Design idempotent synchronisation and error recovery.

Authority access is machine-to-machine

The 2025 platform requirements specify secure machine-to-machine communication between an eFTI platform and at least one eFTI Gate. That means authority access should not be modelled as an ordinary user-facing portal flow.

An integration layer should preserve the distinction between customer operations and authority-access interactions, including authentication, requested subsets and follow-up communication.

Adminyra is not presenting itself as a certified eFTI platform

Adminyra's current work is focused on the software boundary and readiness layer around eFTI. Certification rules and remaining specifications are still being completed at European level.

The practical objective is to make transport software ready to connect cleanly to the certified ecosystem when the chosen platform or service-provider route is clear.