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

COPARN Container announcement

The UN/EDIFACT message ordering a terminal or depot to release, make available, accept or call down containers, or announcing their arrival.

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

What is the EDIFACT COPARN message?

COPARN is the UN/EDIFACT container announcement message. The directory describes it as containing an order to release, make available, accept or call down containers, or to announce the impending arrival of containers. It belongs to the family of container messages that streamline intermodal container handling.

Shipping lines use COPARN to tell depots which empty containers to release for a booking and to tell terminals to accept full export containers. Without the announcement, gate staff may refuse the trucker. It is common in port community systems.

How the EDIFACT COPARN message worksDiagram of the UN/EDIFACT COPARN Container announcement message. Shipping line or its agent sends it to terminal or depot. It usually follows IFTMBC. 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 SG4 loop with NAD (Name and address) and the required SG13 loop with EQD (Equipment details). 9 conditional segment groups are listed by their trigger segment.How the EDIFACT COPARN message worksContainer announcement: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMBCBooking confirmationCOPARNSENDERShipping line or itsagentRECEIVERTerminal or depotCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCODECOContainer gate2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage COPARNUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG4 · repeats up to 9NADName and addressMandatory group SG13 · repeats many timesEQDEquipment details+ 9 conditional groups, starting with:RFFTDTCTAGIDTMPDGSDAMNADBlue 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 COPARN. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT COPARN message worksDiagram of the UN/EDIFACT COPARN Container announcement message. Shipping line or its agent sends it to terminal or depot. It usually follows IFTMBC. 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 SG4 loop with NAD (Name and address) and the required SG13 loop with EQD (Equipment details). 9 conditional segment groups are listed by their trigger segment.How the EDIFACT COPARNmessage worksContainer announcement: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMBCBooking confirmationCOPARNSENDERShipping line orits agentRECEIVERTerminal ordepotCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCODECOContainer gate2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message COPARN (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG4 · repeats upto 9NADName and addressMandatory group SG13 · repeatsmany timesEQDEquipment details+ 9 conditional groups, starting with:RFFTDTCTAGIDTMPDGSDAMNADBlue 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 COPARN.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends COPARN, 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 COPARN 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 a depot to release empty containers for a booking
  • Announcing full export containers to a terminal
  • Calling down containers from a depot to a terminal

Where it fits in the message flow

Usually follows IFTMBC Booking confirmation
This message COPARN Container announcement
Usually followed by CODECO Container gate

Structure

Mandatory segments in COPARN (directory D.21A)

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

Practical example

COPARN in practice

A shipping line confirms a booking for two 40-foot containers. It sends the inland depot a COPARN to release two empty containers against the booking number, and the terminal a COPARN announcing the two full containers for the planned vessel. The trucker collects the empties, the exporter loads them, and the terminal accepts them at the gate.

Implementation

Implementation considerations for COPARN

  • Send announcements before truckers arrive.
  • Use booking numbers the depot and terminal can match.
  • Specify container type and condition requirements.
  • Watch for gate events (CODECO) that confirm execution.

How ECOM helps

Automate COPARN 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

3PL and Warehousing

Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.

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

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

Request a Demo Contact us