eFTI common data set

One common data model beneath many regulatory requirements.

Delegated Regulation (EU) 2024/2024 establishes the eFTI common data set and eFTI data subsets used to represent regulatory freight information.

Adminyra eFTI
TMS / ERP / logistics software
Adminyra eFTI platform
eFTI Gate / regulated exchange
EU data definitionsTechnical characteristicsCode listsBusiness rules
01

Map instead of replacing your internal model

Transport systems already have concepts for consignors, goods, locations, vehicles and references. The eFTI model gives regulatory exchange a harmonised representation.

The integration challenge is to maintain a controlled mapping between internal fields and the applicable eFTI schema revision, not to rebuild the operational database.

02

Keep schema revisions explicit

Adminyra records the schema revision used for each dataset version so validation behaviour can evolve without ambiguity.

This also reduces coupling between a customer's TMS model and future specification changes.

FAQ

Practical questions about eFTI Common Data Set

Do all shipments use every eFTI data element?

No. The applicable data subsets determine which regulatory information is relevant to a particular consignment movement.

Is Adminyra already a certified eFTI platform?

No. Adminyra eFTI is under active development. Production authority exchange stays disabled until the required interoperability, conformity-assessment and certification steps are complete.

Can we integrate before production certification?

Yes. Data mapping, sandbox API work, CMDS lifecycle design and application integration can be prepared before production Gate trust is enabled.

Primary sources

Official EU material behind this page

Build before the rush

Prepare the integration before 9 July 2027.

Start with a real freight-data mapping in the sandbox. Production Gate exchange remains locked until the certification and interoperability path is complete.