Get Ready for eFTI!  9 July 2027 – countdown to compliance starts now!✦

Overview

Dangerous goods data does not originate with the carrier. It originates with the shipper, at the moment a transport is booked — and everything downstream inherits whatever quality it had at that point. DCSA’s pilot works on that origin.

The scenario is a full multimodal journey: a shipper books dangerous goods with a container shipping line, the goods enter the EU by sea, and continue to their final destination by rail, road and/or inland waterway. Different competent authorities — port, customs, road safety — check the dangerous goods data shared and verify compliance with the applicable regulations, with the inspection completed digitally and without reliance on paper. Several scenarios cover emergency cases.

The distinctive element is an API. A shipper Dangerous Goods Declaration API, compliant with both eFTI and the European Maritime Single Window environment, is being developed and tested so that dangerous goods data can be provided correctly at booking and reused from there onwards. DCSA intends to make it freely available to all stakeholders, which is what turns a pilot into something the container shipping industry can adopt. The scope is deliberately complete: all eFTI components are covered, the movement crosses both internal EU borders and the EU external border, and the maritime leg tests interoperability and data reuse beyond the strict eFTI scope.

Lead beneficiary

DCSA (Digital Container Shipping Association)

Countries involved

Movements between EU Member States and across EU external borders

Transport modes

Barge, rail, road and maritime

Main stakeholders

DCSA · three dangerous goods competent authorities, including a port authority · a chemical shipper, two container shipping lines and two inland transport operators · nine container transport operators and a wider number of large chemical companies and dangerous goods shippers for validation · IT solution providers · booking systems, port community systems and transport management systems.

eFTI components

eFTI Gate · eFTI Platform · AAP · Registry of identifiers · CA application

Timeline

Planning 15.03.2026 – 30.06.2026
Development 01.07.2026 – 30.03.2027
Piloting 01.07.2027 – 30.09.2028
Results 01.10.2028 – 15.02.2029

Pilot type

Focused largely on the private sector, with authorities playing an important role in the end-to-end testing
  • Ensure source dangerous goods data is compliant and can be reused throughout the journey of the goods, regardless of transport mode, platform or IT system, Member State or transport service provider.
  • Test and validate the exchange of eFTI dangerous goods data in business-to-business and business-to-authority settings, involving multiple public and private stakeholders.
  • Ensure interoperability between inland dangerous goods data requirements under eFTI and maritime dangerous goods data requirements under the European Maritime Single Window environment.
  • Showcase and promote the use of eFTI platforms within the container shipping industry and among its customers.
UC1

A shipper books transport of dangerous goods with a container shipping line; the goods enter the EU by sea and continue to their final destination by rail, road and/or inland waterway.

UC2

The Multimodal Dangerous Goods API is used as input to an eFTI platform of the transport operator.

UC3

Port, customs, road safety and other competent authorities check the dangerous goods data and verify compliance, completing the inspection digitally.

UC4

Different scenarios are piloted to cover several emergency cases.

The pilot expects to test and validate the end-to-end exchange of eFTI dangerous goods data in business-to-business and business-to-authority settings, involving multiple public and private sector stakeholders, and to support the private sector in sending and receiving source dangerous goods data.