In short and in plain language
From July 2027, officials must accept freight data in digital form. The data has to come through a checked platform.
For shops this is a free choice. Paper is still allowed. It is not yet clear if it will be a must later.
The data mostly comes from the program for goods and orders. It holds the customer, the address, the weight and the boxes. Dangerous goods need more facts.
A program in the middle turns the data into the right form. It checks if all is fine. Then it sends the data on.
We help you check your data. We also build the link.
A building materials dealer supplies construction sites with its own trucks, heavy goods go out through two freight forwarders, and part of the range is dangerous goods, such as solvents or gas cylinders. Every route carries a delivery note, accompanying documents and, for the dangerous goods, a transport document. Now the word from the forwarding side is that freight papers will go digital from July 2027. Logistics management and IT end up with three questions: What actually changes, is it mandatory, and which data does the ERP need to hold for it? This article answers them from the interface perspective. It explains what the EU regulation on electronic freight transport information, eFTI for short, covers and what it does not, which data fields the common eFTI data set provides for, where these fields sit in the ERP today and which tasks a middleware takes on between the ERP, the forwarder and a certified eFTI platform. First, an honest assessment: for businesses, eFTI is voluntary for now. The benefit lies in setting up a clean data model early, not in a deadline that merchants would have to meet.
Key takeaways
- From 9 July 2027, authorities must accept freight transport information that businesses provide electronically via a certified eFTI platform (BMV). The date follows from 30 months after the first eFTI legal acts entered into force.
- For merchants, forwarders and carriers, eFTI is voluntary: they can continue to use paper freight documents for now (BMV). The Commission will only consider an obligation in its evaluation due by 21 February 2029 (Art. 16(1) Regulation (EU) 2020/1056).
- eFTI transmits structured data sets instead of documents. Consignor and consignee names hold at most 35 characters, the UN number has four digits, and weights carry a unit code (Delegated Regulation (EU) 2024/2024).
- The fields come from the order, delivery note, item master and route planning in the ERP. The middleware maps them to the eFTI data set, checks lengths and code lists and writes the inspection link (UIL) back to the delivery note.
- Only around 14 percent of 566 surveyed companies from logistics, shipping businesses and IT services had heard of the eFTI regulation by fall 2024, and just over 1 percent felt well informed about it (BALM).
- The BMV expressly advises against using the national data sets published by the Commission without checking them. Field mappings therefore belong in the middleware with version control, not hard-coded in the ERP export.
What changes on 9 July 2027
The basis is Regulation (EU) 2020/1056 on electronic freight transport information. It entered into force on 20 August 2020 and obliges the authorities of the member states to accept legally required information on the carriage of goods in electronic form during inspections, provided that businesses make it available in the intended format via certified platforms (BMV). All modes of transport are covered: road and rail freight, inland waterways and air freight.
The regulation itself sets out when this obligation for authorities applies: 30 months after the first of the delegated and implementing acts that define the data set and the authorities' access entered into force (Art. 5(1) Regulation (EU) 2020/1056). These first legal acts entered into force in January 2025 (European Commission). This produces the date given by the German Federal Ministry for Transport: from 9 July 2027, the eFTI regulation applies in full, and the authorities of the member states must accept information transmitted electronically via certified eFTI platforms (BMV).
In practice, this means that from that day, an authority carrying out an inspection on the road, at the depot or at the company must accept the required information even if it is available digitally via a certified platform instead of on paper. All competent authorities must be able to carry out paperless inspections based on digital data (BMV). The regulation does not add information or language requirements beyond the existing rules; it is about the same content in a different form (BMV).
The legal framework for the platforms themselves is not yet complete. The Commission set out the functional requirements for eFTI platforms in Implementing Regulation (EU) 2025/2243. It plans to adopt the remaining implementing specifications, including the rules for certifying platforms and service providers, by December 2026 according to its own timeline (European Commission). Anyone planning today is therefore planning against a framework whose last building block is still missing. That is no argument against preparing the ERP, but it is an argument against committing early to a specific platform offering.
Mandatory or voluntary: what applies to merchants
The regulation places obligations on the authorities, not on businesses. The BMV puts it clearly: cargo owners, forwarders and carriers may provide the legally required information digitally via certified platforms, but can continue to use freight documents in analog form for now (BMV). The Commission also states in the implementing regulation on platforms that businesses may continue to present the required information on paper (Implementing Regulation (EU) 2025/2243, recital 8).
Anyone who chooses the digital route is bound by rules, however. The data must then have been processed on a certified eFTI platform, be available in machine-readable form and, at the authority's request, in human-readable form; this view is shown on site on the screen of a device belonging to the business (Art. 4(2) and (4) Regulation (EU) 2020/1056). A PDF generated in-house on the driver's tablet is therefore not an eFTI submission, even if its content is complete.
The words for now carry weight. By 21 February 2029, the Commission must evaluate the regulation and present a report (Art. 16(1) Regulation (EU) 2020/1056). In doing so, it will expressly consider initiatives to introduce an obligation for businesses to provide the required information electronically. No such obligation has been adopted, and this article does not claim otherwise. Businesses that have structured their data by then will not have to rebuild under time pressure if an obligation does follow.
Only certain information is covered. The regulation names information under Article 6(1) of EEC Regulation No 11, information on combined transport, cabotage evidence, information on waste shipments and the transport document for dangerous goods under chapter 5.4 of ADR, RID and ADN (Art. 2(1) Regulation (EU) 2020/1056). National rules that the member states have notified to the Commission are added to this. For Germany, the annex lists, among others, the accompanying document under section 7 of the German Road Haulage Act (GüKG) and the German ordinance on the carriage of dangerous goods by road, rail and inland waterway (GGVSEB) (Delegated Regulation (EU) 2024/2025).
What this means for a merchant depends on how it delivers. If it carries its own goods to customers with its own vehicles and staff, this is usually own-account transport, which does not require a road haulage authorization (sections 1(2) and 9 GüKG). The accompanying document under section 7 GüKG, on the other hand, concerns transport operations that do require such an authorization; it names the goods carried, the loading and unloading places and the customer who placed the order (section 7(1) GüKG). Dangerous goods are a separate matter: for domestic transport by road, the ADR rules apply (section 1(3) GGVSEB), including its rules on the transport document, regardless of whether a forwarder or the company's own truck does the driving.
| Situation | Typical documents today | Data behind them in the ERP |
|---|---|---|
| Delivery with own truck as own-account transport, no dangerous goods | Delivery note; no accompanying document under section 7 GüKG, as no authorization is required (section 9 GüKG) | Order, delivery address, items, quantities |
| Delivery with own truck, with dangerous goods | Transport document under ADR chapter 5.4 (section 1(3) GGVSEB) | Item master with UN number, name, class, packing group; quantity per route |
| Shipment via forwarder or carrier within Germany | Carrier's accompanying document (section 7(1) GüKG), often also a consignment note (section 408 HGB) | Consignor, consignee, goods, loading and unloading place, weights, packages |
| Dangerous goods via forwarder | Transport document under ADR; the dangerous goods data comes from the shipper | The same dangerous goods fields as for own deliveries |
| Cross-border, combined transport, cabotage | Evidence under EU law (Art. 2(1) Regulation (EU) 2020/1056) | Core consignment data, plus modes of transport and transshipment points |
The contract of carriage is a separate matter. The consignment note governs the relationship between consignor and carrier; an electronic record is already treated as equivalent today if authenticity and integrity are preserved (section 408(3) HGB). For cross-border road freight, an additional protocol to the CMR on the electronic consignment note governs the civil-law relationships of the parties and does not introduce any obligation to communicate electronically (German government bill on the e-CMR additional protocol). eFTI, by contrast, concerns the route from the business to the authority. The data overlaps to a large extent: according to Delegated Regulation (EU) 2024/2024, freight transport information is for the most part the same information that businesses exchange anyway for their operational processes.
How far the industry has come: figures from the BALM survey
The German Federal Office for Logistics and Mobility (BALM) has measured how well known the topic is. 566 companies from the transport and logistics sector, shipping businesses with own-account transport and IT services took part in the online survey from 16 September to 6 October 2024 (BALM). Among the shippers, retail made up the largest group with 37 companies, followed by construction with 35 (BALM), in other words businesses with their own transport, like the building materials dealer described at the start.
The result is sobering. The majority of the companies surveyed, 77 percent, had not heard of the eFTI regulation before the survey, and just under 9 percent were unsure (BALM). Only around 14 percent had already heard of it, and only one in ten of these companies felt well informed; relative to all respondents, that was just over 1 percent (BALM). Anyone looking into eFTI today is early, not late.
Willingness is there nonetheless. Of the companies that did not know the regulation or did not know it well, 46 percent would in principle be willing to provide freight transport information to authorities electronically; among logistics companies the figure was slightly higher at 47 percent than among shipping businesses at 40 percent (BALM). Those who were undecided most often cited a possible dependency on software and IT service providers at 53 percent, followed by a lack of knowledge, unclear investment costs and legal consequences at 52 percent each (BALM).
The willing companies saw the reduction of internal administrative work as the biggest benefit, named by 55 percent; shippers named the reduction of error sources third, at 45 percent (BALM). At the time of the survey, 20 percent of the companies used digital consignment notes, and around 29 percent were planning to (BALM). Only 16 percent of respondents used ERP software (BALM).
Official statistics show a similar picture for the transport, storage, postal and courier sector: in 2023, around 15 percent of all companies there used ERP software, and around 31 percent of companies with 10 or more employees (Statistisches Bundesamt 2023, via BALM). For the merchant, this leads to a sober assessment: structured data on the consignment, items and dangerous goods often originates with the shipper, not with the carrier. Merchants who maintain it properly in their own ERP can supply it to every partner and later to a platform as well.
Structured data sets instead of documents
eFTI does not work with documents. The regulation relies on structured data sets that are defined in law, so authorities only access the information they need and are authorized to inspect (BMV). A data element is the smallest unit of information with a unique definition and technical characteristics such as format, length and character set (Art. 3 Regulation (EU) 2020/1056).
Delegated Regulation (EU) 2024/2024 establishes the common eFTI data set and the data subsets. Each subset corresponds to a specific legal requirement, such as dangerous goods law or a national rule; the common data set contains all elements, and elements needed by several subsets appear only once (Art. 3 Regulation (EU) 2020/1056). So a consignment does not involve filling in several forms, but one data set from which each authority retrieves the part it is responsible for.
For the interface, the technical characteristics are what matters, because they determine what the ERP has to deliver. Some examples from the common data set in table 1 of Delegated Regulation (EU) 2024/2024:
- Consignor and consignee name: text with at most 35 characters, as are the street name and city name of the address (Delegated Regulation (EU) 2024/2024)
- Gross weight of the consignment: a number with a unit code, permitted values being gram, kilogram and tonne (GRM, KGM, TNE); it includes the packaging but not the transport equipment
- Number of packages and description of goods, the latter as text with at most 512 characters (Delegated Regulation (EU) 2024/2024)
- Dangerous goods per consignment item: UN number as a four-digit number, proper shipping name with at most 128 characters (Delegated Regulation (EU) 2024/2024)
- Further dangerous goods data as codes: hazard class, packing group, tunnel restriction code and an indicator for limited quantities
- Places and times: place of acceptance by the carrier, place of receipt and the date of acceptance
Two consequences follow immediately. First, long company names from the ERP do not simply fit into a field with 35 characters; how to handle truncation and special characters between systems is described in the article on umlauts, accents and field lengths. Second, the data set expects units as codes. Anyone who keeps quantities in bags, pallets or big bags in the ERP needs a clean conversion into weight, as shown in the article on units of measure and pack sizes. Many merchants already know the pattern from customs data from the ERP: the transmission is not the hard part, the completeness of the master data is.
Do not adopt national data sets without checking
Where the fields come from in the ERP
The Commission expressly expects businesses to draw on existing systems. According to the implementing regulation on platforms, businesses should be able to use, as far as possible, information available in internal systems such as enterprise resource planning or transport management systems that they use to manage consignment notes and transport orders (Implementing Regulation (EU) 2025/2243, recital 7). For a merchant with its own deliveries, this is usually the ERP with order, delivery note and item master, supplemented by route planning. How the ERP is connected to the shop, warehouse and partners is described on our page on ERP and inventory integration.
A comparison with the consignment note shows how much of this already exists. The carrier can request a consignment note with twelve items of information, including the name and address of the consignor, carrier and consignee, the place and date of acceptance, the place of delivery, the type of goods and packaging, the number, marks and numbers of the packages and the gross weight (section 408(1) HGB). These are almost the same core fields that the eFTI data set holds for the consignment. The following table maps them to the usual sources in the ERP.
| eFTI field group | Source in the ERP | Typical gap |
|---|---|---|
| Consignor with name and address | Company master data, shipping warehouse or plant | Several warehouse locations without their own address in the master data |
| Consignee with name and address | Customer master and different delivery address in the order | Construction site address as free text, company name longer than 35 characters |
| Carrier | Forwarder master data or own fleet | Own vehicles without a record, forwarder only stored as a shipping method |
| Place of acceptance and receipt | Warehouse location, delivery address, delivery date | Date only as a requested date, not as the actual acceptance |
| Gross weight, packages, packaging | Delivery note with packages, item weights | Item weight missing or net only, packages not recorded |
| Description of goods | Item description, product group | Internal abbreviations instead of a clear description |
| Dangerous goods per item | Item master with data from the safety data sheet | UN number present, packing group and tunnel code missing |
| Transport document identifier | Delivery note or shipment number | One number for several routes after a partial delivery |
Weight deserves a close look. In the eFTI data set, the gross weight of the consignment includes the packaging but not the weight of the transport equipment (Delegated Regulation (EU) 2024/2024). Implementing Regulation (EU) 2025/2243 names trailers, pallets or containers as examples of transport equipment. For a building materials dealer whose delivery notes include pallets, this is a real question for the data logic: is the pallet weight included in the gross weight on the delivery note or not? The answer should be defined and documented once, not estimated anew for each route.
For dangerous goods, the source is the safety data sheet, whose transport section holds the information for carriage. How to take this information into the item master as fields is described in the article on hazardous goods and hazardous substance data from the ERP. eFTI adds the requirement that the information is needed per consignment item, with the gross weight or volume of the dangerous goods. So the ERP must not only know that an item is a dangerous good, but also how much of it is on which route. The assessment under dangerous goods law remains with the shipping company; the interface supplies data, not a classification.
On the platform, each data set belongs to one consignment movement: goods carried by one means of transport from the same loading place to the same unloading place under one contract of carriage (Art. 1 Implementing Regulation (EU) 2025/2243). If a delivery is split or loaded onto two routes, this results in two consignment movements and therefore two data sets. How partial quantities run cleanly between the shop and the ERP is shown in the article on partial deliveries and part invoices. For eFTI, this logic has to extend to the route, not just to the order.
The certified platform and the inspection route
Without a platform there is no eFTI. For inspection purposes, the data does not sit in the merchant's ERP but on an eFTI platform certified by an accredited conformity assessment body; information that authorities receive via such a platform carries a certification mark (Art. 12 Regulation (EU) 2020/1056). A business can develop a platform itself and have it certified, or use one through an eFTI service provider, which must grant authorities direct access to the data free of charge (Art. 3 and Art. 10 Regulation (EU) 2020/1056).
For the ERP, one definition from Implementing Regulation (EU) 2025/2243 is important: the tributary ICT system. This means a system outside the platform through which business users connect to the platform to process eFTI data (Art. 1 Implementing Regulation (EU) 2025/2243). Platforms must offer access via a user interface, via machine-to-machine communication over secure connections to such systems, or both (Art. 4(1) Implementing Regulation (EU) 2025/2243). An ERP that automatically passes consignment data to the platform is exactly this case, and the connection is a classic piece of API development with certificates, retries and logging.
On the platform, a separate data set is kept for each consignment movement, the so-called eFTI CMDS, to which the platform automatically assigns a unique identifier (Art. 1 and Art. 8 Implementing Regulation (EU) 2025/2243). Business users can create, edit, read, download and archive it and add the signatures of the shipper, carrier and consignee (Art. 9(1) Implementing Regulation (EU) 2025/2243). Every processing operation is logged, and if a value is changed or deleted, the original value is retained (Art. 9(5) Implementing Regulation (EU) 2025/2243).
During an inspection, the business shows the link to the data set, the so-called UIL. The authority can process it directly if it is shown in machine-readable form on the screen of a device or presented on paper (Art. 2(1) Implementing Regulation (EU) 2024/1942); the recitals give a barcode or QR code on a mobile phone or tablet as examples. The authority then retrieves the data from the platform via a government eFTI Gate, and communication between gate and platform uses the XML format (Art. 9(1) Implementing Regulation (EU) 2024/1942). If a platform confirms receipt of a request but does not deliver any data within 60 seconds, the authority receives a no response message (Art. 3(3) Implementing Regulation (EU) 2024/1942).
For the merchant, this leads to two practical points. The UIL belongs back in the ERP so that it appears on the delivery note or in the driver app. And the platform must also respond when the ERP is down for maintenance, because the authority queries the platform, not the ERP. If the authority finds that information is incomplete, it can send the business a follow-up message (Art. 3(4) Implementing Regulation (EU) 2024/1942); the platform notifies the authorized users (Art. 3(2) Implementing Regulation (EU) 2025/2243). This message should also end up with the order in the ERP and not in a mailbox that nobody reads.
What the middleware takes on
It makes sense to place a middleware between the ERP and the platform, for the same reason as with shipping service providers: the ERP should deliver its data once, and the translation into third-party formats belongs in one central place. We described this for carrier interfaces in the article on shipping and logistics interfaces; eFTI adds dangerous goods, contact with authorities and logging requirements. Typical tasks are:
- Build consignment movements: compile one data set per vehicle and unloading place from route planning and delivery notes
- Map fields: assign ERP fields to the elements of the common eFTI data set, with one version per state of the legal acts
- Check values: validate lengths, character sets, code lists and unit codes before handover and report errors with a reference to the order
- Write back the UIL: store the link to the data set with the delivery note and output it as a QR code on paper and in the driver app
- Apply corrections: transmit reloading, partial quantities and cancellations before departure as edits, so that the log shows the history
- Process feedback: assign follow-up messages from the authority and status messages from the platform to the order
- Keep the paper route: be able to print the previous accompanying document if the platform fails
The logs deserve attention. An eFTI platform records every data processing operation and keeps the logs available to the authorities for verification purposes (Art. 9(1) Regulation (EU) 2020/1056). The same traceability should apply in the ERP and the middleware: which version of a delivery note was transmitted when, and with what result. How to describe such data flows for auditors is shown in the article on GoBD process documentation.
# Mapping delivery note -> eFTI data set (excerpt, example)
version: "2024-2024-v1"
consignment_movement:
key: [route_id, unloading_place]
fields:
eFTI51_consignor_name:
source: warehouse.company_name
max_length: 35
on_overflow: use_short_name
eFTI68_consignee_name:
source: order.delivery_address.name
max_length: 35
eFTI41_gross_weight:
source: sum(delivery_note.packages.gross_kg)
unit_code: KGM
include_pallet: false
eFTI47_package_count:
source: count(delivery_note.packages)
eFTI232_un_number:
source: item.dangerous_goods.un_number
format: n4
validation:
on_error: report_to_order
write_back:
uil: delivery_note.efti_linkThe excerpt shows one possible structure, not a format defined by the regulation. What matters is that rules such as the handling of excess length or pallet weight exist as configuration and are not scattered across the export program. If the Commission changes the data set, a new version of the mapping is created, tested and activated on a set date. This is the same way of working that a middleware uses to manage other formats from shipping service providers or marketplaces.
An eFTI-ready data model in five steps
Take stock
Which routes run with your own vehicles, which via forwarders? Which items are dangerous goods? Which documents are printed today, and by whom? The answers show which data subsets actually apply.
Close gaps in the master data
Maintain gross item weights, packaging type, dangerous goods fields, warehouse locations with addresses and forwarders as partners in their own right. This pays off even without eFTI, because the same data improves delivery notes, shipping labels and consignment notes.
Define the consignment movement
Decide how a data set is created from order, delivery note and route, how partial quantities are handled and where the identifier of the data set is stored in the ERP.
Mapping in the middleware
Create the field mapping with version control, check lengths and code lists and run test data against the current state of the data set, without committing to a platform yet.
Choose platform and partners
Only once certification rules and certified platforms are available, connect the platform, put the UIL on the delivery note and in the driver app and agree with the forwarders who keeps which data set.
Which routes run with your own vehicles, which via forwarders? Which items are dangerous goods? Which documents are printed today, and by whom? The answers show which data subsets actually apply.
Maintain gross item weights, packaging type, dangerous goods fields, warehouse locations with addresses and forwarders as partners in their own right. This pays off even without eFTI, because the same data improves delivery notes, shipping labels and consignment notes.
Decide how a data set is created from order, delivery note and route, how partial quantities are handled and where the identifier of the data set is stored in the ERP.
Create the field mapping with version control, check lengths and code lists and run test data against the current state of the data set, without committing to a platform yet.
Only once certification rules and certified platforms are available, connect the platform, put the UIL on the delivery note and in the driver app and agree with the forwarders who keeps which data set.
In our experience, it is not the transmission that takes the most time, but maintaining the master data. That is why it is worth starting there, even while the platform question is still open. Merchants who mostly ship via parcel services, carry no dangerous goods and have no fleet of their own can watch eFTI calmly; as things stand, the obligation lies with the authorities. For wholesalers with their own fleet, the calculation is different: many routes run with paperwork every day, and every missing piece of information costs time during an inspection. How shop and ERP work together in wholesale is described on the page on ERP integration for wholesale. You can find an overview of our services around ERP interfaces on the services page.
Voluntary does not mean without consequences
Related Articles
Umlauts, Accents, Field Lengths: Names Between Shop and ERP
Why customer names arrive garbled in the ERP: define the character set per system, normalize to NFC, transliterate only for labels, truncate with a warning.
Customer data in integration logs: what may be kept
Customer data in integration logs: which fields debugging needs, how to mask them and how to set separate retention for logs and the dead-letter queue.
Multi-Entity ERP: Running One Shop Across Company Codes
Corporate groups running several ERP entities and one shop: item routing, number ranges, tax codes, stock aggregation and order splitting done properly.