EDI Dataflow From The 3PL Standpoint: Scenario One

There are many scenarios related to the 3PL, supplier, and trading partner’s EDI dataflow. In an effort to satisfy ship windows, ensure delivery of goods (and do so in a timely manner), from 3PL to the trading partner, careful considerations must be placed on full-cycle flow of each transaction. To provide more insight on how this data flow works, we’re going to present you a scenario in how it might function. 

Below, is a legend to help distinguish the purpose of each EDI transaction code.

3PL Shipping

850: retail purchase order
856: retail advanced shipment notice
940: Warehouse Shipping Order
945: Warehouse Shipping Advice
943: Warehouse Stock Transfer Shipping Advice
944: Warehouse Stock Transfer Receipt Advice
810: invoice (not discussed in the article)


To begin with, the trading partner creates a purchase order in their ERP and exports into a specified data format. Their EDI system translates to an 850. The 850 is sent to the supplier’s 3rd party EDI provider via VAN, SFTP, AS2, etc. The supplier’s 3rd party EDI provider translates the 850 to a specified data format and provides it to the supplier, which is imported into the supplier’s ERP. The 850 is also translated to a 940 and sent to the 3PL via VAN, SFTP, AS2, etc. 

Read Full Article here.

Average: 5 (1 vote)

Share this post