EDI compliance for depot operators

Most depot operators treat EDI as an IT issue: mapping fields, configuring endpoints, and working through formats. For your customers, the tank container operators and lessors, EDI is something more critical. It is their compliance record.

When an operator sends a pre-advice, expects a structured gate-in confirmation, approves a repair estimate, or needs an electronic cleaning certificate (eECD), that exchange is audit-critical. If a message arrives late, is missing the previous-cargo field, or lands in the wrong format, the dispute lands on your desk.

From nice to have to contractual requirement

Tank operators used to accept scanned PDFs, emails, or phone calls. Increasingly, they expect electronic data exchange by default, and they set the standards, not the depot. In the tank container industry that means working with several formats at once:

A depot with dozens of customers cannot build a custom integration for each one, or translate every inbound message by hand. Every message has to be received, validated, and answered correctly, every time.

What sound EDI practice looks like in the yard

Good EDI starts with the tank's operational lifecycle, not with the syntax. Each tank movement generates a chain of related messages:

1. Pre-advice: the operator announces the tank, with its UN number and previous cargo
2. Gate-in and inspection: arrival, condition, and status
3. Work orders: cleaning, heating, testing, or repair
4. Authorizations and certificates: estimate approvals and eECD generation
5. Release and gate-out: the equipment release order
6. Invoicing: aligned with the approved work

Three habits make this flow dependable:

1. Validate at the gate, not after planning Check incoming pre-advices as they arrive. Are the UN number and previous cargo recognized and complete? An automatic rejection sent back to the operator takes minutes, while a wrong cleaning order can cost a full shift.

2. Confirm every message explicitly Every pre-advice should trigger an accepted or rejected reply. Silence creates blind spots for both sides. An explicit confirmation records what was received and sets clear expectations before the truck reaches the gate.

3. Keep messages on the tank file EDI messages should not sit in a separate IT log. Inbound instructions and outbound confirmations belong in the depot order record. When a customer or auditor asks what was approved and when, your team should be able to answer from the file in seconds.

Where compliance breaks down

Disputes rarely come from an EDI server failing. They come from the manual handovers in between:

• a planner re-typing an emailed pre-advice into the depot system
• a cleaning certificate printed, scanned, and emailed separately
• an estimate revised by phone without updating the electronic record

Every manual step adds the risk of error, extends dwell time, and breaks the audit trail. The fix is not more checks at the end of the month. It is removing manual handovers from the start.

An action for this quarter

Review your partner list:

1. List your top 20 customers by volume.
2. Note how each one's orders arrive: EDI, portal, email, or phone.
3. Identify where manual re-keying creates a bottleneck or a liability.
4. For high-volume customers, use the next contract renewal to set up a standard electronic message flow.

How DEPOT Software helps

DEPOT Software connects these exchanges through SYNDA, our B2B and EDI layer. SYNDA handles the common tank industry formats, including CEDEX, IICL, OTF, and eECD, and turns incoming messages into yard orders without manual data entry.

Want to see how your customer message flows would work on a standard connection? Let's talk about your depot