Search

Skip to end of metadata
Go to start of metadata

Outgoing EDI 204

Below is the Cloud Logistics EDI 204 specification for files sent to partners.

Codes that can be used in the L11 (L1101) with a 22 qualifier (L1102) to represent accessorial charges (L1103):

L108_codes.txt

Incoming EDI 990

Below is the Cloud Logistics EDI 990 specification for files received from partners.

Incoming EDI 214

Below is the Cloud Logistics EDI 214 specification for files received from partners.

Incoming EDI 315

Below is the Cloud Logistics EDI 315 specification for ocean status details received from partners.

Incoming EDI 310

Below is the Cloud Logistics EDI 310 specification for files received from partners.

Incoming EDI 210

Below is the Cloud Logistics EDI 210 specification for files received from partners.

Outgoing EDI 997

Below is the Cloud Logistics EDI 997 specification for files sent to partners in response to files received by partners.

Incoming EDI 997 Specification Download Link

Incoming EDI 850

The EDI 850 is a Purchase Order transaction set, used to place an order for goods or services. The 850 generally provides the same information you would find in a paper Purchase Order (PO) document, including:

  • Item, prices and quantities ordered
  • Shipping details

Incoming EDI 856

The incoming EDI 856 is the Ship Notice/Manifest transaction. In the Cloud Logistics TMS, the EDI 856 is used to create deliveries in the shipper portal. The EDI 856 typically comes from a shipper's vendor and lets the shipper know when freight is ready to ship. A shipper can then tender the delivery to the appropriate carrier.

  • No labels