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

COSTOR Container stuffing/stripping order

The UN/EDIFACT message ordering that specified goods or consignments be stuffed into, or stripped from, less-than-container-load containers.

Sent by
Forwarder, consolidator or shipping line
Received by
Container freight station or warehouse
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT COSTOR message?

COSTOR is the UN/EDIFACT container stuffing/stripping order. The directory defines it as an order that specified goods or consignments, already delivered or still to be delivered, be stuffed into or stripped from LCL containers. It is part of the family of container messages for intermodal handling.

The order tells the container freight station which consignments belong in which container, in what sequence and with what handling instructions. The station confirms the work with a COSTCO. It is commonly used at container freight stations and consolidation warehouses.

How the EDIFACT COSTOR message worksDiagram of the UN/EDIFACT COSTOR Container stuffing/stripping order message. Forwarder, consolidator or shipping line sends it to container freight station or warehouse. It usually follows IFCSUM. It is usually followed by COSTCO. 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), the required SG6 loop with EQD (Equipment details) and the required SG11 loop with CNI (Consignment information). 7 conditional segment groups are listed by their trigger segment.How the EDIFACT COSTOR message worksContainer stuffing/stripping order: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFCSUMForwarding andconsolidation summaryCOSTORSENDERForwarder,consolidator orshipping lineRECEIVERContainer freightstation or warehouseCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCOSTCOContainerstuffing/strippingconfirmation2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage COSTORUNH … 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 detailsMandatory group SG11 · repeats many timesCNIConsignment information+ 7 conditional groups, starting with:RFFLOCCTANADDGSTMPGIDBlue 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 COSTOR. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT COSTOR message worksDiagram of the UN/EDIFACT COSTOR Container stuffing/stripping order message. Forwarder, consolidator or shipping line sends it to container freight station or warehouse. It usually follows IFCSUM. It is usually followed by COSTCO. 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), the required SG6 loop with EQD (Equipment details) and the required SG11 loop with CNI (Consignment information). 7 conditional segment groups are listed by their trigger segment.How the EDIFACT COSTORmessage worksContainer stuffing/stripping order: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSIFCSUMForwarding and consolidationsummaryCOSTORSENDERForwarder,consolidator orshipping lineRECEIVERContainerfreight stationor warehouseCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCOSTCOContainer stuffing/strippingconfirmation2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message COSTOR (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+ required SG11 (CNI) and 7 conditionalgroups, starting with:RFFLOCCTANADDGSTMPGIDBlue 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 COSTOR.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends COSTOR, 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 COSTOR 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 consolidation of LCL cargo into containers
  • Ordering the stripping of import containers
  • Giving loading sequence and handling instructions

Where it fits in the message flow

Usually follows IFCSUM Forwarding and consolidation summary
This message COSTOR Container stuffing/stripping order
Usually followed by COSTCO Container stuffing/stripping confirmation

Structure

Mandatory segments in COSTOR (directory D.21A)

In UN/EDIFACT directory D.21A, the COSTOR message has 59 segment positions arranged in 18 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)
  • SG11 (CNI)
  • UNT

Practical example

COSTOR in practice

A forwarder has 14 consignments waiting at a container freight station for a weekly consolidation to Dubai. It sends the station a COSTOR assigning the consignments to one 40-foot container, with the loading sequence, fragile cargo instructions and the seal to use. The station stuffs the container and confirms with a COSTCO.

Implementation

Implementation considerations for COSTOR

  • Specify consignments and handling instructions clearly.
  • Include dangerous goods segregation requirements.
  • Send orders in time for the station to plan labor.
  • Reconcile each COSTCO confirmation with the order.

How ECOM helps

Automate COSTOR with ECOM

Industry

3PL and Warehousing

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

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.

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

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

Request a Demo Contact us