eFTI and ICS2: why freight teams need one live shipment record before 2027

What is changing?

Freight has always involved documentation. The difference now is that authorities, customers and operators increasingly need the data behind the documents to be structured, searchable and ready earlier in the movement.

Two major examples are eFTI and ICS2. For a high-level overview of both frameworks, see our eFTI and ICS2 freight compliance guide.

eFTI is the EU framework for electronic freight transport information. Its direction is clear: reduce reliance on paper and make regulatory transport information easier to share electronically with authorities.

ICS2 is the EU advance cargo information system. It requires safety and security data to be submitted before goods arrive, so customs authorities can assess risk earlier in the supply chain.

For freight operators, the message is obvious: compliance is becoming a data quality problem.

The real issue is not the regulation. It is the workflow.

A lot of freight teams will treat eFTI and ICS2 as a compliance project. That is only half right.

The bigger issue is operational.

When shipment information is scattered, every compliance task becomes harder:

1. Data is copied from emails into spreadsheets.
2. Documents are stored away from the live shipment record.
3. Quote details change but compliance data is not updated.
4. A route changes but permit and document checks lag behind.
5. Customs data depends on someone manually checking multiple systems.
6. Teams rely on individual memory instead of a shared live view.

That might work when volumes are low and deadlines are forgiving. It breaks when customers expect faster responses, authorities expect better data and teams are already overloaded.

Why a TMS alone is not enough

A TMS is important. It records structured shipment data and gives the business a system of record.

But a lot of the work that creates compliance risk happens before and around the TMS:

1. The first quote request arrives by email.
2. The customer sends a PDF with missing information.
3. The rate comes from a carrier portal or internal tariff.
4. The planner changes the route.
5. A document arrives in a separate inbox.
6. The customer asks for an update in an old email thread.
7. A permit or compliance check depends on data held outside the TMS.

This is why freight operators need an operational layer around the TMS.

Not a replacement.

A layer that connects the messy work, structures it and keeps it aligned. That operational layer is what a freight operating system provides.

What is one live shipment record?

One live shipment record means every operational input for a movement connects to the same current reference. That includes:

1. Customer emails.
2. Quote requests.
3. Rates and surcharges.
4. Container, vehicle or asset details.
5. Route and permit information.
6. Customs and compliance data.
7. Documents.
8. Status updates.
9. Exceptions.
10. Internal decisions and audit history.

Instead of each team working from a different version of the truth, everyone works from the same live operational picture.

That is the foundation for reliable automation.

How this helps with eFTI and ICS2 readiness

A live shipment record does not magically make an operator compliant. Compliance obligations still need to be confirmed with the right customs, legal and regulatory specialists.

But it does solve the operational problem that sits underneath most compliance failures: inconsistent data.

A live shipment record helps teams:

1. Keep documents tied to the movement they belong to.
2. Spot missing information earlier.
3. Reduce manual rekeying.
4. Keep quote, route, permit and compliance data aligned.
5. Give operators a clearer audit trail.
6. Make structured data available to the systems that need it.
7. Avoid late surprises before border, permit or document deadlines.

The point is not to add another compliance dashboard. The point is to stop compliance becoming a disconnected afterthought. Compliance automation and document automation work best when they run against the same live reference from the start.

What freight teams should do now

Freight teams do not need to rip out their TMS or rebuild their whole operation to prepare.

They should start by mapping where shipment data currently lives.

Ask these questions:

1. Where does the first customer request arrive?
2. Where is quote data created?
3. Where are rates checked?
4. Where are documents stored?
5. Where are route and permit decisions recorded?
6. Where is customs or compliance data prepared?
7. Where do changes get communicated?
8. Which parts are copied by hand?
9. Which fields regularly go missing?
10. Which checks happen too late?

The answers will show the real risk areas.

Most operators will find the same pattern: the issue is not one bad system. The issue is too many disconnected handoffs.

The best starting point: email into operations

For many freight forwarders and hauliers, the inbox is still the start of the shipment.

That makes email into operations automation one of the highest impact starting points.

When an inbound request arrives, the system should be able to extract the key details, link the email to the right shipment record, flag missing information and trigger the next workflow.

That could be quote building, document checking, route planning or compliance review.

This is where AI is useful. Not as a chatbot on top of the business, but as a way to structure messy operational inputs so teams can act faster and with fewer errors.

Where FRAI fits

FRAI works around the systems freight teams already use.

It creates one live reference per shipment and connects the workflows around it: quoting, email into operations, documents, compliance, heavy haulage planning, permits, scheduling and asset tracking.

The goal is simple.

Keep the TMS and ERP in place.

Connect the work around them.

Make the shipment record live.

Automate the manual handoffs that slow teams down and create risk.

For eFTI and ICS2 readiness, that means compliance data is not treated as a last minute document task. It becomes part of the live operational flow from the start. Book a demo to see how this fits your operation.

A practical preparation checklist

Freight operators preparing for digital compliance should focus on these steps:

1. Audit where shipment data is created, copied and changed.
2. Identify which fields are needed for compliance checks.
3. Connect emails and documents to the shipment record.
4. Reduce spreadsheet based rekeying.
5. Create a live view of missing or conflicting information.
6. Link documents to the movement they support.
7. Keep quote, route, permit and compliance workflows aligned.
8. Build an audit trail of changes and decisions.
9. Integrate with existing TMS, ERP, customs and compliance tools.
10. Start with one workflow, then expand.

The operators who prepare early will not just reduce compliance risk. They will also remove manual work from the wider operation.