Freight Data Is Already Digital, but the Authority Cannot Read It: Is the eFTI Project Ready?
Test the regulatory dataset, certified platform and authority retrieval path before treating a digital freight file as an eFTI implementation project.
Signals to watch
- A named freight operation and legal information requirement map to a defined eFTI dataset
- The platform or service provider has a specific certification state and technical owner
- An authority inspection, pilot or 9 July 2027 rollout has a tested retrieval path and date
Digital freight data is not automatically ready for electronic Freight Transport Information, or eFTI. The project is ready only when a freight-data provider can name the covered regulatory dataset, show which certified eFTI platform or service processes it, and demonstrate how a competent authority retrieves the machine-readable record for one shipment. A transport-management-system export or emailed PDF proves only that data exists.
This is the recurring problem for a freight-data platform business-development lead reviewing authorised road, rail, inland-waterway and logistics-technology Telegram groups. The useful Signal is a broken regulatory handoff before an authority pilot, inspection design or 2027 rollout. Seeing it a day late can miss the data-architecture workshop. Quoting from “all documents are digital” can commit a supplier to a certification or authority interface that has not even been identified.
The following fragment is illustrative, not a real operator request or authority finding:
“CMR and dangerous-goods files are already in our TMS. Need eFTI access for two countries before the next pilot.”
The message does not name the freight operation, legal information requirement, Member States, dataset version, platform, certification, authority interface, shipment identifier or pilot acceptance test.
eFTI is an authority-access route, not a file format label
Regulation (EU) 2020/1056 creates a legal framework for economic operators to make specified regulatory freight transport information available electronically to competent authorities. An eFTI platform is an information-and-communications-technology solution used to process that information. An eFTI service processes it through an eFTI platform, alone or with other systems.
The distinction matters because a company can digitise a consignment note, store it in a transport management system and exchange it with a carrier without using the eFTI route. Conversely, one eFTI platform may process data that originates in several operational systems. The commercial question is therefore not “Do you have electronic documents?” It is “Which legally required data must which authority retrieve, from which certified processing environment?”
The Regulation also preserves an important choice. Economic operators are not forced to use electronic means for every covered record. When they choose to make the information available electronically under eFTI, the qualifying data and access path must follow the Regulation. That boundary prevents a sales team from turning a voluntary digitisation project into a false universal mandate.
Readiness test one: identify the regulatory dataset
Begin with one freight operation, not the customer’s entire document archive. Record the transport mode, origin and destination, goods, responsible economic operator and the Union or national legal requirement that asks for the information.
Then map fields. A useful dataset note states which source system owns each required data element, its legal meaning, format, update event and validation rule. “Shipment number” is too vague if the authority expects a data element tied to a particular legal requirement. “Dangerous goods attached” is too vague if the controlled dataset needs the substance, quantity, packaging or carrier role in structured form.
The first acceptance result is modest: one covered information requirement can be reproduced from traceable source fields without copying a PDF by hand. If the legal scope or data definition is still disputed, the work is dataset analysis—not yet platform integration.
Readiness test two: prove the certified processing route
Article 9 of Regulation 2020/1056 sets functional requirements for eFTI platforms, including a unique electronic identifying link between a shipment and its data, authorised-user controls, processing logs and authority access. Implementing Regulation (EU) 2025/2243 provides detailed functional specifications for the platform layer.
Ask which legal entity is the platform developer, which entity provides the service, and which certification applies to which version. A software vendor’s security certificate, cloud audit or product brochure is not the eFTI compliance certificate described by the Regulation. A platform reassessment may also be required when the technical specifications change.
For a scoped opportunity, preserve the platform version, certification status, conformity-assessment body or planned route, service-provider dependency and the system owner responsible for remediation. If the prospective buyer has selected no platform and no certification route, the immediate deliverable may be architecture and vendor selection rather than an integration quote.
Readiness test three: retrieve one shipment as an authority would
The Commission’s eFTI timeline says that, as of January 2026, platforms and service providers can prepare for operations and Member State authorities may start accepting data stored on certified platforms. The Regulation applies in full on 9 July 2027, when Member State authorities must accept qualifying information shared through certified eFTI platforms.
The production test should follow the inspection path. Create one shipment record, generate its unique electronic identifying link, authenticate through the intended authority access point, request the covered dataset and confirm that the returned machine-readable data matches the current source record. Test an update and an unavailable connection as well. A QR code is only a carrier for the identifying link; it is not proof that the authority reached the correct data.
This test exposes four different failures:
- the identifier does not resolve to the intended shipment;
- the requesting authority cannot authenticate or lacks the right access;
- the platform returns an incomplete or stale regulatory dataset; or
- the operational source changed without an auditable eFTI update.
Each failure belongs to a different owner. Quoting “an authority application programming interface (API)” without that ownership map hides the project’s actual work.
The example request needs three separate work orders
Return to the illustrative message. “CMR and dangerous-goods files are in our TMS” supports a source-system inventory. It does not prove that both documents are covered in the same way, that both countries use the same authority path, or that one certification covers the intended platform and service.
A bounded proposal could contain three work orders:
- Dataset mapping: identify the legal requirements and reproduce one regulatory dataset from the transport-management system.
- Platform route: select or confirm the certified platform and service-provider responsibilities for the deployed version.
- Authority retrieval: test the shipment link, authentication, access rights, machine-readable response and update history in each participating country.
The DCSA electronic bill-of-lading handoff solves a commercial document-state problem, while the ICS2 rejection route concerns customs safety-and-security filing. Neither record can be relabelled as eFTI evidence. For a separate maritime verifier request, use the FuelEU scope test.
TOP Prospect can join fragments from Telegram groups the user deliberately connects and is authorised to access, retain source and time, remove obvious duplicates and place the request in a human review queue. It cannot determine legal coverage, certify a platform, access an authority system, test a production shipment or contact the writer. The pricing page describes that discovery boundary.
The original request becomes implementation-ready when one row can name the freight operation, legal dataset, certified processing route, authority retrieval test, accountable owner and date. Until those six items exist, sell the missing analysis—not a full eFTI integration by assumption.
Frequently asked questions
Does a PDF transport document count as eFTI?
Not by itself. When an operator chooses the electronic eFTI route, the regulatory information must be processed on a certified eFTI platform and made available to the authority in machine-readable form through the required secure access path.
Must every freight operator switch to eFTI?
Regulation (EU) 2020/1056 does not force economic operators to use electronic means for every record. It requires authorities to accept qualifying information when an operator uses the Regulation’s electronic route.
When does the eFTI Regulation apply in full?
The European Commission timeline states 9 July 2027. From that date, Member State authorities must accept information shared by operators through certified eFTI platforms under the Regulation.
What proves that an eFTI integration works?
A test should connect one covered dataset to one shipment identifier, a valid platform or service-provider certification state, and an authenticated authority retrieval that returns the intended machine-readable data.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
