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

COREOR Container release order

The UN/EDIFACT message that orders the release of containers and authorizes a specified party to pick them up.

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 COREOR message?

COREOR is the UN/EDIFACT container release order. The directory defines it as an order to release containers, giving permission for them to be picked up by, or on behalf of, a specified party. It is part of the family of container messages for intermodal handling.

For import containers, the release order is issued once freight is paid and documents are in order. It names the carrier or trucker allowed to collect, so the terminal can release containers to the right party and refuse others.

How the EDIFACT COREOR message worksDiagram of the UN/EDIFACT COREOR Container release order message. Shipping line or its agent sends it to terminal or depot. It usually follows IFTMAN and CODENO. 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 TDT (Transport information) and the required SG4 loop with NAD (Name and address). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT COREOR message worksContainer release order: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMANArrival noticeCODENOPermitexpiration/clearanceready noticeCOREORSENDERShipping line or itsagentRECEIVERTerminal or depotCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCODECOContainer gate2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage COREORUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 1TDTTransport informationMandatory group SG4 · repeats up to 9NADName and address+ 5 conditional groups, starting with:RFFLOCCTAGIDEQDBlue 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 COREOR. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT COREOR message worksDiagram of the UN/EDIFACT COREOR Container release order message. Shipping line or its agent sends it to terminal or depot. It usually follows IFTMAN and CODENO. 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 TDT (Transport information) and the required SG4 loop with NAD (Name and address). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT COREORmessage worksContainer release order: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMANArrival noticeCODENOPermit expiration/clearance readynoticeCOREORSENDERShipping line orits agentRECEIVERTerminal ordepotCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCODECOContainer gate2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message COREOR (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 1TDTTransport informationMandatory group SG4 · repeats upto 9NADName and address+ 5 conditional groups, starting with:RFFLOCCTAGIDEQDBlue 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 COREOR.Your trading partner's implementation guide adds itsown requirements.

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

  • Releasing import containers for pickup
  • Authorizing a named trucker or rail operator
  • Cancelling or changing a release

Where it fits in the message flow

Usually follows IFTMAN Arrival noticeCODENO Permit expiration/clearance ready notice
This message COREOR Container release order
Usually followed by CODECO Container gate

Structure

Mandatory segments in COREOR (directory D.21A)

In UN/EDIFACT directory D.21A, the COREOR message has 67 segment positions arranged in 19 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)
  • UNT

Practical example

COREOR in practice

An importer pays the freight on two containers that have arrived in Antwerp. The shipping line sends the terminal a COREOR releasing both containers to the importer's chosen trucking company, with a release reference. When the trucker arrives, the terminal checks the reference, releases the containers and reports the gate-out with a CODECO.

Implementation

Implementation considerations for COREOR

  • Name the authorized party precisely to prevent wrong releases.
  • Check customs status as well; a line release does not override customs holds.
  • Send cancellations promptly if a release must be withdrawn.
  • Protect release references against misuse.

How ECOM helps

Automate COREOR 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 COREOR?

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

Request a Demo Contact us