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

COSTCO Container stuffing/stripping confirmation

The UN/EDIFACT message confirming that goods or consignments have been stuffed into, or stripped from, less-than-container-load containers.

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

What is the EDIFACT COSTCO message?

COSTCO is the UN/EDIFACT container stuffing/stripping confirmation. The directory defines it as confirmation that specified goods or consignments have been stuffed into, or stripped from, LCL (less than container load) containers. It is part of the family of container messages for intermodal handling.

It answers a stuffing or stripping order (COSTOR) and tells the forwarder exactly what went into or came out of each container, including discrepancies such as short or damaged packages. It is commonly used at container freight stations, where LCL cargo is consolidated.

How the EDIFACT COSTCO message worksDiagram of the UN/EDIFACT COSTCO Container stuffing/stripping confirmation message. Container freight station or warehouse sends it to forwarder, consolidator or shipping line. It usually follows COSTOR. 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 SG10 loop with CNI (Consignment information). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT COSTCO message worksContainer stuffing/stripping confirmation: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSCOSTORContainerstuffing/stripping orderCOSTCOSENDERContainer freightstation or warehouseRECEIVERForwarder,consolidator orshipping lineCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage COSTCOUNH … 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 SG10 · repeats many timesCNIConsignment information+ 6 conditional groups, starting with:RFFLOCCTADGSTMPGIDBlue 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 COSTCO. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT COSTCO message worksDiagram of the UN/EDIFACT COSTCO Container stuffing/stripping confirmation message. Container freight station or warehouse sends it to forwarder, consolidator or shipping line. It usually follows COSTOR. 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 SG10 loop with CNI (Consignment information). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT COSTCOmessage worksContainer stuffing/stripping confirmation: whosends it, where it fits and what the directorymarks mandatory1 WHERE IT FITSUSUALLY FOLLOWSCOSTORContainer stuffing/stripping orderCOSTCOSENDERContainerfreight stationor warehouseRECEIVERForwarder,consolidator orshipping lineCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message COSTCO (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 SG10 (CNI) and 6 conditionalgroups, starting with:RFFLOCCTADGSTMPGIDBlue 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 COSTCO.Your trading partner's implementation guide adds itsown requirements.

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

  • Confirming the stuffing of consolidated cargo
  • Confirming the stripping of an import container
  • Reporting package shortages or damage found

Where it fits in the message flow

Usually follows COSTOR Container stuffing/stripping order
This message COSTCO Container stuffing/stripping confirmation

Structure

Mandatory segments in COSTCO (directory D.21A)

In UN/EDIFACT directory D.21A, the COSTCO message has 54 segment positions arranged in 16 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)
  • SG10 (CNI)
  • UNT

Practical example

COSTCO in practice

A container freight station strips an import LCL container for a forwarder. It sends a COSTCO listing each consignment taken out, the packages counted, one consignment short by two cartons and the warehouse location of each. The forwarder notifies the affected consignee and arranges delivery of the rest.

Implementation

Implementation considerations for COSTCO

  • Report discrepancies at consignment level.
  • Match confirmations to the order (COSTOR).
  • Include seal numbers and stuffing dates for export containers.
  • Use consignment references consistent with the consolidation summary.

How ECOM helps

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

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

Request a Demo Contact us