CONNECT · EDI
Operational EDI integration for terminals and third parties
A preadvice lands by email. Someone transcribes it. Someone else verifies it. The order goes out late. When the carrier asks, nobody has the same answer. Essentos Connect removes that chain: it is the terminal connectivity software that turns EDI messages into operational statuses feeding gate, yard, execution and billing without manual intervention, on the Essentos C-CORE architecture (Cargo-Centric Orchestration, Rules and Evidence).
Connect is not a message viewer. It is the EDI integration layer for terminal operating system flows in Spain, Europe and the United States, joining external data with the real operation of the terminal. Preadvices, releases, loading instructions and access events run through a single channel, with traceability and no double entry.
Typical impact
Fewer rekeys between the incoming EDI message and the operational order
Alignment between what the terminal executes and what it publishes to third parties
Fewer calls and emails with third parties about service status
From messages to decisions
The COPARN arrives by email. Someone opens it, reads it and keys it into the system by hand. Three hours later the carrier asks about status and no two people give the same answer. The release shows up the next day in another email nobody opens.
The COPARN comes in, is validated and generates an operational status with no manual step. The release activates the order. CODECO goes out when the event is confirmed. Carrier, agent and terminal work on the same reality.
How Connect structures the terminal data flow
Every day, the terminal exchanges dozens of messages with carriers, agents, port authorities and external systems. Connect organizes that traffic in three layers:
-
Operational inputs: preadvices, releases, loading instructions and VGM certifications that decide what can run, when and under which requirements
-
Confirmed outputs: gate, yard and dispatch events that third parties need to move forward without calling to check
-
Exchange traceability: receipt acknowledgement, consistency between sent and executed and a record of every EDI transaction with context
Carrier, freight forwarder, port authority and terminal team work on the same operational version. No competing truths, no calls to confirm what should already be confirmed.
EDI messages Connect handles
Connect processes the EDI messages that drive daily execution in container terminals:
-
COPARN: preadvice that triggers planning ahead of physical arrival
-
COREOR: release or delivery order that enables execution
-
COPINO: loading instructions with specific operational requirements
-
VERMAS: VGM certification validated before loading is authorized
-
CODECO: entry or exit event published once it is confirmed at the gate
-
COARRI: arrival notice that feeds discharge planning
-
APERAK: receipt acknowledgement that closes the exchange loop
Every message has a concrete operational effect. Connect makes sure that effect happens without manual rekeying, without intermediate emails and without gaps between what the system receives and what the terminal executes.
SIMPLE: compliance built into the operation
The exchanges SIMPLE requires are not a separate requirement. Connect folds them into the operational flow so the terminal complies without adding manual steps or duplicating information in parallel systems.
The result is double: regulatory compliance and operational gain. The same data that feeds SIMPLE feeds gate, yard and billing. One input, multiple uses.
Where Connect removes real friction
The difference shows up in the moments where manual coordination costs the most:
-
The preadvice arrives in advance and gate, yard and planning already know what to expect before the truck shows up
-
The carrier receives a CODECO consistent with what actually happened and stops calling to verify
-
The release activates the order before the team starts executing without a confirmed authorization
-
The freight forwarder checks status in the portal instead of sending an email someone will have to answer
Fewer interruptions, fewer discrepancies, less time spent moving data that should flow on its own.
Progressive rollout: start with what drives execution
You do not have to connect everything at once. Connect activates in phases based on real operational impact:
-
Phase 1: incoming messages that drive execution. COPARN, COREOR and COPINO so planning and gate work with real data from day one
-
Phase 2: outbound events third parties need. CODECO and COARRI so carriers and agents receive confirmations without phone calls
-
Phase 3: supporting integrations with ERP, billing and external platforms that complete the terminal data flow
The terminal sees value from phase one without interrupting the live operation.
Frequently asked questions
What types of EDI integration for terminal operating system does Connect support? ▾
Essentos Connect supports EDI (EDIFACT, XML, CSV), connections to Port Community Systems, customs systems and external platforms. As terminal connectivity software, it structures messages so they arrive as operational signals, not as files to review, for container, intermodal and inland terminals in Spain, Europe and the United States.
Does Connect replace the existing EDI system? ▾
No. Connect plugs into the existing EDI system and translates the messages into operational events inside Essentos. There is no need to replace the communications infrastructure.