EDI (Electronic Data Interchange)

Seaboard Marine has been very active in advancements with Electronic Data Interchange (EDI).

Our Current Capabilities


  • Transportation Carrier Shipment Status (Message 214)

    This transaction set can be used by a transportation carrier to provide shippers, consignees, and their agents with the status of shipments in terms of dates, times, locations, route, identifying numbers, and conveyance.

  • Booking Request (Message 300)

    The shipper or forwarder can use this transaction set to reserve cargo space.

  • Booking Confirmation (Message 301)

    This message is used to confirm the Booking Request (Message 300).

  • Ocean Shipping Instructions (Message 304)

    This message supplies the same information as the Shipper's Letter of Instruction. It provides all the information necessary to prepare and distribute a contract of carriage (ocean bill of lading and other shipping documents).

  • Manifest data (Message 309)

    This message is a summary of bills of lading on a manifest. It's currently being used to exchange information with several overseas governmental authorities.

  • Automated Commercial Environment System (ACE) with US Customs (Message 309)

    This system transmits inbound cargo information to US Customs and receives cargo release/hold status from US Customs.

  • Bill of Lading data and Ocean Invoice (Message 310)

    This message includes all information normally found on a bill of lading, including freight charges.

  • Arrival Notification (Message 312)

    This message is used to notify Consignee of shipment arrival.

  • Shipment Status (message 315)

    This message is used to report status or event details (cargo receipt, departure and arrival) for individual shipments.

  • Terminal Operations and Intermodal Ramp Activity (Message 322)

    This message is used to communicate terminal and intermodal ramp activities (i.e. "ingates" and "outgates")

  • Vessel Schedule and Itinerary (Message 323)

    This message provides all information necessary to communicate the schedule and itinerary of an ocean vessel.

  • Rail Carrier Shipment Information (Message 404)

    This message set can be used to transmit rail-carrier-specific bill of lading information to a railroad.

  • Rail Carrier Freight Details and Invoice (Message 410)

    This message set can be used to provide detailed information of charges associated with a rail movement. The information is provided by a rail carrier and is sent to the freight payer.

  • Functional Acknowledgement (Message 997)

    The message set can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents.


  • Application Error and acknowledgement message (APERAK)

    APERAK can be used for two purposes:
    1) to inform a message issuer that his message has been received by the addressee's application but was rejected because of errors encountered during processing of the application.
    2) acknowledge receipt of the message by the addressee's application to a message issuer.

  • Bayplan/stowage plan occupied and empty locations message (BAPLIE)

    The BAPLIE message is used by and between various parties to advise the exact stowage positions of the cargo on board of an ocean vessel.

  • Container discharge/loading report message (COARRI)

    This message serves to facilitate the intermodal handling of containers by streamlining the information exchange.

  • Container gate-in/gate-out report message (CODECO)

    A message by which a terminal confirms that the containers specified have been delivered or picked up by the inland carrier (road, rail or barge).

  • Functional Acknowledgement (CONTRL)

    CONTRL is a message syntactically acknowledging or rejecting, with error indication, a received interchange, functional group or message.

  • Customs cargo report message (CUSCAR)

    This message permits the transfer of data from a carrier to a Customs administration for the purpose of meeting Customs cargo reporting requirements.


  • UN- Automated System for Customs Data (ASYCUDA)
  • Other XML customized messages


  • Electronic invoicing and reconciliation with most of our equipment leasing companies


  • Seaboard has the ability to interconnect with customers via value-added networks (VAN), via FTP, SFTP or via AS2 (preferred method)
Planned EDI Services

New EDI opportunities are continually being evaluated. If necessary, our EDI specialists will work with you to explore customer-specific EDI requirements.

For any EDI questions please email us at EDIAdmin@seaboardmarine.com