972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Transport

COEDOR Transport equipment stock and profile report

The UN/EDIFACT message used to report transport equipment in stock at a terminal or depot, or in a line's fleet, and new equipment profiles.

Sent by
Terminal, depot, container freight station or shipping line
Received by
Shipping line or equipment owner
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT COEDOR message?

COEDOR is the UN/EDIFACT transport equipment stock and profile report. The directory defines it as a message to report transport equipment either in stock at the sending party, such as a terminal, depot or container freight station, or in the fleet operated by a shipping line. It also reports the profiles of newly acquired equipment.

Stock reports let shipping lines reconcile their own records of where containers are against what depots and terminals actually hold, which is essential for repositioning empties and controlling equipment costs.

How the EDIFACT COEDOR message worksDiagram of the UN/EDIFACT COEDOR Transport equipment stock and profile report message. Terminal, depot, container freight station or shipping line sends it to shipping line or equipment owner. It usually starts the exchange. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG2 loop with NAD (Name and address) and the required SG4 loop with EQD (Equipment details). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT COEDOR message worksTransport equipment stock and profile report: who sends it, where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCOEDORSENDERTerminal, depot,container freightstation or shipping lineRECEIVERShipping line orequipment ownerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage COEDORUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 9NADName and addressMandatory group SG4 · repeats many timesEQDEquipment details+ 6 conditional groups, starting with:RFFCTADAMTDTDGSTMPBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for COEDOR. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT COEDOR message worksDiagram of the UN/EDIFACT COEDOR Transport equipment stock and profile report message. Terminal, depot, container freight station or shipping line sends it to shipping line or equipment owner. It usually starts the exchange. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG2 loop with NAD (Name and address) and the required SG4 loop with EQD (Equipment details). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT COEDORmessage worksTransport equipment stock and profile report:who sends it, where it fits and what thedirectory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCOEDORSENDERTerminal, depot,container freightstation orshipping lineRECEIVERShipping line orequipmentownerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message COEDOR (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 9NADName and addressMandatory group SG4 · repeatsmany timesEQDEquipment details+ 6 conditional groups, starting with:RFFCTADAMTDTDGSTMPBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for COEDOR.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends COEDOR, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around COEDOR and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Reporting containers in stock at a depot
  • Reconciling equipment inventory with a shipping line
  • Reporting profiles of new equipment

Where it fits in the message flow

This message COEDOR Transport equipment stock and profile report

No other message routinely comes directly before or after COEDOR; it is exchanged when the business event occurs. If the partners agree, the receiver confirms each interchange with a CONTRL syntax and service report.

Structure

Mandatory segments in COEDOR (directory D.21A)

In UN/EDIFACT directory D.21A, the COEDOR message has 39 segment positions arranged in 10 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • SG2 (NAD)
  • SG4 (EQD)
  • UNT

Practical example

COEDOR in practice

A depot in Rotterdam holds empty containers for several shipping lines. Each night it sends each line a COEDOR listing its containers in stock, with type, condition and date of arrival. One line compares the report with its own tracking and finds three containers it thought were at another depot.

Implementation

Implementation considerations for COEDOR

  • Send stock reports on a regular schedule.
  • Reconcile against gate events (CODECO) to find gaps.
  • Report equipment condition so lines can plan repairs.
  • Use standard container type and condition codes.

How ECOM helps

Automate COEDOR with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related transport messages

All 36 transport messages

Need help with COEDOR?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us