EDI for empty depots is not a side hobby for IT. For a physical empty yard in the ~200–5,000 TEU band, it is how shipping lines learn that a box arrived, left, or changed status — without calling your gate clerk.

CODECO (and related empty-move messaging) only stays credible when it reflects the same events your yard used for inventory, holds, and billing. Re-keying gate facts into a second tool is how mismatches — and escalations — are born.

ContainerHub is positioned as the ops spine that keeps gate, digital EIR, yard status, and line-facing truth aligned so EDI can be fed cleanly. It is not generic EDI middleware, and it is not freight TMS.

What CODECO means for the depot desk

You do not need to memorize every segment table to run a good depot. You do need to know that the line’s planning and billing systems trust the message only if it matches what actually happened at the gate and in the yard.

Related empty-move and status messaging (COARRI-style contexts at some terminals, or line-specific variants) sits in the same family of problems: one physical event, one digital truth, then outbound messaging. Treat “CODECO” as the operator label for that empty-move handshake — not as a claim that every partner uses one identical map.

What the desk actually owns:

Correct container ID, size/type, and owner/line context
Timestamp that matches commercial reality (not “when we typed it later”)
Condition / hold outcomes that change availability
A path to resend or correct without inventing a second history

If those inputs are soft, no amount of “we sent EDI” saves the relationship.

Why lines escalate when gate ≠ EDI

Lines escalate when their

From the line’s seat, that looks like inventory risk and billing risk. From your seat, it often started as a Monday return surge where paper EIRs and chat photos outran the system.

The painful part is not the protocol. It is the gap between lane capture and outbound message. Manual re-key into a separate EDI workstation after the truck left is a classic failure mode: the clerk who saw the box is not the person who typed the segment, and peak week multiplies the error rate.

When gate events and EDI diverge, the phone tree starts: “send EIR,” “confirm status,” “why does your file disagree with ours?” That is desk load you cannot bill, and trust you burn faster than TEU count errors.

Soft check: if line escalations still begin with “your EDI doesn’t match what we see,” map the chain from digital Gate In / EIR through yard status on containerhub.ai or review pricing. Soft CTA only — no directory claim pitch.

Spreadsheet / email until peak week

Email and Excel can look “fine” for EDI-adjacent work when volume is calm.

A typical fragile stack:

Gate sheet or paper EIR in the lane
Photos in WhatsApp or a shared drive
A clerk retypes moves into a spreadsheet “for the line”
Someone else pastes or uploads into an EDI tool, mailbox, or partner portal
Corrections live in rep

If this sounds familiar, you are not alone — and you are not looking for a prettier spreadsheet. You are looking for an ops system that makes the outbound message a consequence of the gate event, not a parallel project. For the empty-yard framing of that spine, see empty container depot software. For why spreadsheet ops stop scaling under surge, the honest comparison sits at /vs/excel.

Gate → EIR → yard → EDI chain

The minimum clean chain for EDI for empty depots is short. Every shortcut you take shows up later as an exception.

1. Gate event (physical truth)

Capture Gate In / Gate Out while the visit is real: container identity, truck/driver context you need, timestamp, and enough structure that the record can stand alone later. Peak windows need batch-friendly paths for clean empties without skipping evidence you will need in a dispute. That is the job of gate management software for depots — digital lane capture and EIR, not a second product slug competing with it.

2. Digital EIR (interchange evidence)

Bind condition narrative, photos, and acknowledgements to the same movement. The EIR is not “nice PDF packaging.” It is what you open when the line challenges seal, damage, or time.

Outbound CODECO-style (and related) messages should be generated from — or tightly validated against — that same event chain. Manual re-key into disconnected codeco edi software or a separate mailbox is where silent drift starts.

Operator rule of thumb: if you cannot point from a sent message back to the gate event and EIR, you do not have a controllable process. You have a hope.

This post is an operator explainer, not an integration cookbook. Partner maps, segment variants, and certification questions belong in a scoped implementation conversation — not in marketing claims.

Software must-haves: audit trail, re-sends, exceptions

When buyers search software edi codeco or codeco edi software, they often get middleware glossaries. Empty-depot buyers should demand ops-level controls instead.

Audit trail

Who recorded the gate move, when, and with what evidence
What changed on the unit after Gate In (hold, grade, repair outcome)
What was sent outbound, when, and under which partner/line context

Without that trail, every dispute becomes archaeology.

Controlled re-sends and corrections

Mistakes happen. What matters is whether you can:

Correct the operational record once
Re-send or replace the outbound message without inventing a third version in email
Show the line a coherent history

Shadow “just send another file” habits create duplicate inventory ghosts.

Exception queues humans can work

One spine, not two systems of record

Demand that gate, EIR, yard, and messaging share one unit timeline. If the demo shows a beautiful EDI console that still needs nightly CSV from the gate sheet, you are buying the peak-week problem again — only with more licenses.

Honest framing for ContainerHub: it is depot/yard ops SaaS that keeps the operational truth ready for line connectivity. Do not treat it as a claim of universal EDI certification, a full trading-partner network, or freight TMS.

USA multi-line depots

USA mid-market empty depots rarely look like a single-line terminal with one TOS.

More often you have:

Multiple shipping lines and leasing programmes on one yard
Different expectations for timing, status codes, and document packs
Shared gates and labor across clients
Commercial pressure on free days, storage, and handling that must match event clocks

That environment punishes any process where each line’s EDI is a separate manual cottage industry. The durable pattern is: one gate/yard truth per unit, then partner-specific outbound rules — not one spreadsheet per line that drifts by Friday.

USA-first buyers should also stay clear of category traps:

Not freight forward

Soft CTA: keep gate/yard truth ready for line EDI

If your desk still reconciles gate sheets against what lines received, the fix is not a louder email template. It is a cleaner chain from Gate In → EIR → yard status → outbound messaging.

ContainerHub is built as that depot/yard ops spine for empty-container facilities: digital gate and EIR, inspections and M&R on the same unit history, yard positions and holds, billing-oriented event clocks, client portal visibility, and AI Jarvis with human approval before live records change — so line-facing EDI has something trustworthy to stand on.

It is not EDI middleware sold as a standalone translator. It is not freight TMS. Soft CTA only: review the product and plans; no directory “claim your listing” pitch.

Soft next step

Walk one peak return day against the Gate → EIR → yard → EDI chain above
See plan limits on pricing
Request a demo with your real multi-line exception cases (failed message, hold blocking availability, correction/re-send)

Visit ContainerHub · Pricing · Related product page: Gate management software for depots

Not marine TOS projects whose core is vessel/rail berth planning
Yes physical empty depot / inland yard ops in roughly the 200–5,000 TEU band, where gate queues, digital EIR, holds, and line trust are daily work

Multi-line reality is exactly why soft discipline in chat threads does not scale — and why the ops spine has to feed EDI, not the other way around.

Good edi operations at a depot are mostly exception handling:

Failed or rejected messages
Identity mismatches (number, size/type, owner)
Events blocked because the unit is on hold
Partner-specific rules that need a human decision before release

A black-box “EDI ran overnight” with no queue is not a control system. It is a surprise generator.

3. Yard status (availability truth)

Gate completion should refresh inventory and position/hold state on one timeline. If EDI says available while the unit is on hold or wrongly stacked, you have already lost the plot. Yard positions and holds belong with the same unit record — see container yard management software.

4. EDI / line messaging (outbound consequence)

ly-all threads

That stack fails in predictable ways:

Two truths: the yard sheet and the EDI export disagree by afternoon
No owner: who fixed container number X after the truck left?
Peak week: return windows and release surges outrun typing capacity
Dispute mode: you cannot open one unit timeline with event, photo, hold, and what was sent systems and your yard tell different stories.

Common triggers:

EDI says Gate In; your portal or spreadsheet still shows the unit as out
EDI says available; your yard has it on damage hold or buried behind a blocked bay
Timestamp on the message does not match free-day / storage clocks the commercial team uses
A correction email arrives days later with no audit trail the line can trust

On the desk, CODECO is shorthand for “tell the line what happened to this empty, in a format their systems accept.”

In practice, depot teams care about a short list of events:

Empty Gate In (return / drop-off)
Empty Gate Out (dispatch / release)
Status changes that lines treat as inventory-relevant (damage hold, repair complete, available again — depending on your programme)

CODECO EDI for Empty Container Depots: What Lines Expect (and What Breaks Without It)