EDI solution for logistics

The logistics industry is one of the most complex and rapidly evolving sectors, where the efficient exchange of data among multiple parties is critical to success. Electronic Data Interchange (EDI) transactions have become an essential tool for logistics companies to streamline their business processes, improve data accuracy, and reduce costs. EDI transactions in logistics include transactions related to order processing, shipment tracking, inventory management, and more. The use of EDI transactions has helped logistics companies enhance visibility into their supply chain operations, improve inventory accuracy, and reduce order processing times. With the increasing demand for faster and more efficient supply chain operations, the adoption of EDI transactions has become a critical success factor for logistics companies to compete in the market. In this context, it is essential for logistics companies to understand the benefits of EDI transactions and adopt them to stay competitive in today's fast-paced business environment.

Adeptia also offers an EDI solution for logistics that comprises the following EDI Transactions:

This Transaction is used by shippers or their agents to offer a shipment to a carrier or motor carrier for transportation. The 204 message provides the carrier with details of the load to be transported, including origin and destination information, the type and quantity of products being transported, and any special instructions or requirements.

EDI 204 4010 Outbound Transaction details

EDI 204 4010 Outbound Transaction details
Name	Motor Carrier Load Tender EDI 204 4010 Outbound from XML
Description	Outbound Transaction to send Motor Carrier Load Tender EDI 204 4010 from the received canonical XML file.
Type	EDI Outbound
Network	Logistics
Partner Name	Logistics Partner
Project	EDI Logistics
EDI Standard	X12
EDI Standard Version	4010
Transaction Set	204
Source and Target	SFTP, Adeptia hosted FTP server
Source File Name	EDI_Outbound_204_4010_SourceFile.xml
Output File Name Pattern	Motor_Carrier_Load_Tender_EDI_204_4010_XML_Output_month-dd-yyyy_hh:mm:ss.SSS.xml For example, Motor_Carrier_Load_Tender_EDI_204_4010_XML_Output_April-05-2023_18:05:23.003.xml
Trigger Type	File Exist
Action Type	Create File

EDI 204 4010 Inbound Transaction details

EDI 204 4010 Inbound Transaction details
Name	Motor Carrier Load Tender EDI 204 4010 Inbound to XML
Description	Inbound Transaction to receive Motor Carrier Load Tender EDI 204 4010 and generate canonical XML file.
Type	EDI Inbound
Network	Logistics
Partner Name	Logistics Partner
Project	EDI Logistics
EDI Standard	X12
EDI Standard Version	4010
Transaction Set	204
Source and Target	SFTP, Adeptia hosted FTP server
Source File Name	EDI_Inbound_204_4010_SourceFile.txt
Output File Name Pattern	Motor_Carrier_Load_Tender_EDI_204_4010_XML_Output_month-dd-yyyy_hh:mm:ss.SSS.xml For example, Motor_Carrier_Load_Tender_EDI_204_4010_XML_Output_Nov-12-2022_13:45:55.123.xml
Trigger Type	File Exist
Action Type	Create File

This Transaction is used by motor carriers or their agents to provide shippers or their agents with details of the freight shipment and to invoice them for transportation charges. The 210 message provides information about the freight being transported, including origin and destination details, weight, and any additional charges.

EDI 210 4010 Outbound Transaction details

EDI 210 4010 Outbound Transaction details
Name	Motor Carrier Freight Details and Invoice EDI 210 4010 Outbound from XML
Description	Outbound Transaction to send Motor Carrier Freight Details and Invoice EDI 210 4010 from the received canonical XML file.
Type	EDI Outbound
Network	Logistics
Partner Name	Logistics Partner
Project	EDI Logistics
EDI Standard	X12
EDI Standard Version	4010
Transaction Set	210
Source and Target	SFTP, Adeptia hosted FTP server
Source File Name	EDI_Outbound_210_4010_SourceFile.xml
Output File Name Pattern	MotorCarrierFreightDetailsandInvoice_EDI_210_4010_Output_month-dd-yyyy_hh:mm:ss.SSS.xml For example, MotorCarrierFreightDetailsandInvoice_EDI_210_4010_Output_Jan-17-2023_15:56:22.789.xml
Trigger Type	File Exist
Action Type	Create File

EDI 210 4010 Inbound Transaction details

EDI 210 4010 Inbound Transaction details
Name	Motor Carrier Freight Details and Invoice 210 4010 Inbound to XML
Description	Inbound transaction to receive Motor Carrier Freight Details and Invoice EDI 210 4010 and generate canonical XML File.
Type	EDI Inbound
Network	Logistics
Partner Name	Logistics Partner
Project	EDI Logistics
EDI Standard	X12
EDI Standard Version	4010
Transaction Set	210
Source and Target	SFTP, Adeptia hosted FTP server
Source File Name	EDI_Inbound_210_4010_SourceFile.edi
Output File Name Pattern	MotorCarrierFreightDetailsandInvoice_XML_month-dd-yyyy_hh:mm:ss.SSS.xml For example, MotorCarrierFreightDetailsandInvoice_XML_Nov-21-2022_10:15:46.312.xml
Trigger Type	File Exist
Action Type	Create File

This transaction is used to provide shippers or their agents with transportation carrier shipment status updates. The 214 message provides real-time information about the shipment, including pickup and delivery times, any delays or issues encountered during transit, and expected arrival times.

EDI 214 4010 Outbound Transaction details

EDI 214 4010 Outbound Transaction details
Name	Transportation Carrier Shipment Status Message EDI 214 4010 Outbound From XML
Description	Outbound Transaction to send Transportation Carrier Shipment Status Message EDI 214 4010 from the received canonical XML file.
Type	EDI Outbound
Network	Logistics
Partner Name	Logistics Partner
Project	EDI Logistics
EDI Standard	X12
EDI Standard Version	4010
Transaction Set	214
Source and Target	SFTP, Adeptia hosted FTP server
Source File Name	EDI_Outbound_214_4010_SourceFile.xml
Output File Name Pattern	TransportationCarrierShipmentStatusMessage_EDI_214_4010_XML_Output_month-dd-yyyy_hh:mm:ss.SSS.xml For example, TransportationCarrierShipmentStatusMessage_EDI_214_4010_XML_Output_Mar-14-2023_13:46:55.456.xml
Trigger Type	File Exist
Action Type	Create File

EDI 214 4010 Inbound Transaction details

EDI 214 4010 Inbound Transaction details
Name	Transportation Carrier Shipment Status Message EDI 214 4010 Inbound to XML
Description	Inbound Transaction to receive Transportation Carrier Shipment Status Message EDI 214 4010 and generate canonical XML file.
Type	EDI Inbound
Network	Logistics
Partner Name	Logistics Partner
Project	EDI Logistics
EDI Standard	X12
EDI Standard Version	4010
Transaction Set	214
Source and Target	SFTP, Adeptia hosted FTP server
Source File Name	EDI_Inbound_214_4010_SourceFile.txt
Output File Name Pattern	TransportationCarrier_EDI_214_4010_XML_Output_month-dd-yyyy_hh:mm:ss.SSS.xml For example, TransportationCarrier_EDI_214_4010_XML_Output_Apr-13-2023_13:12:46.056.xml
Trigger Type	File Exist
Action Type	Create File

This Transaction is used to send the response by acknowledging the receipt and validity of the transaction, and providing information on any errors or issues that were encountered during processing. It contains information such as the sender and receiver of the original transaction, the date and time the transaction was received, and a status code indicating whether the transaction was accepted or rejected.

ACK EDI 997 4010 Outbound Transaction details

ACK EDI 997 4010 Outbound Transaction details
Name	Logistics Partner ACK EDI 997 4010 Outbound
Description	EDI Acknowledgement 997 (ACK) 4010 version to be used for all Inbound EDI 4010 Transactions. When you want to send an acknowledgment against an Inbound EDI Transaction, you need to use Logistics Partner ACK EDI 997 4010 Outbound Transaction.
Type	EDI Outbound
Network	Logistics
Partner Name	Logistics Partner
Project	EDI Logistics
EDI Standard	X12
EDI Standard Version	4010
Transaction Set	997
Target	SFTP, Adeptia hosted FTP server
Output File Name Pattern	edi_ack_997_4010_logistics_yyyyddmm_HHmmss.SSS.txt For example, edi_ack_997_4010_logistics_20231304_134636.003.txt
Action Type	Create File

ACK EDI 997 4010 Inbound Transaction details

ACK EDI 997 4010 Inbound Transaction details
Name	Logistics Partner ACK EDI 997 4010 Inbound
Description	EDI Acknowledgement 997 (ACK) 4010 version to be used for all Outbound EDI 4010 Transactions. When you want to receive an acknowledgment against an Outbound EDI Transaction, you need to use Logistics Partner ACK EDI 997 4010 Inbound Transaction.
Type	EDI Inbound
Network	Logistics
Partner Name	Logistics Partner
Project	EDI Logistics
EDI Standard	X12
EDI Standard Version	4010
Transaction Set	997
Source	SFTP, Adeptia hosted FTP server
Trigger Type	File Exist

Industry solutions

EDI solution for logistics

Analytics

Related content