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

COPRAR Container discharge/loading order

The UN/EDIFACT message a shipping line sends to order a terminal to discharge specified containers from, or load them onto, a vessel.

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

What is the EDIFACT COPRAR message?

COPRAR is the UN/EDIFACT container discharge/loading order. The directory defines it as a message ordering the container terminal to discharge specified containers from a seagoing vessel or to load them into one. It is part of the family of container messages for intermodal container handling.

The loading list tells the terminal which export containers in its yard belong on a vessel; the discharge list tells it which containers on board are for that port. The terminal confirms the result with a COARRI.

How the EDIFACT COPRAR message worksDiagram of the UN/EDIFACT COPRAR Container discharge/loading order message. Shipping line or its agent sends it to container terminal. It usually follows BAPLIE. It is usually followed by COARRI. 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 TDT (Transport information), the required SG4 loop with NAD (Name and address) and the required SG6 loop with EQD (Equipment details). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT COPRAR message worksContainer discharge/loading order: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSBAPLIEBayplan/stowage planoccupied and emptylocationsCOPRARSENDERShipping line or itsagentRECEIVERContainer terminalCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCOARRIContainerdischarge/loadingreport2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage COPRARUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 1TDTTransport informationMandatory group SG4 · repeats up to 9NADName and addressMandatory group SG6 · repeats many timesEQDEquipment details+ 6 conditional groups, starting with:RFFLOCCTATMPDGSTDTBlue 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 COPRAR. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT COPRAR message worksDiagram of the UN/EDIFACT COPRAR Container discharge/loading order message. Shipping line or its agent sends it to container terminal. It usually follows BAPLIE. It is usually followed by COARRI. 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 TDT (Transport information), the required SG4 loop with NAD (Name and address) and the required SG6 loop with EQD (Equipment details). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT COPRARmessage worksContainer discharge/loading order: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSBAPLIEBayplan/stowage plan occupied andempty locationsCOPRARSENDERShipping line orits agentRECEIVERContainerterminalCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCOARRIContainer discharge/loading report2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message COPRAR (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 1TDTTransport informationMandatory group SG4 · repeats upto 9NADName and addressMandatory group SG6 · repeatsmany timesEQDEquipment details+ 6 conditional groups, starting with:RFFLOCCTATMPDGSTDTBlue 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 COPRAR.Your trading partner's implementation guide adds itsown requirements.

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

  • Sending a vessel's loading list to a terminal
  • Sending a discharge list for a port call
  • Updating lists before vessel operations start

Where it fits in the message flow

Usually follows BAPLIE Bayplan/stowage plan occupied and empty locations
This message COPRAR Container discharge/loading order
Usually followed by COARRI Container discharge/loading report

Structure

Mandatory segments in COPRAR (directory D.21A)

In UN/EDIFACT directory D.21A, the COPRAR message has 45 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 (TDT)
  • SG4 (NAD)
  • SG6 (EQD)
  • UNT

Practical example

COPRAR in practice

Before a vessel calls at Valencia, the shipping line sends the terminal a COPRAR discharge list of 420 containers and a loading list of 380 containers, with weights, ports of discharge, reefer settings and dangerous goods details. The terminal plans operations, and after the call it reports the work done with COARRI messages.

Implementation

Implementation considerations for COPRAR

  • Send lists before the terminal's cut-off for planning.
  • Keep lists consistent with bookings and bayplans.
  • Include dangerous goods and reefer details completely.
  • Reconcile COARRI confirmations with the order.

How ECOM helps

Automate COPRAR 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.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

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

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

Request a Demo Contact us