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

COHAOR Container special handling order

The UN/EDIFACT message ordering a terminal or depot to perform special handling or services on containers.

Sent by
Shipping line, its agent or forwarder
Received by
Terminal, depot or service provider
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT COHAOR message?

COHAOR is the UN/EDIFACT container special handling order. The directory defines it as an order to perform a specified special handling or service on containers. It is part of the family of container messages for intermodal handling.

Special handling covers services beyond normal moves, such as cleaning, fumigation, inspection, pre-tripping reefers, weighing or moving containers to an inspection area. Ordering them electronically ensures the terminal performs and bills the right service on the right container. Each order should identify the containers and the service exactly.

How the EDIFACT COHAOR message worksDiagram of the UN/EDIFACT COHAOR Container special handling order message. Shipping line, its agent or forwarder sends it to terminal, depot or service provider. It usually starts the exchange. It is usually followed by CODECO. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) 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 COHAOR message worksContainer special handling order: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCOHAORSENDERShipping line, its agentor forwarderRECEIVERTerminal, depot orservice providerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCODECOContainer gate2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage COHAORUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 9NADName and addressMandatory group SG4 · repeats many timesEQDEquipment details+ 6 conditional groups, starting with:RFFCTATDTNADDGSTMPBlue 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 COHAOR. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT COHAOR message worksDiagram of the UN/EDIFACT COHAOR Container special handling order message. Shipping line, its agent or forwarder sends it to terminal, depot or service provider. It usually starts the exchange. It is usually followed by CODECO. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) 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 COHAORmessage worksContainer special handling order: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCOHAORSENDERShipping line,its agent orforwarderRECEIVERTerminal, depotor serviceproviderCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCODECOContainer gate2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message COHAOR (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 9NADName and addressMandatory group SG4 · repeatsmany timesEQDEquipment details+ 6 conditional groups, starting with:RFFCTATDTNADDGSTMPBlue 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 COHAOR.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends COHAOR, 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 COHAOR 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

  • Ordering pre-trip inspection of reefer containers
  • Ordering cleaning or fumigation
  • Moving containers for customs or veterinary inspection

Where it fits in the message flow

This message COHAOR Container special handling order
Usually followed by CODECO Container gate

Structure

Mandatory segments in COHAOR (directory D.21A)

In UN/EDIFACT directory D.21A, the COHAOR message has 37 segment positions arranged in 11 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
  • SG2 (NAD)
  • SG4 (EQD)
  • UNT

Practical example

COHAOR in practice

A shipping line needs ten empty reefer containers ready for a fruit export booking. It sends the depot a COHAOR ordering a pre-trip inspection and set-point check for each container. The depot performs the service, reports the containers ready, and bills the line for the service.

Implementation

Implementation considerations for COHAOR

  • Use the service codes the terminal or depot recognizes.
  • Reference the containers and bookings precisely.
  • Confirm completion before releasing containers.
  • Reconcile ordered services with invoices.

How ECOM helps

Automate COHAOR with ECOM

Industry

Trucking and Transportation

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

Solution

Logistics Automation

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

Industry

Food and Beverage

Grocery and foodservice EDI for food and beverage manufacturers, with lot, date and inventory data.

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 COHAOR?

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

Request a Demo Contact us