We Make EDI Integration Easy


Below you will essential information in regards to this EDI. If you have any specific questions about integrating your EDI with your ERP and eCommerce please reach out. Take advantage of our "start planning" feature to map out your integration needs. 

Request A Demo Start Planning
 
What is a 312 - Arrival Notice (Ocean) document?

The 312 EDI document type contains information regarding Arrival Notice (Ocean) Transaction Set (312) for use within the context of an Electronic Data Interchange (EDI) environment.Standard EDI formats include X12, ANSI, EDIFACT and its subsets.

What makes up the 312 - Arrival Notice (Ocean) document?

An EDI 312 - Arrival Notice (Ocean) document is organized into segment and data elements. Examples of data elements on the 312 EDI document includes all the information necessary for a consignee to receive a shipment including customs, payments due, and estimated arrival date and time of shipment. There are an infinite number of possibilities available for a company to include data on an 312 - Arrival Notice (Ocean).

How is a 312 - Arrival Notice (Ocean) used?

The 312 Arrival Notice (Ocean) document can be used to provide all the information necessary for a consignee to receive a shipment including customs, payments due, and estimated arrival date and time of shipment.

How is a 312 - Arrival Notice (Ocean) processed?

An EDI solution is required to process the EDI documents received into an ERP or accounting system or into a readable format for manual entry. Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed.

eBridge Connections has pre-built maps for all EDI transaction documents including 850 purchase orders, 810 invoices, and 856 advance shipping notices.