eFTI Compliance in 2026: Why Your Freight Data Becomes a Regulated Interface Before July 2027

The eFTI Regulation turns regulatory freight information into a machine-readable interface that competent authorities across the EU are obliged to accept. It applies to road, rail, inland waterway and air movements, and it covers dangerous goods, waste shipments, cabotage records, combined transport and carriage documentation. The operational consequence is not that paper disappears. It is that the data has to be assembled, held on a certified platform and served on demand at the point of inspection, by the party standing at the roadside, who in a subcontracted chain originates almost none of it. Modelling that chain shows a 37 point gap in readiness between an own-account operation and a three-tier subcontracted one carrying the identical load, which is why platforms that hold consignment state across parties, Locus among them, matter more than the document format does.

Why eFTI Matters: The Business Case

The Regulation exists because freight still moves on paper. Regulation (EU) 2020/1056 records that the movement of goods is accompanied by a large amount of information still exchanged in paper format between businesses and competent authorities, and identifies the absence of any Union-level obligation on authorities to accept electronic freight information as the main reason digitalisation has stalled. The European Commission puts the expected saving at around €1 billion a year in reduced administrative burden across EU transport and logistics.

Also Read: TMS API Integration for European Retail

The scope is wider than most operators assume. Article 2 brings in carriage documentation under Regulation No 11, combined transport under Directive 92/106/EEC, cabotage records under Article 8(3) of Regulation (EC) No 1072/2009, waste shipment information under Regulation (EC) No 1013/2006, and dangerous goods documentation under Chapter 5.4 of ADR, RID and ADN. It also absorbs national requirements that Member States notify into Part B of Annex I, which means the required subset varies by country crossed rather than being uniform across the Union.

The share of movements exposed to that variation is substantial. Eurostat records that in 2025, national movements accounted for 62.2% of EU road freight in tonne-kilometres, international transport for 24.4%, cross trade for 10.7% and cabotage for 2.7%. Close to two fifths of the work crosses a border, and those movements average 604 km for international and 722 km for cross trade against 97 km nationally, so they pass through more jurisdictions and more enforcement authorities per load. The national subsets in Part B therefore apply to the longest and most complex movements rather than to a marginal tail.

The timetable is now short. The Commission’s implementation page records the first implementing and delegated acts entering into force in January 2025, certified eFTI platforms and service providers able to begin operating from January 2026, remaining specifications due December 2026, and full application on 9 July 2027, when authorities must accept data served through certified platforms. An operator starting integration work in 2027 is starting after the deadline that matters.

How the eFTI Obligation Actually Works

The model below uses explicitly illustrative inputs: a cross-border road movement carrying five applicable instrument families, a subcontracting chain of up to three tiers, and a 95% probability that any one instrument’s data survives a single handoff as structured, machine-readable content. These are model inputs, not measured Locus averages.

Step 1: The data must sit on a certified platform, not in your systems

Article 4 requires that where an operator makes regulatory information available electronically, it does so on the basis of data processed on a certified eFTI platform and, where applicable, by a certified eFTI service provider. Holding the information in an ERP or a TMS is not sufficient on its own. It has to reach a platform that has been certified under a Member State accreditation scheme.

Step 2: Machine-readable is the default, human-readable is the fallback

Information must be made available in machine-readable format over an authenticated and secure connection to the platform’s data source, and in human-readable format at the authority’s request. The human-readable version must be shown on the spot, on the screen of a device owned by the operator, which puts a rendering requirement directly on the driver application rather than on a back-office portal.

Step 3: Every shipment needs a unique electronic identifying link

The operator must communicate a unique electronic identifying link that lets the authority identify the regulatory information related to that specific shipment. That link is the interface. It presumes a consignment identifier that is stable across every party and system touching the load, which is precisely what a subcontracted chain usually lacks.

Also Read: Fleet Utilisation in European Cross-Border Freight

Step 4: The dataset is distributed across companies, not systems

This is the structural point. Each instrument in scope originates with a different party, and the party inspected is the one at the end of the chain.

Instrument	Originates with	Handoffs to the roadside
Dangerous goods, ADR/RID/ADN Ch 5.4	Consignor	3
Waste shipment, Reg 1013/2006	Notifier or consignor	3
Combined transport, Dir 92/106/EEC	Intermodal operator	2
Carriage document, Reg No 11 Art 6	Contracting carrier	1
Cabotage record, Reg 1072/2009 Art 8(3)	Performing haulier	0

Step 5: Presentability is a product, so it collapses rather than degrades

A dataset is presentable only if every applicable instrument arrived intact. That makes readiness the product of the individual survival probabilities, not the weakest of them.

Chain	2 instruments	3 instruments	4 instruments	5 instruments
Own account	100.0%	100.0%	100.0%	100.0%
Shipper to haulier	90.2%	90.2%	90.2%	90.2%
Shipper to 3PL to haulier	81.5%	77.4%	77.4%	77.4%
Shipper to 4PL to 3PL to haulier	73.5%	66.3%	63.0%	63.0%

At 95% per handoff, a three-tier chain carrying five instruments presents a complete dataset at 63% of inspections. The other 37% are not non-compliant movements. They are compliant movements that cannot prove it.

Step 6: Exposure runs inversely to control

Reading the survival rates by instrument produces the finding that matters commercially. Cabotage data, which the performing haulier generates itself, survives every time. Dangerous goods and waste data, which carry the most serious consequences if unavailable, originate furthest upstream and survive least.

Instrument	Survives to the roadside	Consequence if unavailable
Dangerous goods	85.7%	Vehicle immobilised
Waste shipment	85.7%	Illegal shipment exposure
Combined transport	90.2%	Loses the exemption claimed
Carriage document	95.0%	Administrative penalty
Cabotage record	100.0%	Cabotage infringement

The operator carries the highest exposure on precisely the data it has the least ability to produce.

This inverts how readiness programmes are usually scoped. Carriage documentation and cabotage records are the instruments an operator sees every day, holds itself and can reach quickly, so they become the pilot. A programme scoped that way passes its own tests and still fails at the roadside, because the movement that gets stopped is the dangerous goods consignment whose classification data arrived three companies ago as an attachment. The sensible sequencing is the reverse of the comfortable one: start with the instrument that originates furthest upstream and carries the heaviest consequence, because that is the integration that takes longest to build and involves the party with the least commercial incentive to help. Everything the haulier already owns can be connected afterwards in a fraction of the time.

Step 7: Crossing borders stacks national subsets on top

Because Part B of Annex I carries national requirements notified by each Member State, a route must satisfy the union of the national subsets it touches. Holding the three-tier chain constant, presentability falls from 63.0% on a single-country movement to 54.0% across two Member States, 46.3% across three and 34.1% across five.

Own Account vs Subcontracted Chain: Key Differences

Dimension	Own-account operation	Three-tier subcontracted chain
Where the dataset originates	One legal entity	Three or four legal entities
Complete dataset at inspection, model	100.0%	63.0%
Party bearing the roadside obligation	The same party that holds the data	The party holding the least of it
Fix available	Internal integration	Contractual plus integration across companies
Handoff fidelity needed for a 99% pass rate	Not applicable	99.89% per handoff
Effect of adding an instrument	None, data already held	Multiplies against every upstream hop
Effect of adding a country	One national subset	One national subset per party per country

The fidelity row is the one to dwell on. Reaching a 99% roadside pass rate on a three-tier chain requires every handoff to run at 99.89%. That is an integration specification, not a process-discipline target, and no amount of driver training or carrier briefing reaches it.

It also explains why the usual commercial response will not work. The instinct on reading a compliance obligation is to push it down the contract chain, requiring each subcontractor to warrant that it holds the data. That allocates the penalty without changing the arithmetic, because the subcontractor still cannot produce what the consignor never sent it in structured form. Contractual flow-down converts an operational failure into a dispute, which is more expensive than the original problem and arrives later.

What to Look for in a Platform Before July 2027

A consignment identifier that survives the handoff. The unique electronic identifying link presumes one stable reference across every party. Ask how the platform maintains that identifier when a load is tendered to a subcontractor whose own system assigns its own reference, because that is where the link breaks.

Structured capture at origin, not re-keying downstream. Dangerous goods classification and waste notification data are created by the consignor. If they enter your estate as a PDF attachment or a free-text field, they are not machine-readable and will not serve an eFTI request regardless of what platform sits downstream. The test is whether a field arriving from a consignor can be queried, not merely stored and displayed, because an eFTI request resolves against data elements rather than against documents.

Planning and execution reading one consignment record. The instruments in scope attach to the consignment, not to the vehicle, so the record has to survive re-planning, re-assignment and subcontracting without forking. Where planning and execution run on separate systems, the identifier usually diverges at the first replan, and the link served to an authority then points at a record that no longer describes what is on the vehicle. Holding both in one planning and dispatch layer is what keeps the reference stable.

Also Read: TMS, ERP and WMS API Integration: What to Look For in a Platform

Certified platform integration as a roadmap item with a date. Certification is a Member State accreditation process, and the operator’s obligation is to serve data from a certified platform. Ask the vendor directly whether it intends to be certified, to integrate with certified providers, or neither, and get the answer before the specifications close in December 2026.

Human-readable rendering on the driver’s own device. Article 4(4) requires display on the spot, on the operator’s own equipment. A compliance capability that lives in a web portal a dispatcher can open does not satisfy it. This is a driver application requirement.

Operation logs that preserve superseded values. Article 9 requires that every processing operation be logged and that where a data element is modified or erased, the original is preserved. Many logistics systems overwrite in place. Ask specifically whether history is retained at field level, because retrofitting that is expensive.

What This Looks Like in Practice: Real-World Results

A Fortune 50 parcel and logistics network across 120 countries ran more than a million freight shipments a year through 51 sites with a driver pool of 4,500 split between captive and third-party capacity, and made dispatch decisions site by site with no shared view of state. Centralising planning and execution on Locus moved weekly execution rate from 75% to 92% and surfaced $14M+ in unused capacity at 99.99% uptime. The relevant feature for eFTI is the captive and third-party split. Any operator running mixed capacity faces the chain problem this article models, and a single shared state layer is what makes upstream data reachable from the leg that gets inspected.

A leading ASEAN apparel retailer running last mile almost entirely through carriers reduced carrier onboarding from three months to three days, a 97% improvement, and cut WISMO and returns queries by more than 40% after harmonising every carrier’s own status codes into one standard set synced to OMS and WMS. That normalisation work is the same discipline eFTI now demands. The operators who will find July 2027 straightforward are the ones who already stopped accepting each partner’s native format.

The model supplies the third result. Holding load, route and rules constant and varying only who carries it moved complete-dataset presentability from 100% to 63%. Nothing about the shipment changed. The gap is created entirely by the number of company boundaries the data must cross.

Also Read: Real-Time Visibility Across European Borders

Common eFTI Preparation Mistakes to Avoid

Reading it as a document digitisation project. The obligation is a served, machine-readable dataset behind an authenticated link, not a scanned CMR. A document management programme can complete successfully and leave the operator unable to answer a single eFTI request.

Assuming the TMS covers it. The TMS holds the transport leg. Dangerous goods classification, waste notification and combined transport declarations originate elsewhere, and those are the instruments with the worst consequences when missing.

Treating subcontracted volume as the carrier’s problem. The roadside obligation falls on the operator performing the movement, but the data it needs is generated by parties above it. Tendering the load does not tender the assembly problem.

Planning to the 2027 date rather than to the specifications. Remaining implementing specifications are due December 2026, and certified platforms could begin operating from January 2026. The integration work sits between those two dates, not after them, which leaves a considerably shorter runway than the headline deadline suggests.

Also Read: Who Is Allowed to See It: European Control Tower Access Limits

How Locus Supports eFTI Readiness

Locus, the world’s first Decision-Intelligent, Agentic TMS, holds consignment, party and execution state as one object across owned fleets, contracted operators and carrier legs rather than as separate records per party. That single-state design is the precondition for the eFTI dataset, because a unique electronic identifying link can only be maintained where one identifier survives every tender and subcontract. The platform connects to ERP, WMS, OMS and carrier systems through prebuilt connectors and an API-first design across 1,000+ carriers spanning EDI and REST endpoints, which is where upstream instrument data has to enter structured rather than as an attachment. Governance mechanisms covering explainability, traceability and audit trail support the operation-log requirements the Regulation places on platforms.

The platform reasons over more than 250 real-world constraints across 1.5B+ deliveries, 360+ enterprise customers and 30+ countries at 99.99% uptime, with $320M+ in aggregate logistics cost savings. Locus has been recognised by Gartner for seven consecutive years, including the 2026 Gartner Hype Cycle for Supply Chain Execution and Logistics Technologies and the 2026 Gartner Market Guide for Multicarrier Parcel Management Solutions, where ShipFlex is featured as a Representative Vendor. Locus holds Leader designation in the QKS SPARK Matrix for Transportation Management Systems 2025 and the #1 position for Route Planning in G2’s 2026 Best Software Awards.

In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Locus continues to operate independently.

eFTI readiness is not a document problem and it is not solved by the operator closest to the inspection. The Regulation requires a machine-readable dataset served from a certified platform behind a unique shipment link, and the instruments carrying the heaviest consequences originate three company boundaries upstream of the vehicle being checked. Modelling that chain puts a three-tier subcontracted operation at 63% presentability against 100% for the same load carried own-account, and reaching a 99% pass rate would require every handoff to run at 99.89%, which is an integration standard rather than a procedural one. Locus makes it reachable by holding one consignment state across every party in the chain. Request a Locus eFTI readiness assessment to map your own instrument mix against your subcontracting depth.

Frequently Asked Questions

What is the eFTI Regulation?

Regulation (EU) 2020/1056 establishes a legal framework requiring competent authorities across the EU to accept regulatory freight transport information when operators make it available electronically through certified eFTI platforms. It covers road, rail, inland waterway and air, and applies to dangerous goods, waste shipments, cabotage records, combined transport and carriage documentation.

When does eFTI become mandatory?

Authorities must accept electronically served information from 30 months after the first delegated and implementing acts entered into force, which places full application on 9 July 2027. Certified platforms and service providers could begin operating from January 2026, and the remaining Commission specifications are due in December 2026.

Does eFTI force operators to go paperless?

No. It obliges authorities to accept electronic information and sets the conditions under which they must. Operators may still present information on paper where the underlying legal act allows it. What changes is that an operator choosing the electronic route must do it through a certified platform in the prescribed format, rather than by emailing a PDF.

Is holding the data in our TMS enough?

Not on its own. Article 4 requires the information to be processed on a certified eFTI platform and served over an authenticated connection with a unique electronic identifying link. A TMS can be the source of much of the dataset, but the serving layer has to be certified, and several instruments in scope originate outside the TMS entirely.

Who is responsible when the data is missing at a roadside check?

The economic operator making the information available, which in practice is the party performing the movement. That is the structural difficulty the model quantifies, because dangerous goods and waste data originate with the consignor and have to survive every handoff down to the vehicle being inspected.

Does the required dataset differ by country?

Yes. Article 2(1)(c) brings in national requirements that Member States notify into Part B of Annex I, so a cross-border movement has to satisfy the union of the national subsets on its route. In the model, holding the chain constant, presentability falls from 63.0% in one Member State to 34.1% across five.