EDI CODECO: automatic delivery to shipping lines

This guide explains what ContainerHub’s EDI system does when you record gate movements—in plain language. You do not need to know EDIFACT or technical message formats to follow along.

Note: ContainerHub’s EDI runs automatically once it is configured. Operators do not need to know anything about EDI for it to work.

What EDI means for a depot

Shipping lines (Maersk, MSC, CMA CGM, Hapag-Lloyd, Evergreen, and others) need to know where each container is at all times—including whether it entered or left a depot.

Companies exchange that information using a standard structured messaging system called EDI (electronic data interchange). When a container enters or leaves your depot, the line often requires the depot to notify them with a specific message. For depot gate movements, that message is typically CODECO, reporting arrival or departure at your facility.

In short: your daily Gate In / Gate Out is what the line wants reflected in a CODECO so their inventory and traceability match the depot’s reality.

How it works in ContainerHub

The flow is designed so operators keep their usual routine:

  1. The operator records Gate In or Gate Out in ContainerHub as usual (customer, container, move details).
  2. ContainerHub automatically generates the corresponding CODECO message.
  3. ContainerHub emails that message to the EDI address configured for that line.
  4. The line receives the confirmation in their EDI processing pipeline.
  5. The operator does nothing extra for EDI: the gate record is enough.

Flow: gate record in ContainerHub, CODECO generation, delivery to the line

One-line summary

A correctly recorded gate move triggers CODECO delivery, provided EDI settings for the depot and the line (customer) are in place.

Your depot’s EDI email

Each company in ContainerHub is automatically assigned a unique EDI email in this format:

company-name-edi@containerhub.es

That address is the sender for all EDI messages generated by that depot. Lines usually maintain an authorized sender list (whitelist): they only accept messages from addresses they have registered.

Your admin should share this email with each line when the depot is approved or when the EDI channel opens, so the line can add it to their whitelist.

Important: Share your EDI email with each line before you go live. If the line has not whitelisted your address, messages may be rejected.

Where to find it in the app

You can see this address under Settings → Company → EDI email.

Unique depot EDI email and relationship to the line’s whitelist

Tip: Keep the EDI email in an internal runbook so commercial and operations quote the same address when talking to lines.

Configuring each line’s EDI email

For ContainerHub to send CODECO to a given line, an admin must enter the EDI address the line provided on the customer record that represents that line in your depot.

Steps:

  1. Go to Depot → Clients.
  2. Open the customer record for the line.
  3. In the EDI email field, enter the address the line gave you.
  4. Save.

If EDI email is empty, ContainerHub does not send EDI for that line. The depot can still operate; there is simply no automatic CODECO notification until the email is set.

Which messages are sent and when

Only certain gate events trigger CODECO. Other day-to-day work does not generate automatic EDI to the line through this path.

EventEDI messageSent to
Gate In recordedCODECO (inbound)The container’s line (per customer configuration)
Gate Out recordedCODECO (outbound)The container’s line (per customer configuration)

No automatic EDI is generated for: moving a container in the yard, creating a quotation, recording damage, or actions other than inbound/outbound gate events as above.

EDI contacts for major lines in Latin America

Each line defines its own EDI address and partner process. The depot should request that address when registering as an approved depot or when opening interchange with the line. Do not rely on copied generic addresses—they change, and the right contact is usually the line’s local representative or partner portal.

LineHow to obtain the EDI email
MaerskContact your local Maersk representative or use the Maersk partner portal
MSCContact the MSC agency at your port
CMA CGMCMA CGM partner portal or local agency
Hapag-LloydLocal Hapag-Lloyd agency
EvergreenLocal Evergreen agency

Note: Exact addresses can change. Always confirm the current EDI email with the line before saving it on the customer record.

EDI send history

ContainerHub will log outbound EDI messages (date, time, line, container number, and status: sent or error) so you can audit and troubleshoot without relying only on raw outbound mail.

That history screen will be available under Reports → EDI (coming soon).

Until then, validate specific sends with your admin and the line’s EDI contact, and double-check depot EDI email and customer EDI email settings.

Related links